Search

OML (LFDv2)

Deprecation warning:

This specification has been deprecated. Please view the OML (V3) message specification for the most recent OML specs.

Introduction

This document describes the technical specifications of the ZorgDomein HL7 V2.5.1 OML (LFDv2) message. This message is used for sending diagnostic requests.

The subsequent sections describe the contents of these segments. The abbreviation ‘Elem.nr’ denotes the element number. Options of a specific field within a segment implies that multiple options can be supplied by repeating the field. Exception: OBR-4, where multiple options can be supplied by repeating the segment. In any case, all available options will be supplied in the message.

ZorgDomein adheres to the message structure and the required fields as specified in the international HL7 V2.5.1 specifications.

In this document, the term ‘acting referrer’ describes the person that used ZorgDomein and actually referred the patient. The term ‘responsible referrer’ describes the person that is responsible for that referral. The two often relate to the same person.

If the ZorgDomein content consists of a value between two double quotes, that value is the fixed value of that specific element.

Segment specifications

MSH - Message Header

Elem.nr.Field nameZorgDomein content
1Field Separator“|”.
2Encoding Characters“^~\&”.
3.1Sending Application“ZorgDomein”.
5.1Receiving ApplicationName of the receiving application.
6.1Receiving FacilityName of the receiving facility.
7.1Date/Time Of MessageDate/time of message creation.
Format: yyyyMMddHHmmss+HHmm.
9.1Message Type“OML”.
9.2“O21”.
9.3“OML_O21”.
10Message Control IDUnique message identifier.
11.1Processing ID“P”.
12.1Version ID“2.5.1”.
17Country Code“NLD”.
18Character Set“8859/1”.

PID - Patient Identification

Elem.nr.Field nameZorgDomein content
1Set ID - PID“1”.
Option: Patient’s BSN
3.1Patient Identifier ListThe patient’s BSN.
3.4.1“NLMINBIZA”.
3.5“NNNLD”.
Option: XIS patient ID
3.1Patient Identifier ListXIS patient ID.
3.4.1The AGB-code of the facility.
3.5“PI”.
The option “XIS patient ID” supplies all available patient IDs by repeating this field.
Option: ZorgDomein patient ID
3.1Patient Identifier ListZorgDomein patient ID.
3.4.1“ZorgDomein”.
3.5“PI”.
Option: ZorgDomein number
3.1Patient Identifier ListZorgDomein number.
Format: ZDnnnnnnnnn, where each n denotes a digit.
3.4.1“ZorgDomein”.
3.5“VN”.
5.1.1Patient NameThe patient’s full surname.
5.1.2Prefix of surname in PID-5.1.3.
5.1.3The patient’s own surname (without prefix).
5.1.4Prefix of surname in PID-5.1.5.
5.1.5The patient’s spouse surname (without prefix).
5.2The patient’s first initial.
5.3The patient’s second and further initials, separated by spaces.
5.7“L”.
7.1Date/Time ofBirthThe patient’s date of birth.
Format: yyyyMMdd.
8Administrative SexIf the patient’s sex is male: “M”.
If the patient’s sex is female: “F”.
If the patient’s sex is not specified: “O”.
If the patient’s sex is unknown: “U”.
11.1.1Patient AddressCombination of PID-11.1.2, PID-11.1.3, and PID-11.2.
11.1.2The patient’s home street name.
11.1.3The patient’s home dwelling number.
11.2The patient’s home other designation.
11.3The patient’s home city name.
11.5The patient’s home postal code.
11.6The patient’s home country code.
11.7“M”.
Option: Patient’s phone number
13.1Phone Number - HomeThe patient’s phone number.
13.2“PRN”.
13.3“PH”.
Option: Patient’s mobile phone number
13.1Phone Number - HomeThe patient’s mobile phone number.
13.2“ORN”.
13.3“CP”.
31Identity Unknown IndicatorIf the referrer’s verification of the BSN is unknown: “Y”.
Else: “N”.
32Identity Reliability Code“NNNLD”.
The current referrer’s XIS interfaces does not include whether the BSN is verified by the responsible referrer or not. Until the verification of the BSN is supported, PID-31 always supplies: “Y” and PID-32: “NNNLD”.

PV1 - Patient Visit

Elem.nr.Field nameZorgDomein content
1Set ID - PV1“1”.
2Patient Class“O”.
51Visit Indicator“V”.

PV2 - Patient Visit - Additional Information

Elem.nr.Field nameZorgDomein content
3.1Admit ReasonCode of health care product.
3.2Name of health care product.
3.3“99zda”.

IN1 - Insurance

Elem.nr.Field nameZorgDomein content
1Set ID - IN1“1”.
2.2Insurance Plan ID“null”.
3.1Insurance Company IDIf UZOVI number is present: UZOVI number.
Else: “0”.
3.4.1If UZOVI number is present: “VEKTIS”.
Else: “LOCAL”.
3.5If UZOVI number is present: “UZOVI”.
4.1Insurance Company NameThe patient’s insurance company name.
36Policy NumberThe patient’s policy number.

ORC - Common Order

