Question
· Sep 17

HL7 Schema for parsing custom Orbis HL7 messages

#HL7 #Health Connect

Hello community,

is anybody located in the DACH area healthcare sector working with Dedalus Orbis as patient master and uses a custom HL7 schema for parsing Orbis message structures into Health Connect?

We're facing a migration and I ask myself if I have to create a schema by myself, based on the pdf documentation given by the company. This is a tedious task,  so hopefully there is somebody out there willing to share his or her experience.

Kind regards,

Martin 

Product version: IRIS 2021.1
$ZV: IRIS for UNIX (SUSE Linux Enterprise Server for x86-64) 2021.1 (Build 215U) Wed Jun 9 2021 09:48:27 EDT [HealthConnect:3.3.0] [HealthConnect:3.3.0]
Discussion (1)2
Log in or sign up to continue
DC AI Bot · Sep 17

To parse custom Orbis HL7 messages into Health Connect, you may need to create or adapt a custom HL7 schema. Common practices and tools for such customization involve:

  1. Using Existing HL7 Versions: Health Connect allows you to browse HL7 schemas for all HL7 v2 versions up to 2.8.2. Through the Management Portal, you can access detailed structures including messages, segments, fields, and associated code tables under Interoperability -> Interoperate -> HL7 v2.x -> HL7 v2.x Schema Structures [1].

  2. Creating Custom HL7 Schemas: If your setup requires custom mappings, Healthcare HL7 XML provides utilities for creating lookup tables to address mappings of HL7 XML group names and EnsLib.HL7.Message group names. For each schema being integrated, these lookup tables need to be established [2].

  3. Transform Custom Messages: InterSystems IRIS for Health enables transforming proprietary/custom data into standard HL7 formats using Data Transformation Language (DTL). You can use graphical drag-and-drop tools for mapping fields and set fixed values or dynamic mappings [3][4].

  4. Schema Modifications and Dynamic Data Structures: In cases where dynamic data structures are needed, such as varying OBX data types depending on another field's value, a custom HL7 schema can be developed. This may involve copying an existing schema like HL7 2.5 and marking it as standard to allow non-resolved references [2].

  5. Leverage Open Source Applications: There are open-source applications and sample projects for transforming messages. Examples include transforming HL7 files using ER7/XML formats or testing production configurations [2].

If the migration is complex, it might be worth consulting the HL7 schemas or online courses related to Health Connect to streamline the setup. If you require example scripts or deeper assistance, reaching out to peers on the Developer Community would be beneficial [5].

Sources:

0 0