Loading...
Recommendations
Explore
FHIR Listener
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 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
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
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
Developing a FHIR Listener Channel
After deploying a FHIR Listener channel, the "/metadata" endpoint will already be configured to return an auto-generated capability statement. The FHIR server is now technically up and ready to receive requests. The next step is to use the source map information the connector provides, create your transformers and destinations, and return the appropriate responses. If you send a FHIR request to your channel (for example, POSTing a Patient resource), you'll see in the message browser that certain FHIR-specific variables are automatically injected into the source map. These are the possible variables: fhirInteraction: The inferred interaction for this request (e.g. "create", "read", "update", "delete"). fhirType: The type of resource the interaction/request is for (e.g. "Patient", "Binary"). This will be absent for system-level interactions. fhirId: The logical ID of the resource associated with the request. Not all interactions require the client to send an ID, so this may be absent. fh
Mirth® Connect by NextGen Healthcare FHIR Connector User Guide
Interacting With Your Server in a Browser
You can also view resources from your FHIR server in any modern browser. For example, the capability statement: CapabilityStatement Resource data shown in Web browser Or, searching on a particular patient: If anything goes wrong and the server returns an OperationOutcome, you will see that as well: The web pages served to clients are generated from HTML templates in the extensions/fhir/public_html/ folder in your installation directory. These three templates are available: template.html:This is the main template for all pages that are served. Use this to include common headers/footers, CSS/JS assets, or anything else that you will show on all pages. The "mainContainer" div is where specific page content is populated. resource.html: This is the template used for any resource returned by the server. This includes virtually everything, the only exception being Binary resources (when you don't request a specific return format in the URL). landingpage.html: This is the template used for the
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
