|
|
| (6 intermediate revisions by the same user not shown) |
| 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 described in section 4.1, with the exception of the following XDSDocumentEntry metadata fields <u>'''highlighted''</u><u>'</u> in the table below.
| |
| {|border="2" cellspacing="0" cellpadding="4" width="100%"
| |
| |-
| |
| |align = "center" |align = "center"|<font size = "1">XDSDocumentEntry</font><br><font size = "1">Attribute</font>
| |
| |align = "center"|<font size = "1">Optional?</font>
| |
| |align = "center"|<font size = "1">Constrained?</font><br>
| |
| |align = "center"|<font size = "1">Extended Discussion?</font>
| |
| |align = "center"|<font size = "1">Source Type</font>
| |
| |align = "center"|<font size = "1">Source/ Value</font>
| |
| |-
| |
|
| |
|
| |-
| | In the summer of 2007, the BPPC profile for which the Consent Binding applies was transferred to the IT Infrastructure Domain. The current profile supplement can be found here http://www.ihe.net/Technical_Framework/index.cfm#IT |
| |-
| |
| | |
| |authorPerson
| |
| |align = "center"|<u>'''R'''</u>
| |
| |
| |
| |4.1.1.1
| |
| |
| |
| |
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |classCode
| |
| |align = "center"|R
| |
| |
| |
| |4.1.1.2
| |
| |<u>'''FAD'''</u>
| |
| |<font size = "1"><u>'''Consent'''</u></font>
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |classCodeDisplayName
| |
| |align = "center"|R
| |
| |
| |
| |4.1.1.2
| |
| |<u>'''FAD'''</u>
| |
| |<font size = "1"><u>'''Consent'''</u></font>
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |confidentialityCode
| |
| |align = "center"|R
| |
| |
| |
| |4.1.1.3
| |
| |
| |
| |
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |eventCodeList
| |
| |<u>'''R'''</u><br>
| |
| |
| |
| |4.1.1.4
| |
| |<u>'''CADT'''</u>
| |
| |<font size = "1"><u>'''/ClinicalDocument/authorization<br> /consent/code/@code'''</u></font>
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |eventCodeDisplay<br>NameList
| |
| |align = "center"|<br><u>'''R'''</u>
| |
| |
| |
| |4.1.1.4
| |
| |<u>'''CADT'''</u>
| |
| |<font size = "1"><u>'''/ClinicalDocument/authorization<br> /consent/code/@displayName'''</u></font>
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |legalAuthenticator
| |
| |align = "center"|<u>'''R2'''</u>
| |
| |
| |
| |4.1.1.5
| |
| |SAT
| |
| |<font size = "1">$person <nowiki><</nowiki>= /ClinicalDocument/<br> legalAuthenticator</font>
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |serviceStartTime
| |
| |align = "center"|<u>'''R'''</u>
| |
| |
| |
| |4.1.1.6
| |
| |SA
| |
| |<font size = "1">/ClinicalDocument<br> /documentationOf/serviceEvent<br> /effectiveTime/low/@value</font>
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |serviceStopTime
| |
| |align = "center"|R2
| |
| |
| |
| |4.1.1.6
| |
| |SA
| |
| |<font size = "1">/ClinicalDocument<br> /documentationOf/serviceEvent<br> /effectiveTime/high/@value</font>
| |
| |-
| |
| | |
| |-
| |
| |-
| |
| | |
| |}
| |
| | |
| ====Extended Discussion====
| |
| =====author=====
| |
| The author is a required element, and is the person issuing the consent (e.g. the patient, guardian, or legal guardian).
| |
| | |
| =====classCode and classCodeDisplayName=====
| |
| These attributes are fixed to the value "Consent" by this binding.
| |
| | |
| =====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.
| |
| | |
| =====eventCodeList and eventCodeDisplayNameList=====
| |
| The eventCodeList shall be populated using the codes identifying the policies that have been consented to within the document. The eventCodeDisplayNameList shall be populated using the display names for those policies.
| |
| | |
| =====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.
| |
| | |
| =====serviceStartTime and serviceStopTime=====
| |
| The serviceStartTime shall be present and indicates the effective start time of the consent. 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 effectiveStopTime is assumed to be controlled by XDS Affinity Domain policy. | |
Consent Binding to XDS
In the summer of 2007, the BPPC profile for which the Consent Binding applies was transferred to the IT Infrastructure Domain. The current profile supplement can be found here http://www.ihe.net/Technical_Framework/index.cfm#IT