© 2024 IQVIA - All Rights Reserved
ClinAxys Lab HL7 Order File Field Mapping Overrides
- Stuart Robertson
- Riggi Luckiesh
- Steffan Stringer (Unlicensed)
Introduction
This page documents deviations from our default HL7 lab interface files made for the ClinAxys interface used by some customer sites. ONLY deviations from the parent document will be described here. For any fields not mentioned, please refer to the parent document here ClinSpark / ClinAxys Lab Integration.
OBX - AOE
The ClinAxys interface does not have the standard AOE entries in the outbound order.
HL7 Result File
A result file is received from the safety lab. Each result for a specimen contains an ORC, and one more more OBR and OBX segments.
ClinSpark takes from the result files ONLY information about which tests were resulted and the data about those results. It obtains from the ORC the barcode of the specimen, then reads each OBR/OBX to obtain details about the test performed.
Any additional information is ignored. The PID and MSH header are not inspected, as ClinSpark is the source of truth of patient information, not the safety lab producing the result file.
Here is an example result file we’ll look at:
ORC
The values obtained from this segment can be seen here:
Field | Field Value | Any Transformation Logic |
|---|---|---|
1 | This is the ClinSpark specimen barcode. It is expected to match the barcode value for that specimen which was originally sent in the HL7 order file. In ClinSpark this is called the Specimen Material ID | None |
2 | This is the Filler Order Number. It is a unique identifier assigned by the safety lab, referred to in ClinSpark as the assession number. | None |
3 | The order status field is in ORC-5. In this example it is omitted. ClinSpark will however record any values returned here and make them available in the UI. Here are the expected values. | None |
OBR
OBR segments 2 and 3 are the same as ORC segments 2 and 3. They are compared to ensure they match however their values are not used.
Field | Field Value | Any Transformation Logic |
|---|---|---|
1 | Lab test code. This is the identifier for the lab test according to the external safety lab. | None |
2 | Lab test name. This is a more human readable and descriptive name for the test. | None |
3 | Observation Date and Time. Docs here. | None |
4 | OBR.22, Reported Date and Time. This field is used to indicate the date and time that the results are composed into a report and released, or that a status, | None |
OBX
Field | Field Value | Any Transformation Logic |
|---|---|---|
1 | Value Type. Indicates whether the result is numeric, text, etc. | Incoming value is a 1-3 character code. ClinSpark displays its meaning. |
2 | Observation Sub ID. By convention this is the LOINC code assigned by the lab. | None |
3 | Reported Result. | This will appear in ClinSpark in one of two fields, depending on the value type. See the annotated screenshot of the test result page. |
4 | Units. | None |
5 | Reference Range | ClinSpark will parse this string into the low and high values if appropriate. See the annotated screenshot of the test result page. |
6 | Alert Flags. OBX.8 | None |
7 | None | |
8 | Date/Time Of The Observation | None |
Exported and Printed Copies Are Uncontrolled