HL7 Terminology
1.0.0 - Publication

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

SecurityObservationType - TTL Representation

(back to description)

Raw ttl

Source view

@prefix fhir: <http://hl7.org/fhir/> .
@prefix owl: <http://www.w3.org/2002/07/owl#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .

# - resource -------------------------------------------------------------------

 a fhir:ValueSet;
  fhir:nodeRole fhir:treeRoot;
  fhir:Resource.id [ fhir:value "v3-SecurityObservationType"];
  fhir:Resource.language [ fhir:value "en"];
  fhir:DomainResource.text [
     fhir:Narrative.status [ fhir:value "generated" ];
     fhir:Narrative.div "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><h2>SecurityObservationType</h2><div><p>Type of security metadata observation made about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security metadata are used in security labels. According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator’s clearance to the target’s security label. All of the following must be true for authorization to be granted:</p>\n<ul>\n<li>The security policy identifiers shall be identical,</li>\n<li>The classification level of the initiator shall be greater than or equal to that of the target (that is, there shall be at least one value in the classification list of the clearance greater than or equal to the classification of the target), and</li>\n<li>For each security category in the target label, there shall be a security category of the same type in the initiator’s clearance and the initiator’s classification level shall dominate that of the target.</li>\n</ul>\n</div><ul><li>Include codes from <a href=\"CodeSystem-v3-ActCode.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActCode</code></a> where concept  is-a  <a href=\"CodeSystem-v3-ActCode.html#v3-ActCode-SECOBS\">SECOBS</a></li></ul></div>"
  ];
  fhir:ValueSet.url [ fhir:value "http://terminology.hl7.org/ValueSet/v3-SecurityObservationType"];
  fhir:ValueSet.identifier [
     fhir:index 0;
     fhir:Identifier.system [ fhir:value "urn:ietf:rfc:3986" ];
     fhir:Identifier.value [ fhir:value "urn:oid:2.16.840.1.113883.1.11.20457" ]
  ];
  fhir:ValueSet.version [ fhir:value "2.0.0"];
  fhir:ValueSet.name [ fhir:value "SecurityObservationType"];
  fhir:ValueSet.title [ fhir:value "SecurityObservationType"];
  fhir:ValueSet.status [ fhir:value "active"];
  fhir:ValueSet.date [ fhir:value "2014-03-26T00:00:00-04:00"^^xsd:dateTime];
  fhir:ValueSet.description [ fhir:value "Type of security metadata observation made about an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security metadata are used in security labels. According to ISO/TS 22600-3:2009(E) A.9.1.7 SECURITY LABEL MATCHING, Security label matching compares the initiator’s clearance to the target’s security label. All of the following must be true for authorization to be granted:\r\n\r\n *  The security policy identifiers shall be identical,\r\n *  The classification level of the initiator shall be greater than or equal to that of the target (that is, there shall be at least one value in the classification list of the clearance greater than or equal to the classification of the target), and\r\n *  For each security category in the target label, there shall be a security category of the same type in the initiator’s clearance and the initiator’s classification level shall dominate that of the target."];
  fhir:ValueSet.immutable [ fhir:value "true"^^xsd:boolean];
  fhir:ValueSet.compose [
     fhir:ValueSet.compose.include [
       fhir:index 0;
       fhir:ValueSet.compose.include.system [ fhir:value "http://terminology.hl7.org/CodeSystem/v3-ActCode" ];
       fhir:ValueSet.compose.include.filter [
         fhir:index 0;
         fhir:ValueSet.compose.include.filter.property [ fhir:value "concept" ];
         fhir:ValueSet.compose.include.filter.op [ fhir:value "is-a" ];
         fhir:ValueSet.compose.include.filter.value [ fhir:value "SECOBS" ]       ]     ]
  ].

# - ontology header ------------------------------------------------------------

 a owl:Ontology;
  owl:imports fhir:fhir.ttl.