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

ActRelationshipICSRInvestigation - JSON Representation

(back to description)

Raw json

Source view

{
  "resourceType" : "ValueSet",
  "id" : "v3-ActRelationshipICSRInvestigation",
  "language" : "en",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><h2>ActRelationshipICSRInvestigation</h2><div><p><strong>Description:</strong> The ways that product safety Investigations, about which information is captured in an Individual Case Safety Report, are related to each other. One investigation may be performed at a patient care institution, and the second by a manufacturer, a third by a regulatory agency. They may all investigate the same case and are thus related. Other kinds of relationships are replacement (if the mode of the Investigation is changed).</p>\n</div><ul><li>Include these codes as defined in <a href=\"CodeSystem-v3-ActRelationshipType.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType</code></a><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-RPLC\">RPLC</a></td><td>replaces</td><td>A replacement source act replaces an existing target act. The state of the target act being replaced becomes obselete, but the act is typically still retained in the system for historical reference. The source and target must be of the same type.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SEQL\">SEQL</a></td><td>is sequel</td><td>An act relationship indicating that the source act follows the target act. The source act should in principle represent the same kind of act as the target. Source and target need not have the same mood code (mood will often differ). The target of a sequel is called antecedent. Examples for sequel relationships are: revision, transformation, derivation from a prototype (as a specialization is a derivation of a generalization), followup, realization, instantiation.</td></tr><tr><td><a href=\"CodeSystem-v3-ActRelationshipType.html#v3-ActRelationshipType-SPRT\">SPRT</a></td><td>has support</td><td>Used to indicate that an existing service is suggesting evidence for a new observation. The assumption of support is attributed to the same actor who asserts the observation. Source must be an observation, target may be any service (e.g., to indicate a status post).</td></tr></table></li></ul></div>"
  },
  "url" : "http://terminology.hl7.org/ValueSet/v3-ActRelationshipICSRInvestigation",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.1.11.20353"
    }
  ],
  "version" : "2.0.0",
  "name" : "ActRelationshipICSRInvestigation",
  "title" : "ActRelationshipICSRInvestigation",
  "status" : "active",
  "date" : "2014-03-26T00:00:00-04:00",
  "description" : "**Description:** The ways that product safety Investigations, about which information is captured in an Individual Case Safety Report, are related to each other. One investigation may be performed at a patient care institution, and the second by a manufacturer, a third by a regulatory agency. They may all investigate the same case and are thus related. Other kinds of relationships are replacement (if the mode of the Investigation is changed).",
  "compose" : {
    "include" : [
      {
        "system" : "http://terminology.hl7.org/CodeSystem/v3-ActRelationshipType",
        "concept" : [
          {
            "code" : "RPLC"
          },
          {
            "code" : "SEQL"
          },
          {
            "code" : "SPRT"
          }
        ]
      }
    ]
  }
}