Current Build

4.3.15.119 HL7 Version 2 Table 0119

Vocabulary Work Group Maturity Level: N/AExternal Use Context: Any

This is a table defined as part of HL7 v2 .

Summary

Code System URL:http://terminology.hl7.org/CodeSystem/v2-0119
Value Set URL:http://terminology.hl7.org/ValueSet/v2-0119
Version:2.9
Name:v2.0119
Title:v2 ORDER CONTROL
Definition:

FHIR Value set/code system definition for HL7 v2 table 0119 ( ORDER CONTROL)

OID:??
CodeSystem ResourceXML / JSON
ValueSet ResourceXML / JSON

Note: V2 code systems may or may not be case sensitive. V2 Code systems will have the CodeSystem.caseSensitive correctly populated in a future version of this specification.

This value set is not currently used

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

CodeDisplayDefinitionCommentsVersion
AF en: Order/service refill request approval
nl: Aanvraag/service herhaling verzoek goedgekeurd
en: Placer Applications. AF is a response to RF where the placer authorizing a refill or quantity of refills.
nl: Placer applicaties. AF is een antwoord op RF waarbij de placer een herhaling autoriseert of een bepaalde hoeveelheid om aan te vullen
added v2.3
CA en: Cancel order/service request
de: Auftrag stornieren
nl: Annuleer aanvraag/service verzoek
en: 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.
nl: Placer of filler applicaties. Een annulering is een verzoek voor de placer aan de filler, of de filler aan de placer, om de eerder aangevraagde service niet te doen. Bevestiging van het annuleringverzoek wordt gegeven door de filler of de placer, bijv. een bericht met
from v2.1
CH en: Child order/service
de: nachgeordneter Auftrag
nl: Onderliggende/deel aanvraag/service
en: Placer or Filler Applications. Used in conjunction with the PA - Parent order control code. Refer to PA order control code for discussion.
nl: Placer of filler applicaties. Gebruikt in samenwerking met de code PA - Bovenliggende aanvraag/service. Zie PA voor verdere discussie.
from v2.1
CN en: Combined result
de: Kumulatives Ergebnis (zu mehreren Aufträgen)
nl: Gecombineerd resultaat
en: 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>
nl: Filler applicaties. De gecombineerde resultaatcode geeft een mechanisme om resultaten te sturen die zijn gekoppeld aan twee of meer aanvragen. Deze situatie komt vaak voor in radiologieverslagen als de radioloog één verslag dicteert voor twee of meer onderzoeken
from v2.1
CP en: Cancel process step
nl: Annuleer processtap
en: 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.
nl: Filler applicaties. De code CP - Annuleer processtap is bedoeld voor in ORC-1 bij Filler-naar-Filler communicatie, bijv. LIS-naar-Analyzer, om verschil te kunnen maken tussen code CDA (Placer-naar-Filler). De Filler moet antwoorden met een acceptatie van
added v2.8
CR en: Canceled as requested
de: Auftrag anweisungsgemäß storniert
nl: Geannuleerd zoals gevraagd
en: Filler or Placer Applications. A response by the filler or placer application that a request to cancel (CA by the placer application) was performed successfully.
nl: Filler of Placer applicaties. Een antwoord van de filler of placer applicatie om aan te geven dat een verzoek om te annuleren (CA door de placer applicatie) succesvol is uitgevoerd.
added v2.2
DC en: Discontinue order/service request
de: Auftragsausführung abbrechen
nl: Breek aanvraag/service verzoek af
en: 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.
nl: Placer of filer applicaties. Een verzoek van de placer aan de filler, of van de filler aan de placer, om een eerder aangevraagde service af te breken. Het verschil tussen afbreken en annuleren is dat afbreken de aanvraag/service betreft en alle
from v2.1
DE en: Data errors
de: Datenfehler
nl: Gegevens fouten
en: Placer or Filler Applications.
nl: Placer of filler applicaties.
from v2.1
DF en: Order/service refill request denied
nl: Aanvraag/service herhaal verzoek afgekeurd
en: 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.
nl: Placer applicaties. In antwoord op een autorisatieverzoek om te herhalen (RF) door de filler applicatie, geeft DF aan dat de placer geen autorisatie geeft voor herhaling van de order. ORC-16 Order Control Code Reason kan worden gebruikt om de reden voor afkeuring aan te geven.
added v2.3
DR en: Discontinued as requested
de: Auftragsausführung anweisungsgemäß abgebrochen
nl: Afgebroken zoals gevraagd
en: Filler or Placer Applications. The filler or placer, in response to a request to discontinue (DC from the placer or filler application), has discontinued the order/service.
nl: Filler of placer applicaties. De filler of placer heeft de aanvraag/service afgebroken, in antwoord op een verzoek deze af te breken (DC van de aplcer of filler applicatie).
from v2.1
FU en: Order/service refilled, unsolicited
nl: Aanvraag/service herhaald, ongevraagd
en: Filler Applications. FU notifies the placer that the filler issued a refill for the order at the patient's request.
nl: Filler applicaties. Deze code meldt aan de placer dat de filler een herhaling heeft gedaan voor de aanvraag op verzoek van de patiënt.
added v2.3
HD en: Hold order request
de: Auftragsbearbeitung aussetzen
nl: Houd aanvraag aan verzoek
en: Placer Applications. Typical responses include, but are not limited to, CR - Cancelled as requested, UC - Unable to Cancel.
nl: Placer applicaties. De meest voorkomende, maar niet enige, antwoord zijn CR - Geannuleerd zoals gevraagd, UC - Kon niet annuleren.
from v2.1
HR en: On hold as requested
de: Auftragsbearbeitung anweisungsgemäß ausgesetzt
nl: Aangehouden zoals gevraagd
en: Filler Applications.
nl: Filler applicaties.
from v2.1
LI en: Link order/service to patient care problem or goal
nl: Koppel aanvraag/service aan patiënt zorgprobleem of doel
en: Placer or Filler Applications. Refer to Chapter 12 Patient Care for complete discussion.
nl: Placer of filler applicaties. Zie Hoofdstuk 12 Patient Care voor vollledige discussie.
added v2.3.1
MC en: Miscellaneous Charge - not associated with an order
nl: Overige charge - niet gekoppeld aan een aanvraag
en: applies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11
nl: van toepassing op DFT^P03^DFT_P03 en DFT^P11^DFT_P11
added v2.6
NA en: Number assigned
de: Nummer zugewiesen
nl: Nummer toegekend
en: 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
nl: Placer applicaties. Er zijn drie omstandigheden waarin verzoeken van een aanvraagnummer (ORC-2 Placer aanvraagnummer of ORC-3 Filler aanvraagnummer): (1) Als de filler applicatie een ORC-3 Filler aanvraagnummer moet aanvragen van een centrale applicatie
from v2.1
NR Notification Receivedadded v2.9
NW en: New order/service
de: Neuer Auftrag
nl: Nieuwe aanvraag/service
en: Placer Applications. See comments for NA - Number Assigned.
nl: Placer applicaties. Zie opmerkingen voor NA - Nummer toegekend
from v2.1
OC en: Order/service canceled
de: Auftrag storniert
nl: Aanvraag/service geannuleerd
en: Filler Applications.
nl: Filler applicaties.
added v2.2
OD en: Order/service discontinued
de: Auftragsausführung abgebrochen
nl: Aanvraag/service afgebroken
en: Filler Applications.
nl: Filler applicaties.
from v2.1
OE en: Order/service released
nl: Aanvraag/service vrijgegeven
en: Filler Applications.
nl: Filler applicaties.
added v2.3
OF en: Order/service refilled as requested
nl: Aanvraag/service herhaald zoals gevraagd
en: Filler Applications. OF directly responds to the placer system's request for a refill.
nl: Filler applicaties. OF is een direct antwoord op het verzoek voor herhaling van een placer system.
added v2.3
OH en: Order/service held
de: Auftragsbearbeitung ausgesetzt
nl: Aanvraag/service aangehouden
en: Filler Applications.
nl: Filler applicaties.
added v2.2
OK en: Order/service accepted & OK
de: Auftrag akzeptiert
nl: Aanvraag/service geaccepteerd en OK
en: Filler Applications. See comments for NA - Number Assigned.
nl: Filler applicaties. Zie opmerkingen voor NA - Nummer toegekend
from v2.1
OP en: Notification of order for outside dispense
nl: Notificatie van aanvraag voor verstrekking door derde
en: 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.
nl: Placer applicaties. Deze aanvraagbeheer codes worden gebruikt voor communicatie van aanvragen tussen systemen waarbij de aanvraag bedoeld is ter informatie. Een aanvraag wordt bijvoorbeeld uitgevoerd door een leverancier anders dan de communicerende systemen.
added v2.5
OR en: Released as requested
de: Auftragsbearbeitung anweisungsgemäß wiederaufgenommen
nl: Vrijgegeven zoals gevraagd
en: Filler Applications.
nl: Filler applicaties.
from v2.1
PA en: Parent order/service
de: Hauptauftrag
nl: Bovenliggende aanvraag/service
en: 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).
nl: Filler applicaties. De codes voor bovenliggende (PA) en onderliggende/deel (CH) ondersteunen het onderscheiden van "onderliggende/deel" aanvragen van een "bovenliggende" aanvraag zonder dat de bovenliggende (oorspronkelijke aanvraag) wijzigt. Een of meer ORC segmenten met een ORC-1 Aanvraagbeheer PA waarden worden gevolgd door
from v2.1
PR en: Previous Results with new order/service
nl: Vorige resultaten met nieuwe aanvraag/service
en: 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.
nl: Placer applicaties. PR geeft aan dat deze ORC deel is van een ORU
added v2.4
PY en: Notification of replacement order for outside dispense
nl: Notificatie van vervangende aanvraag voor verstrekking door derde
en: Placer Applications. See comments for OP - Notification of order for outside dispense.
nl: Placer applicatie. Zie opmerkingen voor OP - Notificatie van aanvraag voor verstrekking door derde.
added v2.5
RA Recommendation Acceptedadded v2.9
RC Recommended Changeadded v2.9
RD Recommendation Declinedadded v2.9
RE en: Observations/Performed Service to follow
de: Untersuchungsergebnisse folgen (in späteren Segmenten dieser Nachricht)
nl: Observaties/uitgevoerde server volgen
en: 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).
nl: Placer of filler applicaties. Deze code wordt gebruikt voor het doorgeven van patiënt-specifieke informatie met een aanvraag. Een aanvraag-detailsegment (bijv. OBR) kan worden gevolgd door een of meer observatiesegmenten (OBX). Ieder observatie die kan worden ge
from v2.1
RF en: Refill order/service request
nl: Herhaal aanvraag/service verzoek
en: 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.
nl: Placer of filler applicaties. Deze code ondersteunt verzoeken door de filler of de placer. De filler kan een autorisatie voor herhaling vragen van de placer. Een placer-systeem kan een herhaling vragen van het filler-systeem. Meestal is het antwoord
added v2.3
RL en: Release previous hold
de: Auftragsberabeitung wiederaufnehmen
nl: Geef vorige vastgehouden vrij
en: Placer Applications.
nl: Placer applicaties.
added v2.2
RO en: Replacement order
de: Ersatzauftrag
nl: Vervangende aanvraag
en: 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.
nl: Placer of filler applicaties. Een vervanging is de substitutie van een of meer aanvragen voor een of meer eerder aangevraagde services. De vervangen aanvragen worden behandeld alsof ze zijn geannuleerd. Of en ondere welke omstandigheden een aanvraagde service vervangen kan worden hangt af van lokale
from v2.1
RP en: Order/service replace request
de: Auftrag ersetzen
nl: Aanvraag/service vervanging verzoek
en: 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
nl: Placer applicaties. Een vervanging is de substitutie van een of meer aanvragen voor eerder aangevraagde services. Zie opmerking 1 bij RO - Vervangende aanvraag voor verder discussie. De code voor vervangende aanvraag staat de filler toe om
from v2.1
RQ en: Replaced as requested
de: Auftrag anweisungsgemäß ersetzt
nl: Vervangen zoals gevraagd
en: 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
nl: Filler applicaties. Een vervanging is de substitutie van een of meer aanvragen voor een of meer eerder aangevraagd services. Zie opmerking 1 bij RO - Vervangende aanvraag voor verder discussie. De code voor vervangende aanvraag staat de filler toe om
added v2.2
RR en: Request received
de: Anforderung erhalten
nl: Verzoek ontvangen
en: 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.
nl: Placer of filler applicaties. Behouden vanwege backward compatibiliteit. In de huidige versie is deze equivalent aan een ontvangstbevestiging. De code RR geeft aan dat een aanvraagbericht is ontvangen en latere wordt verwerkt. De aanvraag heeft
from v2.1
RU en: Replaced unsolicited
de: Auftrag ersetzt (ohne Anweisung)
nl: Vervangen ongevraagd
en: 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
nl: Filler applicaties. Een vervanging is de substitutie van een of meer aanvragen voor een of meer eerder aangevraagde services. Zie opmerking 1 bij RO - Vervangende aanvraag voor verder discussie. De code RU staat de filler applicatie toe om
from v2.1
SC en: Status changed
de: Statusänderung
nl: Status gewijzigd
en: Placer or Filler Applications.
nl: Placer of filler applicaties.
added v2.2
SN en: Send order/service number
de: Auftrags- bzw. Bearbeitungsnummer zuweisen / übermitteln
nl: Stuur aanvraag/service nummer
en: Placer Applications. See comments for NA - Number Assigned.
nl: Placer applicaties. Zie opmerkingen voor NA - Nummer toegekend.
from v2.1
SQ Supplemented as requestedadded v2.9
SR en: Response to send order/service status request
de: Auftragsstatus (Antwort)
nl: Antwoord op stuur aanvraag/service status verzoek
en: Filler Applications.
nl: Filler applicaties.
added v2.2
SS en: Send order/service status request
de: Auftragsstatus senden
nl: Stuur aanvraag/service status verzoek
en: Placer Applications.
nl: Placer applicaties.
from v2.1
SU Supplement this orderadded v2.9
UA en: Unable to accept order/service
de: Auftragsannahme nicht möglich
nl: Kon aanvraag/service niet accepteren
en: 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.
nl: Filler applicaties. De code UA wordt gebruikt wanneer een nieuwe aanvraag niet worden geaccepteerd door de filler. Mogelijk redenen zijn voorschriften voor een medicijn waarvoor de patiënt allergisch is of een aanvraag waarvoor bepaalde apparatuur nodig is
added v2.3
UC en: Unable to cancel
de: Auftragsstornierung nicht möglich
nl: Kon niet annuleren
en: 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.
nl: Placer of filler applicaties. De code UC wordt gebruikt wanneer de aangevraagde service op een punt zit waarbij deze niet meer kan worden geannuleerd door de placer of de filler of als lokale regels annulering door de filler verhinderen. Gebruik van deze code is afhankelijk van de waarde
added v2.2
UD en: Unable to discontinue
de: Abbrechen nicht möglich
nl: Kon niet afbreken
en: 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.
nl: Filler of placer applicaties. Deze code wordt gebruikt als de aangevraagde service op een punt zit dat afgebreken door de placer of filler niet meer mogelijk is of wanneer lokale regels afbreken door de filler verhinderen. Gebruik van deze code hangt af van
from v2.1
UF en: Unable to refill
nl: Kon niet herhalen
en: Filler Applications. Negative response to RF Refill order/service request, indicating that the receiving application was not able to complete the refill request.
nl: Filler applicaties. Negatief antwoord op RF - Herhaal aanvraag/service verzoek, dat aangeeft dat de ontvangende applicatie het herhaalverzoek niet kon uitvoeren.
added v2.3
UH en: Unable to put on hold
de: Aussetzen nicht möglich
nl: Kon niet aanhouden
en: Filler Applications.
nl: Filler applicaties.
from v2.1
UM en: Unable to replace
de: Ersetzen nicht möglich
nl: Kon niet vervangen
en: Filler Applications.
nl: Filler applicaties.
added v2.2
UN en: Unlink order/service from patient care problem or goal
nl: Ontkoppel aanvraag/service van patiënt zorgprobleem of doel
en: Placer or Filler Applications. Refer to Chapter 12 Patient Care for complete discussion.
nl: Placer of filler applicaties. Zie Hoofdstuk 12 Patient Care voor vollledige discussie.
added v2.3.1
UR en: Unable to release
de: Wiederaufnahme nicht möglich
nl: Kon niet vrijgeven
en: Filler Applications.
nl: Filler applicaties.
from v2.1
UX en: Unable to change
de: Änderung nicht möglich
nl: Kon niet wijzigen
en: Filler Applications.
nl: Filler applicaties.
from v2.1
XO en: Change order/service request
de: Auftrag ändern
nl: Wijzig aanvraag/service verzoek
en: Placer Applications.
nl: Placer applicaties.
added v2.2
XR en: Changed as requested
de: Auftrag anweisungsgemäß geändert
nl: Gewijzigd zoals gevraagd
en: Filler Applications.
nl: Filler applicaties.
from v2.1
XX en: Order/service changed, unsol.
de: Auftrag geändert (ohne Anweisung)
nl: Order/service gewijzigd, ongevraagd
en: Filler Applications.
nl: Filler applicaties.
from v2.1

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

