In the reporting of clinical data, the OBR serves as the report header. It identifies the observation set represented by the following atomic observations. It includes the relevant ordering information when that applies. It contains many of the attributes that usually apply to all of the included observations.
When a set of observations is ordered, the order message contains an OBR segment. However, observations can be collected and reported without an antecedent order. When observations are reported, the report message also includes one or more OBR segments. So, the OBR segment is like a turn-around document. Some fields in the OBR segment apply only to the ordering message and some to the reporting message. To those familiar with healthcare procedures, these should be obvious from their names (e.g., transcriptionist or principal result interpreter could only apply to the reporting phase). However, we have also flagged them in Figure 7-4 to indicate whether placer, filler, or both may send data in a given field.
Figure 7-4. OBR attributes
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM # |
ELEMENT NAME |
1 |
4 |
SI |
C |
00237 |
Set ID - OBR |
||
2 |
75 |
EI |
C |
00216 |
Placer Order Number |
||
3 |
75 |
EI |
C |
00217 |
Filler Order Number + |
||
4 |
200 |
CE |
R |
00238 |
Universal Service ID |
||
5 |
2 |
ID |
X |
00239 |
Priority |
||
6 |
26 |
TS |
X |
00240 |
Requested Date/time |
||
7 |
26 |
TS |
C |
00241 |
Observation Date/Time # |
||
8 |
26 |
TS |
O |
00242 |
Observation End Date/Time # |
||
9 |
20 |
CQ |
O |
00243 |
Collection Volume * |
||
10 |
60 |
XCN |
O |
Y |
00244 |
Collector Identifier * |
|
11 |
1 |
ID |
O |
0065 |
00245 |
Specimen Action Code * |
|
12 |
60 |
CE |
O |
00246 |
Danger Code |
||
13 |
300 |
ST |
O |
00247 |
Relevant Clinical Info. |
||
14 |
26 |
TS |
C |
00248 |
Specimen Received Date/Time * |
||
15 |
300 |
CM |
O |
0070 |
00249 |
Specimen Source * |
|
16 |
80 |
XCN |
O |
Y |
00226 |
Ordering Provider |
|
17 |
40 |
XTN |
O |
Y/2 |
00250 |
Order Callback Phone Number |
|
18 |
60 |
ST |
O |
00251 |
Placer field 1 |
||
19 |
60 |
ST |
O |
00252 |
Placer field 2 |
||
20 |
60 |
ST |
O |
00253 |
Filler Field 1 + |
||
21 |
60 |
ST |
O |
00254 |
Filler Field 2 + |
||
22 |
26 |
TS |
C |
00255 |
Results Rpt/Status Chng - Date/Time + |
||
23 |
40 |
CM |
O |
00256 |
Charge to Practice + |
||
24 |
10 |
ID |
O |
0074 |
00257 |
Diagnostic Serv Sect ID |
|
25 |
1 |
ID |
C |
0123 |
00258 |
Result Status + |
|
26 |
400 |
CM |
O |
00259 |
Parent Result + |
||
27 |
200 |
TQ |
O |
Y |
00221 |
Quantity/Timing |
|
28 |
150 |
XCN |
O |
Y/5 |
00260 |
Result Copies To |
|
29 |
150 |
CM |
O |
00261 |
Parent * |
||
30 |
20 |
ID |
O |
0124 |
00262 |
Transportation Mode |
|
31 |
300 |
CE |
O |
Y |
00263 |
Reason for Study |
|
32 |
200 |
CM |
O |
00264 |
Principal Result Interpreter + |
||
33 |
200 |
CM |
O |
Y |
00265 |
Assistant Result Interpreter + |
|
34 |
200 |
CM |
O |
Y |
00266 |
Technician + |
|
35 |
200 |
CM |
O |
Y |
00267 |
Transcriptionist + |
|
36 |
26 |
TS |
O |
00268 |
Scheduled Date/Time + |
||
37 |
4 |
NM |
O |
01028 |
Number of Sample Containers * |
||
38 |
60 |
CE |
O |
Y |
01029 |
Transport Logistics of Collected Sample * |
|
39 |
200 |
CE |
O |
Y |
01030 |
Collector's Comment * |
|
40 |
60 |
CE |
O |
01031 |
Transport Arrangement Responsibility |
||
41 |
30 |
ID |
O |
0224 |
01032 |
Transport Arranged |
|
42 |
1 |
ID |
O |
0225 |
01033 |
Escort Required |
|
43 |
200 |
CE |
O |
Y |
01034 |
Planned Patient Transport Comment |
The complete description of these fields is provided below as well as in Chapter 4.
7.3.1.0 OBR field definitions
The daggered (+) items in this segment are not created by the placer known to the filler, not the placer. They are created by the filler and valued as needed when the OBR segment is returned as part of a report. Hence on a new order sent to the filler, they are not valued. There is an exception when the filler initiates the order. In that case, the filler order number is valued and the placer order number may be blank.They are valued by the filler as needed when the OBR segment is returned as part of a report.
The starred (*) fields are only relevant when an observation is associated with a specimen. These are completed by the placer when the placer obtains the specimen. They are completed by the filler when the filler obtains the specimen.
OBR-7-observation date/time and OBR-8-observation end date/time (flagged with #) are the physiologically relevant times. In the case of an observation on a specimen, they represent the start and end of the specimen collector. In the case of an observation obtained directly from a subject (eg., BP, Chest X-ray), they represent the start and end time of the observation.
Definition: For the first order transmitted, the sequence number shall be 1; for the second order, it shall be 2; and so on.
Components: <entity identifier (ST)> ^ <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)>
Definition: This field is identical to ORC-2-placer order number.
The first component is a string of up to 15 characters that identifies an individual order segment (e.g., OBR). It is assigned by the placer (ordering application). It identifies an order uniquely among all orders from a particular ordering application. The application ID is a string of up to six (6) characters that will be uniquely associated with an application. A given institution or group of intercommunicating institutions should establish a unique list of applications that may be potential placers and fillers and assign unique application IDs.
The second component contains the application ID of the placing application. The two components are separated by a component delimiter.
Components: <entity identifier (ST)> ^ <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)>
Definition: This is a permanent identifier for an order and its associated observations. It is a special case of the Entity Identifier data type (see Section 2.8.15, "EI - entity identifier," of Chapter 2).
The first component is a string that identifies an individual order segment (e.g., OBR). It is assigned by the order filling (receiving) application. It identifies an order uniquely among all orders from a particular filling application (e.g., clinical laboratory).
The second component is the filler application ID.
OBR-3-filler order number is identical to ORC-3-filler order number.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^<alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field is the identifier code for the requested observation/test/battery. This can be based on local and/or "universal" codes. We recommend the "universal" procedure identifier. The structure of this CE data type is described in the control section.
Definition: This field has been retained for backward compatibility only. It is not used. Previously priority (e.g., STAT, ASAP), but that information is carried as the sixth component of OBR-27-quantity/timing.
Definition: This field has been retained for backward compatibility only. This is not used. Previously requested date/time. That information is now carried in the fourth component of the OBR-27-quantity/timing.
Definition: This field is the clinically relevant date/time of the observation. In the case of observations taken directly from a subject, it is the actual date and time the observation was obtained. In the case of a specimen-associated study, this field shall represent the date and time the specimen was collected or obtained. (This is a results-only field except when the placer or a third-party has already drawn the specimen.) This field is conditionally required. When the OBR is transmitted as part of a report message, the field must be filled in. If it is transmitted as part of a request and a sample has been sent along as part of the request, this field must be filled in because this specimen time is the physiologically relevant date-time of the observation.
Definition: This field is the end date and time of a study or timed specimen collection. If an observation takes place over a substantial period of time, it will indicate when the observation period ended. For observations made at a point in time, it will be null. This is a results field except when the placer or a party other than the filler has already drawn the specimen.
Components: <quantity (NM)> ^ <units (CE)>
Definition: For laboratory tests, the collection volume is the volume of a specimen. The default unit is ML. Specifically, units should be expressed in the ISO Standard unit abbreviations (ISO-2955,1977). This is a results-only field except when the placer or a party has already drawn the specimen. (See Chapter 7 for full details about units.)
Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID )> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <univerwsal ID type (ID)>
Subcomponents of assigning facility ID: <namespace ID (IS)> & <universal ID (ST)> & <univerwsal ID type (ID)>
Definition: When a specimen is required for the study, this field will identify the person, department, or facility that collected the specimen. Either name or ID code, or both, may be present.
Definition: This field is the action to be taken with respect to the specimens that accompany or precede this order. The purpose of this field is to further qualify (when appropriate) the general action indicated by the order control code contained in the accompanying ORC segment. For example, when a new order (ORC - "NW") is sent to the lab, this field would be used to tell the lab whether or not to collect the specimen ("L" or "O"). Refer to HL7 table 0065 - Specimen action code for valid values.
Table 0065 - Specimen action code
Value |
Description |
A |
Add ordered tests to the existing specimen |
G |
Generated order; reflex order |
L |
Lab to obtain specimen from patient |
O |
Specimen obtained by service other than Lab |
P |
Pending specimen; Order sent prior to delivery |
R |
Revised order |
S |
Schedule the tests specified below |
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field is the code and/or text indicating any known or suspected patient or specimen hazards, e.g., patient with active tuberculosis or blood from a hepatitis patient. Either code and/or text may be absent. However, the code is always placed in the first component position and any free text in the second component. Thus, free text without a code must be preceded by a component delimiter.
Definition: This field is the additional clinical information about the patient or specimen will be provided here. This field is used to report the suspected diagnosis and clinical findings on requests for interpreted diagnostic studies. Examples include reporting the amount of inspired carbon dioxide for blood gasses, the point in the menstrual cycle for cervical pap tests, and other conditions that influence test interpretations. For some orders this information may be sent on a more structured form as a series of OBX segments (see Chapter 7) that immediately follow the order segment.
Definition: For observations requiring a specimen, the specimen received date/time is the actual login time at the diagnostic service. This field must contain a value when the order is accompanied by a specimen, or when the observation required a specimen and the message is a report.
Components: <specimen source name or code (CE)> ^ <additives (TX)> ^ <freetext (TX)> ^ <body site (CE)> ^ <site modifier (CE)> ^ <collection method modifier code (CE)>
Definition: This field is the site where the specimen should be obtained or where the service should be performed.
The first component contains the specimen source name or code (as a CE data type component). (Even in the case of observations whose name implies the source, a source may be required, e.g., blood culture-heart blood.) Refer to HL7 table 0070 - Source of specimen for valid entries.
The second component should include free text additives to the specimen such as Heparin, EDTA, or Oxlate, when applicable.
The third is a free text component describing the method of collection when that information is a part of the order. When the method of collection is logically an observation result, it should be included as a result segment.
The fourth component specifies the body site from which the specimen was obtained, and the fifth is the site modifier. For example, the site could be anticubital foss, and the site modifier "right." The components of the CE fields become subcomponents. Refer to HL7 table 0163 - Administrative site for valid entries.
Table 0163 - Administrative site
Value |
Description |
Value |
Description |
BE |
Bilateral Ears |
LVL |
Left Vastus Lateralis |
OU |
Bilateral Eyes |
NB |
Nebulized |
BN |
Bilateral Nares |
PA |
Perianal |
BU |
Buttock |
PERIN |
Perineal |
CT |
Chest Tube |
RA |
Right Arm |
LA |
Left Arm |
RAC |
Right Anterior Chest |
LAC |
Left Anterior Chest |
RACF |
Right Antecubital Fossa |
LACF |
Left Antecubital Fossa |
RD |
Right Deltoid |
LD |
Left Deltoid |
RE |
Right Ear |
LE |
Left Ear |
REJ |
Right External Jugular |
LEJ |
Left External Jugular |
OD |
Right Eye |
OS |
Left Eye |
RF |
Right Foot |
LF |
Left Foot |
RG |
Right Gluteus Medius |
LG |
Left Gluteus Medius |
RH |
Right Hand |
LH |
Left Hand |
RIJ |
Right Internal Jugular |
LIJ |
Left Internal Jugular |
RLAQ |
Rt Lower Abd Quadrant |
LLAQ |
Left Lower Abd Quadrant |
RLFA |
Right Lower Forearm |
LLFA |
Left Lower Forearm |
RMFA |
Right Mid Forearm |
LMFA |
Left Mid Forearm |
RN |
Right Naris |
LN |
Left Naris |
RPC |
Right Posterior Chest |
LPC |
Left Posterior Chest |
RSC |
Right Subclavian |
LSC |
Left Subclavian |
RT |
Right Thigh |
LT |
Left Thigh |
RUA |
Right Upper Arm |
LUA |
Left Upper Arm |
RUAQ |
Right Upper Abd Quadrant |
LUAQ |
Left Upper Abd Quadrant |
RUFA |
Right Upper Forearm |
LUFA |
Left Upper Forearm |
RVL |
Right Vastus Lateralis |
LVG |
Left Ventragluteal |
RVG |
Right Ventragluteal |
The fifth component indicates whether the specimen is frozen as part of the collection method. Suggested values are F (Frozen); R (Refrigerated). If the component is blank, the specimen is assumed to be at room temperature.
Table 0070 - Specimen source codes
Value |
Description |
Value |
Description |
Value |
Description |
ABS |
Abscess |
FLU |
Body fluid, unsp |
SER |
Serum |
AMN |
Amniotic fluid |
GAS |
Gas |
SKN |
Skin |
ASP |
Aspirate |
GAST |
Gastric fluid/contents |
SKM |
Skeletal muscle |
BPH |
Basophils |
GEN |
Genital |
SPRM |
Spermatozoa |
BIFL |
Bile fluid |
GENC |
Genital cervix |
SPT |
Sputum |
BLDA |
Blood arterial |
GENL |
Genital lochia |
SPTC |
Sputum - coughed |
BBL |
Blood bag |
GENV |
Genital vaginal |
SPTT |
Sputum - tracheal aspirate |
BLDC |
Blood capillary |
HAR |
Hair |
STON |
Stone (use CALC) |
BPU |
Blood product unit |
IHG |
Inhaled Gas |
STL |
Stool = Fecal |
BLDV |
Blood venous |
IT |
Intubation tube |
SWT |
Sweat |
BON |
Bone |
ISLT |
Isolate |
SNV |
Synovial fluid (Joint fluid) |
BRTH |
Breath (use EXHLD) |
LAM |
Lamella |
TEAR |
Tears |
BRO |
Bronchial |
WBC |
Leukocytes |
THRT |
Throat |
BRN |
Burn |
LN |
Line |
THRB |
Thrombocyte (platelet) |
CALC |
Calculus (=Stone) |
LNA |
Line arterial |
TISS |
Tissue |
CDM |
Cardiac muscle |
LNV |
Line venous |
TISG |
Tissue gall bladder |
CNL |
Cannula |
LIQ |
Liquid NOS |
TLGI |
Tissue large intestine |
CTP |
Catheter tip |
LYM |
Lymphocytes |
TLNG |
Tissue lung |
CSF |
Cerebral spinal fluid |
MAC |
Macrophages |
TISPL |
Tissue placenta |
CVM |
Cervical mucus |
MAR |
Marrow |
TSMI |
Tissue small intestine |
CVX |
Cervix |
MEC |
Meconium |
TISU |
Tissue ulcer |
COL |
Colostrum |
MBLD |
Menstrual blood |
TUB |
Tube NOS |
CBLD |
Cord blood |
MLK |
Milk |
ULC |
Ulcer |
CNJT |
Conjunctiva |
MILK |
Breast milk |
UMB |
Umbilical blood |
CUR |
Curettage |
NAIL |
Nail |
UMED |
Unknown medicine |
CYST |
Cyst |
NOS |
Nose (nasal passage) |
URTH |
Urethra |
DIAF |
Dialysis fluid |
ORH |
Other |
UR |
Urine |
DOSE |
Dose med or substance |
PAFL |
Pancreatic fluid |
URC |
Urine clean catch |
DRN |
Drain |
PAT |
Patient |
URT |
Urine catheter |
DUFL |
Duodenal fluid |
PRT |
Peritoneal fluid /ascites |
URNS |
Urine sediment |
EAR |
Ear |
PLC |
Placenta |
USUB |
Unknown substance |
EARW |
Ear wax (cerumen) |
PLAS |
Plasma |
VOM |
Vomitus |
ELT |
Electrode |
PLB |
Plasma bag |
BLD |
Whole blood |
ENDC |
Endocardium |
PLR |
Pleural fluid (thoracentesis fld) |
BDY |
Whole body |
ENDM |
Endometrium |
PMN |
Polymorphonuclear neutrophils |
WAT |
Water |
EOS |
Eosinophils |
PPP |
Patelet poor plasma |
WICK |
Wick |
RBC |
Erythrocytes |
PRP |
Platelet rich plasma |
WND |
Wound |
EYE |
Eye |
PUS |
Pus |
WNDA |
Wound abscess |
EXHLD |
Exhaled gas (=breath) |
RT |
Route of medicine |
WNDE |
Wound exudate |
FIB |
Fibroblasts |
SAL |
Saliva |
WNDD |
Wound drainage |
FLT |
Filter |
SEM |
Seminal fluid |
XXX |
To be specified in another part of the message |
FIST |
Fistula |
Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID )> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <univerwsal ID type (ID)>
Subcomponents of assigning facility ID: <namespace ID (IS)> & <universal ID (ST)> & <univerwsal ID type (ID)>
Definition: This field identifies the provider who ordered the test. Either the ID code or the name, or both, may be present. This is the same as ORC-12-ordering provider.
Components: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)>
Definition: This field is the telephone number for reporting a status or a result using the Standard format with extension and/or beeper number when applicable.
Definition: This field is user field #1. Text sent by the placer will be returned with the results.
Definition: This field is similar to placer field #1.
Definition: This field is definable for any use by the filler (diagnostic service).
Definition: This field is similar to filler field #1.
Definition: This field specifies the date/time results reported or status changed. This field is used to indicate the date and time that the results are composed into a report and released, or that a status, as defined in Order Status, is entered or changed. (This is a results field only.) When other applications (such as office or clinical database applications) query the laboratory application for untransmitted results, the information in this field may be used to control processing on the communications link. Usually, the ordering service would want only those results for which the reporting date/time is greater than the date/time the inquiring application last received results.
Components: <dollar amount (MO)> ^ <charge code (CE)>
Definition: This field is the charge to the ordering entity for the studies performed when applicable. The first component is a dollar amount when known by the Filler. The second is a charge code when known by the filler (results only).
Definition: This field is the section of the diagnostic service where the observation was performed. If the study was performed by an outside service, the identification of that service should be recorded here. Refer to HL7 table 0074 - Diagnostic service section ID for valid entries.
Table 0074 - Diagnostic service section ID
Value |
Description |
Value |
Description |
AU |
Audiology |
OUS |
OB Ultrasound |
BG |
Blood gases |
OT |
Occupational Therapy |
BLB |
Blood bank |
OTH |
Other |
CUS |
Cardiac Ultrasound |
OSL |
Outside Lab |
CTH |
Cardiac catheterization |
PHR |
Pharmacy |
CT |
CAT scan |
PT |
Physical Therapy |
CH |
Chemistry |
PHY |
Physician (Hx. Dx, admission note, etc.l) |
CP |
Cytopathology |
PF |
Pulmonary function |
EC |
Electrocardiac (e.g., EKG, EEC, Holter) |
RAD |
Radiology |
EN |
Electroneuro (EEG, EMG,EP,PSG) |
RX |
Radiograph |
HM |
Hematology |
RUS |
Radiology ultrasound |
ICU |
Bedside ICU Monitoring |
RC |
Respiratory Care (therapy) |
IMM |
Immunology |
RT |
Radiation therapy |
LAB |
Laboratory |
SR |
Serology |
MB |
Microbiology |
SP |
Surgidal Pathology |
MCB |
Mycobacteriology |
TX |
Toxicology |
MYC |
Mycology |
VUS |
Vascular Ultrasound |
NMS |
Nuclear medicine scan |
VR |
Virology |
NMR |
Nuclear magnetic resonance |
XRC |
Cineradiograph |
NRS |
Nursing service measures |
Definition: This field is the status of results for this order. This conditional field is required whenever the OBR is contained in a report message. It is not required as part of an initial order.
There are two methods of sending status information. If the status is that of the entire order, use ORC-15-order effective date/time and ORC-5-order status. If the status pertains to the order detail segment, use OBR-25-result status and OBR-22-results report/status change - date/time. If both are present, the OBR values override the ORC values.
This field would typically be used in a response to an order status query where the level of detail requested does not include the OBX segments. When the individual status of each result is necessary, OBX-11-observ result status may be used. Refer to HL7 table 0123 - Result status for valid entries.
Value |
Description |
Value |
Description |
O |
Order received; specimen not yet received |
R |
Results stored; not yet verified |
I |
No results available; specimen received, procedure incomplete |
F |
Final results; results stored and verified. Can only be changed with a corrected result. |
S |
No results available; procedure scheduled, but not done |
X |
No results available; Order canceled. |
A |
Some, but not all, results available |
Y |
No order on record for this test. (Used only on queries) |
P |
Preliminary: A verified early result is available, final results not yet obtained |
Z |
No record of this patient. (Used only on queries) |
C |
Correction to results |
Components: <OBX-3-observation identifier of parent result (CE)> ^ <OBX-4-sub-ID of parent result (ST)> ^ <part of OBX-5 observation result from parent (TX) see discussion>
Definition: This field is defined to make it available for other types of linkages (e.g., toxicology). This important information, together with the information in OBR-29-parent number, uniquely identifies the parent results OBX segment related to this order. The value of this OBX segment in the parent result is the organism or chemical species about which this battery reports. E.g., if the current battery is an antimicrobial susceptibility, the parent results identified OBX contains a result which identifies the organism on which the susceptibility were run. This indirect linkage is preferred because the name of the organism in the parent result may undergo several preliminary values prior to finalization.
The third component may be used to record the name of the microorganism identified by the parent result directly. The organism in this case should be identified exactly as it is in the parent culture.
We emphasize that this field does not take the entire result field from the parent. It is meant only for the text name of the organism or chemical subspecies identified. This field is included only to provide a method for linking back to the parent result for those systems which could not generate unambiguous Observation Ids and sub-Ids.
This field is present only when the parent result is identified by OBR-29-parent number and the parent spawn child orders for each of many results. (See Chapter 7 for more details about this linkage.)
A second mode of conveying this information is to use a standard observation result segment (OBX). If more than one organism is present, OBX-4-subID is used to distinguish them. In this case, the first OBX with subID N will contain a value identifying the Nth microorganism, and each additional OBX with subID N will contain susceptibility values for a given antimicrobial test on this organism.
Components: <quantity (CQ)> ^ <interval (CM)> ^ <duration> ^ <start date/time (TS)> ^ <end date/time (TS)> ^ <priority (ID)> ^ <condition (ST)> ^ <text (TX)> ^ <conjunction (ID)> ^ <order sequencing>
Definition: This field contains information about how many services to perform at one service time and how often the service times are repeated, and to fix duration of the request. See Section 4.4, "Quantity/Timing (TQ) Definition."
Components: <ID number (ST)> ^ <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <source table (IS)> ^ <assigning authority (HD)> ^ <name type code(ID)> ^ <identifier check digit (ST)> ^ <code identifying the check digit scheme employed (ID )> ^ <identifier type code (IS)> ^ <assigning facility (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <univerwsal ID type (ID)>
Subcomponents of assigning facility ID: <namespace ID (IS)> & <universal ID (ST)> & <univerwsal ID type (ID)>
Definition: This field is the people who are to receive copies of the results. By local convention, either the ID number or the name may be absent.
Components: <parent's placer order number (EI)> ^ <parent's filler order number (EI)>
Subomponents of parents placer order number: <entity identifier (ST)> & <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (IS)>
Subomponents of parents filler order number: <entity identifier (ST)> & < <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (IS)>
Definition: This field is identical to ORC-8-parent. This field relates a child to its parent when a parent-child relationship exists. For example, observations that are spawned by previous observations, e.g., antimicrobial susceptibilities spawned by blood cultures, need to record the parent (blood culture) filler order number here. The parent-child mechanism is described under the order control field notes (see Segment ORC field notes in Section 4.3.1.1.1, "Table notes for order control codes of ORC." It is required when the order is a child.
Parent is a two-component field. The first component contains the parents placer order number. The second component is optional and contains the parents filler order number. The components of the placer order number and the filler order number are transmitted in subcomponents of the two components of this field.
Definition: This field identifies how (or whether) to transport a patient, when applicable. Refer to HL7 table 0124 - Transportation mode for valid codes.
Table 0124 - Transportation mode
Value |
Description |
CART |
Cart - patient travels on cart or gurney |
PORT |
The examining device goes to patient's location |
WALK |
Patient walks to diagnostic service |
WHLC |
Wheelchair |
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field is the code or text using the conventions for coded fields given in the Control/Query Chapter (Chapter 2). This is required for some studies to obtain proper reimbursement.
Components: <name (CN)> ^ <start date/time (TS)> ^ <end date/time (TS)> ^ <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <patient location type (IS)> ^ <building (IS)> ^ <floor (IS)>
Definition: This field identifies the physician or other clinician who interpreted the observation and is responsible for the report content.
Components: <name (CN)> ^ <start date/time (TS)> ^ <end date/time (TS)> ^ <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <patient location type (IS)> ^ <building (IS)> ^ <floor (IS)>
Definition: This field identifies the clinical observer who assisted with the interpretation of this study.
Components: <name (CN)> ^ <start date/time (TS)> ^ <end date/time (TS)> ^ <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <patient location type (IS)> ^ <building (IS)> ^ <floor (IS)>
Definition: This field identifies the performing technician.
Components: <name (CN)> ^ <start date/time (TS)> ^ <end date/time (TS)> ^ <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <patient location type (IS)> ^ <building (IS)> ^ <floor (IS)>
Definition: This field identifies the report transcriber.
Definition: This field is the date/time the filler scheduled an observation, when applicable (e.g., action code in OBR-11-specimen action code = "S"). This is a result of a request to schedule a particular test and provides a way to inform the Placer of the date/time a study is scheduled (result only).
Definition: This field identifies the number of containers for a given sample. For sample receipt verification purposes; may be different from the total number of samples which accompany the order.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field is the means by which a sample reaches the diagnostic service provider. This information is to aid the lab in scheduling or interpretation of results. Possible answers: routine transport van, public postal service, etc. If coded, requires a user-defined table.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field is for reporting additional comments related to the sample. If coded, requires a user-defined table. If only free text is reported, it is placed in the second component with a null in the first component, e.g., ^difficult clotting after venepuncture and echymosis..
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field is an indicator of who is responsible for arranging transport to the planned diagnostic service. Examples: Requester, Provider, Patient. If coded, requires a user defined table.
Definition: This field is an indicator of whether transport arrangements are known to have been made. Refer to HL7 table 0224 - Transport arranged for valid codes.
Table 0224 - Transport arranged
Value |
Description |
A |
Arranged |
N |
Not Arranged |
U |
Unknown |
Definition: This field is an indicator that the patient needs to be escorted to the diagnostic service department. Note: The nature of the escort requirements should be stated in the "Planned Patient Transport Comment" field (OBR-43). See HL7 table 0225 - Escort required for valid values.
Value |
Description |
R |
Required |
N |
Not Required |
U |
Unknown |
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field is the code or free text comments on special requirements for the transport of the patient to the diagnostic service department. If coded, requires a user-defined table.