HL7 Terminology (THO)
6.0.1 - Publication
HL7 Terminology (THO)
6.0.1 - Publication
This page is part of the HL7 Terminology (v6.0.1: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
| Active as of 2019-12-01 |
<CodeSystem xmlns="http://hl7.org/fhir">
<id value="v2-0119"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem v2-0119</b></p><a name="v2-0119"> </a><a name="hcv2-0119"> </a><a name="v2-0119-en-US"> </a><p><b>Properties</b></p><p><b>This code system defines the following properties for its concepts</b></p><table class="grid"><tr><td><b>Name</b></td><td><b>Code</b></td><td><b>URI</b></td><td><b>Type</b></td><td><b>Description</b></td></tr><tr><td>status</td><td>status</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#status</td><td>code</td><td>Status of the concept</td></tr><tr><td>deprecated</td><td>deprecated</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated</td><td>code</td><td>Version of HL7 in which the code was deprecated</td></tr><tr><td>V2 Concept Comment</td><td>v2-concComment</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment</td><td>string</td><td>V2 Concept Comment</td></tr><tr><td>V2 Concept Comment As Published</td><td>v2-concCommentAsPub</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub</td><td>string</td><td>V2 Concept Comment As Published</td></tr><tr><td>HL7 Concept Usage Notes</td><td>HL7usageNotes</td><td>http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes</td><td>string</td><td>HL7 Concept Usage Notes</td></tr></table><p><b>Concepts</b></p><p>This case-sensitive code system <code>http://terminology.hl7.org/CodeSystem/v2-0119</code> defines the following codes in a Is-A hierarchy:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td><td><b>V2 Concept Comment</b></td><td><b>V2 Concept Comment As Published</b></td><td><b>HL7 Concept Usage Notes</b></td><td><b>Deutsch (German, de)</b></td></tr><tr><td style="white-space:nowrap">AF<a name="v2-0119-AF"> </a></td><td>Order/service refill request approval</td><td>AF is a response to RF where the placer authorizing a refill or quantity of refills.</td><td>Placer Applications .</td><td>Placer Applications.<p>AF is a response to RF where the placer authorizing a refill or quantity of refills.</td><td/><td/></tr><tr><td style="white-space:nowrap">CA<a name="v2-0119-CA"> </a></td><td>Cancel order/service request</td><td>Cancel order/service request</td><td>Placer or Filler Applications</td><td>Placer or Filler Applications.
A cancellation is a request by the placer for the filler, or the filler to the placer, not to do a previously ordered service. Confirmation of the cancellation request is provided by the filler or placer, e.g., a message with an ORC-1-order control value of CR.
Typical responses include, but are not limited to, CR – Cancelled as requested, UC – Unable to Cancel.</td><td/><td>Auftrag stornieren</td></tr><tr><td style="white-space:nowrap">CH<a name="v2-0119-CH"> </a></td><td>Child order/service</td><td>Child order/service</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.<p>Used in conjunction with the PA - Parent order control code. Refer to PA order control code for discussion.</td><td>Used in conjunction with the PA - Parent order control code. Refer to PA order control code for discussion.</td><td>nachgeordneter Auftrag</td></tr><tr><td style="white-space:nowrap">CN<a name="v2-0119-CN"> </a></td><td>Combined result</td><td>Combined result</td><td>Filler Applications.</td><td>Filler Applications.
The combined result code provides a mechanism to transmit results that are associated with two or more orders. This situation occurs commonly in radiology reports when the radiologist dictates a single report for two or more exams represented as two or more orders. For example, knee and hand films for a rheumatoid arthritis patient might generate a single dictation on the part of the radiologist.
When such results are reported the CN code replaces the RE code in all but the last ORC, and the results follow the last ORC and its OBR. An example follows of a single report following three ORCs:
MSH|...<cr>
PID|...<cr>
ORC|CN|...<cr>
OBR|1|A4461XA^HIS|81641^RAD|73666^Bilateral Feet|...<cr>
ORC|CN|...<cr>
OBR|2|A4461XB^HIS|81642^RAD|73642^Bilateral Hand PA|...<cr>
ORC|RE|...<cr>
OBR|3|A4461XC^HIS|81643^RAD|73916^Bilateral Knees|...<cr>
OBX|1|CE|73916&IMP|1|Radiologist’s Impression|...<cr>
OBX|2|CE|73642&IMP|1|Radiologist’s Impression|...<cr>
OBX|3|FT|73642&GDT|1|Description|...<cr></td><td/><td>Kumulatives Ergebnis (zu mehreren Aufträgen)</td></tr><tr><td style="white-space:nowrap">CP<a name="v2-0119-CP"> </a></td><td>Cancel process step</td><td>Cancel process step</td><td>Filler Applications.</td><td>Filler Applications.
The control code CP – Cancel process step should be used in the ORC-1 for communication Filler-to-Filler, e.g., LIS-to-Analyzer, to differentiate from code CA (Placer-to-Filler).
The Filler should response with an acceptance of the cancellation using ORC-1 = CR and ORC-5 = CA.</td><td/><td/></tr><tr><td style="white-space:nowrap">CR<a name="v2-0119-CR"> </a></td><td>Canceled as requested</td><td>Canceled as requested</td><td>Filler or Placer Applications.</td><td>Filler or Placer Applications.<p>A response by the filler or placer application that a request to cancel (CA by the placer application) was performed successfully.</td><td>A response by the filler or placer application that a request to cancel (CA by the placer application) was performed successfully.</td><td>Auftrag anweisungsgemäß storniert</td></tr><tr><td style="white-space:nowrap">DC<a name="v2-0119-DC"> </a></td><td>Discontinue order/service request</td><td>Discontinue order/service request</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.
A request by the placer for the filler, or the filler to the placer, to discontinue a previously requested service. The differentiation between discontinue and cancel is that discontinue effects the order/service and all future occurrences, cancel refers to just the present action.
Typical responses include, but are not limited to, CR – Cancelled as requested, UC – Unable to Cancel.</td><td/><td>Auftragsausführung abbrechen</td></tr><tr><td style="white-space:nowrap">DE<a name="v2-0119-DE"> </a></td><td>Data errors</td><td>Data errors</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.</td><td/><td>Datenfehler</td></tr><tr><td style="white-space:nowrap">DF<a name="v2-0119-DF"> </a></td><td>Order/service refill request denied</td><td>Order/service refill request denied</td><td>Placer Applications.</td><td>Placer Applications.
In response to a Filler application requesting refill authorization (RF), DF indicates that the placer does not authorize refills for the order. ORC-16 Order Control Code reason may be used to indicate the reason for the request denial. Some suggested values include:
AA Patient unknown to the provider
AB Patient never under provider care
AC Patient no longer under provider care
AD Patient has requested refill too soon
AE Medication never prescribed for the patient
AF Patient should contact provider first
AG Refill not appropriate
Note that these values originate from the NCPDP SCRIPT Response Segment Code List Qualifiers. Materials Reproduced with the consent of ©National Council for Prescription Drug Programs, Inc. 1988, 1992, 2002 NCPDP.</td><td/><td/></tr><tr><td style="white-space:nowrap">DR<a name="v2-0119-DR"> </a></td><td>Discontinued as requested</td><td>Discontinued as requested</td><td>Filler or Placer Applications.</td><td>Filler or Placer Applications.<p>The filler or placer, in response to a request to discontinue (DC from the placer or filler application), has discontinued the order/service.</td><td>The filler or placer, in response to a request to discontinue (DC from the placer or filler application), has discontinued the order/service.</td><td>Auftragsausführung anweisungsgemäß abgebrochen</td></tr><tr><td style="white-space:nowrap">FU<a name="v2-0119-FU"> </a></td><td>Order/service refilled, unsolicited</td><td>Order/service refilled, unsolicited</td><td>Filler Applications.</td><td>Filler Applications.<p>FU notifies the placer that the filler issued a refill for the order at the patient's request.</td><td>FU notifies the placer that the filler issued a refill for the order at the patient's request.</td><td/></tr><tr><td style="white-space:nowrap">HD<a name="v2-0119-HD"> </a></td><td>Hold order request</td><td>Hold order request</td><td>Placer Applications.</td><td>Placer Applications.<p>Typical responses include, but are not limited to, CR - Cancelled as requested, UC - Unable to Cancel.</td><td>Typical responses include, but are not limited to, CR - Cancelled as requested, UC - Unable to Cancel.</td><td>Auftragsbearbeitung aussetzen</td></tr><tr><td style="white-space:nowrap">HR<a name="v2-0119-HR"> </a></td><td>On hold as requested</td><td>On hold as requested</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Auftragsbearbeitung anweisungsgemäß ausgesetzt</td></tr><tr><td style="white-space:nowrap">LI<a name="v2-0119-LI"> </a></td><td>Link order/service to patient care problem or goal</td><td>Link order/service to patient care problem or goal</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.<p>Refer to Chapter 12 Patient Care for complete discussion.</td><td>Refer to Chapter 12 Patient Care for complete discussion.</td><td/></tr><tr><td style="white-space:nowrap">MC<a name="v2-0119-MC"> </a></td><td>Miscellaneous Charge - not associated with an order</td><td>Miscellaneous Charge - not associated with an order</td><td>applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11</td><td>applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11</td><td>applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11</td><td/></tr><tr><td style="white-space:nowrap">NA<a name="v2-0119-NA"> </a></td><td>Number assigned</td><td>Number assigned</td><td>Placer Applications.</td><td>Placer Applications.
There are three circumstances that involve requesting an order number (ORC-2-placer order number or ORC-3-filler order number):
(1) When the filler application needs to request an ORC-3-filler order number from a centralized application (e.g., HIS).
SN – The send order number code provides a mechanism for the filler to request an ORC-3-filler order number from some centralized application (called “other” in the table below), such as a central HIS, by sending an ORM message containing an ORC-1-order control value of SN. This ORC has a null ORC-3-filler order number and an ORC-2-placer order number created by the filler application when the filler originates the order.
The order (SN type) message can be acknowledged by either one of two methods:
a) By an order application acknowledgement message containing an ORC-1-order control value of OK. Then an unsolicited order message can be sent at a future time, containing an ORC with ORC-1-order control value of NA to provide the actual number assigned.
b) By an order acknowledgement message containing an ORC-1-order control value of NA as described below.
NA – The number assigned code allows the “other” application to notify the filler application of the newly-assigned filler order number. ORC-1-order control contains value of NA, ORC-2-placer order number (from the ORC with the SN value), and the newly-assigned filler order number.
Code From ORC-2-Placer Order Number ORC-3-Filler Order Number
SN filler application placer order number^filler application ID Null
NA other application placer order number^filler application ID filler order number^filler application ID
Note: Both the placer order number and the filler order number have the filler’s application ID
(2) When the filler application needs to request an ORC-2-placer order number from some other application (e.g., Order Entry).
SN – The send order number code provides a mechanism for the filler application to request an ORC-2-placer order number from another application (called “other” in the table below) by sending an order message containing an ORC-1-order control value of SN. This ORC has a null ORC-2-placer order number and an ORC-3-filler order number created by the filler application when the filler originates the order.
The order (SN type) message can be acknowledged by two methods:
a) By an order application acknowledgement message containing an ORC-1-order control value of OK. Then an unsolicited order message can be sent at a future time, containing an ORC-1-order control value of NA to provide the actual number assigned.
b) By an order acknowledgement message containing an ORC-1-order control value of NA as described below.
NA – The number assigned code allows the “other” application to notify the filler application of the newly-assigned ORC-2-placer order number. The ORC contains an ORC-1-order control value of NA, the newly-assigned ORC-2-placer order number, and the ORC-3-filler order number (from the ORC with the SN value).
Code From ORC-2-Placer Order Number ORC-3-Filler Order Number
SN filler application null filler order number^filler application ID
NA other application placer order number^placer application ID filler order number^filler application ID
Note: The new ORC-2-placer order number has the placer’s application ID
(3) When an application (not the filler application) wants to assign an ORC-3-filler order number for a new order.
NW – When the application creating an order (not the filler application) wants to assign a filler order number for a new order.
or
RO – (RO following an RP). In this case, the “other” application completes ORC-3-filler order number, using the filler application ID as the second component of the filler order number.
Code From ORC-2-Placer Order Number ORC-3-Filler Order Number
NW or RO Other application to filler application placer order number^placer application ID filler order number^filler application ID</td><td/><td>Nummer zugewiesen</td></tr><tr><td style="white-space:nowrap">NR<a name="v2-0119-NR"> </a></td><td>Notification Received</td><td>Notifies the Filler that the Placer received a cancellation, discontinuance, or other state change notice</td><td>Placer Applications.</td><td/><td/><td/></tr><tr><td style="white-space:nowrap">NW<a name="v2-0119-NW"> </a></td><td>New order/service</td><td>New order/service</td><td>Placer Applications.</td><td>Placer Applications.<p>See comments for NA - Number Assigned.</td><td>See comments for NA - Number Assigned.</td><td>Neuer Auftrag</td></tr><tr><td style="white-space:nowrap">OC<a name="v2-0119-OC"> </a></td><td>Order/service canceled</td><td>Order/service canceled</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Auftrag storniert</td></tr><tr><td style="white-space:nowrap">OD<a name="v2-0119-OD"> </a></td><td>Order/service discontinued</td><td>Order/service discontinued</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Auftragsausführung abgebrochen</td></tr><tr><td style="white-space:nowrap">OE<a name="v2-0119-OE"> </a></td><td>Order/service released</td><td>Order/service released</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td/></tr><tr><td style="white-space:nowrap">OF<a name="v2-0119-OF"> </a></td><td>Order/service refilled as requested</td><td>Order/service refilled as requested</td><td>Filler Applications.</td><td>Filler Applications.<p>OF directly responds to the placer system's request for a refill.</td><td>OF directly responds to the placer system's request for a refill.</td><td/></tr><tr><td style="white-space:nowrap">OH<a name="v2-0119-OH"> </a></td><td>Order/service held</td><td>Order/service held</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Auftragsbearbeitung ausgesetzt</td></tr><tr><td style="white-space:nowrap">OK<a name="v2-0119-OK"> </a></td><td>Order/service accepted & OK</td><td>Order/service accepted & OK</td><td>Filler Applications.</td><td>Filler Applications.<p>See comments for NA - Number Assigned.</td><td>See comments for NA - Number Assigned.</td><td>Auftrag akzeptiert</td></tr><tr><td style="white-space:nowrap">OP<a name="v2-0119-OP"> </a></td><td>Notification of order for outside dispense</td><td>Notification of order for outside dispense</td><td>Placer Applications.</td><td>Placer Applications.
These order control codes are used to communicate an order between systems where the order is intended for informational purposes. For example, an order that will be performed by a vendor outside the enterprise of communicating systems. The communicating systems may need to maintain information relative to the order for clinical continuity, but no actions to perform the ordered service are intended.
OP represents an informational version of NW, PY represents the informational-only version of RO. NW and RO table notes also apply to OP and PY, respectively.</td><td/><td/></tr><tr><td style="white-space:nowrap">OR<a name="v2-0119-OR"> </a></td><td>Released as requested</td><td>Released as requested</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Auftragsbearbeitung anweisungsgemäß wiederaufgenommen</td></tr><tr><td style="white-space:nowrap">PA<a name="v2-0119-PA"> </a></td><td>Parent order/service</td><td>Parent order/service</td><td>Filler Applications.</td><td>Filler Applications.
The parent (PA) and child (CH) order control codes allow the spawning of “child” orders from a “parent” order without changing the parent (original order). One or more ORC segments with an ORC-1-order control value of PA are followed by one or more ORC segments with an ORC-1-order control value of CH. Whether OBR segments must be present is determined by the value of ORC-6-response flag.
For example, suppose that a microbiology culture produced two organisms and corresponding susceptibility reports. Then the sequence of segments would be as follows: (see figure 4-4)
The assignment of placer order numbers in the parent-child paradigm depends on whether the placer or filler creates the child order and in the latter case, on whether the placer supports the SN/NA transaction. If the placer creates the child orders it will assign their placer order numbers according to its usual procedures. If the filler creates the child orders there are two possibilities: each child will inherit the placer order number of its parent, or the filler will use the SN/NA transaction to request that the placer assign a placer order number. In either case, the filler application creates the filler order numbers of the children according to its usual procedures.
Whenever a child order is transmitted in a message the ORC segment’s ORC-8-parent is valued with the parent’s filler order number (if originating from the filler) and with the parent’s placer order number (if originating from the filler or if originating from the placer).
The parent child mechanism can be used to “expand” a parent order (e.g., an order for three EKGs on successive mornings).</td><td/><td>Hauptauftrag</td></tr><tr><td style="white-space:nowrap">PR<a name="v2-0119-PR"> </a></td><td>Previous Results with new order/service</td><td>Previous Results with new order/service</td><td>Placer Applications.</td><td>Placer Applications.
PR indicates that this ORC is part of an ORU structure containing previous observation, which is embedded in the order.
At least two main use cases require that the complete results of the previous observations be transmitted with the order.
• Diagnostic laboratories referring tests to another lab for either confirmation of results (HIV, etc.) or due to not being equipped to do the tests (genetic testing, etc.).
• Diagnostic laboratories sending test results to Knowledge Bases for the automated generation of diagnostic comments for inclusion into the lab report.</td><td/><td/></tr><tr><td style="white-space:nowrap">PY<a name="v2-0119-PY"> </a></td><td>Notification of replacement order for outside dispense</td><td>Notification of replacement order for outside dispense</td><td>Placer Applications.</td><td>Placer Applications.<p>See comments for OP - Notification of order for outside dispense.</td><td>See comments for OP - Notification of order for outside dispense.</td><td/></tr><tr><td style="white-space:nowrap">RA<a name="v2-0119-RA"> </a></td><td>Recommendation Accepted</td><td>Identifies that this previously recommended replacement order has been accepted</td><td>Placer Applications:
Used in the Recommendation Accepted message; includes the assigned placer order number for the accepted replacement order
Filler Applications:
Used in the acknowledgment response message to the Recommendation Accepted message</td><td/><td/><td/></tr><tr><td style="white-space:nowrap">RC<a name="v2-0119-RC"> </a></td><td>Recommended Change</td><td>Identifies that this OBR represents a recommended replacement order</td><td>Filler Applications.
Used in the recommendation message sent to the placer</td><td/><td/><td/></tr><tr><td style="white-space:nowrap">RD<a name="v2-0119-RD"> </a></td><td>Recommendation Declined</td><td>Identifies that this previously sent recommended replacement order has been declined</td><td>Placer Applications:
Used in the Recommendation Declined message
Filler Applications:
Used in the acknowledgment response message to the Recommendation Declined message</td><td/><td/><td/></tr><tr><td style="white-space:nowrap">RE<a name="v2-0119-RE"> </a></td><td>Observations/Performed Service to follow</td><td>Observations/Performed Service to follow</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.
The observations-to-follow code is used to transmit patient-specific information with an order. An order detail segment (e.g., OBR) can be followed by one or more observation segments (OBX). Any observation that can be transmitted in an ORU message can be transmitted with this mechanism. When results are transmitted with an order, the results should immediately follow the order or orders that they support.
The following example shows the sequence of segments for three Pharmacy orders. It illustrates the use of the RE code:
Segment Order Control Comment
MSH
PID
ORC NW First new order
RXO First order segment
ORC NW 2nd new order
RXO 2nd order segment
[ORC RE Patient-specific observation, optional in V 2.2
OBR] Observation OBR, optional in V 2.2
OBX An observation segment
OBX Another observation segment
OBX Another observation segment
OBX Another observation segment
ORC NW 3rd order
RXO 3rd order segment
In this version of HL7, results can be transmitted with an order as one or more OBX segments without the necessity of including the ORC and OBR segments.
Observations can be transmitted in an ORU message without using an ORC. There are times when it is necessary to transmit information not included in the OBR segments of the ORU message. In this case, it is recommended that the ORC be included in the ORU message.
The order control value of RE is required only in ORM messages to indicate that an order is followed by observation results (OBX). The RE code is not necessary in the ORU message because it is expected that the OBR segments can be followed by observation results (OBX).</td><td/><td>Untersuchungsergebnisse folgen (in späteren Segmenten dieser Nachricht)</td></tr><tr><td style="white-space:nowrap">RF<a name="v2-0119-RF"> </a></td><td>Refill order/service request</td><td>Refill order/service request</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.
RF accommodates requests by either the filler or the placer. The filler may be requesting refill authorization from the placer. A placer system may be requesting a refill to be done by the filler system.
Typical responses include, but are not limited to: For a Filler request AF – Order/service refill request approval, DF – Order/service refill request denied; for a Placer request RE – Observations/Performed Service to follow, UF – Unable to refill.</td><td/><td/></tr><tr><td style="white-space:nowrap">RL<a name="v2-0119-RL"> </a></td><td>Release previous hold</td><td>Release previous hold</td><td>Placer Applications.</td><td>Placer Applications.</td><td/><td>Auftragsberabeitung wiederaufnehmen</td></tr><tr><td style="white-space:nowrap">RO<a name="v2-0119-RO"> </a></td><td>Replacement order</td><td>Replacement order</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.
A replacement is the substitution of one or more orders for one or more previously ordered services.
The replaced orders are treated as though they were canceled. If and when an ordered service can be replaced are local site-specific determinations.
Use the parent/child order control codes if the site specifies that the original order must remain intact. Do not use the replacement codes under this circumstance.
For each order to be replaced, use an ORC-1-order control value of RP (request for a replacement going to a filler) or RU (an unsolicited replacement created by the filler) used by the filler to notify the placer and/or other systems). By local agreement, the ORC segment (with RP or RU) may be followed by its original order detail segment. The ORC segments (with RP or RU) must be followed by an ORC segment with an ORC-1-order control value of RO (indicating the replacement order). By local agreement, the ORC with the RO value may be followed by an order detail segment.
For example, suppose that an ancillary application were replacing two OBR orders with three different orders. The sequence of segments would be as follows:
Seg Order Control Comment
ORC RU 1st replaced ORC
OBR 1st replaced order’s detail segment
ORC RU 2nd replaced ORC
OBR 2nd replaced order’s detail segment
ORC RO 1st replacement ORC
OBR 1st replacement order’s detail segment
ORC RO 2nd replacement ORC
OBR 2nd replacement order’s detail segment
ORC RO 3rd replacement ORC
OBR 3rd replacement order’s detail segment
Whether the OBR segments must be present is determined by the value of ORC-6-response flag.
The described replacement method will handle all possible cases of replacement: one into one, many into one, one into many, and many into many. If the placer sent this request to the filler with two RPs, and this was a response back from the filler to the placer, the two RUs (replaced unsolicited) would be two RQs (replaced as requested). (see figure 4-3)
Seg Order Control Comment
ORC RQ 1st replaced ORC
OBR 1st replaced order’s detail segment
ORC RQ 2nd replaced ORC
OBR 2nd replaced order’s detail segment
ORC RO 1st replacement ORC
OBR 1st replacement order’s detail segment
ORC RO 2nd replacement ORC
OBR 2nd replacement order’s detail segment
ORC RO 3rd replacement ORC
OBR 3rd replacement order’s detail segment
The replacement order code is sent by the filler application to another application indicating the exact replacement ordered service. It is used with the RP and RU order control codes as described above.
The rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).
In the case of the RU type (i.e., unsolicited replacement by the filler), the filler order number is generated as usual by the filler application. The placer order number is identical to the placer order number of the first transmitted ORC with an order control value of RU.
In the case of the RP type (i.e., a replacement request from another application to the filler), the placer order number is generated by the placer application using the procedure for new orders. The filler order number is generated by the filler application using the procedure identical for new orders.
If a replacement sequence is used in an ORU message (i.e., during results reporting), the following are the recommended segments to be used for the replacement orders:
ORC with an order control value of RO.
Any OBR segments (can be replaced by any order detail segments).
Optionally followed by observation result segments (OBX)
NTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message.</td><td/><td>Ersatzauftrag</td></tr><tr><td style="white-space:nowrap">RP<a name="v2-0119-RP"> </a></td><td>Order/service replace request</td><td>Order/service replace request</td><td>Placer Applications.</td><td>Placer Applications.
A replacement is the substitution of one or more orders for one or more previously ordered services. See comment 1 on RO – Replacement Order for further discussion.
The order replace request code permits the order filler to replace one or more new orders with one or more new orders, at the request of the placer application.
The rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).
In the case of the RU type (i.e., unsolicited replacement by the filler), the filler order number is generated as usual by the filler application. The placer order number is identical to the placer order number of the first transmitted ORC with an order control value of RU.
In the case of the RP type (i.e., a replacement request from another application to the filler), the placer order number is generated by the placer application using the procedure for new orders. The filler order number is generated by the filler application using the procedure identical for new orders.
If a replacement sequence is used in an ORU message (i.e., during results reporting), the following are the recommended segments to be used for the replacement orders:
a) ORC with an order control value of RO
b) Any OBR segments (can be replaced by any order detail segments)
c) Optionally followed by observation result segments (OBX)
d) NTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message</td><td/><td>Auftrag ersetzen</td></tr><tr><td style="white-space:nowrap">RQ<a name="v2-0119-RQ"> </a></td><td>Replaced as requested</td><td>Replaced as requested</td><td>Filler Applications.</td><td>Filler Applications.
A replacement is the substitution of one or more orders for one or more previously ordered services. See comment 1 on RO – Replacement Order for further discussion.
The order replace request code permits the order filler to replace one or more new orders with one or more new orders, at the request of the placer application.
The replacement order code is sent by the filler application to another application indicating the exact replacement ordered service. It is used with the RP and RU order control codes as described above.
The rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).
In the case of the RU type (i.e., unsolicited replacement by the filler), the filler order number is generated as usual by the filler application. The placer order number is identical to the placer order number of the first transmitted ORC with an order control value of RU.
In the case of the RP type (i.e., a replacement request from another application to the filler), the placer order number is generated by the placer application using the procedure for new orders. The filler order number is generated by the filler application using the procedure identical for new orders.
If a replacement sequence is used in an ORU message (i.e., during results reporting), the following are the recommended segments to be used for the replacement orders:
a) ORC with an order control value of RO
b) Any OBR segments (can be replaced by any order detail segments)
c) Optionally followed by observation result segments (OBX)
d) NTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message</td><td/><td>Auftrag anweisungsgemäß ersetzt</td></tr><tr><td style="white-space:nowrap">RR<a name="v2-0119-RR"> </a></td><td>Request received</td><td>Request received</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.
Left in for backward compatibility. In the current version it is equivalent to an accept acknowledgment. The request-received code indicates that an order message has been received and will be processed later. The order has not yet undergone the processing that would permit a more exact response.</td><td/><td>Anforderung erhalten</td></tr><tr><td style="white-space:nowrap">RU<a name="v2-0119-RU"> </a></td><td>Replaced unsolicited</td><td>Replaced unsolicited</td><td>Filler Applications.</td><td>Filler Applications.
A replacement is the substitution of one or more orders for one or more previously ordered services. See comment 1 on RO – Replacement Order for further discussion.
The unsolicited replacement code permits the filler application to notify another application without being requested from the placer application.
The rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).
In the case of the RU type (i.e., unsolicited replacement by the filler), the filler order number is generated as usual by the filler application. The placer order number is identical to the placer order number of the first transmitted ORC with an order control value of RU.
In the case of the RP type (i.e., a replacement request from another application to the filler), the placer order number is generated by the placer application using the procedure for new orders. The filler order number is generated by the filler application using the procedure identical for new orders.
If a replacement sequence is used in an ORU message (i.e., during results reporting), the following are the recommended segments to be used for the replacement orders:
a) ORC with an order control value of RO
b) Any OBR segments (can be replaced by any order detail segments)
c) Optionally followed by observation result segments (OBX)
d) NTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message</td><td/><td>Auftrag ersetzt (ohne Anweisung)</td></tr><tr><td style="white-space:nowrap">SC<a name="v2-0119-SC"> </a></td><td>Status changed</td><td>Status changed</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.</td><td/><td>Statusänderung</td></tr><tr><td style="white-space:nowrap">SN<a name="v2-0119-SN"> </a></td><td>Send order/service number</td><td>Send order/service number</td><td>Placer Applications.</td><td>Placer Applications.<p>See comments for NA - Number Assigned.</td><td>See comments for NA - Number Assigned.</td><td>Auftrags- bzw. Bearbeitungsnummer zuweisen / übermitteln</td></tr><tr><td style="white-space:nowrap">SQ<a name="v2-0119-SQ"> </a></td><td>Supplemented as requested</td><td>Supplementation confirmation message indicating that an order was supplemented as requested.</td><td>This code is used in the acknowledgment response to the request messages.</td><td/><td/><td/></tr><tr><td style="white-space:nowrap">SR<a name="v2-0119-SR"> </a></td><td>Response to send order/service status request</td><td>Response to send order/service status request</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Auftragsstatus (Antwort)</td></tr><tr><td style="white-space:nowrap">SS<a name="v2-0119-SS"> </a></td><td>Send order/service status request</td><td>Send order/service status request</td><td>Placer Applications.</td><td>Placer Applications.</td><td/><td>Auftragsstatus senden</td></tr><tr><td style="white-space:nowrap">SU<a name="v2-0119-SU"> </a></td><td>Supplement this order</td><td>Identifies existing orders to be supplemented in Supplementation Recommendation (filler to placer) and Supplementation Request (placer to filler) messages.</td><td>For example this code is used in the filler’s order message to identify an order that is missing a recommended order based on organizational protocol for example as described in the IHE Laboratory Communication (LCC) profile (LAB-6).</td><td/><td/><td/></tr><tr><td style="white-space:nowrap">UA<a name="v2-0119-UA"> </a></td><td>Unable to accept order/service</td><td>Unable to accept order/service</td><td>Filler Applications.</td><td>Filler Applications.
An unable to accept code is used when a new order cannot be accepted by the filler. Possible reasons include requesting a prescription for a drug which the patient is allergic to or for an order which requires certain equipment resources which are not available such that the order cannot be filled. Note that this is different from the communication level acceptance as defined within the MSA segment.</td><td/><td>Auftragsannahme nicht möglich</td></tr><tr><td style="white-space:nowrap">UC<a name="v2-0119-UC"> </a></td><td>Unable to cancel</td><td>Unable to cancel</td><td>Filler or Placer Applications.</td><td>Filler or Placer Applications.
An unable-to-cancel code is used when the ordered service is at a point that it cannot be canceled by the placer or filler or when local rules prevent cancellation by the filler. The use of this code is dependent on the value of ORC-6-response flag.
If the filler initiated the request to cancel and the placer is unable to cancel while the filler cannot proceed with the fulfillment of that order, then the necessary communication to resolve the conflict is outside the scope of these messages.</td><td/><td>Auftragsstornierung nicht möglich</td></tr><tr><td style="white-space:nowrap">UD<a name="v2-0119-UD"> </a></td><td>Unable to discontinue</td><td>Unable to discontinue</td><td>Filler or Placer Applications.</td><td>Filler or Placer Applications.
An unable-to-discontinue code is used when the ordered service is at a point that it cannot be discontinued by the placer or filler or when local rules prevent discontinuance by the filler. The use of this code is dependent on the value of ORC-6-response flag.
If the filler initiated the request to discontinue and the placer is unable to discontinue while the filler cannot proceed with the fulfillment of that order, then the necessary communication to resolve the conflict is outside the scope of these messages.</td><td/><td>Abbrechen nicht möglich</td></tr><tr><td style="white-space:nowrap">UF<a name="v2-0119-UF"> </a></td><td>Unable to refill</td><td>Unable to refill</td><td>Filler Applications.</td><td>Filler Applications.<p>Negative response to RF Refill order/service request, indicating that the receiving application was not able to complete the refill request.</td><td>Negative response to RF Refill order/service request, indicating that the receiving application was not able to complete the refill request.</td><td/></tr><tr><td style="white-space:nowrap">UH<a name="v2-0119-UH"> </a></td><td>Unable to put on hold</td><td>Unable to put on hold</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Aussetzen nicht möglich</td></tr><tr><td style="white-space:nowrap">UM<a name="v2-0119-UM"> </a></td><td>Unable to replace</td><td>Unable to replace</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Ersetzen nicht möglich</td></tr><tr><td style="white-space:nowrap">UN<a name="v2-0119-UN"> </a></td><td>Unlink order/service from patient care problem or goal</td><td>Unlink order/service from patient care problem or goal</td><td>Placer or Filler Applications.</td><td>Placer or Filler Applications.<p>Refer to Chapter 12 Patient Care for complete discussion.</td><td>Refer to Chapter 12 Patient Care for complete discussion.</td><td/></tr><tr><td style="white-space:nowrap">UR<a name="v2-0119-UR"> </a></td><td>Unable to release</td><td>Unable to release</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Wiederaufnahme nicht möglich</td></tr><tr><td style="white-space:nowrap">UX<a name="v2-0119-UX"> </a></td><td>Unable to change</td><td>Unable to change</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Änderung nicht möglich</td></tr><tr><td style="white-space:nowrap">XO<a name="v2-0119-XO"> </a></td><td>Change order/service request</td><td>Change order/service request</td><td>Placer Applications.</td><td>Placer Applications.</td><td/><td>Auftrag ändern</td></tr><tr><td style="white-space:nowrap">XR<a name="v2-0119-XR"> </a></td><td>Changed as requested</td><td>Changed as requested</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Auftrag anweisungsgemäß geändert</td></tr><tr><td style="white-space:nowrap">XX<a name="v2-0119-XX"> </a></td><td>Order/service changed, unsol.</td><td>Order/service changed, unsol.</td><td>Filler Applications.</td><td>Filler Applications.</td><td/><td>Auftrag geändert (ohne Anweisung)</td></tr></table></div>
</text>
<url value="http://terminology.hl7.org/CodeSystem/v2-0119"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.18.48"/>
</identifier>
<version value="2.0.0"/>
<name value="OrderControlCodes"/>
<title value="orderControlCodes"/>
<status value="active"/>
<experimental value="false"/>
<date value="2019-12-01"/>
<publisher value="Health Level Seven International"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="hq@HL7.org"/>
</telecom>
</contact>
<description
value="HL7-defined code system of concepts which are used to determine the function of the order segment. Depending on the message, the action specified by one of these control codes may refer to an order or an individual service. Used in Version 2.x messaging of orders in the ORC segment."/>
<purpose
value="Underlying Master Code System for V2 table 0119 (Order Control Codes)"/>
<copyright
value="This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html"/>
<caseSensitive value="true"/>
<valueSet value="http://terminology.hl7.org/ValueSet/v2-0119"/>
<hierarchyMeaning value="is-a"/>
<compositional value="false"/>
<versionNeeded value="false"/>
<content value="complete"/>
<property>
<code value="status"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#status"/>
<description value="Status of the concept"/>
<type value="code"/>
</property>
<property>
<code value="deprecated"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecated"/>
<description value="Version of HL7 in which the code was deprecated"/>
<type value="code"/>
</property>
<property>
<code value="v2-concComment"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment"/>
<description value="V2 Concept Comment"/>
<type value="string"/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub"/>
<description value="V2 Concept Comment As Published"/>
<type value="string"/>
</property>
<property>
<code value="HL7usageNotes"/>
<uri
value="http://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotes"/>
<description value="HL7 Concept Usage Notes"/>
<type value="string"/>
</property>
<concept id="1359">
<code value="AF"/>
<display value="Order/service refill request approval"/>
<definition
value="AF is a response to RF where the placer authorizing a refill or quantity of refills."/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications ."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.<p>AF is a response to RF where the placer authorizing a refill or quantity of refills."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1360">
<code value="CA"/>
<display value="Cancel order/service request"/>
<definition value="Cancel order/service request"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag stornieren"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications"/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.
A cancellation is a request by the placer for the filler, or the filler to the placer, not to do a previously ordered service. Confirmation of the cancellation request is provided by the filler or placer, e.g., a message with an ORC-1-order control value of CR.
Typical responses include, but are not limited to, CR – Cancelled as requested, UC – Unable to Cancel."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1361">
<code value="CH"/>
<display value="Child order/service"/>
<definition value="Child order/service"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="nachgeordneter Auftrag"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.<p>Used in conjunction with the PA - Parent order control code. Refer to PA order control code for discussion."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="Used in conjunction with the PA - Parent order control code. Refer to PA order control code for discussion."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1362">
<code value="CN"/>
<display value="Combined result"/>
<definition value="Combined result"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Kumulatives Ergebnis (zu mehreren Aufträgen)"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.
The combined result code provides a mechanism to transmit results that are associated with two or more orders. This situation occurs commonly in radiology reports when the radiologist dictates a single report for two or more exams represented as two or more orders. For example, knee and hand films for a rheumatoid arthritis patient might generate a single dictation on the part of the radiologist.
When such results are reported the CN code replaces the RE code in all but the last ORC, and the results follow the last ORC and its OBR. An example follows of a single report following three ORCs:
MSH|...<cr>
PID|...<cr>
ORC|CN|...<cr>
OBR|1|A4461XA^HIS|81641^RAD|73666^Bilateral Feet|...<cr>
ORC|CN|...<cr>
OBR|2|A4461XB^HIS|81642^RAD|73642^Bilateral Hand PA|...<cr>
ORC|RE|...<cr>
OBR|3|A4461XC^HIS|81643^RAD|73916^Bilateral Knees|...<cr>
OBX|1|CE|73916&IMP|1|Radiologist’s Impression|...<cr>
OBX|2|CE|73642&IMP|1|Radiologist’s Impression|...<cr>
OBX|3|FT|73642&GDT|1|Description|...<cr>"/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1363">
<code value="CP"/>
<display value="Cancel process step"/>
<definition value="Cancel process step"/>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.
The control code CP – Cancel process step should be used in the ORC-1 for communication Filler-to-Filler, e.g., LIS-to-Analyzer, to differentiate from code CA (Placer-to-Filler).
The Filler should response with an acceptance of the cancellation using ORC-1 = CR and ORC-5 = CA."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1364">
<code value="CR"/>
<display value="Canceled as requested"/>
<definition value="Canceled as requested"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag anweisungsgemäß storniert"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler or Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler or Placer Applications.<p>A response by the filler or placer application that a request to cancel (CA by the placer application) was performed successfully."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="A response by the filler or placer application that a request to cancel (CA by the placer application) was performed successfully."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1365">
<code value="DC"/>
<display value="Discontinue order/service request"/>
<definition value="Discontinue order/service request"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsausführung abbrechen"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.
A request by the placer for the filler, or the filler to the placer, to discontinue a previously requested service. The differentiation between discontinue and cancel is that discontinue effects the order/service and all future occurrences, cancel refers to just the present action.
Typical responses include, but are not limited to, CR – Cancelled as requested, UC – Unable to Cancel."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1366">
<code value="DE"/>
<display value="Data errors"/>
<definition value="Data errors"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Datenfehler"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1367">
<code value="DF"/>
<display value="Order/service refill request denied"/>
<definition value="Order/service refill request denied"/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.
In response to a Filler application requesting refill authorization (RF), DF indicates that the placer does not authorize refills for the order. ORC-16 Order Control Code reason may be used to indicate the reason for the request denial. Some suggested values include:
AA Patient unknown to the provider
AB Patient never under provider care
AC Patient no longer under provider care
AD Patient has requested refill too soon
AE Medication never prescribed for the patient
AF Patient should contact provider first
AG Refill not appropriate
Note that these values originate from the NCPDP SCRIPT Response Segment Code List Qualifiers. Materials Reproduced with the consent of ©National Council for Prescription Drug Programs, Inc. 1988, 1992, 2002 NCPDP."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1368">
<code value="DR"/>
<display value="Discontinued as requested"/>
<definition value="Discontinued as requested"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsausführung anweisungsgemäß abgebrochen"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler or Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler or Placer Applications.<p>The filler or placer, in response to a request to discontinue (DC from the placer or filler application), has discontinued the order/service."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="The filler or placer, in response to a request to discontinue (DC from the placer or filler application), has discontinued the order/service."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1369">
<code value="FU"/>
<display value="Order/service refilled, unsolicited"/>
<definition value="Order/service refilled, unsolicited"/>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.<p>FU notifies the placer that the filler issued a refill for the order at the patient's request."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="FU notifies the placer that the filler issued a refill for the order at the patient's request."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1370">
<code value="HD"/>
<display value="Hold order request"/>
<definition value="Hold order request"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsbearbeitung aussetzen"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.<p>Typical responses include, but are not limited to, CR - Cancelled as requested, UC - Unable to Cancel."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="Typical responses include, but are not limited to, CR - Cancelled as requested, UC - Unable to Cancel."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1371">
<code value="HR"/>
<display value="On hold as requested"/>
<definition value="On hold as requested"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsbearbeitung anweisungsgemäß ausgesetzt"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1372">
<code value="LI"/>
<display value="Link order/service to patient care problem or goal"/>
<definition value="Link order/service to patient care problem or goal"/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.<p>Refer to Chapter 12 Patient Care for complete discussion."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="Refer to Chapter 12 Patient Care for complete discussion."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1373">
<code value="MC"/>
<display value="Miscellaneous Charge - not associated with an order"/>
<definition value="Miscellaneous Charge - not associated with an order"/>
<property>
<code value="v2-concComment"/>
<valueString value="applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11"/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11"/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString value="applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11"/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1374">
<code value="NA"/>
<display value="Number assigned"/>
<definition value="Number assigned"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Nummer zugewiesen"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.
There are three circumstances that involve requesting an order number (ORC-2-placer order number or ORC-3-filler order number):
(1) When the filler application needs to request an ORC-3-filler order number from a centralized application (e.g., HIS).
SN – The send order number code provides a mechanism for the filler to request an ORC-3-filler order number from some centralized application (called “other” in the table below), such as a central HIS, by sending an ORM message containing an ORC-1-order control value of SN. This ORC has a null ORC-3-filler order number and an ORC-2-placer order number created by the filler application when the filler originates the order.
The order (SN type) message can be acknowledged by either one of two methods:
a) By an order application acknowledgement message containing an ORC-1-order control value of OK. Then an unsolicited order message can be sent at a future time, containing an ORC with ORC-1-order control value of NA to provide the actual number assigned.
b) By an order acknowledgement message containing an ORC-1-order control value of NA as described below.
NA – The number assigned code allows the “other” application to notify the filler application of the newly-assigned filler order number. ORC-1-order control contains value of NA, ORC-2-placer order number (from the ORC with the SN value), and the newly-assigned filler order number.
Code From ORC-2-Placer Order Number ORC-3-Filler Order Number
SN filler application placer order number^filler application ID Null
NA other application placer order number^filler application ID filler order number^filler application ID
Note: Both the placer order number and the filler order number have the filler’s application ID
(2) When the filler application needs to request an ORC-2-placer order number from some other application (e.g., Order Entry).
SN – The send order number code provides a mechanism for the filler application to request an ORC-2-placer order number from another application (called “other” in the table below) by sending an order message containing an ORC-1-order control value of SN. This ORC has a null ORC-2-placer order number and an ORC-3-filler order number created by the filler application when the filler originates the order.
The order (SN type) message can be acknowledged by two methods:
a) By an order application acknowledgement message containing an ORC-1-order control value of OK. Then an unsolicited order message can be sent at a future time, containing an ORC-1-order control value of NA to provide the actual number assigned.
b) By an order acknowledgement message containing an ORC-1-order control value of NA as described below.
NA – The number assigned code allows the “other” application to notify the filler application of the newly-assigned ORC-2-placer order number. The ORC contains an ORC-1-order control value of NA, the newly-assigned ORC-2-placer order number, and the ORC-3-filler order number (from the ORC with the SN value).
Code From ORC-2-Placer Order Number ORC-3-Filler Order Number
SN filler application null filler order number^filler application ID
NA other application placer order number^placer application ID filler order number^filler application ID
Note: The new ORC-2-placer order number has the placer’s application ID
(3) When an application (not the filler application) wants to assign an ORC-3-filler order number for a new order.
NW – When the application creating an order (not the filler application) wants to assign a filler order number for a new order.
or
RO – (RO following an RP). In this case, the “other” application completes ORC-3-filler order number, using the filler application ID as the second component of the filler order number.
Code From ORC-2-Placer Order Number ORC-3-Filler Order Number
NW or RO Other application to filler application placer order number^placer application ID filler order number^filler application ID"/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1375">
<code value="NR"/>
<display value="Notification Received"/>
<definition
value="Notifies the Filler that the Placer received a cancellation, discontinuance, or other state change notice"/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1376">
<code value="NW"/>
<display value="New order/service"/>
<definition value="New order/service"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Neuer Auftrag"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.<p>See comments for NA - Number Assigned."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString value="See comments for NA - Number Assigned."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1377">
<code value="OC"/>
<display value="Order/service canceled"/>
<definition value="Order/service canceled"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag storniert"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1378">
<code value="OD"/>
<display value="Order/service discontinued"/>
<definition value="Order/service discontinued"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsausführung abgebrochen"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1379">
<code value="OE"/>
<display value="Order/service released"/>
<definition value="Order/service released"/>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1380">
<code value="OF"/>
<display value="Order/service refilled as requested"/>
<definition value="Order/service refilled as requested"/>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.<p>OF directly responds to the placer system's request for a refill."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="OF directly responds to the placer system's request for a refill."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1381">
<code value="OH"/>
<display value="Order/service held"/>
<definition value="Order/service held"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsbearbeitung ausgesetzt"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1382">
<code value="OK"/>
<display value="Order/service accepted & OK"/>
<definition value="Order/service accepted & OK"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag akzeptiert"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.<p>See comments for NA - Number Assigned."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString value="See comments for NA - Number Assigned."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1383">
<code value="OP"/>
<display value="Notification of order for outside dispense"/>
<definition value="Notification of order for outside dispense"/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.
These order control codes are used to communicate an order between systems where the order is intended for informational purposes. For example, an order that will be performed by a vendor outside the enterprise of communicating systems. The communicating systems may need to maintain information relative to the order for clinical continuity, but no actions to perform the ordered service are intended.
OP represents an informational version of NW, PY represents the informational-only version of RO. NW and RO table notes also apply to OP and PY, respectively."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1384">
<code value="OR"/>
<display value="Released as requested"/>
<definition value="Released as requested"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsbearbeitung anweisungsgemäß wiederaufgenommen"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1385">
<code value="PA"/>
<display value="Parent order/service"/>
<definition value="Parent order/service"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Hauptauftrag"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.
The parent (PA) and child (CH) order control codes allow the spawning of “child” orders from a “parent” order without changing the parent (original order). One or more ORC segments with an ORC-1-order control value of PA are followed by one or more ORC segments with an ORC-1-order control value of CH. Whether OBR segments must be present is determined by the value of ORC-6-response flag.
For example, suppose that a microbiology culture produced two organisms and corresponding susceptibility reports. Then the sequence of segments would be as follows: (see figure 4-4)
The assignment of placer order numbers in the parent-child paradigm depends on whether the placer or filler creates the child order and in the latter case, on whether the placer supports the SN/NA transaction. If the placer creates the child orders it will assign their placer order numbers according to its usual procedures. If the filler creates the child orders there are two possibilities: each child will inherit the placer order number of its parent, or the filler will use the SN/NA transaction to request that the placer assign a placer order number. In either case, the filler application creates the filler order numbers of the children according to its usual procedures.
Whenever a child order is transmitted in a message the ORC segment’s ORC-8-parent is valued with the parent’s filler order number (if originating from the filler) and with the parent’s placer order number (if originating from the filler or if originating from the placer).
The parent child mechanism can be used to “expand” a parent order (e.g., an order for three EKGs on successive mornings)."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1386">
<code value="PR"/>
<display value="Previous Results with new order/service"/>
<definition value="Previous Results with new order/service"/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.
PR indicates that this ORC is part of an ORU structure containing previous observation, which is embedded in the order.
At least two main use cases require that the complete results of the previous observations be transmitted with the order.
• Diagnostic laboratories referring tests to another lab for either confirmation of results (HIV, etc.) or due to not being equipped to do the tests (genetic testing, etc.).
• Diagnostic laboratories sending test results to Knowledge Bases for the automated generation of diagnostic comments for inclusion into the lab report."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1387">
<code value="PY"/>
<display value="Notification of replacement order for outside dispense"/>
<definition
value="Notification of replacement order for outside dispense"/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.<p>See comments for OP - Notification of order for outside dispense."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="See comments for OP - Notification of order for outside dispense."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1388">
<code value="RA"/>
<display value="Recommendation Accepted"/>
<definition
value="Identifies that this previously recommended replacement order has been accepted"/>
<property>
<code value="v2-concComment"/>
<valueString
value="Placer Applications:
Used in the Recommendation Accepted message; includes the assigned placer order number for the accepted replacement order
Filler Applications:
Used in the acknowledgment response message to the Recommendation Accepted message"/>
</property>
<property>
<code value="status"/>
<valueCode value="N"/>
</property>
</concept>
<concept id="1389">
<code value="RC"/>
<display value="Recommended Change"/>
<definition
value="Identifies that this OBR represents a recommended replacement order"/>
<property>
<code value="v2-concComment"/>
<valueString
value="Filler Applications.
Used in the recommendation message sent to the placer"/>
</property>
<property>
<code value="status"/>
<valueCode value="N"/>
</property>
</concept>
<concept id="1390">
<code value="RD"/>
<display value="Recommendation Declined"/>
<definition
value="Identifies that this previously sent recommended replacement order has been declined"/>
<property>
<code value="v2-concComment"/>
<valueString
value="Placer Applications:
Used in the Recommendation Declined message
Filler Applications:
Used in the acknowledgment response message to the Recommendation Declined message"/>
</property>
<property>
<code value="status"/>
<valueCode value="N"/>
</property>
</concept>
<concept id="1391">
<code value="RE"/>
<display value="Observations/Performed Service to follow"/>
<definition value="Observations/Performed Service to follow"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value
value="Untersuchungsergebnisse folgen (in späteren Segmenten dieser Nachricht)"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.
The observations-to-follow code is used to transmit patient-specific information with an order. An order detail segment (e.g., OBR) can be followed by one or more observation segments (OBX). Any observation that can be transmitted in an ORU message can be transmitted with this mechanism. When results are transmitted with an order, the results should immediately follow the order or orders that they support.
The following example shows the sequence of segments for three Pharmacy orders. It illustrates the use of the RE code:
Segment Order Control Comment
MSH
PID
ORC NW First new order
RXO First order segment
ORC NW 2nd new order
RXO 2nd order segment
[ORC RE Patient-specific observation, optional in V 2.2
OBR] Observation OBR, optional in V 2.2
OBX An observation segment
OBX Another observation segment
OBX Another observation segment
OBX Another observation segment
ORC NW 3rd order
RXO 3rd order segment
In this version of HL7, results can be transmitted with an order as one or more OBX segments without the necessity of including the ORC and OBR segments.
Observations can be transmitted in an ORU message without using an ORC. There are times when it is necessary to transmit information not included in the OBR segments of the ORU message. In this case, it is recommended that the ORC be included in the ORU message.
The order control value of RE is required only in ORM messages to indicate that an order is followed by observation results (OBX). The RE code is not necessary in the ORU message because it is expected that the OBR segments can be followed by observation results (OBX)."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1392">
<code value="RF"/>
<display value="Refill order/service request"/>
<definition value="Refill order/service request"/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.
RF accommodates requests by either the filler or the placer. The filler may be requesting refill authorization from the placer. A placer system may be requesting a refill to be done by the filler system.
Typical responses include, but are not limited to: For a Filler request AF – Order/service refill request approval, DF – Order/service refill request denied; for a Placer request RE – Observations/Performed Service to follow, UF – Unable to refill."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1393">
<code value="RL"/>
<display value="Release previous hold"/>
<definition value="Release previous hold"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsberabeitung wiederaufnehmen"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1394">
<code value="RO"/>
<display value="Replacement order"/>
<definition value="Replacement order"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Ersatzauftrag"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.
A replacement is the substitution of one or more orders for one or more previously ordered services.
The replaced orders are treated as though they were canceled. If and when an ordered service can be replaced are local site-specific determinations.
Use the parent/child order control codes if the site specifies that the original order must remain intact. Do not use the replacement codes under this circumstance.
For each order to be replaced, use an ORC-1-order control value of RP (request for a replacement going to a filler) or RU (an unsolicited replacement created by the filler) used by the filler to notify the placer and/or other systems). By local agreement, the ORC segment (with RP or RU) may be followed by its original order detail segment. The ORC segments (with RP or RU) must be followed by an ORC segment with an ORC-1-order control value of RO (indicating the replacement order). By local agreement, the ORC with the RO value may be followed by an order detail segment.
For example, suppose that an ancillary application were replacing two OBR orders with three different orders. The sequence of segments would be as follows:
Seg Order Control Comment
ORC RU 1st replaced ORC
OBR 1st replaced order’s detail segment
ORC RU 2nd replaced ORC
OBR 2nd replaced order’s detail segment
ORC RO 1st replacement ORC
OBR 1st replacement order’s detail segment
ORC RO 2nd replacement ORC
OBR 2nd replacement order’s detail segment
ORC RO 3rd replacement ORC
OBR 3rd replacement order’s detail segment
Whether the OBR segments must be present is determined by the value of ORC-6-response flag.
The described replacement method will handle all possible cases of replacement: one into one, many into one, one into many, and many into many. If the placer sent this request to the filler with two RPs, and this was a response back from the filler to the placer, the two RUs (replaced unsolicited) would be two RQs (replaced as requested). (see figure 4-3)
Seg Order Control Comment
ORC RQ 1st replaced ORC
OBR 1st replaced order’s detail segment
ORC RQ 2nd replaced ORC
OBR 2nd replaced order’s detail segment
ORC RO 1st replacement ORC
OBR 1st replacement order’s detail segment
ORC RO 2nd replacement ORC
OBR 2nd replacement order’s detail segment
ORC RO 3rd replacement ORC
OBR 3rd replacement order’s detail segment
The replacement order code is sent by the filler application to another application indicating the exact replacement ordered service. It is used with the RP and RU order control codes as described above.
The rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).
In the case of the RU type (i.e., unsolicited replacement by the filler), the filler order number is generated as usual by the filler application. The placer order number is identical to the placer order number of the first transmitted ORC with an order control value of RU.
In the case of the RP type (i.e., a replacement request from another application to the filler), the placer order number is generated by the placer application using the procedure for new orders. The filler order number is generated by the filler application using the procedure identical for new orders.
If a replacement sequence is used in an ORU message (i.e., during results reporting), the following are the recommended segments to be used for the replacement orders:
ORC with an order control value of RO.
Any OBR segments (can be replaced by any order detail segments).
Optionally followed by observation result segments (OBX)
NTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1395">
<code value="RP"/>
<display value="Order/service replace request"/>
<definition value="Order/service replace request"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag ersetzen"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.
A replacement is the substitution of one or more orders for one or more previously ordered services. See comment 1 on RO – Replacement Order for further discussion.
The order replace request code permits the order filler to replace one or more new orders with one or more new orders, at the request of the placer application.
The rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).
In the case of the RU type (i.e., unsolicited replacement by the filler), the filler order number is generated as usual by the filler application. The placer order number is identical to the placer order number of the first transmitted ORC with an order control value of RU.
In the case of the RP type (i.e., a replacement request from another application to the filler), the placer order number is generated by the placer application using the procedure for new orders. The filler order number is generated by the filler application using the procedure identical for new orders.
If a replacement sequence is used in an ORU message (i.e., during results reporting), the following are the recommended segments to be used for the replacement orders:
a) ORC with an order control value of RO
b) Any OBR segments (can be replaced by any order detail segments)
c) Optionally followed by observation result segments (OBX)
d) NTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message"/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1396">
<code value="RQ"/>
<display value="Replaced as requested"/>
<definition value="Replaced as requested"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag anweisungsgemäß ersetzt"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.
A replacement is the substitution of one or more orders for one or more previously ordered services. See comment 1 on RO – Replacement Order for further discussion.
The order replace request code permits the order filler to replace one or more new orders with one or more new orders, at the request of the placer application.
The replacement order code is sent by the filler application to another application indicating the exact replacement ordered service. It is used with the RP and RU order control codes as described above.
The rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).
In the case of the RU type (i.e., unsolicited replacement by the filler), the filler order number is generated as usual by the filler application. The placer order number is identical to the placer order number of the first transmitted ORC with an order control value of RU.
In the case of the RP type (i.e., a replacement request from another application to the filler), the placer order number is generated by the placer application using the procedure for new orders. The filler order number is generated by the filler application using the procedure identical for new orders.
If a replacement sequence is used in an ORU message (i.e., during results reporting), the following are the recommended segments to be used for the replacement orders:
a) ORC with an order control value of RO
b) Any OBR segments (can be replaced by any order detail segments)
c) Optionally followed by observation result segments (OBX)
d) NTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message"/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1397">
<code value="RR"/>
<display value="Request received"/>
<definition value="Request received"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Anforderung erhalten"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.
Left in for backward compatibility. In the current version it is equivalent to an accept acknowledgment. The request-received code indicates that an order message has been received and will be processed later. The order has not yet undergone the processing that would permit a more exact response."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1398">
<code value="RU"/>
<display value="Replaced unsolicited"/>
<definition value="Replaced unsolicited"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag ersetzt (ohne Anweisung)"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.
A replacement is the substitution of one or more orders for one or more previously ordered services. See comment 1 on RO – Replacement Order for further discussion.
The unsolicited replacement code permits the filler application to notify another application without being requested from the placer application.
The rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).
In the case of the RU type (i.e., unsolicited replacement by the filler), the filler order number is generated as usual by the filler application. The placer order number is identical to the placer order number of the first transmitted ORC with an order control value of RU.
In the case of the RP type (i.e., a replacement request from another application to the filler), the placer order number is generated by the placer application using the procedure for new orders. The filler order number is generated by the filler application using the procedure identical for new orders.
If a replacement sequence is used in an ORU message (i.e., during results reporting), the following are the recommended segments to be used for the replacement orders:
a) ORC with an order control value of RO
b) Any OBR segments (can be replaced by any order detail segments)
c) Optionally followed by observation result segments (OBX)
d) NTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message"/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1399">
<code value="SC"/>
<display value="Status changed"/>
<definition value="Status changed"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Statusänderung"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1400">
<code value="SN"/>
<display value="Send order/service number"/>
<definition value="Send order/service number"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value
value="Auftrags- bzw. Bearbeitungsnummer zuweisen / übermitteln"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer Applications.<p>See comments for NA - Number Assigned."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString value="See comments for NA - Number Assigned."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1401">
<code value="SQ"/>
<display value="Supplemented as requested"/>
<definition
value="Supplementation confirmation message indicating that an order was supplemented as requested."/>
<property>
<code value="v2-concComment"/>
<valueString
value="This code is used in the acknowledgment response to the request messages."/>
</property>
<property>
<code value="status"/>
<valueCode value="N"/>
</property>
</concept>
<concept id="1402">
<code value="SR"/>
<display value="Response to send order/service status request"/>
<definition value="Response to send order/service status request"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsstatus (Antwort)"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1403">
<code value="SS"/>
<display value="Send order/service status request"/>
<definition value="Send order/service status request"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsstatus senden"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1404">
<code value="SU"/>
<display value="Supplement this order"/>
<definition
value="Identifies existing orders to be supplemented in Supplementation Recommendation (filler to placer) and Supplementation Request (placer to filler) messages."/>
<property>
<code value="v2-concComment"/>
<valueString
value="For example this code is used in the filler’s order message to identify an order that is missing a recommended order based on organizational protocol for example as described in the IHE Laboratory Communication (LCC) profile (LAB-6)."/>
</property>
<property>
<code value="status"/>
<valueCode value="N"/>
</property>
</concept>
<concept id="1405">
<code value="UA"/>
<display value="Unable to accept order/service"/>
<definition value="Unable to accept order/service"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsannahme nicht möglich"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.
An unable to accept code is used when a new order cannot be accepted by the filler. Possible reasons include requesting a prescription for a drug which the patient is allergic to or for an order which requires certain equipment resources which are not available such that the order cannot be filled. Note that this is different from the communication level acceptance as defined within the MSA segment."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1406">
<code value="UC"/>
<display value="Unable to cancel"/>
<definition value="Unable to cancel"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftragsstornierung nicht möglich"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler or Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler or Placer Applications.
An unable-to-cancel code is used when the ordered service is at a point that it cannot be canceled by the placer or filler or when local rules prevent cancellation by the filler. The use of this code is dependent on the value of ORC-6-response flag.
If the filler initiated the request to cancel and the placer is unable to cancel while the filler cannot proceed with the fulfillment of that order, then the necessary communication to resolve the conflict is outside the scope of these messages."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1407">
<code value="UD"/>
<display value="Unable to discontinue"/>
<definition value="Unable to discontinue"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Abbrechen nicht möglich"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler or Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler or Placer Applications.
An unable-to-discontinue code is used when the ordered service is at a point that it cannot be discontinued by the placer or filler or when local rules prevent discontinuance by the filler. The use of this code is dependent on the value of ORC-6-response flag.
If the filler initiated the request to discontinue and the placer is unable to discontinue while the filler cannot proceed with the fulfillment of that order, then the necessary communication to resolve the conflict is outside the scope of these messages."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1408">
<code value="UF"/>
<display value="Unable to refill"/>
<definition value="Unable to refill"/>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Filler Applications.<p>Negative response to RF Refill order/service request, indicating that the receiving application was not able to complete the refill request."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="Negative response to RF Refill order/service request, indicating that the receiving application was not able to complete the refill request."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1409">
<code value="UH"/>
<display value="Unable to put on hold"/>
<definition value="Unable to put on hold"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Aussetzen nicht möglich"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1410">
<code value="UM"/>
<display value="Unable to replace"/>
<definition value="Unable to replace"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Ersetzen nicht möglich"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1411">
<code value="UN"/>
<display value="Unlink order/service from patient care problem or goal"/>
<definition
value="Unlink order/service from patient care problem or goal"/>
<property>
<code value="v2-concComment"/>
<valueString value="Placer or Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString
value="Placer or Filler Applications.<p>Refer to Chapter 12 Patient Care for complete discussion."/>
</property>
<property>
<code value="HL7usageNotes"/>
<valueString
value="Refer to Chapter 12 Patient Care for complete discussion."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1412">
<code value="UR"/>
<display value="Unable to release"/>
<definition value="Unable to release"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Wiederaufnahme nicht möglich"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1413">
<code value="UX"/>
<display value="Unable to change"/>
<definition value="Unable to change"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Änderung nicht möglich"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1414">
<code value="XO"/>
<display value="Change order/service request"/>
<definition value="Change order/service request"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag ändern"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Placer Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1415">
<code value="XR"/>
<display value="Changed as requested"/>
<definition value="Changed as requested"/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag anweisungsgemäß geändert"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
<concept id="1416">
<code value="XX"/>
<display value="Order/service changed, unsol."/>
<definition value="Order/service changed, unsol."/>
<designation>
<language value="de"/>
<use>
<system
value="http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"/>
<code value="preferredForLanguage"/>
</use>
<value value="Auftrag geändert (ohne Anweisung)"/>
</designation>
<property>
<code value="v2-concComment"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="v2-concCommentAsPub"/>
<valueString value="Filler Applications."/>
</property>
<property>
<code value="status"/>
<valueCode value="A"/>
</property>
</concept>
</CodeSystem>
IG © 2020+ HL7 International - Vocabulary Work Group. Package hl7.terminology#6.0.1 based on FHIR 5.0.0. Generated 2024-07-18
Links: Table of Contents |
QA Report
| Version History 
|
|
Propose a change