FHIR Sender
Setting FHIR Sender Properties
Selecting an Interaction / Operation
Setting FHIR Sender Properties
Selecting an Interaction / Operation
Recommendations
Explore
Mirth® Connect by NextGen Healthcare FHIR Connector User Guide
Selecting an Interaction / Operation
If you haven't retrieved a remote capability statement, then by default the FHIR Sender will be populated with all known resources, interactions, operations, and parameters. Once you retrieve and cache a capability statement, only the interactions etc. supported by the server will be shown in the drop-down menus. The first thing to decide is whether you want your FHIR Sender destination to invoke a Resource-specific interaction, or a System-wide interaction. Select either Resource or System next to Interaction Type: The Interaction / Operation drop-down menu will change depending on which interaction type you choose. Once you select one, the Path and options underneath it will change. Creating/Updating/Patching Interactions Other Interactions Searching Parent topic: FHIR Sender
Mirth® Connect by NextGen Healthcare FHIR Connector User Guide
Setting FHIR Sender Properties
After installing, you should now have "FHIR Sender" as one of your destination connector options. It is similar to the HTTP Sender: Image of the Edit Channel - Fhir Sender window The first option in the FHIR Sender Settings allows you to select the FHIR version to use in the destination connector. The default selected version is R4. Each version of FHIR has a different set of resources, so selecting a different version changes the list of resources in the Resources drop-down. The content of each resource also varies between FHIR versions. For example, a Patient resource in R4 does not have the exact same set of properties as a Patient resource in STU3. The properties in the Builder reflect these differences. Retrieving and Viewing Capabilities Parent topic: FHIR Sender
Mirth® Connect by NextGen Healthcare FHIR Connector User Guide
FHIR Listener
Developing a FHIR Listener Channel Handling Responses Interacting With Your Server in a Browser Generating Resource Narratives Setting FHIR Listener Properties Developing a FHIR Listener Channel Handling Responses Interacting With Your Server in a Browser Generating Resource Narratives Setting FHIR Listener Properties
Mirth® Connect by NextGen Healthcare User Guide
FHIR Connector
This extension provides FHIR Listener and FHIR Sender connectors, a new FHIR data type, a FHIR Resource Builder available as both a transformer step and code template type, and some helper/utility classes for working with responses. Fast Healthcare Interoperability Resources (FHIR) is a new set of HL7 healthcare standards. Its main focus is on the ease of implementation, based on RESTful HTTP using XML or JSON. Components called "resources" are used to store and exchange data between systems. The resources are XML or JSON documents following a standard definition, and include the actual resource data (like patient demographics), metadata, tags, and a human-readable description. However, they are also fully extensible, meaning that additional implementation-specific data elements can be added if needed. This extension provides FHIR Listener and FHIR Sender connectors, a new FHIR data type, a FHIR Resource Builder available as both a transformer step and code template type, and some help
Mirth® Connect by NextGen Healthcare FHIR Connector User Guide
Notes on Implementation
First, note that certain interactions have been selectively enabled for certain resource types. For this example we'll only actually be implementing some interactions, so this is largely for illustration. You can enable or disable interactions as you see fit, so that the generated conformance statement will reflect that support to clients. On the source connector settings, we also have a custom "response" variable selected. This indicates that the FhirResponse object the FHIR Listener uses will be retrieved from the response map. Source Transformer Here we have a single step. We use destination set filtering to decide in advance which destination to send a message to. Each destination is named according to one of the possible FHIR interactions, like "create" or "update". Because the interaction of the request will be in the "fhirInteraction" source map variable, we can use that to directly filter on destinations:var interaction = sourceMap.get('fhirInteraction'); if (interaction == 'op
Mirth® Connect by NextGen Healthcare FHIR Connector User Guide
Handling Responses
Let's say you've set up a destination that specifically handles the "create" interaction. Once you've created the resource and stored it (for example, in a database somewhere), the next step is to return a proper response back to the client. Each interaction is different and may require different response headers and status codes. You can view the summary table for responses here, but for ease of use, this FHIR extension also includes a couple of utility classes. FhirResponse FhirResponseFactory Parent topic: FHIR Listener
