Order and result messages for pathology information systems

Transcription

1 Implementation guideline HL7 version 2.4 Order and result messages for pathology information systems PATHOLOGY, LABORATORY Date August 22, 2013 ID Author Heitmann Consulting and Services Dr. K.U. Heitmann Reviewers Nictiz Drs. T. van Stijn Nictiz Drs. C.E. Hülsmann

2 Index H-1 Introduction Original author Revision Review Translation Status Document history 5 H-2 Exchange format and workflow overview Version of the HL7 protocol Workflow overview 6 H-3 Order to the pathology laboratory Process Specification of message composition (segments) MSH segment PID segment PV1 segment ORC segment OBR segment SAC segment OBX segment 20 H-4 Order confirmation of receipt Variant Variant Variant MSA segment SAC segment 27 August 22, 2013 Order and result messages for pathology information systems

3 H-5 Pathology laboratory results Specification of message composition (segments) MSH segment PID segment PV1 segment ORC segment OBR segment OBX segment 38 H-6 Confirmation of receiving result message 41 H-7 Appendix I Communication MLLP U-DPS attributes concerning the HL7 connection 42 H-8 Appendix II Concepts 43 August 22, 2013 Order and result messages for pathology information systems

4 H-1 Introduction This document describes the HL7 version 2.4 messages used to order a study to be executed on tissue, cellular material or an autopsy on a non-living person. An order message is sent to the pathology laboratory. In addition, this document describes the result messages as a response to the described order messages. The document is based on earlier versions of two documents by Tieto Healthcare Netherlands BV: [1] Documentatie koppelingen U-DPS ZIS: HL7 ORU koppeling versie 2.4, document version 1.0, 24 December 2008 and [2] Documentatie HL7 koppelingen: ORM koppeling versie NL 2.4, document version 1.1.1, 24 November 2010 These documents as well as the current document are based on the following document that is owned bij the HL7 Netherlands Foundation: Implementatie Gids HL7 Versie 2.4 NL (Implementation guideline HL7 version 2.4 NL) In that document, the following chapters have mainly served as a source for the present document: [3] Chapter 2: Control [4] Chapter 3: Patient Administration [5] Chapter 4: Order Entry [6] Chapter 7: Observation Reporting 1.1. Original author Fons Geerts, Tieto Healthcare Netherlands BV 1.2. Revision Dr. K.U. Heitmann (Heitmann Consulting and Services) 1.3. Review Drs. T. van Stijn (Nictiz) Drs. C.E. Hülsman (Nictiz) 1.4. Translation This document has been translated from Dutch into English by Drs. C.E. Hülsmann. The purpose of translation is serving all software vendors that operate nationally and or internationally, developing software for the Dutch market Status Final August 22, 2013 Order and result messages for pathology information systems 4

5 1.6. Document history Version Date (ymd) Description Author Original document title: HL7 ORU koppeling versie 2.4 [1] Original document title: ORM koppeling versie NL 2.4 [2] Revision and merge of the first two ducuments, changes to version 2.4 and new message types/trigger events Addition of report number and sample number in the confirmation message and making LOINC codes compulsory where possible Addition to Specimen Source, adjustments made because of incoming comments More comments and clarifications from earlier versions, reporting protocol and ACK messages elaborated, correction of typing mistakes Fons Geerts Fons Geerts Dr. K. Heitmann Dr. K. Heitmann Dr. K. Heitmann Dr. K. Heitmann Correction of typing mistake OML event Dr. K. Heitmann Several changes after review by NICTIZ, mainly of semantic or syntactic nature Change of message type name ORU; addition of OBR-31 Reason for study Adjustment of Abstract Syntax Message for messages (addition of symbols) Dr. A. Huisman (MedicalPHIT for RIVM) Dr. K. Heitmann Dr. K. Heitmann Document review and lay-out change Drs. C.E. Hülsmann Addition of the SAC segment in OML^O21 after receiving vendor feedback February 8th Additional code for Reason for study, revision of the SAC segment, additional code for OBX-3 (additional note on material), examples Translation from Dutch into English, adjustment of note PID-3, update of par. 3.1: use of BSN is compulsory Dr. K. Heitmann Dr. K. Heitmann Drs. C.E. Hülsmann August 22, 2013 Order and result messages for pathology information systems 5

