Setting FHIR Sender Properties

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

FHIR Sender

Setting FHIR Sender Properties Selecting an Interaction / Operation Setting FHIR Sender Properties Selecting an Interaction / Operation

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

Retrieving and Viewing Capabilities

The FHIR Sender has the ability to request a Capability Statement from the remote server and cache it locally. Enter the Capabilities URL, which can be either the Base URL or the /metadata URL. Then click on the Get Capabilities button. Once the capability statement has been successfully retrieved, the Capabilities label will be populated with a short summary of the remote server's capabilities: To view more details, click on the View Capabilities button: The Summary tab here shows some general information about the server's capabilities, like which system/resource interactions or operations are supported. To view the entire capability statement, click on the XML or JSON tab. Note: The Capabilities URL is optional, and is only used on the client-side to retrieve and cache the remote capability statement. The URL field is where actual deploy-time requests will be sent. The URL will automatically be populated when Get Capabilities is used. If the server presents a specific implementation

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

Setting FHIR Listener Properties

After installing, you should now have "FHIR Listener" as one of your source connector options. You can see that it's quite similar to the HTTP Listener: The first option in the FHIR Listener Settings allows you to select the FHIR version to use in the source connector. The default selected version is R4. Each version of FHIR has a different set of resources, so selecting a different version in the drop-down will change the list of resources in the Resources table. You can find documentation about FHIR resources at http://hl7.org/fhir/R4/resourcelist.html. A FHIR server provides a capability statement that gives clients an overview of the application. This includes what resources and interactions the application supports, and any other requirements it has. The FHIR Listener connector settings affect what values show up in the capability statement. They are as follows (see also — Resource CapabilityStatement - Detailed Descriptions): Capability Statement Template: If set, this will provi

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

Sending Sample Requests

Once you've made any necessary tweaks to the channel or configuration map (like pointing it to your local database), save and deploy it. The FHIR Listener channel will be up and running, and you should be able to request the home page at the URL http://localhost:9001/r4/, or the conformance statement at the URL http://localhost:9001/r4/metadata. Note that the IP, port, or base context path may be different depending on your source connector settings. If you request a resource (like the conformance statement) in a web browser, it will return the HTML template with the resource narrative (if available): Image of the HTML template of the CapabilityStatement Resource Creating a Patient Resource After verifying the /metadata endpoint works correctly, try creating a new Patient resource. To do this, POST a request to http://localhost:9001/r4/Patient. You can go here to get some example patient resources: Resource Patient - Examples. If you choose an XML-formatted resource, use "application/f

Setting FHIR Sender Properties

Recommendations

Selecting an Interaction / Operation

FHIR Sender

Retrieving and Viewing Capabilities

Setting FHIR Listener Properties

FHIR Connector

Sending Sample Requests

Selecting an Interaction / Operation

FHIR Sender

Retrieving and Viewing Capabilities

Setting FHIR Listener Properties

FHIR Connector

Sending Sample Requests