Close
Search

ORU (PDF)

Introduction

This document describes the technical specifications of the ZorgDomein HL7 V2.4 ORU (PDF) message. This message contains metadata about a request form or referral letter and the form or letter itself in PDF format. The message model describes the structure of this message.

The subsequent section further describes the contents of these segments. The abbreviation ‘Elem.nr’ denotes the element number.

ZorgDomein adheres to the required fields as specified in the international HL7 V2.4 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 specification

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.
7Date/Time Of MessageDate/time of message creation. Format: yyyyMMddHHmmss+HHmm.
9.1Message Type“ORU”.
9.2“R01”.
10Message Control IDIn case of Patient Conversation export: Unique message identifier.
Else: ZorgDomein number. Format: ZDnnnnnnnnn, where each n denotes a digit.
11.1Processing ID“P”.
12.1Version ID“2.4”.

PID - Patient Identification

Elem.nr.Field nameZorgDomein content
1Set ID - PID“1”.
3.1Patient Identifier ListTwo options, depending on presence. A overrides B:
A) CS-Zorgportaal patient ID.
B) The patient’s BSN.
3.4.1If PID-3.1 option A: “ZIS”.
Else: “NLMINBIZA”.
3.5If PID-3.1 option A: “PI”.
Else: “NNNLD”.
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”.
7Date/Time of BirthThe patient’s date of birth. Format: yyyyMMdd.
8Administrative SexIf the patient’s sex is male: “M”.
If the patient’s sex is female: “F”.
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“H”.
13.1Phone Number - HomeThe patient’s phone number.
13.2Use Code"NET" (When email is pressent).
13.3Equipement type"Internet" (When email is pressent).
13.4Email addressThe patient’s email adress.

PV1 - Patient Visit

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

ORC - Common Order

Elem.nr.Field nameZorgDomein content
1Order Control“NW”.
2.1Placer Order NumberIn case of Patient Conversation export: Unique message identifier.
Else: ZorgDomein number. Format: ZDnnnnnnnnn, where each n denotes a digit.
9Date/Time Of MessageDate/time of message creation. Format: yyyyMMddHHmmss+HHmm
10.1Entered ByThe acting referrer’s AGB code.
10.2.3The 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 is known.
12.2.3The responsible referrer’s full surname.
12.3The responsible referrer’s initials.
12.9.1“VEKTIS”.
14.1Call Back Phone NumberThe phone number of the practice.

OBR - Observation Request

Elem.nr.Field nameZorgDomein content
1Set ID - OBR“1”.
2.1Placer Order NumberIn case of Patient Conversation export: Unique message identifier.
Else: ZorgDomein number. Format: ZDnnnnnnnnn, where each n denotes a digit.
4.1Universal Service IdentifierIn case of Patient Conversation export: "PO".
Else: Code of cluster.
4.2In case of Patient Conversation export: "Patiëntoverleg".
Else: Name of specialism.
4.3“ZORGDOMEIN”.
7Observation Date/TimeDate/time of respective logistic referral. Format: yyyyMMddHHmmss+HHmm.
16.1Ordering ProviderThe responsible referrer’s AGB code.
16.2.3The responsible referrer’s full surname.
16.3The responsible referrer’s initials.
16.9.1“VEKTIS”.

OBX(1) - Observation/Result

Elem.nr.Field nameZorgDomein content
1Set ID - OBX“1”.
2Value Type“NM”.
3.1Observation IdentifierThree options, depending on what type of document the message contains:
A) If referral letter: “VB”.
B) If diagnostic request or questionnaire: “AF”.
C) If patient conversation chat log: “PO”.
3.3“123”.
11Observation Result Status“F”.

OBX(2) - Observation/Result

Elem.nr.Field nameZorgDomein content
1Set ID - OBX“2”.
2Value Type“ED”.
3.1Observation IdentifierIn case of Patient Conversation export: "PO".
Else: Code of reason of referral.
3.2In case of Patient Conversation export: "Patiëntoverleg".
Else: The leaf node of the reason of referral.
3.3“ZORGDOMEIN”.
5.2Observation Value“application”.
5.3“pdf”.
5.4“Base64”.
5.5If OBX(1)-3.1 option A: referral letter in PDF format, encoded in Base64.
If OBX(1)-3.1 option B: diagnostic request or questionnaire in PDF format, encoded in Base64.
11Observation Result Status“F”.

OBX(3) - Observation/Result

Elem.nr.Field nameZorgDomein content
1Set ID - OBX“3”.
2Value Type“FT”.
3.1Observation IdentifierCode of health care product.
3.2Name of health care product.
3.3“ZORGDOMEIN”.
11Observation Result Status“F”.

Version history

VersionDateAuthorDescription
1.010-3-2016Gido Duif-
1.123-3-2016Gido DuifChange in OBX-11. Structural change in segment specifications tables.
1.222-4-2016Gido DuifChange in OBX(1)-3.1 and OBX(2)-5.5.
1.329-4-2016Gido DuifTextual corrections.
1.426-4-2017Gido DuifAdded OBX(1)-11 and OBX(3)-11. Added option “PO” to OBX(1)-3.1.
1.519-6-2018Gido DuifAdded Patient Conversation functionality: change in MSH-10, ORC-2.1, OBR-2.1, OBR-4, and OBX(2)-3.1.