The Data Analysis profiles that are provided with IBM® Integration Bus Healthcare Pack are used to analyze specific types of healthcare data.
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 IBM Integration Bus product 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 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 Integration Bus Healthcare Pack 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.
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 IBM Integration Bus product documentation.
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 Integration Bus Healthcare Pack 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.