HL7 Terminology
1.0.0 - Publication

This page is part of the HL7 Terminology (v1.0.0: Release) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

orderControlCodes

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/v2-0119
Version:2.8.0
Name:OrderControlCodes
Title:orderControlCodes
Status:Active
Content:All the concepts defined by the code system are included in the code system resource
Definition:

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.

Publisher:HL7, Inc
OID:2.16.840.1.113883.18.48 (for OID based terminology systems)
Content Mode:Complete
Value Set:http://terminology.hl7.org/ValueSet/v2-0119 ( is the value set for all codes in this code system)
Copyright:

Copyright HL7. Licensed under creative commons public domain

Source Resource:XML / JSON / Turtle

This Code system is referenced in the content logical definition of the following value sets:

orderControlCodes

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.

Copyright Statement: Copyright HL7. Licensed under creative commons public domain

Properties

CodeURLDescriptionType
statushttp://terminology.hl7.org/CodeSystem/utg-concept-properties#statusStatus of the conceptcode
deprecatedhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-table-deprecatedVersion of HL7 in which the code was deprecatedcode
v2-concCommenthttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentV2 Concept Commentstring
v2-concCommentAsPubhttp://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPubV2 Concept Comment As Publishedstring
HL7usageNoteshttp://terminology.hl7.org/CodeSystem/utg-concept-properties#HL7usageNotesHL7 Concept Usage Notesstring

This code system http://terminology.hl7.org/CodeSystem/v2-0119 defines the following codes:

CodeDisplayDefinitionV2 Table StatusV2 Concept CommentV2 Concept Comment As PublishedHL7 Concept Usage Notes
AF Order/service refill request approvalAF is a response to RF where the placer authorizing a refill or quantity of refills.APlacer Applications .Placer Applications.<p>AF is a response to RF where the placer authorizing a refill or quantity of refills.
CA Cancel order/service requestCancel order/service requestAPlacer or Filler ApplicationsPlacer 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.
CH Child order/serviceChild order/serviceAPlacer or Filler Applications.Placer or Filler Applications.<p>Used in conjunction with the PA - Parent order control code. Refer to PA order control code for discussion.Used in conjunction with the PA - Parent order control code. Refer to PA order control code for discussion.
CN Combined resultCombined resultAFiller Applications.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>
CP Cancel process stepCancel process stepAFiller Applications.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.
CR Canceled as requestedCanceled as requestedAFiller or Placer Applications.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.A response by the filler or placer application that a request to cancel (CA by the placer application) was performed successfully.
DC Discontinue order/service requestDiscontinue order/service requestAPlacer or Filler Applications.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.
DE Data errorsData errorsAPlacer or Filler Applications.Placer or Filler Applications.
DF Order/service refill request deniedOrder/service refill request deniedAPlacer Applications.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.
DR Discontinued as requestedDiscontinued as requestedAFiller or Placer Applications.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.The filler or placer, in response to a request to discontinue (DC from the placer or filler application), has discontinued the order/service.
FU Order/service refilled, unsolicitedOrder/service refilled, unsolicitedAFiller Applications.Filler Applications.<p>FU notifies the placer that the filler issued a refill for the order at the patient's request.FU notifies the placer that the filler issued a refill for the order at the patient's request.
HD Hold order requestHold order requestAPlacer Applications.Placer Applications.<p>Typical responses include, but are not limited to, CR - Cancelled as requested, UC - Unable to Cancel.Typical responses include, but are not limited to, CR - Cancelled as requested, UC - Unable to Cancel.
HR On hold as requestedOn hold as requestedAFiller Applications.Filler Applications.
LI Link order/service to patient care problem or goalLink order/service to patient care problem or goalAPlacer or Filler Applications.Placer or Filler Applications.<p>Refer to Chapter 12 Patient Care for complete discussion.Refer to Chapter 12 Patient Care for complete discussion.
MC Miscellaneous Charge - not associated with an orderMiscellaneous Charge - not associated with an orderAapplies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11
NA Number assignedNumber assignedAPlacer Applications.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
NR Notification ReceivedNotifies the Filler that the Placer received a cancellation, discontinuance, or other state change noticeAPlacer Applications.
NW New order/serviceNew order/serviceAPlacer Applications.Placer Applications.<p>See comments for NA - Number Assigned.See comments for NA - Number Assigned.
OC Order/service canceledOrder/service canceledAFiller Applications.Filler Applications.
OD Order/service discontinuedOrder/service discontinuedAFiller Applications.Filler Applications.
OE Order/service releasedOrder/service releasedAFiller Applications.Filler Applications.
OF Order/service refilled as requestedOrder/service refilled as requestedAFiller Applications.Filler Applications.<p>OF directly responds to the placer system's request for a refill.OF directly responds to the placer system's request for a refill.
OH Order/service heldOrder/service heldAFiller Applications.Filler Applications.
OK Order/service accepted & OKOrder/service accepted & OKAFiller Applications.Filler Applications.<p>See comments for NA - Number Assigned.See comments for NA - Number Assigned.
OP Notification of order for outside dispenseNotification of order for outside dispenseAPlacer Applications.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.
OR Released as requestedReleased as requestedAFiller Applications.Filler Applications.
PA Parent order/serviceParent order/serviceAFiller Applications.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).
PR Previous Results with new order/servicePrevious Results with new order/serviceAPlacer Applications.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.
PY Notification of replacement order for outside dispenseNotification of replacement order for outside dispenseAPlacer Applications.Placer Applications.<p>See comments for OP - Notification of order for outside dispense.See comments for OP - Notification of order for outside dispense.
RA Recommendation AcceptedIdentifies that this previously recommended replacement order has been acceptedNPlacer 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
RC Recommended ChangeIdentifies that this OBR represents a recommended replacement orderNFiller Applications. Used in the recommendation message sent to the placer
RD Recommendation DeclinedIdentifies that this previously sent recommended replacement order has been declinedNPlacer Applications: Used in the Recommendation Declined message Filler Applications: Used in the acknowledgment response message to the Recommendation Declined message
RE Observations/Performed Service to followObservations/Performed Service to followAPlacer or Filler Applications.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).
RF Refill order/service requestRefill order/service requestAPlacer or Filler Applications.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.
RL Release previous holdRelease previous holdAPlacer Applications.Placer Applications.
RO Replacement orderReplacement orderAPlacer or Filler Applications.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.
RP Order/service replace requestOrder/service replace requestAPlacer Applications.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
RQ Replaced as requestedReplaced as requestedAFiller Applications.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
RR Request receivedRequest receivedAPlacer or Filler Applications.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.
RU Replaced unsolicitedReplaced unsolicitedAFiller Applications.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
SC Status changedStatus changedAPlacer or Filler Applications.Placer or Filler Applications.
SN Send order/service numberSend order/service numberAPlacer Applications.Placer Applications.<p>See comments for NA - Number Assigned.See comments for NA - Number Assigned.
SQ Supplemented as requestedSupplementation confirmation message indicating that an order was supplemented as requested.NThis code is used in the acknowledgment response to the request messages.
SR Response to send order/service status requestResponse to send order/service status requestAFiller Applications.Filler Applications.
SS Send order/service status requestSend order/service status requestAPlacer Applications.Placer Applications.
SU Supplement this orderIdentifies existing orders to be supplemented in Supplementation Recommendation (filler to placer) and Supplementation Request (placer to filler) messages.NFor 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).
UA Unable to accept order/serviceUnable to accept order/serviceAFiller Applications.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.
UC Unable to cancelUnable to cancelAFiller or Placer Applications.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.
UD Unable to discontinueUnable to discontinueAFiller or Placer Applications.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.
UF Unable to refillUnable to refillAFiller Applications.Filler Applications.<p>Negative response to RF Refill order/service request, indicating that the receiving application was not able to complete the refill request.Negative response to RF Refill order/service request, indicating that the receiving application was not able to complete the refill request.
UH Unable to put on holdUnable to put on holdAFiller Applications.Filler Applications.
UM Unable to replaceUnable to replaceAFiller Applications.Filler Applications.
UN Unlink order/service from patient care problem or goalUnlink order/service from patient care problem or goalAPlacer or Filler Applications.Placer or Filler Applications.<p>Refer to Chapter 12 Patient Care for complete discussion.Refer to Chapter 12 Patient Care for complete discussion.
UR Unable to releaseUnable to releaseAFiller Applications.Filler Applications.
UX Unable to changeUnable to changeAFiller Applications.Filler Applications.
XO Change order/service requestChange order/service requestAPlacer Applications.Placer Applications.
XR Changed as requestedChanged as requestedAFiller Applications.Filler Applications.
XX Order/service changed, unsol.Order/service changed, unsol.AFiller Applications.Filler Applications.

