HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 7.0.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

• Narrative Content
• XML
• JSON
• TTL
• History

ValueSet: ObligationPolicy

Official URL: http://terminology.hl7.org/ValueSet/v3-ObligationPolicy				Version: 3.0.0
Active as of 2014-03-26			Responsible: Health Level Seven International	Computable Name: ObligationPolicy
Other Identifiers: OID:2.16.840.1.113883.1.11.20445
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

Conveys the mandated workflow action that an information custodian, receiver, or user must perform.

Examples:

• encrypt

Usage Note: Per OASIS XACML, an obligation is an operation specified in a policy or policy that is performed in conjunction with the enforcement of an access control decision.

References

• Included into SecurityControlObservationValue

Logical Definition (CLD)

 

Expansion

---

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