6 H-2 Exchange format and workflow overview 2.1. Version of the HL7 protocol U-DPS uses the HL7 protocol version 2.4 NL. The BSN is the Dutch national identification number called Burgerservicenummer, also used in the healthcare sector to identify a person. Whether or not this BSN has to be delivered to the receiving oranizations, depends on the urge of the representatives of these organizations. In most cases, these organizations are Hospitals, the receiver of the messages being the Hospital Information System (HIS). The HL7 Netherlands Foundation has served as the main advisor for the specifications in this document. However, this foundation does not own any specific guidelines on the composition of an order message for a pathology laboratory. For this reason, this document emphasizes the use of the OBX segment as part of the message as far as the Kind of material and Clinical information is concerned Workflow overview Diagram 1 is an overview of all involved actors (application roles) and the HL7 v2.4 messages that are involved. Diagram 1: Interactions between a lab order placer (original order initiator) and lab order filler (original order executor, in this case the pathology laboratory) August 22, 2013 Order and result messages for pathology information systems 6

7 A requesting system (order placer) sends requests for studies (orders) on tissue, cellular material or an autopsy on a non-living person to the pathology laboratory (order filler) by sending a Lab Order Message OML^O21 (Message Type OML, Trigger event O21). After receiving the request, the pathology laboratory can reply by sending a Lab Order Response ORL^O22 (asynchronous). The pathology laboratory can send the study result using an Unsolicited Laboratory Observation Message ORU^R01. In order to confirm the receipt of the study results, the order placer then sends an acknowledgement message (ACK^R01) (synchronous). In the following chapters the composition of the mentioned messages will be further elaborated as well as the segments that are used in this document. Note: The Lab Order Message OML^O21 is a new message since version 2.4 and replaces the old ORM message. It is merely the same as the OMG message with some extensions. August 22, 2013 Order and result messages for pathology information systems 7

8 H-3 Order to the pathology laboratory In order to support the requests for study of tissue, cellular material or executing an autopsy on a non-living person that are sent to the pathology laboratory, U-DPS supports a system for electronic ordering. This system is using the HL7 protocol. From now on in this document the U-DPS system is mentioned when referring to the system that receives the order (order filler), where this can also be another information system at the pathology department Process The order placer, e.g. an HIS, sends an order and U-DPS confirms receiving the order by sending a return message. The laboratory can already inform the order placer about the study report number and the sample number in this return message. However, in this stage informing the order placer about these numbers is optional. The study is executed at the pathology laboratory, and after that, when closing it, the order placer is informed about the study results and the order number. Placing the order is done by an authorized healthcare provider (HCP) and has to be interpreted as an official order to perform a study. The code and name of the requesting HCP are used in the pathology study report. Also, the order message is a source for patient information concerning his name and address, a description of the material type and clinical information, that is available in the study result report. Use of the BSN in digital communication in healthcare is compulsory. For this reason, using the 2.4 version of this protocol is a necessity Specification of message compostion (segments) The Lab Order Message OML^O21 uses the following HL7 v2.4 segments: Segment MSH PID PV1 { } ORC [ ] OBR Description Message header Patient identification Patient visit Order communication Observation Request [ { SAC } ] Specimen Container Details [ { OBX } ] Observation/Result (Legend: Abstract Message Syntax, [ ] optional, { } one or more recurrences) August 22, 2013 Order and result messages for pathology information systems 8

9 3.3. MSH segment Table 1: HL7 Attribute Table - MSH - Message Header SEQ LEN DT OPT RP/# TBL# ITEM # ELEMENT NAME U-DPS 1 1 ST R Field Separator 2 4 ST R Encoding Characters ^~& HD O Sending Application Contents agreed on by all parties concerned HD O Sending Facility Contents agreed on by all parties concerned HD O Receiving Application Contents agreed on by all parties concerned HD O Receiving Facility Contents agreed on by all parties concerned 7 26 TS R Date/Time Of Message Format: YYYYMMDDhhmmss 8 40 ST O Security 9 13 CM R 0076/ Message Type OML^O21 note MSH ST R Message Control ID 11 3 PT R Processing ID P VID R Version ID NM O Sequence Number ST O Continuation Pointer 15 2 ID O Accept Acknowledgment Type 16 2 ID O Application Acknowledgment Type 17 3 ID O Country Code ID O Y Character Set CE O Principal Language Of Message ID O Alternate Character Set Handling Scheme ID O Y Conformance Statement ID Note MSH9: Element 9 in the MSH segment (Message type), in short MSH-9, has the following value: OML^O21. In the response message Lab Order Response ORL^O22 (see chapter H-5 in this document) the value is: ORL^O22. And so on PID segment Table 2: HL7 Attribute Table PID Patient identification SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME U-DPS 1 4 SI O Set ID - PID 2 20 CX B Patient ID August 22, 2013 Order and result messages for pathology information systems 9

