InterSystems IRIS for Health™ provides a platform for building scalable applications for healthcare interoperability. Each instance of InterSystems IRIS for Health comes with:
For this activity, you will review and launch an HL7 application that is capable of receiving HL7 messages. The application has been built for a small clinic that needs to route messages among their registration, research, lab, and billing facilities. Their application performs the following tasks:
Click the above link to launch the development sandbox, which includes a temporary instance and built-in IDE. No knowledge of coding is necessary to complete this tutorial, as the Learning Labs contain all of the code you will need.
shared/directory in the project files. The shared folder is mapped to share data with a directory within the InterSystems IRIS for Health instance.
shared/quickstarts-hl7/data/sample_data/directory to the
shared/quickstarts-hl7/data/registration/directory. The message should disappear from the
registration/directory upon being processed by the production.
shared/quickstarts-hl7/data/archive/and notice that the incoming message has been copied here for future reference. Locate the
shared/quickstarts-hl7/data/billing/directory and the
shared/quickstarts-hl7/data/lab/directory, which should contain outgoing HL7 messages. As you can see, the production has transformed the message differently for each endpoint. You can verify this by opening the messages in a text editor and comparing them.
INTEROP. Navigate to the Production Configuration interface by navigating to Interoperability > Configure > Production. If the
HL7QS.Productionis not already running, click Start at the top of the page. This production has been built from the HL7 production template provided with all instances of InterSystems IRIS for Health. Here, you can develop and monitor the pieces of the HL7 production and the messages that are processed by it. Notice there are three columns: Services, Processes, and Operations. The architecture of this application follows from the standard architecture of an InterSystems IRIS for Health production. As you can see below, the leftmost column contains the services for data input, the middle column contains data transformation and routing, and the rightmost column handles data output.
fromRegFile, and then click the Messages tab in the right-most pane. Click Go to Message Viewer. Select one of the messages that was sent. Now click the Contents tab, where you can see the full contents of the incoming HL7 message. Note that the raw text of the input file has been interpreted based on a designated HL7 schema. Clicking on a field will bring you to the schema definition.
PatientRegDBOperationhas saved the information extracted from the HL7 message. Return to the Management Portal, ensure the namespace is
INTEROP, navigate to System Explorer > SQL. When data has been created or objects have been saved, the tables may be viewed here. In the Execute Query tab, retrieve the
PatientRegdata by executing the following query:
Select * from HL7QS.PatientRegThe table only includes a few columns with data extracted from the HL7 message.
Watch a demonstration of the exercise above.