Elem.nr.Field nameZorgDomein content
1Order ControlIn case of new order/service: “NW”.
In case of cancel order/service request: “CA”.
In case of replacement order: “RO”.
In case of change order/service request: “XO”.
2.1Placer Order NumberZorgDomein number with sequence number.
Format: ZDnnnnnnnnn_nn, where each n denotes a digit. The underscore is followed by the sequence number, which is unique within the message, starting from 01.
3.1Filler Order NumberOrder number of the receiving facility.
4.1Placer Group NumberZorgDomein number.
Format: ZDnnnnnnnnn, where each n denotes a digit.
9.1Date/Time of TransactionDate/time of diagnostic request initiation.
Format: yyyyMMddHHmmss+HHmm.
10.1Entered ByThe acting referrer’s AGB-code.
10.2.1The acting referrer’s full surname.
10.3The acting referrer’s initials.
10.9.1If ORC-10.1 contains a value: “VEKTIS”.
12.1Ordering ProviderThe responsible referrer’s AGB-code.
12.2.1The responsible referrer’s full surname.
12.3The responsible referrer’s initials.
12.9.1“VEKTIS”.
13.4.1Enterer’s LocationName of the acting referrer’s practice.
13.4.2AGB-code of the acting referrer’s practice.
13.9Name of the acting referrer’s location.
Option: Phone number for results
14.1Call Back Phone NumberPhone number for results.
14.2“WPN”.
14.3“PH”.
Option: Fax number for results
14.1Call Back Phone NumberFax number for results.
14.2“WPN”.
14.3“FX”.
15Order Effective Date/TimeIf ORC-1 contains the value “CA”, “RO” or “XO”:
Updated date/time of diagnostic request.
Format: yyyyMMddHHmmss+HHmm.
17.1Entering OrganizationThe AGB-code of the acting referrer’s practice.
17.2The name of the acting referrer’s practice.
17.3“VEKTIS”.
19.1Action ByThe responsible updater’s AGB-code.
19.2.1The responsible updater’s full surname.
19.3The responsible updater’s initials.
19.9.1If ORC-19.1 contains a value: “VEKTIS”.
21.1Ordering Facility NameThe name of the responsible referrer’s practice.
21.3The AGB-code of the responsible referrer’s practice.
21.6.1“VEKTIS”.

TQ1 - Time/Quantity

Elem.nr.Field nameZorgDomein content
1Set ID - TQ1Sequence number unique within message for TQ1 segment. Initial value: “1”. Equal to respective OBR-1 value.
7.1Start date/timeRequested date for sampling. If TQ1-8.1 also has a value, it explicitly concerns the earliest the date for sampling.
Format: yyyyMMddHHmmss+HHmm.
8.1End date/timeLatest date for sampling.
Format: yyyyMMddHHmmss+HHmm.
9.1PriorityIf the acting referrer wishes the results to be called in or faxed: “S”.
Else: “R”.
11Text instructionInstructions for the collect employee.

OBR - Observation Request

Elem.nr.Field nameZorgDomein content
1Set ID - OBRSequence number unique within message for OBR segment. Initial value: “1”. Equal to respective TQ1-1 value.
2.1Placer Order NumberZorgDomein number with sequence number.
Format: ZDnnnnnnnnn_nn, where each n denotes a digit. The underscore is followed by the sequence number, which is unique within the message, starting from 01.
3.1Filler Order NumberOrder number of the receiving facility.
Option: Diagnostic test
4.1Universal Service IdentifierCode of diagnostic test.
4.2Name of diagnostic test.
4.3If OBR-4.1 contains ZorgDomein defined codes: “99zda”.
If OBR-4.1 contains user defined codes: “99zdl”.
Else: Global standard code (see table 0396 of the international HL7 V2.5.1 specifications).
For each diagnostic test that is selected by the referrer, this option is provided in the message. Exception: see “Option: Diagnostic test group” mentioned below.
Option: Diagnostic test group
4.1Universal Service IdentifierCode of diagnostic test group.
4.2Name of diagnostic test group.
4.3If OBR-4.1 contains ZorgDomein defined codes: “99zda”.
If OBR-4.1 contains user defined codes: “99zdl”.
When the selected diagnostic test group solely consists of required diagnostic tests, this option is provided in the message instead of multiple “Option: Diagnostic test”. All respective information regarding the included diagnostic tests is deduplicated and included in the message.
7.1Observation Date/TimeDate/time the observation/collection was initiated.
Format: yyyyMMddHHmmss+HHmm.
8.1Observation End Date/TimeDate/time the observation/collection was completed.
Format: yyyyMMddHHmmss+HHmm.
10.1Collector IdentifierThe collect employee’s ZorgDomein health care provider ID or AGB-code.
10.2.1The collect employee’s full surname.
10.3The collect employee’s initials.
10.9.1If OBR-10.1 contains a value: “99zda” or “VEKTIS”.
11Specimen Action CodeIf home sampling is requested: “L”.
Else: “O”.
13Relevant Clinical InformationNames of problem groups that include the diagnostic test, as selected by the acting referrer.
16.1Ordering ProviderThe responsible referrer’s AGB-code.
16.2.1The responsible referrer’s full surname.
16.3The responsible referrer’s initials.
16.9.1“VEKTIS”.
Option: Phone number for results
17.1Order Callback Phone NumberPhone number for results.
17.2“WPN”.
17.3“PH”.
Option: Fax number for results
17.1Order Callback Phone NumberFax number for results.
17.2“WPN”.
17.3“FX”.
28.1Result Copies ToCode as entered by the acting referrer to send copy to.
28.2.1Name of person as entered by the acting referrer to send copy to.
28.9.1If OBR-28.1 contains a value: “VEKTIS”.
39.2Collector’s CommentThe collect employee’s comment.

