{
  "package" : "hl7.terminology.r5@6.3.0",
  "definition" : "Replacement order",
  "system" : "http://terminology.hl7.org/CodeSystem/v2-0119",
  "property" : [ {
    "_uri" : "http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concComment",
    "code" : "v2-concComment",
    "valueString" : "Placer or Filler Applications."
  }, {
    "_uri" : "http://terminology.hl7.org/CodeSystem/utg-concept-properties#v2-concCommentAsPub",
    "code" : "v2-concCommentAsPub",
    "valueString" : "Placer or Filler Applications.\r\nA replacement is the substitution of one or more orders for one or more previously ordered services.\r\n\r\nThe replaced orders are treated as though they were canceled. If and when an ordered service can be replaced are local site-specific determinations.\r\n\r\nUse 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. \r\n\r\nFor 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. \r\n\r\nFor example, suppose that an ancillary application were replacing two OBR orders with three different orders. The sequence of segments would be as follows:\r\n\r\nSeg\tOrder Control\tComment\r\nORC\tRU\t1st replaced ORC\r\nOBR\t\t1st replaced order’s detail segment\r\n\t\t\r\nORC\tRU\t2nd replaced ORC\r\nOBR\t\t2nd replaced order’s detail segment\r\n\t\t\r\nORC\tRO\t1st replacement ORC\r\nOBR\t\t1st replacement order’s detail segment\r\n\t\t\r\nORC\tRO\t2nd replacement ORC\r\nOBR\t\t2nd replacement order’s detail segment\r\n\t\t\r\nORC\tRO\t3rd replacement ORC\r\nOBR\t\t3rd replacement order’s detail segment\r\n\r\nWhether the OBR segments must be present is determined by the value of ORC-6-response flag.\r\n\r\nThe 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)\r\n\r\nSeg\tOrder Control\tComment\r\nORC\tRQ\t1st replaced ORC\r\nOBR\t\t1st replaced order’s detail segment\r\n\t\t\r\nORC\tRQ\t2nd replaced ORC\r\nOBR\t\t2nd replaced order’s detail segment\r\n\t\t\r\nORC\tRO\t1st replacement ORC\r\nOBR\t\t1st replacement order’s detail segment\r\n\t\t\r\nORC\tRO\t2nd replacement ORC\r\nOBR\t\t2nd replacement order’s detail segment\r\n\t\t\r\nORC\tRO\t3rd replacement ORC\r\nOBR\t\t3rd replacement order’s detail segment\r\n\r\nThe 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.\r\n\r\nThe rules for the order numbers in ORC segments with an order control value of RO are determined by the replacement type (RP or RU).\r\n\r\nIn 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.\r\n\r\nIn 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.\r\n\r\nIf 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:\r\n\r\nORC with an order control value of RO.\r\n\r\nAny OBR segments (can be replaced by any order detail segments).\r\n\r\nOptionally followed by observation result segments (OBX)\r\nNTE segments can appear after the OBR (or any order detail segment) or after an OBX segment as in a regular ORU message."
  }, {
    "_uri" : "http://terminology.hl7.org/CodeSystem/utg-concept-properties#status",
    "code" : "status",
    "valueCode" : "A"
  } ],
  "codesystem" : "88c81107-7179-552f-9017-8cd736febdab",
  "concept_id" : "cb82736b-86c2-5950-ba38-0173e9988672",
  "ancestors" : {
    "RO" : 0
  },
  "id" : "cf616089-8ef4-4787-94b5-da48cbc16406",
  "code" : "RO",
  "display" : "Replacement order",
  "designation" : [ {
    "use" : {
      "code" : "preferredForLanguage",
      "system" : "http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"
    },
    "value" : "Ersatzauftrag",
    "language" : "de"
  } ],
  "version" : "2.0.0"
}