Clinical Document Architecture
2.0.1 - active

Clinical Document Architecture, published by Health Level 7. This is not an authorized publication; it is the continuous build for version 2.0.1). This version is based on the current content of https://github.com/HL7/CDA-core-2.0/ and changes regularly. See the Directory of published versions

Logical Model: Consent (CDA Class)

Official URL: http://hl7.org/cda/stds/core/StructureDefinition/Consent Version: 2.0.1
Active as of 2023-10-03 Computable Name: CDAR2.Consent

This class references the consents associated with this document. The type of consent (e.g. a consent to perform the related ServiceEvent, a consent for the information contained in the document to be released to a third party) is conveyed in Consent.code. Consents referenced in the CDA Header have been finalized (Consent.statusCode must equal “completed”) and should be on file.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from Base

NameFlagsCard.TypeDescription & Constraintsdoco
.. Consent 1..1BaseXML Namespace: urn:hl7-org:v3
Base for all types and resources
... @classCode 0..1csBinding: ActClass (required)
Fixed Value: CONS
... @moodCode 0..1csBinding: ActMood (required)
Fixed Value: EVN
... templateId 0..*II
... code 0..1CEBinding: v3 Code System ActCode (extensible)
... statusCode 1..1CSBinding: ActStatus (required)
.... @code 1..1csFixed Value: completed

doco Documentation for this format

Terminology Bindings (Differential)

PathConformanceValueSet / Code
Consent.classCoderequiredFixed Value: CONS
Consent.moodCoderequiredFixed Value: EVN
Consent.codeextensibleActCode
Consent.statusCoderequiredActStatus

 

Other representations of profile: CSV, Excel