{
  "package" : "hl7.terminology.r5@6.3.0",
  "definition" : "Observations/Performed Service to follow",
  "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\nThe 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.\r\n\r\nThe following example shows the sequence of segments for three Pharmacy orders. It illustrates the use of the RE code:\r\nSegment\tOrder Control\tComment\r\nMSH\t\t\r\nPID\t\t\r\nORC\tNW\tFirst new order\r\nRXO\t\tFirst order segment\r\n\t\t\r\nORC\tNW\t2nd new order\r\nRXO\t\t2nd order segment\r\n[ORC\tRE\tPatient-specific observation, optional in V 2.2\r\n OBR]\t\tObservation OBR, optional in V 2.2\r\nOBX\t\tAn observation segment\r\nOBX\t\tAnother observation segment\r\nOBX\t\tAnother observation segment\r\nOBX\t\tAnother observation segment\r\n\t\t\r\nORC\tNW\t3rd order\r\nRXO\t\t3rd order segment\r\n\r\nIn 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.\r\n\r\nObservations 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.\r\n\r\nThe 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)."
  }, {
    "_uri" : "http://terminology.hl7.org/CodeSystem/utg-concept-properties#status",
    "code" : "status",
    "valueCode" : "A"
  } ],
  "codesystem" : "88c81107-7179-552f-9017-8cd736febdab",
  "concept_id" : "48232cab-d3a0-5014-a0f3-6b3219d33610",
  "ancestors" : {
    "RE" : 0
  },
  "id" : "169c8c9e-fb80-41a9-885c-585b34776cae",
  "code" : "RE",
  "display" : "Observations/Performed Service to follow",
  "designation" : [ {
    "use" : {
      "code" : "preferredForLanguage",
      "system" : "http://terminology.hl7.org/CodeSystem/hl7TermMaintInfra"
    },
    "value" : "Untersuchungsergebnisse folgen (in späteren Segmenten dieser Nachricht)",
    "language" : "de"
  } ],
  "version" : "2.0.0"
}