OBX - Observation/Result

Elem.nr.Field nameZorgDomein content
1Set ID - OBXSequence number unique within the combination of respective ORC, OBR, and OBX segments. Initial value: “1”.
2Value TypeIf OBX-5.2 contains string data: “ST”.
If OBX-5.2 contains formatted text: “FT”.
If OBX-5.2 contains a date: “DT”.
If OBX-5.2 contains encapsulated data: “ED”.
If OBX-5.2 contains coded entry: “CE”.
3.1Observation IdentifierCode of question.
3.2Label of question.
3.3If OBX-3.1 contains a value:
If OBX-3.1 contains ZorgDomein defined codes: “99zda”.
If OBX-3.1 contains user defined codes: “99zdl”.
Else: Global standard code (see table 0396 of the international HL7 V2.5.1 specifications).
5.1Observation ValueCode of answer/option to the question.
5.2Value of answer/option to the question.
5.3If OBX-5.1 contains a value:
If OBX-5.1 contains ZorgDomein defined codes: “99zda”.
If OBX-5.1 contains user defined codes: “99zdl”.
Else: Global standard code (see table 0396 of the international HL7 V2.5.1 specifications).
OBX-5 is repeated in case of multiple answers to a single question.
6.1UnitsUnity of the value of answer/option to the question.
7References RangeThe range to which the answer/option to the question is restricted.
11Observation Result Status“F”.

SPM - Specimen

Elem.nr.Field nameZorgDomein content
1Set ID - SPMSequence number unique within the combination of respective ORC, OBR, and SPM segments. Initial value: “1”.
4.1Specimen TypeCode of specimen source.
4.2Name of specimen source.
4.3If SPM-4.1 contains ZorgDomein defined codes: “99zda”.
If SPM-4.1 contains user defined codes: “99zdl”.
Else: Global standard code (see table 0396 of the international HL7 V2.5.1 specifications).
17.1.1Specimen Collection Date/TimeDate/time the observation was initiated.
Format: yyyyMMddHHmmss+HHmm.
17.2.1Date/time the observation was completed.
Format: yyyyMMddHHmmss+HHmm.

List of possible specimen source names & codes on SPM segment

A fixed set of specimen source codes and names can be expected in SPM-4.1 and SPM-4.2. See the table below for an overview of these codes and names.
Code of specimen sourceName of specimen source
BLDBloed
URUrine
STLFeces
ORHOverig
USPECMicrobiologie

SAC - Specimen Container

Elem.nr.Field nameZorgDomein content
3.1Container IdentifierCode of container.
3.2Name of container.

Version history

DateDescription
25-3-2016Initial formal publication
25-3-2016Change in OBR-7, OBR-8, SAC-7.1, SPM-17.1, and SPM-17.2.
4-4-2016Change in PID-13.2, OBR-4, and OBR-7.
4-4-2016Structural change in document. Change in OBX segment.
22-4-2016Change in MSH-10.
29-4-2016Textual corrections.
4-5-2016Change in PID-3, IN1-3, ORC-14.2, OBR-17.2, and ORC-10
10-5-2016Change in IN1-3.
12-5-2016Change in PID-3, IN1-3, and OBR-10.
24-5-2016Added exception OBR-4 to introduction. Change in SPM-1 and SPM-2.1.1.
25-5-2016Change in ORC-2.1, ORC-2.1, and the SPM specimen source table.
26-5-2016Clarified multiple options mechanics in introduction. Change in PID-3.
1-6-2016Change in “Effect of order manager on OBX segment” table.
15-6-2016Change in OBR-7.1 Added OBR-8.1.
28-6-2016Change in the description below OBR-4 (Diagnostic test group). Clarified the description below PID-3 (XIS patient ID).
7-7-2016Added OBR-16.
22-8-2016Added format to OBR-7.1, OBR-8.1, SPM-17.1.1, and SPM-17.2.
5-9-2016Deleted PID-13 “Option: Patient’s email address”.
13-10-2016Change in PID-3, PID-11.7 and IN1-3. Added PID-31 and PID-32.
9-3-2017Removed OBR-4 “Option: Health care product”. Added PV1-51. Added PV2-3. Removed SPM-2. Change in OBX-5. Textual corrections.
14-7-2017Removed predetermined codes for the Ordermanager.
31-1-2024Added TQ1-8.1 specification and extra comment for TQ1-7.1
1-2-2024Removed invalid specification for empty BSN in PID-3