Mirth Connect and NwHIN Gateway Integration Training

Transcription

1 Mirth Connect and NwHIN Gateway Integration Training Gerald Bortis David Schramm October 3, 2011

2 Objectives Gain a basic understanding of the NwHIN Gateway Learn how to install and configure the NwHIN Gateway on a Mirth Appliance Learn how to integrate an application to the NwHIN Gateway using Mirth Connect Learn how to integrate the NwHIN Gateway with an application through custom adapters

3 Contents Part 1 Overview of NwHIN Gateway Installation and Configuration Gateway Services Outbound Process Part 2 Inbound Process Review and Q & A

4 PART 1

5 Requirements Mirth Appliances Either VM or physical hardware Two preferred for testing gateway integration Mirth Connect or newer NwHIN Gateway Connector and Plugin Light weight HTTP Client for testing RESTClient - Proficiency in Mirth Connect channel development

6 NwHIN Gateway Overview The NwHIN Gateway is an open source software solution that supports health information exchange both locally and at the national level. Based on Nationwide Health Information Network (NwHIN) standards to make sure that health information exchanges are compatible with other exchanges being set up throughout the country.

7 Architecture Health Information System Master Patient Index (MPI) Mirth Connect (Gateway Connector) Local Gateway 0 * Remote Gateway Adapters Mirth Appliance Document Registry and Repository

8 NwHIN Gateway Architecture

9 NwHIN Gateway Architecture Mirth Appliance NwHIN Gateway Mirth Match Mirth Results

10 NwHIN Gateway Components Core Services Gateway Provide core functionality such as location patients, providing documents, and auditing the transactions Enterprise Service Component Default implementations of services needed to support health information exchange (MPI, document registry and repository, etc.) Services are added through adapters

11 Appliance Installation Installed through appliance control panel NwHIN Gateway Mirth Results* Mirth Match* * Demo integration

12 Appliance Network Ports Port Protocol Purpose 8888 TCP Mirth Results & Match (HTTP) 8881 TCP Mirth Results & Match (HTTPS) 4848 TCP Glassfish Admin (Mirth Results & Match) 7048 TCP Glassfish Admin (NwHIN) 7080 TCP Gateway Services (HTTP) 8181 TCP Gateway Services (HTTPS) 3306 TCP MySQL

13 NwHIN Gateway Database External access to the gateway patient correlation database possible using MySQL Workbench.

14 NwHIN Gateway Configuration 1. In the control panel, go to Applications > CONNECT NHIN Gateway 2. Set your home gateway OID Use test OIDs: 1.1, 4.4, 5.5, 3. Add Gateways to Gateway Directory 4. Use Ping feature to test connectivity

15 NwHIN Gateway Configuration Register remote gateways through the appliance control panel, or manually via editing the internalconnection.xml file. /folders/glassfish-aurion-nhin-gateway/domains/nssdomain/config/nhin/internalconnection.xml

16 Certificate Exchange Each gateway must have a self signed cert For each remote gateway that you wish to communicate with, you must exchange certificates Local NwHIN Gateway Remote NwHIN Remote Gateway NwHIN Gateway

17 NwHIN Gateway Extension

18 NwHIN Gateway Extension Home Gateway OID: OID of your local gateway. Example: 4.4 Use same OID as configured on this appliance Configuration Service URL: The URL of the gateway web services. Default: (or port 7080 depending on your configuration) Gateway List Service URL: Points to XML file containing available gateway list. Default Note: This is a service that is provided by the Mirth Appliance Patient Correlation DB URL: Points to MySQL database congaing correlated patient ID, created by the MPI sub-system. Note that the URL must contain the user * and password information embedded as parameter. Default: jdbc:mysql:// :3306/patientcorrelationdb?user=nhincuser&password=nhincpass Use for Appliances, as all services are on the same machine

19 NwHIN Gateway Connector

20 Any architecture, installation or configuration questions? QUESTIONS