CodeDisplayDefinitionCommentsVersion
AF Order/service refill request approvalPlacer Applications. AF is a response to RF where the placer authorizing a refill or quantity of refills.added v2.3
CA Cancel order/service requestPlacer 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.from v2.1
CH Child order/servicePlacer or Filler Applications. Used in conjunction with the PA - Parent order control code. Refer to PA order control code for discussion.from v2.1
CN Combined resultFiller 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>from v2.1
CP Cancel process stepFiller 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.added v2.8
CR Canceled as requestedFiller or Placer Applications. A response by the filler or placer application that a request to cancel (CA by the placer application) was performed successfully.added v2.2
DC Discontinue order/service requestPlacer 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.from v2.1
DE Data errorsPlacer or Filler Applications.from v2.1
DF Order/service refill request deniedPlacer 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.added v2.3
DR Discontinued as requestedFiller or Placer Applications. The filler or placer, in response to a request to discontinue (DC from the placer or filler application), has discontinued the order/service.from v2.1
FU Order/service refilled, unsolicitedFiller Applications. FU notifies the placer that the filler issued a refill for the order at the patient's request.added v2.3
HD Hold order requestPlacer Applications. Typical responses include, but are not limited to, CR - Cancelled as requested, UC - Unable to Cancel.from v2.1
HR On hold as requestedFiller Applications.from v2.1
LI Link order/service to patient care problem or goalPlacer or Filler Applications. Refer to Chapter 12 Patient Care for complete discussion.added v2.3.1
MC Miscellaneous Charge - not associated with an orderapplies to DFT^P03^DFT_P03 and DFT^P11^DFT_P11added v2.6
NA Number assignedPlacer 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 IDfrom v2.1
NR Notification Receivedadded v2.9
NW New order/servicePlacer Applications. See comments for NA - Number Assigned.from v2.1
OC Order/service canceledFiller Applications.added v2.2
OD Order/service discontinuedFiller Applications.from v2.1
OE Order/service releasedFiller Applications.added v2.3
OF Order/service refilled as requestedFiller Applications. OF directly responds to the placer system's request for a refill.added v2.3
OH Order/service heldFiller Applications.added v2.2
OK Order/service accepted & OKFiller Applications. See comments for NA - Number Assigned.from v2.1
OP Notification of order for outside dispensePlacer 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.added v2.5
OR Released as requestedFiller Applications.from v2.1
PA Parent order/serviceFiller 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).from v2.1
PR Previous Results with new order/servicePlacer 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.added v2.4
PY Notification of replacement order for outside dispensePlacer Applications. See comments for OP - Notification of order for outside dispense.added v2.5
RA Recommendation Acceptedadded v2.9
RC Recommended Changeadded v2.9
RD Recommendation Declinedadded v2.9
RE Observations/Performed Service to followPlacer 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).from v2.1
RF Refill order/service requestPlacer 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.added v2.3
RL Release previous holdPlacer Applications.added v2.2
RO Replacement orderPlacer 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.from v2.1
RP Order/service replace requestPlacer 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 messagefrom v2.1
RQ Replaced as requestedFiller 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 messageadded v2.2
RR Request receivedPlacer 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.from v2.1
RU Replaced unsolicitedFiller 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 messagefrom v2.1
SC Status changedPlacer or Filler Applications.added v2.2
SN Send order/service numberPlacer Applications. See comments for NA - Number Assigned.from v2.1
SQ Supplemented as requestedadded v2.9
SR Response to send order/service status requestFiller Applications.added v2.2
SS Send order/service status requestPlacer Applications.from v2.1
SU Supplement this orderadded v2.9
UA Unable to accept order/serviceFiller 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.added v2.3
UC Unable to cancelFiller 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.added v2.2
UD Unable to discontinueFiller 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.from v2.1
UF Unable to refillFiller Applications. Negative response to RF Refill order/service request, indicating that the receiving application was not able to complete the refill request.added v2.3
UH Unable to put on holdFiller Applications.from v2.1
UM Unable to replaceFiller Applications.added v2.2
UN Unlink order/service from patient care problem or goalPlacer or Filler Applications. Refer to Chapter 12 Patient Care for complete discussion.added v2.3.1
UR Unable to releaseFiller Applications.from v2.1
UX Unable to changeFiller Applications.from v2.1
XO Change order/service requestPlacer Applications.added v2.2
XR Changed as requestedFiller Applications.from v2.1
XX Order/service changed, unsol.Filler Applications.from v2.1

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

