HL7 Terminology (THO)
6.0.0 - Publication International flag

This page is part of the HL7 Terminology (v6.0.0: Release) based on FHIR (HL7® FHIR® Standard) v5.0.0. 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

ValueSet: SecurityControlObservationType

Official URL: http://terminology.hl7.org/ValueSet/v3-SecurityControlObservationType Version: 3.0.0
Active as of 2014-03-26 Responsible: Health Level Seven International Computable Name: SecurityControlObservationType
Other Identifiers: OID:2.16.840.1.113883.1.11.20460

Copyright/Legal: 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

Type of security metadata observation made about the control of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security control metadata conveys instructions for secure distribution, transmission, storage or use.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

Generated Narrative: ValueSet v3-SecurityControlObservationType

Language: en

 

Expansion

Generated Narrative: ValueSet

Language: en

Expansion based on codesystem ActCode v9.0.0 (CodeSystem)

This value set contains 1 concepts

CodeSystemDisplayDefinition
  SECCONOBShttp://terminology.hl7.org/CodeSystem/v3-ActCodesecurity control observation

Type of security metadata observation made about the control of an IT resource (data, information object, service, or system capability), which may be used to make access control decisions. Security control metadata convey instructions to users and receivers for secure distribution, transmission, and storage; dictate obligations or mandated actions; specify any action prohibited by refrain policy such as dissemination controls; and stipulate the permissible purpose of use of an IT resource.

Rationale: A security control observation supports requirement to specify applicable management, operational, and technical controls (i.e., safeguards or countermeasures) prescribed for an information system to protect the confidentiality, integrity, and availability of the system and its information. [FIPS 199]

Examples: Types of security control metadata include:

  • handling caveats
  • dissemination controls
  • obligations
  • refrain policies
  • purpose of use constraints

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code

History

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2022-10-18reviseTSMGMarc DuteauFixing missing metadata; up-349
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.
2014-03-26revise2014T1_2014-03-26_001283 (RIM release ID)Vocabulary (Woody Beeler) (no record of original request)Lock all vaue sets untouched since 2014-03-26 to trackingId 2014T1_2014_03_26