Additional Language Displays

CodeDeutsch (German, de)
AF
CAAuftrag stornieren
CHnachgeordneter Auftrag
CNKumulatives Ergebnis (zu mehreren Aufträgen)
CP
CRAuftrag anweisungsgemäß storniert
DCAuftragsausführung abbrechen
DEDatenfehler
DF
DRAuftragsausführung anweisungsgemäß abgebrochen
FU
HDAuftragsbearbeitung aussetzen
HRAuftragsbearbeitung anweisungsgemäß ausgesetzt
LI
MC
NANummer zugewiesen
NR
NWNeuer Auftrag
OCAuftrag storniert
ODAuftragsausführung abgebrochen
OE
OF
OHAuftragsbearbeitung ausgesetzt
OKAuftrag akzeptiert
OP
ORAuftragsbearbeitung anweisungsgemäß wiederaufgenommen
PAHauptauftrag
PR
PY
RA
RC
RD
REUntersuchungsergebnisse folgen (in späteren Segmenten dieser Nachricht)
RF
RLAuftragsberabeitung wiederaufnehmen
ROErsatzauftrag
RPAuftrag ersetzen
RQAuftrag anweisungsgemäß ersetzt
RRAnforderung erhalten
RUAuftrag ersetzt (ohne Anweisung)
SCStatusänderung
SNAuftrags- bzw. Bearbeitungsnummer zuweisen / übermitteln
SQ
SRAuftragsstatus (Antwort)
SSAuftragsstatus senden
SU
UAAuftragsannahme nicht möglich
UCAuftragsstornierung nicht möglich
UDAbbrechen nicht möglich
UF
UHAussetzen nicht möglich
UMErsetzen nicht möglich
UN
URWiederaufnahme nicht möglich
UXÄnderung nicht möglich
XOAuftrag ändern
XRAuftrag anweisungsgemäß geändert
XXAuftrag geändert (ohne Anweisung)

History

DateActionCustodianAuthorComment
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.