CodeDisplayDefinitionCommentsVersion
AF added v2.3
CA Auftrag stornierenfrom v2.1
CH nachgeordneter Auftragfrom v2.1
CN Kumulatives Ergebnis (zu mehreren Aufträgen)from v2.1
CP added v2.8
CR Auftrag anweisungsgemäß storniertadded v2.2
DC Auftragsausführung abbrechenfrom v2.1
DE Datenfehlerfrom v2.1
DF added v2.3
DR Auftragsausführung anweisungsgemäß abgebrochenfrom v2.1
FU added v2.3
HD Auftragsbearbeitung aussetzenfrom v2.1
HR Auftragsbearbeitung anweisungsgemäß ausgesetztfrom v2.1
LI added v2.3.1
MC added v2.6
NA Nummer zugewiesenfrom v2.1
NR added v2.9
NW Neuer Auftragfrom v2.1
OC Auftrag storniertadded v2.2
OD Auftragsausführung abgebrochenfrom v2.1
OE added v2.3
OF added v2.3
OH Auftragsbearbeitung ausgesetztadded v2.2
OK Auftrag akzeptiertfrom v2.1
OP added v2.5
OR Auftragsbearbeitung anweisungsgemäß wiederaufgenommenfrom v2.1
PA Hauptauftragfrom v2.1
PR added v2.4
PY added v2.5
RA added v2.9
RC added v2.9
RD added v2.9
RE Untersuchungsergebnisse folgen (in späteren Segmenten dieser Nachricht)from v2.1
RF added v2.3
RL Auftragsberabeitung wiederaufnehmenadded v2.2
RO Ersatzauftragfrom v2.1
RP Auftrag ersetzenfrom v2.1
RQ Auftrag anweisungsgemäß ersetztadded v2.2
RR Anforderung erhaltenfrom v2.1
RU Auftrag ersetzt (ohne Anweisung)from v2.1
SC Statusänderungadded v2.2
SN Auftrags- bzw. Bearbeitungsnummer zuweisen / übermittelnfrom v2.1
SQ added v2.9
SR Auftragsstatus (Antwort)added v2.2
SS Auftragsstatus sendenfrom v2.1
SU added v2.9
UA Auftragsannahme nicht möglichadded v2.3
UC Auftragsstornierung nicht möglichadded v2.2
UD Abbrechen nicht möglichfrom v2.1
UF added v2.3
UH Aussetzen nicht möglichfrom v2.1
UM Ersetzen nicht möglichadded v2.2
UN added v2.3.1
UR Wiederaufnahme nicht möglichfrom v2.1
UX Änderung nicht möglichfrom v2.1
XO Auftrag ändernadded v2.2
XR Auftrag anweisungsgemäß geändertfrom v2.1
XX Auftrag geändert (ohne Anweisung)from v2.1

