This page is part of the CDA: Clinical Document Architecture (v2.0.0-sd-snapshot1: CDA2 Draft) based on FHIR (HL7® FHIR® Standard) v5.0.0. . For a full list of available versions, see the Directory of published versions
Official URL: http://hl7.org/cda/stds/core/ValueSet/CDASignatureCode | Version: 2.0.0-sd-snapshot1 | |||
Draft as of 2023-12-16 | Computable Name: CDASignatureCode |
A set of codes specifying whether and how the participant has attested his participation through a signature - limited to values allowed in original CDA definition.
Note: CDA Release One represented either an intended (X
) or actual (S
) authenticator. CDA Release Two only represents an actual authenticator, so has deprecated the value of X
.
References
http://terminology.hl7.org/CodeSystem/v3-ParticipationSignature
version 2.1.0
Code | Display | Definition |
S | signed | Signature has been affixed, either written on file, or electronic (incl. digital) signature in Participation.signatureText. |
X | required | A signature for the service is required of this actor. |
Expansion based on codesystem ParticipationSignature v2.1.0 (CodeSystem)
This value set contains 2 concepts
Code | System | Display | Definition |
S | http://terminology.hl7.org/CodeSystem/v3-ParticipationSignature | signed | Signature has been affixed, either written on file, or electronic (incl. digital) signature in Participation.signatureText. |
X | http://terminology.hl7.org/CodeSystem/v3-ParticipationSignature | required | A signature for the service is required of this actor. |
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 |