10 3 250 CX R Y Patient Identifier List Patient number note PID CX B Y Alternate Patient ID - PID XPN R Y Patient Name Patient name note PID XPN O Y Mother s Maiden Name 7 26 TS O Date/Time of Birth Date of birth 8 1 IS O Administrative Sex Gender XPN B Y Patient Alias CE O Y Race XAD O Y Patient Address Patient address information note PID IS B County Code XTN O Y Phone Number - Home XTN O Y Phone Number - Business CE O Primary Language CE O Marital Status CE O Religion CX O Patient Account Number ST B SSN Number - Patient DLN O Driver's License Number - Patient CX O Y Mother's Identifier CE O Y Ethnic Group ST O Birth Place 24 1 ID O Multiple Birth Indicator 25 2 NM O Birth Order CE O Y Citizenship CE O Veterans Military Status CE B Nationality TS O Patient Death Date and Time 30 1 ID O Patient Death Indicator 31 1 ID O Identity Unknown Indicator IS O Y Identity Reliability Code TS O Last Update Date/Time HD O Last Update Facility CE C Species Code CE C Breed Code ST O Strain CE O Production Class Code Note PID3: Patient identifier list (PID-3) Only the ADT message HL7 v2.4 has the possibility to include the BSN, in a recurring PID-03 (sub-)segment, e.g.: August 22, 2013 Order and result messages for pathology information systems 10

11 PID ^^^LOCAL^PI ~ ^^^NLMINBIZA^NNNLD Onwel^Jolanda... The first sub sub segment is the local patient number, the second is the BSN. Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ < assigning authority (HD)> ^ <identifier type code (ID)> ^ < assigning facility (HD) ^ <effective date (DT)> ^ <expiration date (DT)> Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)> Examples BSN ^^^NLMINBIZA^NNNLD^^ Official identity document (passport/identity card) AA ^^^NLMINBIZA^PPN^^ Driver s license ^^^NLRDW^DL^^ Immigration document ^^^NLIND^CZ^^ When using the BSN and the official identity document, stating the date of verification can be necessary. The effective date component can be used to do so. Attention: The formal meaning of effective date is the starting date of the identifier, meaning that from that moment on the identifier is valid. In this case the component effective date is given a different meaning. Table 3: User-defined Table Assigning Authority Code Description Dutch application NLMINBIZA NLMINJUS NLVWS NLIND NLRDW CIBG Prismant Vektis NL Ministerie van Binnenlandse Zaken (Ministry of Internal Affairs) NL Ministerie van Justitie (Ministry of Justice) NL Ministerie van Volksgezondheid, Welzijn en Sport (Ministry of Health, Wellbeing and Sports) NL Immigratie en Naturalisatie Dienst (Immigration Services) NL Rijksdienst voor het Wegverkeer (National road traffic service) NL Centraal Informatiepunt Beroepen Gezondheidszorg (Dutch Central Information office for Healthcare professions) NL Onder andere voor de Landelijke Medische Registratie (LMR) (a.o. for national medical registration) NL Centrum voor informatie en standaardisatie voor de zorgverzekeraars Burgerservicenummer (BSN) Reisdocument (paspoort/identiteitskaart) (BSN, passport/official identity document) Vreemdelingendocument (Immigration document) Rijbewijs (Driver s license) Zorgverlener Identificatienummer UZI (Unique Healthcare Provider Identification number) August 22, 2013 Order and result messages for pathology information systems 11

12 LOCAL <AGB code> (Centre for information and standardization for healthcare insurance companies) Lokaal gedefinieerd (Locally defined) AGB code van de instelling die het patiëntnummer heeft uitgereikt (AGB code of the organization that issued the patient number) Compulsory in case of exchange of healthcare information across institution borders Table 4: HL7 Table Identifier type Code Description Dutch application AM American Express AN Account number DBC identification number BA Bank Account Number To be used for a giro or bank account number. The concerned bank has to be mentioned in the field Assigning Authority. Attention: this was BANK and GIRO in IG 2.3. BR BRN Birth registry number Breed Registry Number CZ Citizenship Card Immigration document as meant by the Dutch identification law WID (Wet op de identificatieplicht) DI Diner s Club card DL Driver s license number e.g. concerning the Dutch identification law WID ( Wet op de identificatieplicht ) DN Doctor number DR Donor Registration Number The Dutch Donorregistratienummer is meant. DS EI EN FI GI GN Discover Card Employee number Employer number Facility ID Guarantor internal identifier Guarantor external identifier HC Health Card Number The Dutch Zorgpasnummer is meant. JHN LN LR MA MC MCN Jurisdictional health number (Canada) License number Local Registry ID Medicaid number Medicare number Microchip Number MR Medical record number Dutch Medisch dossiernummer is meant MS NE NH NI MasterCard National employer identifier National Health Plan Identifier National unique individual identifier NNNLD National Person Identifier where the xxx is the ISO table character (alphabetic) country code NNNLD BSN August 22, 2013 Order and result messages for pathology information systems 12

