HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build)
HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions
Active as of 2023-06-02 |
<ValueSet xmlns="http://hl7.org/fhir">
<id value="v3-SecurityObservationType"/>
<language value="en"/>
<text>
<status value="generated"/>
<div xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><p class="res-header-id"><b>Generated Narrative: ValueSet v3-SecurityObservationType</b></p><a name="v3-SecurityObservationType"> </a><a name="hcv3-SecurityObservationType"> </a><a name="v3-SecurityObservationType-en-US"> </a><div style="display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%"><p style="margin-bottom: 0px">Language: en</p></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>
</text>
<url
value="http://terminology.hl7.org/ValueSet/v3-SecurityObservationType"/>
<identifier>
<system value="urn:ietf:rfc:3986"/>
<value value="urn:oid:2.16.840.1.113883.1.11.20457"/>
</identifier>
<version value="3.0.0"/>
<name value="SecurityObservationType"/>
<title value="SecurityObservationType"/>
<status value="active"/>
<experimental value="false"/>
<date value="2023-06-02"/>
<publisher value="Health Level Seven International"/>
<contact>
<telecom>
<system value="url"/>
<value value="http://hl7.org"/>
</telecom>
<telecom>
<system value="email"/>
<value value="hq@HL7.org"/>
</telecom>
</contact>
<description
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:
* The security policy identifiers shall be identical,
* 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
* For each security category in the target label, there shall be a security category of the same type in the initiator'ijs clearance and the initiator's classification level shall dominate that of the target."/>
<immutable value="true"/>
<copyright
value="This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html"/>
<compose>
<include>
<system value="http://terminology.hl7.org/CodeSystem/v3-ActCode"/>
<filter>
<property value="concept"/>
<op value="is-a"/>
<value value="SECOBS"/>
</filter>
</include>
</compose>
</ValueSet>