HL7 Terminology (THO)
5.2.0 - Publication International flag

This page is part of the HL7 Terminology (v5.2.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

: RoleClassSame - JSON Representation

Active as of 2014-03-26

Raw json | Download


{
  "resourceType" : "ValueSet",
  "id" : "v3-RoleClassSame",
  "language" : "en",
  "text" : {
    "status" : "generated",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><ul><li>Include codes from <a href=\"CodeSystem-v3-RoleClass.html\"><code>http://terminology.hl7.org/CodeSystem/v3-RoleClass</code></a> where concept  is-a  <a href=\"CodeSystem-v3-RoleClass.html#v3-RoleClass-SAME\">SAME</a></li></ul></div>"
  },
  "url" : "http://terminology.hl7.org/ValueSet/v3-RoleClassSame",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.1.11.20168"
    }
  ],
  "version" : "2.0.0",
  "name" : "RoleClassSame",
  "title" : "RoleClassSame",
  "status" : "active",
  "experimental" : false,
  "date" : "2014-03-26",
  "description" : "The \"same\" roleclass asserts an identity between playing and scoping entities: that they are in fact instances of the same entity and, in the case of discrepancies (e.g different DOB, gender), that one or both are in error.\r\n\r\n*Usage:*\r\n\r\nplaying and scoping entities must have same classcode, but need not have identical attributes or values.\r\n\r\n*Example:* \r\n\r\na provider registry maintains sets of conflicting demographic data for what is reported to be the same individual.",
  "immutable" : true,
  "compose" : {
    "include" : [
      {
        "system" : "http://terminology.hl7.org/CodeSystem/v3-RoleClass",
        "filter" : [
          {
            "property" : "concept",
            "op" : "is-a",
            "value" : "SAME"
          }
        ]
      }
    ]
  }
}