21 NwHIN Gateway Communication Gateway services provide mechanisms for: Receiving messages from the adapter and sending them to the NwHIN (outbound) Receiving messages from the NwHIN and passing them to the adapter (inbound)

22 Outbound Process - Components

23 Outbound Process - Overview Mirth Connect extension provides support for outbound requests to the NwHIN Gateway 1. Patient Discovery (MPI)» The service responsible for orchestrating and processing patient discovery, as part of the Patient Discovery service. 2. Document Query (Registry)» The service responsible for orchestrating and processing a document query, as part of the Query for Documents core service. 3. Document Retrieve (Repository)» The service responsible for orchestrating and processing the retrieval of patient documents, as part of the Retrieve Documents service.

24 Outbound Process - Mirth Connect Mirth Connect Source Connector Mappings NwHIN Gateway Connector Web Services NwHIN Gateway 1. A payload is received by the HTTP Listener Source Connector. 2. Patient demographics needed to query for documents is extracted from the message and mapped to the outbound request. 3. A request is submitted to the gateway through the NwHIN Gateway Connector. 4. Retrieved documents are stored in Mirth Connect memory for consumption.

25 Outbound Requests NwHIN CONNECT Sender Document Query Channel Application Document Retrieve Channel Gateway Server Plug-in NwHIN Gateway Mirth Connect

26 Outbound Requests Demographics HTTP Document Query Channel Application Document Retrieve Channel Gateway Server Plug-in NwHIN Gateway Mirth Connect Step 1: Application sends Document Query Channel a set of request variables (source can be any connector type)

27 Outbound Requests Document Query Channel Java Request ID Application Document Retrieve Channel Gateway Server Plug-in NwHIN Gateway Mirth Connect Step 2: Document Query Channel sends request to Gateway Server Plug-in. A unique Request ID is sent back to the Application.

28 Outbound Requests Document Query Channel Application Gateway Server Plug-in SOAP NwHIN Gateway Document Retrieve Channel Mirth Connect Step 3: Gateway Server Plug-in submits the request to the local gateway (using one thread per gateway request). The documents for the patient are stored in memory as they are received.

29 Outbound Requests Document Query Channel Application Request ID HTTP Document Retrieve Channel Java Gateway Server Plug-in NwHIN Gateway Documents Mirth Connect Step 4: Using the Request ID, the Application queries the Document Retrieve Channel which sends a request to the Gateway Server Plug-in which located the documents and returns them to the Application (or errors if no documents).

30 Any outbound process questions? QUESTIONS

31 Outbound Demo - Request XML <request> <patient> <identifiers> <identifier> <id>d123401</id> Request mappings <organizationid>test-01</organizationid> </identifier> </identifiers> <names> <personname> <familyname>younger</familyname> <givenname>gallow</givenname> <type>primary</type> </personname> </names> <dateofbirth> :00:00.0 PDT</dateOfBirth> : Used in conjunction with NwHIN CONNECT Sender Destination Connector

32 Patient Correlation Process What is the patient correlation process? MPI is one of the enterprise services used by the gateway Only the correlated patient ID is stored locally What is the matching algorithm used by the MPI? That is up to you! The light weight reference implementation uses an overly simple exact name match. The Mirth Match and Mural ESC implementations uses a more sophisticated probabilistic matching algorithm. If you are integrating your own MPI, the matching algorithm is what fits the bill for your business rules. What demographic traits should be used by the MPI? Again, up to you. You have at your disposal anything that is provided by the HL7v3 specification. In an NHIN implementation, the NHIN specification provides guidance on required fields.

33 Outbound Demo RESTClient Using RESTClient to send a request

34 Example Outbound Request Once a patient is selected in the EHR, additional request parameters can be added.

35 Secure Channels Secure communication with the appliance? Use the SSL Manager plugin to enabled encrypted communication (HTTPS Listener) Contact to request the plugin

36 Any questions about the outbound demo? QUESTIONS