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

• Narrative Content
• XML
• JSON
• TTL
• History

ValueSet: ActClassConsent

Official URL: http://terminology.hl7.org/ValueSet/v3-ActClassConsent				Version: 2.0.0
Active as of 2014-03-26			Computable Name: ActClassConsent
Other Identifiers: id: urn:oid:2.16.840.1.113883.1.11.20206

The Consent class represents informed consents and all similar medico-legal transactions between the patient (or his legal guardian) and the provider. Examples are informed consent for surgical procedures, informed consent for clinical trials, advanced beneficiary notice, against medical advice decline from service, release of information agreement, etc.

The details of consents vary. Often an institution has a number of different consent forms for various purposes, including reminding the physician about the topics to mention. Such forms also include patient education material. In electronic medical record communication, consents thus are information-generating acts on their own and need to be managed similar to medical activities. Thus, Consent is modeled as a special class of Act.

The “signatures” to the consent document are represented electronically through Participation instances to the consent object. Typically an informed consent has Participation.typeCode of “performer”, the healthcare provider informing the patient, and “consenter”, the patient or legal guardian. Some consent may associate a witness or a notary public (e.g., living wills, advanced directives). In consents where a healthcare provider is not required (e.g. living will), the performer may be the patient himself or a notary public.

Some consent has a minimum required delay between the consent and the service, so as to allow the patient to rethink his decisions. This minimum delay can be expressed in the act definition by the ActRelationship.pauseQuantity attribute that delays the service until the pause time has elapsed after the consent has been completed.

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)

 

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