Healthcare Data Analysis profiles

The Data Analysis profiles that are provided with IBM® WebSphere® Message Broker Connectivity Pack for Healthcare are used to analyze specific types of healthcare data.

IBM WebSphere Message Broker Connectivity Pack for Healthcare provides a number of Data Analysis profiles that are used with a WebSphere Message Broker Data Analysis project to analyze healthcare data that is routed through message flows. Each profile is used for a specific type of healthcare data.
  • Use the HL7 v2 Data Analysis profile to analyze HL7 data, see HL7 v2.
  • Use the HL7 CDA Data Analysis profile to analyze HL7 Clinical Document Architecture (CDA) documents, see HL7 CDA.
  • Use the HL7 v2 (ORU) Data Analysis profile to analyze HL7 Observation Result (ORU) messages, see HL7 v2 (ORU).
  • Use the DICOM Data Analysis profile to analyze Digital Imaging and Communications in Medicine (DICOM) XML data, see DICOM.

HL7 v2

The HL7 standard supports the integration of clinical applications. HL7 v2 messages use a human-readable (ASCII), non-XML encoding syntax that is based on segments (lines) and one-character delimiters.

To acquire a set of HL7 messages in XML format, you can use the DFDL parser in the DFDL schema editor to convert your HL7 messages to XML, and then save the converted messages. For more information about the DFDL schema editor, see DFDL schema editor in the WebSphere Message Broker documentation.

The DFDL support in the Healthcare Connectivity Pack provides a set of DFDL schemas for HL7 v2.5.1, v2.6 and v2.7. The HL7 v2 Data Analysis profile provides a combination of the DFDL schemas to use in the Data Analysis project.

The HL7 v2 Data Analysis profile does not provide any glossary or discriminators because the HL7 v2 DFDL model contains descriptive element names.

HL7 CDA

HL7 CDA is an XML-based mark-up standard that specifies the encoding, structure, and semantics of clinical documents. HL7 CDA documents usually include codes which rely on external services to resolve the codes into meaningful text, for example, the LOINC (Logical Observation Identifiers Names and Codes) Terminology Lookup Service.

HL7 CDA documents are difficult to process because the HL7 CDA standard uses a generic schema model with recursive elements. The HL7 CDA Data Analysis profile in the IBM WebSphere Message Broker Connectivity Pack for Healthcare provides a pre-defined set of discriminators for HL7 CDA documents. These discriminators identify key sections of a CDA document.

Since HL7 CDA documents are already in XML format they do not need any conversion before being processed by the HL7 CDA Data Analysis profile.

You use the HL7 CDA Data Analysis profile to identify elements and highlight them with their meaning (for example PurposeSection, PayersSection, AdvanceDirectivesSection). These names are taken from a glossary of HL7 CDA templates that are defined by a number of organizations, for example, HL7, CDA, Continuity of Care Document (CCD), Healthcare Information Technology Standards Panel (HITSP). The HL7 CDA Data Analysis profile uses a single consistent terminology that is built from a collection of these templates.

For information about the elements that are highlighted when you analyze HL7 CDA documents, see Data elements highlighted in HL7 CDA documents.

The HL7 CDA Data Analysis profile also provides a LOINC Terminology Lookup Service for HL7 CDA documents by using a glossary of clinical terms. For legal reasons, the LOINC database is not provided by the profile but you can download the database from the LOINC web site. You configure the profile with the location of the LOINC database by using the WebSphere Message Broker Toolkit preferences.
Note: You must configure the LOINC database before a HL7 CDA Data Analysis project is created because the terminology codes are only resolved when the CDA documents are first analyzed.

HL7 v2 (ORU)

ORU messages typically carry clinical observations (values such as blood pressure and pulse rate) in an OBX segment.

The HL7 v2 ORU Data Analysis profile provides highlighting for OBX segments in observation results. The code system in an OBX segment must contain the characters LN to identify it as using the LOINC glossary (the code system is stored in the OBX.3.ObservationIdentifier/CWE.3 field). The LOINC glossary is used to resolve the value in the field OBX.3.ObservationIdentifier/CWE.1.

To acquire a set of HL7 ORU messages in XML format, you can load the ORU messages into the DFDL schema editor, parse the ORU messages, and then save the ORU messages as XML. For more information about the DFDL schema editor, see DFDL schema editor in the WebSphere Message Broker documentation.

Note: You must configure the LOINC database before a HL7 v2 (ORU) Data Analysis project is created because the terminology codes are only resolved when the ORU messages are first analyzed.

DICOM

DICOM (Digital Imaging and Communications in Medicine) is a standard for handling, storing, printing, and transmitting information in medical imaging. The DICOM standard includes a file format definition and a network communications protocol.

To acquire a set of DICOM XML messages from a set of DICOM images, you can use the DICOM Test application, see Using the DICOM test application.

The DICOM Data Analysis profile in the IBM WebSphere Message Broker Connectivity Pack for Healthcare includes a glossary service (generated from the DICOM standard) to convert the DICOM attributes into display names.

When you run a data analysis project against DICOM XML files, the elements named Attribute are highlighted. The value of the Tag attribute in each element is resolved by using the DICOM code set (1.2.840.10008) in the glossary service.

Note: Unresolved DICOM attributes are common because many vendors extend the standard with their own proprietary DICOM codes.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 2011, 2014Copyright IBM Corporation 2011, 2014.

        
        Last updated
        
        Last updated : 2015-12-07 14:52:02


Concept topicConcept topic | Version 8.0.0.0 | ha05320