13 NPI National provider identifier The Dutch UZI number PEN Pension Number PI Patient internal identifier Patient number within the organization PN Person number PPN Passport number Passport number, but also in general an official identity document (e.g. in accordance with the Dutch identification law WID: Wet op de identificatieplicht PRN Provider number PT Patient external identifier To be used for e.g. regional patient number, or the patient number in another healthcare institution. RR RRI SL SR SS U UPIN VN VS WC WCN XX Railroad Retirement number Regional registry ID State license State registry ID Social Security number Unspecified Medicare/HCFA s Universal Physician Identification numbers Visit number VISA WIC identifier Workers Comp Number Organization identifier Note PID5: Components: In Version 2.3, replaces the PN data type. <family name (FN)> ^ <given name (ST)> ^ <second and further given names or initials thereof (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (IS)> ^ <name type code (ID) > ^ <name representation code (ID)> ^ <name context (CE)> ^ <name validity range (DR)> ^ <name assembly order (ID)> U-DPS: < second and further given names or initials thereof> contains the Dutch voorletters (initials) Subcomponents of family name: <surname (ST)> & <own surname prefix (ST)> & <own surname (ST)> & <surname prefix from partner/spouse (ST)> & <surname from partner/spouse (ST)> U-DPS: naamvrouw = <own surname> naamman (echtgenoot van) = <surname from partner/spouse> In HL7 version 2.3 the field PID-9 Patient alias was still used to communicate several different parts of the name. In this version however, the datatype XPN is extensive enough to communicate all parts of the Legal name. Note PID11: Components: In Version 2.3 and later, replaces the AD data type. <street August 22, 2013 Order and result messages for pathology information systems 13

14 address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code (ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)> ^ <county/parish code (IS)> ^ <census tract (IS)> ^ <address representation code (ID)> ^ <address validity range (DR)> Subcomponents of street address: <street address (ST)> & <street name (ST)> & <dwelling number (ST)> This field contains all the patient s addresses. The first address in this field has to be the address that is used to correspond with the patient. The field is filled as specified in Table 5. U-DPS does not use all the data in this element. Table 5: HL7 Adress Type componenten en sub-componenten Component Sub component Usage in The Netherlands Street address As of version 2.4 street address is a complex datatype. Different parts of the address can be filled in into the various sub components. Street address Street name Dwelling number Street name and dwelling number should be in this field as a composition, for reasons of backwards compatibility. Straatnaam Huisnummer, some implementations are known where dwelling number and street name are combined in the field Street name. Other designation City State Zip or postal code Country Address type Other geographic designation County/parish code Census tract Address representation code Address validity range Huisnummertoevoeging, additional information to specify the precise dwelling. Woonplaats N.A. Postcode, in case of a Dutch postal code no spaces should be entered: e.g. 2316XA Country in which the specified address is. The first address should have the value M (mailing). Other addresses can be specified, e.g. home address ( H ), or temporary address or residence ( C ). N.A. N.A. N.A. N.A. Starting date and end date of validity of the address can be specified using this field. This could be of use for temporary addresses. Date range start date/time Date range end date/time Starting date of validity of the address Last moment in time when the address is still valid (valid up to and including). Examples: PID ^^^^PI~ ^^^^NNNLD Reubsaet- Geurts&""&Geurts&""&Reubsaet^A^^^^^L F Aelserhof 1^^Elsloo Lb^^6181 LB^NL P N "" N PID ^^^^PI~ ^^^^NNNLD Broek van der Gruiter de&de&gruiter&van der&broek^l.^^^^^l V Postweg August 22, 2013 Order and result messages for pathology information systems 14

15 14&Postweg&14^^Tilburg^^5000KL^^M^^^^^ & ~Logeerstraat 34&Logeerstraat&34^^Best^^7800YY^^C^^^^^ & N 3.5. PV1 segment Table 6: HL7 Attribute Table - PV1 Patient visit SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME U-DPS 1 4 SI O Set ID - PV1 2 1 IS R Patient Class Indication meaning inpatient or outpatient values: see Table PL O Assigned Patient Location Department 4 2 IS O Admission Type CX O Preadmit Number 6 80 PL O Prior Patient Location XCN O Y Attending Doctor XCN O Y Referring Doctor XCN B Y Consulting Doctor 10 3 IS O Hospital Service PL O Temporary Location 12 2 IS O Preadmit Test Indicator 13 2 IS O Re-admission Indicator 14 6 CWE O Admit Source 15 2 IS O Y Ambulatory Status 16 2 IS O VIP Indicator XCN O Y Admitting Doctor 18 2 IS O Patient Type CX O Visit Number Case of illness, in case this is used by the HIS (SAP) FC O Y Financial Class Financial Class 21 2 IS O Charge Price Indicator Charge Price Indicator 22 2 IS O Courtesy Code Courtesy Code 23 2 IS O Credit Rating Credit Rating 24 2 IS O Y Contract Code Contract Code 25 8 DT O Y Contract Effective Date Contract Effective Date NM O Y Contract Amount Contract Amount 27 3 NM O Y Contract Period Contract Period 28 2 IS O Interest Code Interest Code 29 1 IS O Transfer to Bad Debt Code 30 8 DT O Transfer to Bad Debt Date Transfer to Bad Debt Code Transfer to Bad Debt Date IS O Bad Debt Agency Code Bad Debt Agency Code NM O Bad Debt Transfer Amount NM O Bad Debt Recovery Amount Bad Debt Transfer Amount Bad Debt Recovery Amount August 22, 2013 Order and result messages for pathology information systems 15

16 34 1 IS O Delete Account Indicator Delete Account Indicator 35 8 DT O Delete Account Date Delete Account Date 36 3 IS O Discharge Disposition Discharge Disposition CM O Discharged to Location Discharged to Location CE O Diet Type Diet Type 39 2 IS O Servicing Facility Servicing Facility 40 1 IS B Bed Status Bed Status 41 2 IS O Account Status Account Status PL O Pending Location Pending Location PL O Prior Temporary Location Prior Temporary Location TS O Admit Date/Time Admit Date/Time TS O Y Discharge Date/Time Discharge Date/Time NM O Current Patient Balance Current Patient Balance NM O Total Charges Total Charges NM O Total Adjustments Total Adjustments NM O Total Payments Total Payments CX O Alternate Visit ID Alternate Visit ID 51 1 IS O Visit Indicator Visit Indicator XCN B Y Other Healthcare Provider Other Healthcare Provider Table 7: possible values for PV1-2 Code Beschrijving I O P K D B klinisch (inpatient) Poliklinisch (outpatient) Preadmit (Preadmit) MedKeuring (medical test) Dag (day) PolBev (Obstetrics) 3.6. ORC segment Table 8: HL7 Attribute Table ORC Common Order SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME U-DPS 1 2 ID R N Order Control Order status note ORC EI C Placer Order Number Placer order number, delivered by the sending system 3 22 EI C Filler Order Number Filler order number, PA number note ORC EI O Placer Group Number August 22, 2013 Order and result messages for pathology information systems 16

17 5 2 ID O N Order Status 6 1 ID O Response Flag TQ O Y Quantity/Timing Used to specify the priority note ORC CM O Parent 9 26 TS O Date/Time of Transaction Date/time when the order is registered in the ordering system. note ORC XCN O Y Entered By XCN O Y Verified By XCN O Y Ordering Provider Ordering Provider (coded) note ORC PL O Enterer s Location Location (coded) note ORC XTN O Y/ Call Back Phone Number TS O Order Effective Date/Time CE O Order Control Code Reason CE O Entering Organization CE O Entering Device XCN O Y Action By CE O Advanced Beneficiary Notice Code XON O Y Ordering Facility Name XAD O Y Ordering Facility Address XTN O Y Ordering Facility Phone Number XAD O Y Ordering Provider Address CWE O N Order Status Modifier Note ORC1: Of all available codes that can be delivered using this element, U-DPS uses the codes: NW, CA and CR. Table 9: possible values for ORC-1 Code Description NW CA or CR nieuwe order (new order) verwijderen order (cancel order) Cancelling the order can currently only be indicated if the order has not yet been incorporated into a report. August 22, 2013 Order and result messages for pathology information systems 17

18 Note ORC3: The filler order number ( rapportnummer ) will be the unique laboratory order number indicating the registered study. The used format is: <type of study><year> <serial number> type of study can contain: B, C, S, T or M. Year: only the last two digits of the year in which the material is received. Serial number: a pathology/anatomy (PA) number (unique for each laboratory) and possibly a version indicator: A, B, C, D... Examples: T Histologie C Cytologie S Obductie B Cervixcytologie This study report number is only issued when the received order is being processed. This can be at the moment of confirming the order (when processing the order starts), or later, when the report after performing the study is finished. Note ORC7: ORC-7 sub field 6 can contain a character that may cause the priority of the study to be risen. In other words: should the study be performed in emergency, or should it not. U-DPS reacts on the character S. Caused by this S, the field soortaanvraag (kind of order) will contain the value spoed (emergency). All other values lead to a normal priority: normaal. The information is also part of the OBR-27 sub field 6. Note ORC9: Date-time on which the order is entered into the ordering system of the ordering application. Should this field be empty, then the date of de MSH segment can be used as a source. Note ORC12: The ordering provider number that is delivered by the HIS, is converted into an order placer code in U-DPS. When a result is issued, the ordering provider number as known in the HIS will be provided by U-DPS. Note ORC13: In case registering a location code is a necessity, the code will be incorporated into the U-DPS report OBR segment Table 10: HL7 Attribute Table OBR Observation Request SEQ LEN DT OPT RP/# TBL# ITEM # ELEMENT NAME U-DPS 1 4 SI O Set ID - OBR 2 22 EI C Placer Order Number Placer order number, delivered by the sending August 22, 2013 Order and result messages for pathology information systems 18

19 system 3 22 EI C Filler Order Number + Filler order number, PA number CE R Universal Service ID Type of study note OBR4 5 2 ID B Priority - OBR 6 26 TS B Requested Date/Time 7 26 TS C Observation Date/Time # 8 26 TS O Observation End Date/Time # 9 20 CQ O Collection Volume * XCN O Y Collector Identifier * 11 1 ID O Specimen Action Code * CE O Danger Code ST O Relevant Clinical Info TS C Specimen Received Date/Time * CM O Specimen Source * XCN O Y Ordering Provider See ORC segment XTN O Y/ Order Callback Phone Number ST O Placer Field ST O Placer Field ST O Filler Field ST O Filler Field TS C Results Rpt/Status Chng - Date/Time CM O Charge to Practice ID O Diagnostic Serv Sect ID Hospital/institution optional: location of requestor (coded) 25 1 ID C Result Status CM O Parent Result TQ O Y Quantity/Timing XCN O Y/ Result Copies To Receivers of copies of the result report CM O Parent ID O Transportation Mode (code and name to be filled in) CE O Y Reason for Study note OBR CM O Principal Result Interpreter CM O Y Assistant Result Interpreter CM O Y Technician CM O Y Transcriptionist TS O Scheduled Date/Time + August 22, 2013 Order and result messages for pathology information systems 19

20 37 4 NM O Number of Sample Containers * CE O Y Transport Logistics of Collected Sample * CE O Y Collector s Comment * CE O Transport Arrangement Responsibility ID O Transport Arranged 42 1 ID O Escort Required CE O Y Planned Patient Transport Comment CE O Procedure Code CE O Y Procedure Code Modifier CE O Y Placer Supplemental Service Information CE O Y Filler Supplemental Service Information Note OBR4: The sending system can use this field for terms like one of the following: Histologie (Histology) Cytologie (Cytology) Obductie (Autopsy) Cervixcytologie (Cervixcytology) In practice, the pathology department will often decide by itself on the study to be performed. Note OBR31: The reason for study (request) can be specified here. This is optional. For now only one of the following values is permitted: 3.8. SAC segment BVO-DDK (bowel cancer screening) BVO-DDK-NOTP (bowel cancer screening, only for study, it is not permitted to redistribute the information to third parties, e.g. ColonIS) SAC segment specification see paragraph OBX segment Table 11: HL7 Attribute Table OBX Observation SEQ LEN DT OPT RP/# TBL# ITEM# ELEMENT NAME U-DPS 1 4 SI O Set ID - OBX Serial number of the OBX segment 2 2 ID C Value Type FT CE R Observation Identifier note OBX ST C Observation Sub-ID August 22, 2013 Order and result messages for pathology information systems 20