Dit code systeem http://terminology.hl7.org/CodeSystem/v2-0119 definieert de volgende codes:

CodeDisplayDefinitionCommentaarVersie
AF Aanvraag/service herhaling verzoek goedgekeurdPlacer applicaties. AF is een antwoord op RF waarbij de placer een herhaling autoriseert of een bepaalde hoeveelheid om aan te vullenadded v2.3
CA Annuleer aanvraag/service verzoekPlacer of filler applicaties. Een annulering is een verzoek voor de placer aan de filler, of de filler aan de placer, om de eerder aangevraagde service niet te doen. Bevestiging van het annuleringverzoek wordt gegeven door de filler of de placer, bijv. een bericht metfrom v2.1
CH Onderliggende/deel aanvraag/servicePlacer of filler applicaties. Gebruikt in samenwerking met de code PA - Bovenliggende aanvraag/service. Zie PA voor verdere discussie.from v2.1
CN Gecombineerd resultaatFiller applicaties. De gecombineerde resultaatcode geeft een mechanisme om resultaten te sturen die zijn gekoppeld aan twee of meer aanvragen. Deze situatie komt vaak voor in radiologieverslagen als de radioloog één verslag dicteert voor twee of meer onderzoekenfrom v2.1
CP Annuleer processtapFiller applicaties. De code CP - Annuleer processtap is bedoeld voor in ORC-1 bij Filler-naar-Filler communicatie, bijv. LIS-naar-Analyzer, om verschil te kunnen maken tussen code CDA (Placer-naar-Filler). De Filler moet antwoorden met een acceptatie van added v2.8
CR Geannuleerd zoals gevraagdFiller of Placer applicaties. Een antwoord van de filler of placer applicatie om aan te geven dat een verzoek om te annuleren (CA door de placer applicatie) succesvol is uitgevoerd.added v2.2
DC Breek aanvraag/service verzoek afPlacer of filer applicaties. Een verzoek van de placer aan de filler, of van de filler aan de placer, om een eerder aangevraagde service af te breken. Het verschil tussen afbreken en annuleren is dat afbreken de aanvraag/service betreft en alle from v2.1
DE Gegevens foutenPlacer of filler applicaties.from v2.1
DF Aanvraag/service herhaal verzoek afgekeurdPlacer applicaties. In antwoord op een autorisatieverzoek om te herhalen (RF) door de filler applicatie, geeft DF aan dat de placer geen autorisatie geeft voor herhaling van de order. ORC-16 Order Control Code Reason kan worden gebruikt om de reden voor afkeuring aan te geven.added v2.3
DR Afgebroken zoals gevraagdFiller of placer applicaties. De filler of placer heeft de aanvraag/service afgebroken, in antwoord op een verzoek deze af te breken (DC van de aplcer of filler applicatie).from v2.1
FU Aanvraag/service herhaald, ongevraagdFiller applicaties. Deze code meldt aan de placer dat de filler een herhaling heeft gedaan voor de aanvraag op verzoek van de patiënt.added v2.3
HD Houd aanvraag aan verzoekPlacer applicaties. De meest voorkomende, maar niet enige, antwoord zijn CR - Geannuleerd zoals gevraagd, UC - Kon niet annuleren.from v2.1
HR Aangehouden zoals gevraagdFiller applicaties.from v2.1
LI Koppel aanvraag/service aan patiënt zorgprobleem of doelPlacer of filler applicaties. Zie Hoofdstuk 12 Patient Care voor vollledige discussie.added v2.3.1
MC Overige charge - niet gekoppeld aan een aanvraagvan toepassing op DFT^P03^DFT_P03 en DFT^P11^DFT_P11added v2.6
NA Nummer toegekendPlacer applicaties. Er zijn drie omstandigheden waarin verzoeken van een aanvraagnummer (ORC-2 Placer aanvraagnummer of ORC-3 Filler aanvraagnummer): (1) Als de filler applicatie een ORC-3 Filler aanvraagnummer moet aanvragen van een centrale applicatiefrom v2.1
NR added v2.9
NW Nieuwe aanvraag/servicePlacer applicaties. Zie opmerkingen voor NA - Nummer toegekendfrom v2.1
OC Aanvraag/service geannuleerdFiller applicaties.added v2.2
OD Aanvraag/service afgebrokenFiller applicaties.from v2.1
OE Aanvraag/service vrijgegevenFiller applicaties.added v2.3
OF Aanvraag/service herhaald zoals gevraagdFiller applicaties. OF is een direct antwoord op het verzoek voor herhaling van een placer system.added v2.3
OH Aanvraag/service aangehoudenFiller applicaties.added v2.2
OK Aanvraag/service geaccepteerd en OKFiller applicaties. Zie opmerkingen voor NA - Nummer toegekendfrom v2.1
OP Notificatie van aanvraag voor verstrekking door derdePlacer applicaties. Deze aanvraagbeheer codes worden gebruikt voor communicatie van aanvragen tussen systemen waarbij de aanvraag bedoeld is ter informatie. Een aanvraag wordt bijvoorbeeld uitgevoerd door een leverancier anders dan de communicerende systemen.added v2.5
OR Vrijgegeven zoals gevraagdFiller applicaties.from v2.1
PA Bovenliggende aanvraag/serviceFiller applicaties. De codes voor bovenliggende (PA) en onderliggende/deel (CH) ondersteunen het onderscheiden van "onderliggende/deel" aanvragen van een "bovenliggende" aanvraag zonder dat de bovenliggende (oorspronkelijke aanvraag) wijzigt. Een of meer ORC segmenten met een ORC-1 Aanvraagbeheer PA waarden worden gevolgd doorfrom v2.1
PR Vorige resultaten met nieuwe aanvraag/servicePlacer applicaties. PR geeft aan dat deze ORC deel is van een ORU added v2.4
PY Notificatie van vervangende aanvraag voor verstrekking door derdePlacer applicatie. Zie opmerkingen voor OP - Notificatie van aanvraag voor verstrekking door derde.added v2.5
RA added v2.9
RC added v2.9
RD added v2.9
RE Observaties/uitgevoerde server volgenPlacer of filler applicaties. Deze code wordt gebruikt voor het doorgeven van patiënt-specifieke informatie met een aanvraag. Een aanvraag-detailsegment (bijv. OBR) kan worden gevolgd door een of meer observatiesegmenten (OBX). Ieder observatie die kan worden gefrom v2.1
RF Herhaal aanvraag/service verzoekPlacer of filler applicaties. Deze code ondersteunt verzoeken door de filler of de placer. De filler kan een autorisatie voor herhaling vragen van de placer. Een placer-systeem kan een herhaling vragen van het filler-systeem. Meestal is het antwoordadded v2.3
RL Geef vorige vastgehouden vrijPlacer applicaties.added v2.2
RO Vervangende aanvraagPlacer of filler applicaties. Een vervanging is de substitutie van een of meer aanvragen voor een of meer eerder aangevraagde services. De vervangen aanvragen worden behandeld alsof ze zijn geannuleerd. Of en ondere welke omstandigheden een aanvraagde service vervangen kan worden hangt af van lokale from v2.1
RP Aanvraag/service vervanging verzoekPlacer applicaties. Een vervanging is de substitutie van een of meer aanvragen voor eerder aangevraagde services. Zie opmerking 1 bij RO - Vervangende aanvraag voor verder discussie. De code voor vervangende aanvraag staat de filler toe om from v2.1
RQ Vervangen zoals gevraagdFiller applicaties. Een vervanging is de substitutie van een of meer aanvragen voor een of meer eerder aangevraagd services. Zie opmerking 1 bij RO - Vervangende aanvraag voor verder discussie. De code voor vervangende aanvraag staat de filler toe om added v2.2
RR Verzoek ontvangenPlacer of filler applicaties. Behouden vanwege backward compatibiliteit. In de huidige versie is deze equivalent aan een ontvangstbevestiging. De code RR geeft aan dat een aanvraagbericht is ontvangen en latere wordt verwerkt. De aanvraag heeftfrom v2.1
RU Vervangen ongevraagdFiller applicaties. Een vervanging is de substitutie van een of meer aanvragen voor een of meer eerder aangevraagde services. Zie opmerking 1 bij RO - Vervangende aanvraag voor verder discussie. De code RU staat de filler applicatie toe om from v2.1
SC Status gewijzigdPlacer of filler applicaties.added v2.2
SN Stuur aanvraag/service nummerPlacer applicaties. Zie opmerkingen voor NA - Nummer toegekend.from v2.1
SQ added v2.9
SR Antwoord op stuur aanvraag/service status verzoekFiller applicaties.added v2.2
SS Stuur aanvraag/service status verzoekPlacer applicaties.from v2.1
SU added v2.9
UA Kon aanvraag/service niet accepterenFiller applicaties. De code UA wordt gebruikt wanneer een nieuwe aanvraag niet worden geaccepteerd door de filler. Mogelijk redenen zijn voorschriften voor een medicijn waarvoor de patiënt allergisch is of een aanvraag waarvoor bepaalde apparatuur nodig isadded v2.3
UC Kon niet annulerenPlacer of filler applicaties. De code UC wordt gebruikt wanneer de aangevraagde service op een punt zit waarbij deze niet meer kan worden geannuleerd door de placer of de filler of als lokale regels annulering door de filler verhinderen. Gebruik van deze code is afhankelijk van de waardeadded v2.2
UD Kon niet afbrekenFiller of placer applicaties. Deze code wordt gebruikt als de aangevraagde service op een punt zit dat afgebreken door de placer of filler niet meer mogelijk is of wanneer lokale regels afbreken door de filler verhinderen. Gebruik van deze code hangt af vanfrom v2.1
UF Kon niet herhalenFiller applicaties. Negatief antwoord op RF - Herhaal aanvraag/service verzoek, dat aangeeft dat de ontvangende applicatie het herhaalverzoek niet kon uitvoeren.added v2.3
UH Kon niet aanhoudenFiller applicaties.from v2.1
UM Kon niet vervangenFiller applicaties.added v2.2
UN Ontkoppel aanvraag/service van patiënt zorgprobleem of doelPlacer of filler applicaties. Zie Hoofdstuk 12 Patient Care voor vollledige discussie.added v2.3.1
UR Kon niet vrijgevenFiller applicaties.from v2.1
UX Kon niet wijzigenFiller applicaties.from v2.1
XO Wijzig aanvraag/service verzoekPlacer applicaties.added v2.2
XR Gewijzigd zoals gevraagdFiller applicaties.from v2.1
XX Order/service gewijzigd, ongevraagdFiller applicaties.from v2.1