The FhirUtil Utility Class

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

Generating Resource Narratives

Almost all resources can include a human-readable narrative describing the resource. This is an XHTML div element contained in the "narrative" node of the XML/JSON. More information: Narrative. This FHIR extension utilizes HAPI FHIR and Thymeleaf to help auto-generate resource narratives. Several templates are built-in, but you can override them and/or provide your own. The extensions/fhir/narratives/ folder in the installation directory contains all narrative-related resources that aren't built into HAPI. The narratives.properties file determines which HTML templates to use for specific classes. Two resources (CapabilityStatement and OperationOutcome) are overridden by default, and their template HTML pages are in that folder as well for reference. As mentioned before, the FhirUtil class also has a convenience method for generating resource narratives. For more information, check out the HAPI FHIR documentation: Narrative Generation. Parent topic: FHIR Listener

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

FhirResponseFactory

This utility class makes the above even easier, with the following methods: getReadResponse(message, vid, lastModified, statusCode, mimeType) getVreadResponse(message, vid, lastModified, statusCode, mimeType) getUpdateResponse(message, vid, lastModified, statusCode, mimeType) getCreateResponse(message, id, vid, lastModified, statusCode, mimeType) getResponse(message, id, vid, lastModified, statusCode, mimeType) All of these are convenience methods for creating FhirResponse objects. Some methods have multiple versions depending on whether you're sending a payload back. For example instead of the code above, all that would be needed is this: Note that documentation for these classes is included in the Reference list in transformers, and also in the auto-completion dialog. You can also view the Javadoc by going to the extensions/fhir/docs/javadocs/ folder in your installation directory. Once you send back an appropriate FhirResponse object, the FHIR Listener will take care of everything e

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

FHIR Code Template Type

This code template type uses the FHIR Resource Builder to create a new FHIR resource or data type. The FHIR Version option determines which version of FHIR to use when creating this resource. Once created, you can store the object in a map (such as the channel map) or return the object directly from the function itself. This code template creates a JavaScript function. You can edit the name of the function and the arguments it takes in with the Function Signature field. For example, you could rename the function "createPatient" and have it expect a single argument, "msg". After adding or removing arguments, click on Update JSDoc and the JSDoc field below will automatically have those new arguments added into the documentation. You can then edit it to give your own argument descriptions. With the Result option, you can choose to store the resource in a variable map, or return it directly to the caller of the JavaScript function.

Mirth® Connect by NextGen Healthcare FHIR Connector User Guide

FhirResponse

The first is the FhirResponse class. This is an extension of the standard Response class that also allows certain FHIR-specific data to be stored so that the FHIR Listener can automatically return the correct information. Here is a list of the additional methods that can be used: getId / setId: The logical ID of the resource associated with the response. getVid / setVid: The version ID of the resource associated with the response. getStatusCode / setStatusCode: The HTTP status code that will be sent back to the client. getLastModified / setLastModified: The date that will be sent back to the client in the Last-Modified header. getMimeType / setMimeType: The MIME type that will be sent back to the client in the Content-Type header. isIncludeLocationHeader / setIncludeLocationHeader: Determines whether the Location header will be included in the HTTP response. isIncludeETagHeader / setIncludeETagHeader: Determines whether the ETag header will be included in the HTTP response. getHeaders

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

The FhirUtil Utility Class

Recommendations

Generating Resource Narratives

FhirResponseFactory

FHIR Code Template Type

FhirResponse

Sending Sample Requests

Notes on Implementation

Generating Resource Narratives

FhirResponseFactory

FHIR Code Template Type

FhirResponse

Sending Sample Requests

Notes on Implementation

The FhirUtil Utility Class