Other Interactions

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

Searching

When using a search interaction, you'll typically want to include query parameters to narrow your search. Some standard global search parameters are shown in the Query Parameters drop-down menu by default. In addition to those, some resource-specific search parameters may appear, depending on what is present in the Capability Statement. For example, if the server presents a capability statement that says it supports the "family", "given", "identifier", and "name" parameters for the Patient resource, you should see those in the drop-down menu: Parent topic: Selecting an Interaction / Operation

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

Creating/Updating/Patching Interactions

These interactions (as well as transaction/batch and many operations) use one of the entity-enclosing HTTP methods: POST, PUT, or PATCH. When one of these is selected, you also need to specify a request payload/body. You can choose Use Template to enter a direct text template, or Use Builder to use the FHIR Resource Builder to create a payload for you. When using the Builder mode, the resource being built is automatically selected for you, depending on the resource and/or interaction you've chosen. Parent topic: Selecting an Interaction / Operation

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 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 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

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

Other Interactions

Recommendations

Searching

Creating/Updating/Patching Interactions

Selecting an Interaction / Operation

Setting FHIR Listener Properties

Sending Sample Requests

Notes on Implementation

Other Interactions

Searching

Creating/Updating/Patching Interactions

Selecting an Interaction / Operation

Setting FHIR Listener Properties

Sending Sample Requests

Notes on Implementation