ORL - General laboratory order response message to any OML ER7 Note that the overriding of IHE LaboratoryProfile constraints is only allowed innational extensions to this framework 2.15.9.1 2.15.9.2 2.15.9.7 Retained for backward compatibility only 2.15.9.8 Its content is defined within eachtransaction-specific section of thisdocument 2.15.9.9 This field contains a number or otheridentifier that uniquely identifies themessage. Each message shouldbe given a unique identifier by thesending system. The receiving systemwill echo this ID back to the endingsystem in the Message Acknowledgmentsegment(MSA). 2.15.8.2 2.15.9.11 2.15.9.12 2.15.9.13 2.15.4.1 IHE uses only the HL7 originalacknowledgement mode. 2.15.9.15 IHE uses only the HL7 originalacknowledgement mode. 2.15.9.16 2.15.9.17 ASCII: The printable 7-bit ASCII characterset.8859/1: The printable characters from theISO 8859/1 Character set used byWestern Europe. This character set canstill be used, but 8859/15 should be usedby preference. This character set is theforward-compatible version of 8859/1and includes new characters such astheEuro currency symbol.ISO IR87: Code for the Japanese GraphicCharacter set for information interchange(JIS X 0208-1990). 2.15.9.18 2.15.9.19 2.15.9.20 Note that the overriding of IHE LaboratoryProfile constraints is only allowed innational extensions to this framework 2.15.9.21 The IHE Laboratory Technical Frameworkauthorizes only one of the three valuesbelow, taken from HL7 table 0008 2.15.8.1 This field contains the message control IDfrom the MSH-10 - Message Control ID ofthe incoming message for which theacknowledgement is sent 2.15.8.2 2.15.8.3 2.15.8.4 2.15.8.5 2.15.8.6 2.15.5.1 2.15.5.2 2.15.5.3 2.15.5.4 2.15.5.5 2.15.5.6 2.15.5.7 2.15.5.8 2.15.5.9 2.15.5.10 2.15.5.11 2.15.5.12 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 2.15.12.1 2.15.12.2 2.15.12.3 2.15.12.4 2.15.12.5 2.15.12.6 Retained for backward compatibility only 2.15.10.1 2.15.10.2 This field contains the text of thecomment. This text may be formatted. Inorder to delete an existing comment, thefield shall contain empty quotation marks:"" .Comment text of identical type andsourceshall be included in the same occurrenceof an NTE segment, and not be split overmultiple segments. 2.15.10.3 The IHE Laboratory Technical Frameworkpopulates this field with one of the valuesin table IHE0364 2.15.10.4 The specific usage of the fields,withusage " Optional" in the tablePID, is explained in the nationalextensions. 3.4.2.1 3.4.2.2 * 3.4.2.3 3.4.2.4 3.4.2.5 Retained for backward compatibility only Retained for backward compatibility only 3.4.2.6 Retained for backward compatibility only Retained for backward compatibility only If the exact date of birth is not known, thesecond component of this field can beused to describe the degree of precisionof the information entered in the firstcomponent. 3.4.2.7 Retained for backward compatibility only 3.4.2.8 3.4.2.9 Retained for backward compatibility only Retained for backward compatibility only 3.4.2.10 3.4.2.11 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 3.4.2.12 3.4.2.13 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 3.4.2.14 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 3.4.2.15 3.4.2.16 3.4.2.17 the Patient Account Number is not used insome countries: in the US, it must bevalued and the PV1-19 visit number isrequired when PID-18 identifies anaccount that spans more than oneEncounter or Visit. In France, PID-18 maybe used when a patient may havemultiplevisits (each visit having independenttransfer and discharge) but where all thevisit need to be linked under onecase/episode number. 3.4.2.18 3.4.2.19 3.4.2.20 3.4.2.21 3.4.2.22 3.4.2.23 3.4.2.24 3.4.2.25 3.4.2.26 3.4.2.27 3.4.2.28 3.4.2.29 Retained for backward compatibility only 3.4.2.30 3.4.2.31 3.4.2.32 3.4.2.33 Retained for backward compatibility only 3.4.2.35 3.4.2.36 3.4.2.37 3.4.2.38 3.4.2.39 This field may be considered the "triggerevent" identifier for orders. Many ordercontrol codes are defined in the HL7 table0119 - Order Control Codes. The IHELaboratory Technical Framework allowsonly a subset of it This field may be considered the "triggerevent" identifier for orders. Many ordercontrol codes are defined in the HL7 table0119 - Order Control Codes. The IHELaboratory Technical Framework allowsonly a subset of it 4.5.1.1 4.5.1.2 4.5.1.3 required if known to the sender. ThePlacer Group Number represents anidentification of a set of closely relatedorders, i.e. the whole list of batteriesordered by the placer to the laboratoryfor one subject. 4.5.1.4 4.5.1.5 4.5.1.6 4.5.1.7 2.16.50 2.16.67 2.16.78 2.16.82 Retained for backward compatibility only 2.16.82 Retained for backward compatibility only 2.16.78 2.16.78 2.16.83 2.16.38 2.16.50 4.5.1.8 This field contains the date and time ofthe event that initiated the currenttransaction as reflected in ORC-1 OrderControl Code. This field is not equivalentto MSH-7 Date and Time of Message thatreflects the date/time of the creation ofthe physical message.In OML messages "Status changed" sentby the Order Filler, this field contains thedate/time of the last status change of theorder (ORC-5) or one of the orderedbatteries (identified in the following OBR). 4.5.1.9 Retained for backward compatibility only 4.5.1.10 Retained for backward compatibility only Retained for backward compatibility only 4.5.1.11 Retained for backward compatibility only Retained for backward compatibility only This field contains the person (physician)who prescribed the order. See the datamodel in volume 1. 4.5.1.12 Retained for backward compatibility only Retained for backward compatibility only 4.5.1.13 If the field is valued then its value has tomatch the value of the required fieldOBR-17. 4.5.1.14 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 4.5.1.15 Retained for backward compatibility only 4.5.1.16 4.5.1.17 4.5.1.18 4.5.1.19 Retained for backward compatibility only Retained for backward compatibility only 4.5.1.20 This field contains the facility (care unit)placing this order. See the data model involume 1. 4.5.1.21 4.5.1.22 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 4.5.1.23 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 4.5.1.24 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 4.5.1.25 4.5.1.26 This field contains the date/time when thelaboratory results are expected to beavailable. 4.5.1.27 Retained for backward compatibility only 4.5.1.28 4.5.1.29 4.5.1.30 This cycle of IHE Laboratory TechnicalFramework uses doesn't use TQ2segment, and uses only one occurrenceof TQ1 segment, with a single fieldrequired in it : TQ1-9 Priority (CWE). 4.5.4.1 4.5.4.2 2.16.50 4.5.4.3 2.16.16 2.16.38 2.16.50 2.16.50 2.16.50 Constrained to units of time. The codes for unit ofmeasure are specified in the Unified Code for Units ofMeasure (UCUM) [http://aurora.rg.iupui.edu/UCUM]. 2.16.39 2.16.38 2.16.38 2.16.50 Constrained to units of time. The codes for unit ofmeasure are specified in the Unified Code for Units ofMeasure (UCUM) [http://aurora.rg.iupui.edu/UCUM]. 4.5.4.4 4.5.4.5 2.16.50 4.5.4.6 2.16.50 4.5.4.7 Retained for backward compatibility only 4.5.4.8 Retained for backward compatibility only Transactions T1, T2 and T3 restrict theusage to the 6 values: S, A, R, P, C, T oftable 0485 4.5.4.9 4.5.4.10 4.5.4.11 4.5.4.12 4.5.4.13 2.16.50 4.5.4.14 4.5.5.1 4.5.5.2 4.5.5.3 4.5.5.4 4.5.5.5 4.5.5.6 4.5.5.7 4.5.5.8 2.16.50 4.5.5.9 4.5.5.10 4.5.3.1 4.5.1.2 4.5.1.3 4.5.3.4 4.5.3.5 4.5.3.6 Retained for backward compatibility only 4.5.3.7 Retained for backward compatibility only 4.5.3.8 Retained for backward compatibility only 4.5.3.9 2.16.50 4.5.3.10 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.11 4.5.3.12 4.5.3.13 4.5.3.14 Retained for backward compatibility only 4.5.3.15 4.5.1.12 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.17 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 4.5.3.18 4.5.3.19 4.5.3.20 4.5.3.21 4.5.3.22 Retained for backward compatibility only 4.5.3.23 Using ISO 4.5.3.24 4.5.3.25 4.5.3.26 4.5.1.7 2.16.50 2.16.67 2.16.78 2.16.82 Retained for backward compatibility only 2.16.82 Retained for backward compatibility only 2.16.78 2.16.78 2.16.83 2.16.38 2.16.50 4.5.3.28 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.29 4.5.3.30 4.5.3.31 4.5.3.32 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.33 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.34 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.35 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.36 Retained for backward compatibility only 4.5.3.37 4.5.3.38 4.5.3.39 4.5.3.40 4.5.3.41 4.5.3.42 4.5.3.43 4.5.3.44 4.5.3.45 4.5.3.46 4.5.3.47 4.5.3.48 4.5.3.49 The date and time when the specimenwas acquired from the source. The useof the Date Range data type allows fordescription of specimens collected over aperiod of time, for example, 24-hour urinecollection. For specimens collected at apoint in time, only the first component(start date/time) will be populated 7.4.3.1 7.4.3.2 This version of the IHE of LaboratoryTechnical Framework doesn't admitpooling of specimens, therefore themaximum cardinality for the parentspecimen is 1. See the data model involume 1 of this document. 7.4.3.3 7.4.3.4 7.4.3.5 7.4.3.6 7.4.3.7 7.4.3.8 7.4.3.9 7.4.3.10 7.4.3.11 7.4.3.12 2.16.50 7.4.3.13 7.4.3.14 7.4.3.15 This field must be populated if known inOML messages sent by the Order Placer,within transaction T1, and OMLmessages sent by the Order Filler withintransactions T2 and T4 7.4.3.16 The date and time when the specimenwas acquired from the source. The useof the Date Range data type allows fordescription of specimens collected over aperiod of time, for example, 24-hour urinecollection. For specimens collected at apoint in time, only the first component(start date/time) will be populated 7.4.3.17 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.14 Retained for backward compatibility only 7.4.3.19 Retained for backward compatibility only This field is pointless in messages sentby the Order Placer. 7.4.3.20 7.4.3.21 7.4.3.22 7.4.3.23 7.4.3.24 7.4.3.25 2.16.50 For sample receipt verification purposes;may be different from the total number ofspecimens that accompany the order. 7.4.3.26 7.4.3.27 7.4.3.28 7.4.3.29 13.4.3.1 4.5.6.1 13.4.3.3 13.4.3.4 13.4.3.5 4.5.3.15 13.4.3.7 Retained for backward compatibility only 13.4.3.8 13.4.3.9 13.4.3.10 13.4.3.11 13.4.3.12 13.4.3.13 13.4.3.14 13.4.3.15 13.4.3.16 13.4.3.17 13.4.3.18 13.4.3.19 13.4.3.20 8.8.11.4 13.4.3.22 13.4.3.23 13.4.3.24 13.4.3.25 13.4.3.26 8.8.11.7 13.4.3.28 13.4.3.29 13.4.3.30 13.4.3.31 13.4.3.32 13.4.3.33 13.4.3.34 13.4.3.35 13.4.3.36 13.4.3.37 13.4.3.38 13.4.3.39 13.4.3.40 13.4.3.41 13.4.3.42 13.4.3.43 13.4.3.44