This is a battery centric structure... "A system that generates .... " 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 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 3.4.5.17 3.4.5.21 3.4.10.3 3.4.10.4 Retained for backward compatibility only Retained for backward compatibility only 3.4.5.24 3.4.5.36 3.4.4.43 3.4.4.44 3.4.10.9 3.4.10.10 3.4.5.22 3.4.5.23 3.4.10.13 3.4.10.14 3.4.10.15 3.4.10.16 3.4.10.17 3.4.10.18 3.4.10.19 3.4.10.20 3.4.10.21 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 3.4.5.1 3.4.5.2 Retained for backward compatibility only Retained for backward compatibility only 3.4.5.3 3.4.5.4 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 3.4.5.5 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 3.4.5.6 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 3.4.5.7 3.4.5.8 3.4.5.9 3.4.5.10 3.4.5.11 3.4.5.12 3.4.5.13 3.4.2.16 3.4.2.8 3.4.2.7 Retained for backward compatibility only 3.4.5.17 3.4.3.15 3.4.2.26 3.4.2.15 3.4.5.21 3.4.5.22 3.4.5.23 3.4.5.24 3.4.2.17 3.4.2.6 Retained for backward compatibility only Retained for backward compatibility only 3.4.2.28 3.4.2.22 3.4.5.29 3.4.5.30 Retained for backward compatibility only Retained for backward compatibility only 3.4.5.31 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 3.4.5.32 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 3.4.5.33 3.4.5.34 3.4.2.10 3.4.5.36 3.4.5.37 3.4.5.38 3.4.3.16 3.4.3.1 3.4.3.2 3.4.3.3 3.4.3.4 3.4.3.5 3.4.3.6 3.4.3.7 Retained for backward compatibility only Retained for backward compatibility only 3.4.3.8 Retained for backward compatibility only Retained for backward compatibility only 3.4.3.9 Retained for backward compatibility only Retained for backward compatibility only 3.4.3.10 3.4.3.11 3.4.3.12 3.4.3.13 3.4.3.14 3.4.3.15 3.4.3.16 3.4.3.17 Retained for backward compatibility only Retained for backward compatibility only 3.4.3.18 3.4.3.19 3.4.3.20 Retained for backward compatibility only 3.4.3.21 3.4.3.22 3.4.3.23 3.4.3.24 3.4.3.25 3.4.3.26 3.4.3.27 3.4.3.28 3.4.3.29 3.4.3.30 3.4.3.31 3.4.3.32 3.4.3.33 3.4.3.34 3.4.3.35 3.4.3.36 3.4.3.37 Retained for backward compatibility only 3.4.3.38 3.4.3.39 3.4.3.40 3.4.3.41 3.4.3.42 3.4.3.43 3.4.3.44 Retained for backward compatibility only 3.4.3.45 Retained for backward compatibility only 3.4.3.46 3.4.3.47 3.4.3.48 3.4.3.49 3.4.3.50 3.4.3.51 3.4.3.52 Retained for backward compatibility only Retained for backward compatibility only 3.4.4.1 3.4.4.2 3.4.4.3 3.4.4.4 3.4.4.5 3.4.4.6 3.4.4.7 3.4.4.8 Retained for backward compatibility only 3.4.4.9 Retained for backward compatibility only 3.4.4.10 3.4.4.11 3.4.4.12 3.4.4.13 Retained for backward compatibility only Retained for backward compatibility only 3.4.4.14 3.4.4.15 3.4.4.16 3.4.4.17 3.4.4.18 3.4.4.19 3.4.4.20 3.4.4.21 3.4.4.22 3.4.4.23 3.4.4.24 3.4.4.25 3.4.4.26 3.4.4.27 3.4.4.28 3.4.4.29 3.4.4.30 3.4.4.31 3.4.4.32 3.4.4.33 Retained for backward compatibility only 3.4.4.34 3.4.4.35 3.4.4.36 3.4.4.37 3.4.4.38 3.4.4.39 3.4.4.40 3.4.4.41 3.4.4.42 3.4.4.43 3.4.4.44 3.4.4.45 3.4.4.46 3.4.4.47 Retained for backward compatibility only 3.4.4.48 Retained for backward compatibility only 3.4.4.49 6.5.6.1 6.5.1.14 6.5.6.3 6.5.6.4 6.5.6.5 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 6.5.6.6 Retained for backward compatibility only Retained for backward compatibility only 6.5.6.7 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.6.8 6.5.6.9 6.5.6.10 6.5.6.11 6.5.6.12 6.5.6.13 6.5.6.14 6.5.6.15 6.5.6.16 Retained for backward compatibility only Retained for backward compatibility only 6.5.6.17 6.5.6.18 Retained for backward compatibility only 6.5.6.19 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 6.5.6.20 6.5.6.21 6.5.6.22 6.5.6.23 6.5.6.24 6.5.6.25 6.5.6.26 6.5.6.27 6.5.6.28 6.5.6.29 Retained for backward compatibility only 6.5.6.30 Retained for backward compatibility only Retained for backward compatibility only 6.5.6.31 6.5.6.32 6.5.6.33 6.5.6.34 6.5.6.35 6.5.6.36 6.5.6.37 Using ISO 6.5.6.38 Using ISO 6.5.6.39 6.5.6.40 Using ISO 6.5.6.41 Using ISO 6.5.6.42 6.5.6.43 6.5.6.44 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 6.5.6.45 6.5.6.46 6.5.6.47 3.4.5.36 6.5.6.49 6.5.6.50 6.5.6.51 6.5.6.52 6.5.6.53 6.5.7.1 6.5.7.2 6.5.7.3 Retained for backward compatibility only Retained for backward compatibility only 6.5.7.4 6.5.7.5 6.5.7.6 6.5.7.7 Retained for backward compatibility only Retained for backward compatibility only 6.5.7.8 6.5.7.9 Retained for backward compatibility only Retained for backward compatibility only 6.5.7.10 6.5.7.11 6.5.7.12 6.5.7.13 6.5.7.14 3.4.10.20 6.5.7.16 6.5.7.17 6.5.7.18 6.5.7.19 6.5.7.20 6.5.7.21 6.5.7.22 Retained for backward compatibility only Retained for backward compatibility only 6.5.7.23 6.5.7.24 6.5.7.25 6.5.7.26 6.5.7.27 6.5.7.28 2.16.39 2.16.39 2.16.50 2.16.46 6.5.7.29 6.5.7.30 Using ISO 3.4.5.17 3.4.3.15 3.4.2.26 3.4.2.15 3.4.5.21 3.4.5.22 3.4.5.23 3.4.5.24 3.4.2.17 3.4.2.6 Retained for backward compatibility only Retained for backward compatibility only 3.4.2.28 3.4.2.22 3.4.2.16 6.5.7.44 6.5.5.32 6.5.5.49 6.5.5.50 3.4.5.34 6.5.7.49 Retained for backward compatibility only Retained for backward compatibility only 6.5.7.50 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.7.51 6.5.7.52 Retained for backward compatibility only Retained for backward compatibility only 6.5.7.53 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.7.54 6.5.7.55 6.5.7.56 6.5.7.57 6.5.7.58 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.7.59 6.5.7.60 6.5.7.61 6.5.7.62 6.5.7.63 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.7.64 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.7.65 6.5.7.66 6.5.7.67 6.5.7.68 6.5.7.69 6.5.7.70 3.4.2.10 6.5.7.72 6.5.8.1 6.5.8.2 6.5.8.3 Retained for backward compatibility only Retained for backward compatibility only 6.5.8.4 6.5.8.5 6.5.8.6 Retained for backward compatibility only 6.5.8.7 Retained for backward compatibility only 6.5.8.8 Retained for backward compatibility only Retained for backward compatibility only 6.5.8.9 6.5.8.10 6.5.8.11 6.5.8.12 6.5.8.13 Retained for backward compatibility only 6.5.8.14 Retained for backward compatibility only Retained for backward compatibility only 6.5.8.15 6.5.8.16 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.8.17 6.5.8.18 6.5.8.19 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.8.20 Retained for backward compatibility only 6.5.8.21 6.5.8.22 6.5.8.23 6.5.8.24 6.5.8.25 Retained for backward compatibility only Retained for backward compatibility only 6.5.5.1 6.5.5.2 6.5.5.3 Retained for backward compatibility only Retained for backward compatibility only 6.5.5.4 Retained for backward compatibility only Retained for backward compatibility only 6.5.5.5 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 6.5.5.6 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.5.7 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.5.8 Retained for backward compatibility only 6.5.5.9 6.5.5.10 6.5.5.11 6.5.5.12 6.5.5.13 6.5.5.14 6.5.5.15 6.5.5.16 Retained for backward compatibility only Retained for backward compatibility only 6.5.5.17 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 6.5.5.18 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 6.5.5.19 6.5.5.20 6.5.5.21 6.5.5.22 6.5.5.23 6.5.5.24 Retained for backward compatibility only 6.5.5.25 6.5.5.26 6.5.5.27 Using ISO 6.5.5.28 6.5.5.29 6.5.5.30 6.5.5.31 6.5.5.32 3.4.5.17 3.4.3.15 3.4.2.26 3.4.2.15 3.4.5.21 3.4.5.22 3.4.5.23 3.4.5.24 3.4.2.17 3.4.2.6 Retained for backward compatibility only Retained for backward compatibility only 3.4.2.28 3.4.2.22 3.4.5.30 Retained for backward compatibility only Retained for backward compatibility only 3.4.5.31 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 3.4.5.29 6.5.5.48 6.5.5.49 6.5.5.50 6.5.5.51 3.4.5.36 3.4.5.34 6.5.5.54 Retained for backward compatibility only 6.5.5.55 6.5.5.56 3.4.3.16 3.4.6.1 3.4.6.2 3.4.6.3 3.4.6.4 3.4.6.5 3.4.6.6 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 4.5.1.31 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.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 4.5.3.50 4.5.3.4 13.4.10.2 13.4.10.3 13.4.10.4 13.4.9.7 13.4.9.10 13.4.10.7 13.4.10.8 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 3.4.5.7 11.6.4.2 Retained for backward compatibility only Retained for backward compatibility only 7.12.6.7 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only 11.6.4.4 11.6.4.5 Format: [NNN] [(999)]999-9999 [X99999] [B99999] [C anytext] 11.6.3.6 11.6.4.7 6.5.2.1 6.5.2.2 6.5.2.3 6.5.2.4 6.5.2.5 Retained for backward compatibility only 6.5.2.6 6.5.2.7 6.5.2.8 6.5.2.9 6.5.2.10 6.5.2.11 6.5.2.12 6.5.2.13 Using ISO 6.5.2.14 6.5.2.15 6.5.2.16 Retained for backward compatibility only Retained for backward compatibility only 6.5.2.17 6.5.2.18 6.5.2.19 Retained for backward compatibility only 6.5.2.20 6.5.2.21 Since the OBX-18 field should not beused; this OBX-19 field is pointless. This field contains the sequence numberof the OBX. 7.4.2.1 7.4.2.2 The usage of LOINC(r) test codes for theidentification of tests is stronglyrecommended. Details of this freevocabulary can be found athttp://www.loinc.org 7.4.2.3 7.4.2.4 7.4.2.5 7.4.2.6 required if available. This field should bevalued as described in HL7 V2.5 for allobservations for which it is relevant. TheReferences range that figures in this fieldis supposed to be related to age and sexof the patient or to other parameters suchas number of weeks of pregnancy whenapplicable, which makes the OBX-10 field(nature of abnormal test) unnecessary. 7.4.2.7 required if available.This field is required when applicable.Among the possible values listed for thisfield in HL7 table 0078, the actors of IHELaboratory Technical Framework shouldsupport the values of table 0078As described in the above table, the S, R,or I values must be used to indicate theinterpreted result of susceptibilities inmicrobiology, in case the value field(OBX-5) contains a numeric value thatrepresents the MIC (Minimum InhibitiveConcentration). In case the order filleronly reports the interpreted result forsusceptibilities, the S, R, or I value couldbe filled in the value field (OBX-5) with aValue Type (OBX-2) set to "ST". 7.4.2.8 7.4.2.9 7.4.2.10 This field should be filled according toHL7 Table 0085 described in Chapter 7 ofHL7. In this version of the LaboratoryTechnical Version, the possible valuesfor this field are a subset of this table: 7.4.2.11 Since the Reference range given by theorder filler is the one that applies to theObservation result taking into accountsome other parameters like patient age orsex; there is not need to manage thepresent field. The Order Result Trackershould store the observation result andits associated reference range. In casethe Order Result Tracker offers thecapability to compare results of the sameobservation over different requests, itshould then associate each result with itsassociated reference range. 7.4.2.12 Retained for backward compatibility only 7.4.2.13 Required if availableThis field should be valued when theOBX-5 field (Value field) is also valued. Invery exceptional case this informationmay be unknown by the Order Filler(case the test is transmitted in areference lab and observation date andtime is not returned together with theresult), this field can be null and theOrderResult Tracker should not generate anerror. 7.4.2.14 Retained for backward compatibility only Required if available This field is required in case the observation was not produced by the sending organization 7.4.2.15 This field is required when the observation result status (OBX-11) is valued with "D" or "R" or "P" or "F" or "C" or "X" and the Producer's ID field is not valued. It should contain the identity of the observer that causes the change of the observation result status. Only the first component (ID number) of this field is necessary, provided that it is possible to retrieve the full identity of responsible person in the Order Filler system with this only ID number. 7.4.2.16 Retained for backward compatibility only Retained for backward compatibility only 7.4.2.17 Although this information should be available at the Order Filler level, this field should not be used in this first version of the Laboratory Technical Framework 7.4.2.18 Since the OBX-18 field should not be used; this OBX-19 field is pointless. 7.4.2.19 Retained for backward compatibility only Reserved for harmonization with V2.6 7.4.2.20 Reserved for harmonization with V2.6 7.4.2.21 Reserved for harmonization with V2.6 7.4.2.22 7.4.2.23 7.4.2.24 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only This field is required when the observation result status (OBX-11) is valued with "D" or "R" or "P" or "F" or "C" or "X" and the Producer's ID field is not valued. It should contain the identity of the observer that causes the change of the observation result status. Only the first component (ID number) of this field is necessary, provided that it is possible to retrieve the full identity of responsible person in the Order Filler system with this only ID number. 7.4.2.25 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.4 13.4.10.2 13.4.10.3 13.4.10.4 13.4.9.7 13.4.9.10 13.4.10.7 13.4.10.8 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 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 Since the OBX-18 field should not beused; this OBX-19 field is pointless. This field contains the sequence numberof the OBX. 7.4.2.1 7.4.2.2 The usage of LOINC(r) test codes for theidentification of tests is stronglyrecommended. Details of this freevocabulary can be found athttp://www.loinc.org 7.4.2.3 7.4.2.4 7.4.2.5 7.4.2.6 required if available. This field should bevalued as described in HL7 V2.5 for allobservations for which it is relevant. TheReferences range that figures in this fieldis supposed to be related to age and sexof the patient or to other parameters suchas number of weeks of pregnancy whenapplicable, which makes the OBX-10 field(nature of abnormal test) unnecessary. 7.4.2.7 required if available.This field is required when applicable.Among the possible values listed for thisfield in HL7 table 0078, the actors of IHELaboratory Technical Framework shouldsupport the values of table 0078As described in the above table, the S, R,or I values must be used to indicate theinterpreted result of susceptibilities inmicrobiology, in case the value field(OBX-5) contains a numeric value thatrepresents the MIC (Minimum InhibitiveConcentration). In case the order filleronly reports the interpreted result forsusceptibilities, the S, R, or I value couldbe filled in the value field (OBX-5) with aValue Type (OBX-2) set to "ST". 7.4.2.8 7.4.2.9 7.4.2.10 This field should be filled according toHL7 Table 0085 described in Chapter 7 ofHL7. In this version of the LaboratoryTechnical Version, the possible valuesfor this field are a subset of this table: 7.4.2.11 Since the Reference range given by theorder filler is the one that applies to theObservation result taking into accountsome other parameters like patient age orsex; there is not need to manage thepresent field. The Order Result Trackershould store the observation result andits associated reference range. In casethe Order Result Tracker offers thecapability to compare results of the sameobservation over different requests, itshould then associate each result with itsassociated reference range. 7.4.2.12 Retained for backward compatibility only 7.4.2.13 Required if availableThis field should be valued when theOBX-5 field (Value field) is also valued. Invery exceptional case this informationmay be unknown by the Order Filler(case the test is transmitted in areference lab and observation date andtime is not returned together with theresult), this field can be null and theOrderResult Tracker should not generate anerror. 7.4.2.14 Retained for backward compatibility only Required if available This field is required in case the observation was not produced by the sending organization 7.4.2.15 This field is required when the observation result status (OBX-11) is valued with "D" or "R" or "P" or "F" or "C" or "X" and the Producer's ID field is not valued. It should contain the identity of the observer that causes the change of the observation result status. Only the first component (ID number) of this field is necessary, provided that it is possible to retrieve the full identity of responsible person in the Order Filler system with this only ID number. 7.4.2.16 Retained for backward compatibility only Retained for backward compatibility only 7.4.2.17 Although this information should be available at the Order Filler level, this field should not be used in this first version of the Laboratory Technical Framework 7.4.2.18 Since the OBX-18 field should not be used; this OBX-19 field is pointless. 7.4.2.19 Retained for backward compatibility only Reserved for harmonization with V2.6 7.4.2.20 Reserved for harmonization with V2.6 7.4.2.21 Reserved for harmonization with V2.6 7.4.2.22 7.4.2.23 7.4.2.24 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only This field is required when the observation result status (OBX-11) is valued with "D" or "R" or "P" or "F" or "C" or "X" and the Producer's ID field is not valued. It should contain the identity of the observer that causes the change of the observation result status. Only the first component (ID number) of this field is necessary, provided that it is possible to retrieve the full identity of responsible person in the Order Filler system with this only ID number. 7.4.2.25 Retained for backward compatibility only Retained for backward compatibility only 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 Since the OBX-18 field should not beused; this OBX-19 field is pointless. This field contains the sequence numberof the OBX. 7.4.2.1 7.4.2.2 The usage of LOINC(r) test codes for theidentification of tests is stronglyrecommended. Details of this freevocabulary can be found athttp://www.loinc.org 7.4.2.3 7.4.2.4 7.4.2.5 7.4.2.6 required if available. This field should bevalued as described in HL7 V2.5 for allobservations for which it is relevant. TheReferences range that figures in this fieldis supposed to be related to age and sexof the patient or to other parameters suchas number of weeks of pregnancy whenapplicable, which makes the OBX-10 field(nature of abnormal test) unnecessary. 7.4.2.7 required if available.This field is required when applicable.Among the possible values listed for thisfield in HL7 table 0078, the actors of IHELaboratory Technical Framework shouldsupport the values of table 0078As described in the above table, the S, R,or I values must be used to indicate theinterpreted result of susceptibilities inmicrobiology, in case the value field(OBX-5) contains a numeric value thatrepresents the MIC (Minimum InhibitiveConcentration). In case the order filleronly reports the interpreted result forsusceptibilities, the S, R, or I value couldbe filled in the value field (OBX-5) with aValue Type (OBX-2) set to "ST". 7.4.2.8 7.4.2.9 7.4.2.10 This field should be filled according toHL7 Table 0085 described in Chapter 7 ofHL7. In this version of the LaboratoryTechnical Version, the possible valuesfor this field are a subset of this table: 7.4.2.11 Since the Reference range given by theorder filler is the one that applies to theObservation result taking into accountsome other parameters like patient age orsex; there is not need to manage thepresent field. The Order Result Trackershould store the observation result andits associated reference range. In casethe Order Result Tracker offers thecapability to compare results of the sameobservation over different requests, itshould then associate each result with itsassociated reference range. 7.4.2.12 Retained for backward compatibility only 7.4.2.13 Required if availableThis field should be valued when theOBX-5 field (Value field) is also valued. Invery exceptional case this informationmay be unknown by the Order Filler(case the test is transmitted in areference lab and observation date andtime is not returned together with theresult), this field can be null and theOrderResult Tracker should not generate anerror. 7.4.2.14 Retained for backward compatibility only Required if available This field is required in case the observation was not produced by the sending organization 7.4.2.15 This field is required when the observation result status (OBX-11) is valued with "D" or "R" or "P" or "F" or "C" or "X" and the Producer's ID field is not valued. It should contain the identity of the observer that causes the change of the observation result status. Only the first component (ID number) of this field is necessary, provided that it is possible to retrieve the full identity of responsible person in the Order Filler system with this only ID number. 7.4.2.16 Retained for backward compatibility only Retained for backward compatibility only 7.4.2.17 Although this information should be available at the Order Filler level, this field should not be used in this first version of the Laboratory Technical Framework 7.4.2.18 Since the OBX-18 field should not be used; this OBX-19 field is pointless. 7.4.2.19 Retained for backward compatibility only Reserved for harmonization with V2.6 7.4.2.20 Reserved for harmonization with V2.6 7.4.2.21 Reserved for harmonization with V2.6 7.4.2.22 7.4.2.23 7.4.2.24 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only This field is required when the observation result status (OBX-11) is valued with "D" or "R" or "P" or "F" or "C" or "X" and the Producer's ID field is not valued. It should contain the identity of the observer that causes the change of the observation result status. Only the first component (ID number) of this field is necessary, provided that it is possible to retrieve the full identity of responsible person in the Order Filler system with this only ID number. 7.4.2.25 Retained for backward compatibility only Retained for backward compatibility only 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 3.4.5.17 3.4.5.21 3.4.10.3 3.4.10.4 Retained for backward compatibility only Retained for backward compatibility only 3.4.5.24 3.4.5.36 3.4.4.43 3.4.4.44 3.4.10.9 3.4.10.10 3.4.5.22 3.4.5.23 3.4.10.13 3.4.10.14 3.4.10.15 3.4.10.16 3.4.10.17 3.4.10.18 3.4.10.19 3.4.10.20 3.4.10.21 3.4.3.1 3.4.3.2 3.4.3.3 3.4.3.4 3.4.3.5 3.4.3.6 3.4.3.7 Retained for backward compatibility only Retained for backward compatibility only 3.4.3.8 Retained for backward compatibility only Retained for backward compatibility only 3.4.3.9 Retained for backward compatibility only Retained for backward compatibility only 3.4.3.10 3.4.3.11 3.4.3.12 3.4.3.13 3.4.3.14 3.4.3.15 3.4.3.16 3.4.3.17 Retained for backward compatibility only Retained for backward compatibility only 3.4.3.18 3.4.3.19 3.4.3.20 Retained for backward compatibility only 3.4.3.21 3.4.3.22 3.4.3.23 3.4.3.24 3.4.3.25 3.4.3.26 3.4.3.27 3.4.3.28 3.4.3.29 3.4.3.30 3.4.3.31 3.4.3.32 3.4.3.33 3.4.3.34 3.4.3.35 3.4.3.36 3.4.3.37 Retained for backward compatibility only 3.4.3.38 3.4.3.39 3.4.3.40 3.4.3.41 3.4.3.42 3.4.3.43 3.4.3.44 Retained for backward compatibility only 3.4.3.45 Retained for backward compatibility only 3.4.3.46 3.4.3.47 3.4.3.48 3.4.3.49 3.4.3.50 3.4.3.51 3.4.3.52 Retained for backward compatibility only Retained for backward compatibility only 3.4.4.1 3.4.4.2 3.4.4.3 3.4.4.4 3.4.4.5 3.4.4.6 3.4.4.7 3.4.4.8 Retained for backward compatibility only 3.4.4.9 Retained for backward compatibility only 3.4.4.10 3.4.4.11 3.4.4.12 3.4.4.13 Retained for backward compatibility only Retained for backward compatibility only 3.4.4.14 3.4.4.15 3.4.4.16 3.4.4.17 3.4.4.18 3.4.4.19 3.4.4.20 3.4.4.21 3.4.4.22 3.4.4.23 3.4.4.24 3.4.4.25 3.4.4.26 3.4.4.27 3.4.4.28 3.4.4.29 3.4.4.30 3.4.4.31 3.4.4.32 3.4.4.33 Retained for backward compatibility only 3.4.4.34 3.4.4.35 3.4.4.36 3.4.4.37 3.4.4.38 3.4.4.39 3.4.4.40 3.4.4.41 3.4.4.42 3.4.4.43 3.4.4.44 3.4.4.45 3.4.4.46 3.4.4.47 Retained for backward compatibility only 3.4.4.48 Retained for backward compatibility only 3.4.4.49 3.4.6.1 3.4.6.2 3.4.6.3 3.4.6.4 3.4.6.5 3.4.6.6 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 4.5.1.31 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 4.5.3.50 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 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 Since the OBX-18 field should not beused; this OBX-19 field is pointless. This field contains the sequence numberof the OBX. 7.4.2.1 7.4.2.2 The usage of LOINC(r) test codes for theidentification of tests is stronglyrecommended. Details of this freevocabulary can be found athttp://www.loinc.org 7.4.2.3 7.4.2.4 7.4.2.5 7.4.2.6 required if available. This field should bevalued as described in HL7 V2.5 for allobservations for which it is relevant. TheReferences range that figures in this fieldis supposed to be related to age and sexof the patient or to other parameters suchas number of weeks of pregnancy whenapplicable, which makes the OBX-10 field(nature of abnormal test) unnecessary. 7.4.2.7 required if available.This field is required when applicable.Among the possible values listed for thisfield in HL7 table 0078, the actors of IHELaboratory Technical Framework shouldsupport the values of table 0078As described in the above table, the S, R,or I values must be used to indicate theinterpreted result of susceptibilities inmicrobiology, in case the value field(OBX-5) contains a numeric value thatrepresents the MIC (Minimum InhibitiveConcentration). In case the order filleronly reports the interpreted result forsusceptibilities, the S, R, or I value couldbe filled in the value field (OBX-5) with aValue Type (OBX-2) set to "ST". 7.4.2.8 7.4.2.9 7.4.2.10 This field should be filled according toHL7 Table 0085 described in Chapter 7 ofHL7. In this version of the LaboratoryTechnical Version, the possible valuesfor this field are a subset of this table: 7.4.2.11 Since the Reference range given by theorder filler is the one that applies to theObservation result taking into accountsome other parameters like patient age orsex; there is not need to manage thepresent field. The Order Result Trackershould store the observation result andits associated reference range. In casethe Order Result Tracker offers thecapability to compare results of the sameobservation over different requests, itshould then associate each result with itsassociated reference range. 7.4.2.12 Retained for backward compatibility only 7.4.2.13 Required if availableThis field should be valued when theOBX-5 field (Value field) is also valued. Invery exceptional case this informationmay be unknown by the Order Filler(case the test is transmitted in areference lab and observation date andtime is not returned together with theresult), this field can be null and theOrderResult Tracker should not generate anerror. 7.4.2.14 Retained for backward compatibility only Required if available This field is required in case the observation was not produced by the sending organization 7.4.2.15 This field is required when the observation result status (OBX-11) is valued with "D" or "R" or "P" or "F" or "C" or "X" and the Producer's ID field is not valued. It should contain the identity of the observer that causes the change of the observation result status. Only the first component (ID number) of this field is necessary, provided that it is possible to retrieve the full identity of responsible person in the Order Filler system with this only ID number. 7.4.2.16 Retained for backward compatibility only Retained for backward compatibility only 7.4.2.17 Although this information should be available at the Order Filler level, this field should not be used in this first version of the Laboratory Technical Framework 7.4.2.18 Since the OBX-18 field should not be used; this OBX-19 field is pointless. 7.4.2.19 Retained for backward compatibility only Reserved for harmonization with V2.6 7.4.2.20 Reserved for harmonization with V2.6 7.4.2.21 Reserved for harmonization with V2.6 7.4.2.22 7.4.2.23 7.4.2.24 deprecated as of v2.5 Retained for backward compatibility only Retained for backward compatibility only This field is required when the observation result status (OBX-11) is valued with "D" or "R" or "P" or "F" or "C" or "X" and the Producer's ID field is not valued. It should contain the identity of the observer that causes the change of the observation result status. Only the first component (ID number) of this field is necessary, provided that it is possible to retrieve the full identity of responsible person in the Order Filler system with this only ID number. 7.4.2.25 Retained for backward compatibility only 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 6.5.1.1 6.5.1.2 6.5.1.3 6.5.1.4 Retained for backward compatibility only Retained for backward compatibility only 6.5.1.5 Retained for backward compatibility only 6.5.1.6 6.5.1.7 6.5.1.8 6.5.1.9 6.5.1.10 6.5.1.11 Using ISO 6.5.1.12 Using ISO 6.5.1.13 6.5.1.14 6.5.1.15 Using ISO 3.4.3.3 6.5.1.17 3.4.3.18 6.5.1.19 6.5.1.20 Retained for backward compatibility only Retained for backward compatibility only 6.5.1.21 Retained for backward compatibility only Retained for backward compatibility only 6.5.1.22 Using ISO 4.5.1.3 6.5.1.24 Retained for backward compatibility only Retained for backward compatibility only 4.5.3.44 4.5.3.45 4.5.1.20 4.5.3.48 6.5.1.29 6.5.1.30 6.5.1.31 7.8.1.1 7.8.2.1 7.8.3.1 4.5.2.1 Retained for backward compatibility only 4.5.2.2 4.5.2.3 4.5.2.4