Consent Binding to XDS: Difference between revisions
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
===Consent Binding to XDS=== | ===Consent Binding to XDS=== | ||
The consent binding to XDS is the same as the [[Medical Document Binding to XDS, XDM and XDR]], with the exception of the following XDSDocumentEntry metadata fields in the table below. Changes are <u>'''highlighted'' | The consent binding to XDS is the same as the [[Medical Document Binding to XDS, XDM and XDR]], with the exception of the following XDSDocumentEntry metadata fields in the table below. Changes are <u>'''highlighted'''</u>. | ||
{|border="2" cellspacing="0" cellpadding="4" width="100%" | {|border="2" cellspacing="0" cellpadding="4" width="100%" | ||
Revision as of 11:33, 14 May 2007
Consent Binding to XDS
The consent binding to XDS is the same as the Medical Document Binding to XDS, XDM and XDR, with the exception of the following XDSDocumentEntry metadata fields in the table below. Changes are highlighted.
| XDSDocumentEntry Attribute | Optional? | Source Type | Source/ Value |
|---|---|---|---|
| authorPerson The author is a required element, and is the person issuing the consent (e.g. the patient, guardian, or legal guardian). |
R | ||
| classCode This attributes are fixed to the value "Consent" by this binding. |
R | FAD | Consent |
| classCodeDisplayName This attributes are fixed to the value "Consent" by this binding. |
R | FAD | Consent |
| confidentialityCode The binding has not changed from XDS, however, note that a consent document may also be assigned a confidentialityCode, because the content of the document may be restricted to users in specific functional roles due to the possibly sensitive nature of the content of the consent document. |
R | ||
| eventCodeList The eventCodeList shall be populated using the codes identifying the policies that have been consented to within the document. |
R | CADT | /ClinicalDocument/authorization/consent/ code/@code |
| eventCodeDisplayNameList The eventCodeDisplayNameList shall be populated using the display names for those policies. |
R |
CADT | /ClinicalDocument/authorization/consent/ code/@displayName |
| legalAuthenticator The legalAuthenticator of a consent document shall be present if available, If the Patient Privacy Consent is digitally signed than the legalAuthenticator shall be one of the persons whose digital signature attests to the content of the consent document. If the consent is not digitally signed then the legalAuthenticator shall be the representative of the Affinity Domain that is attesting that the patient has consented. |
R2 | SAT | $person <= /ClinicalDocument/legalAuthenticator |
| serviceStartTime The serviceStartTime shall be present and indicates the effective start time of the consent. |
R | SA | /ClinicalDocument/documentationOf/serviceEvent/ effectiveTime/low/@value |
| serviceStopTime The serviceStopTime may be present, and if it is present, indicates the effective time at which the consent is no longer effective. If it is not present, the time at which the consent is no longer effective is controlled by XDS Affinity Domain policy. |
R2 | SA | /ClinicalDocument/documentationOf/serviceEvent/ effectiveTime/high/@value |