Use HL7 nodes
in a message flow to integrate HL7 clinical
applications.
Before you begin
Before you start:
About this task
If there are no patterns that meet your requirements, you
can integrate data from HL7 applications
by creating your own message flow and adding HL7 nodes.
Procedure
To use the data from HL7 applications in message
flows, complete the following steps:
- Collect connection information about your HL7 applications.
- Import the appropriate message model into
your workspace.
- If you are using the DFDL message model:
- Make sure that you are using the documentation that is integrated
with the IBM Integration
Toolkit.
- Click Resources for the Healthcare: HL7 to HL7 DFDL
pattern to
open the document that contains the resources for the pattern.
- Click the appropriate link in the document to import the required
version of the DFDL message model (HL7 version 2.7, HL7 version 2.6, or HL7 version 2.5.1 or earlier)
Note: The DFDL message models occupy
a significant amount of memory, so you should import only the DFDL message model that you require.
Also, to improve the performance and reduce the deployment time of
the message flows, you can delete the chapters that you do not need
from DFDL message model that
you import.
- If you are using the HL7v25P
message set:
- Make sure that you are using the documentation that is integrated
with the IBM Integration
Toolkit.
- Click Resources for the Healthcare: HL7 to HL7
pattern to
open the document that contains the resources for the pattern.
- Click Import the sample resources into your workspace to
import the HL7v25P
message set.
- Create a message flow and add the appropriate HL7 nodes. For information
about the available HL7 nodes
and their purposes, see HL7 nodes in message flows.
-
Complete your message flow.
For more information about developing integration solutions, see
Developing message flows in the IBM Integration Bus product
documentation.
What to do next
Next:Test and debug your integration solution to check that it works correctly.
See Testing and troubleshooting
message flows in the IBM Integration Bus product
documentation.