IHE Patient Care Coordination Technical Framework Vol I

More documents

Recommendations

Info

PCC Technical Framework V3.0, vol. 1 ________________________________________________________________________ 1340 For more details on these profiles, see the IHE IT Infrastructure Technical Framework, found here: http://www.ihe.net/Technical_Framework/. Thus, implementors of the Content Consumer and Content Creator Actors must also implement either the ITI XDS, XDM or XDR Profiles to exchange content, using the bindings listed below. Content Binding Actor Optionality Consent to Share Information Consent Binding to XD* Content Creator Content Consumer R R Medical Documents Medical Document Binding to XD* Content Creator Content Consumer R R 1345 1350 1355 1360 1365 3.3.9 Consent Content Module Table 3.3-5 BPPC Bindings A consent document is a kind of medical document, and shall conform to the requirements of the Consent content module specified in this profile. The content of a consent document shall include the effective time of the consent and coded vocabulary identifying the policies consented to (OID). The content of the consent document may include a text description of what the patient has consented to, and either a facsimile of a wet signature, or a digital signature by the patient (or legal representative). The consent if signed shall use the IHE ITI DSG profile. 3.3.10 BPPC Process Flow The BPPC profile uses the normal process flow of the XD* profiles, depending upon which bindings have been declared. 1. Administrative tasks prior to BPPC use 1. The Affinity Domain will write and agree to the Affinity Domain Policy (lots of lawyers involved). 2. The Affinity Domain Policy will include a small set of Privacy Consent Policies (more lawyers). These are text documents very similar to the privacy consent documents used today. 3. Each Privacy Consent Policy will be given an XDS Affinity Domain unique identifier (OID) 4. The Affinity Domain Policy and all of the Privacy Consent Policies will be published in a way consistent with the Affinity Domain's Policy. It is expected that this will be sufficiently public to support local regulation. _____________________________________________________________________ 49 Revision 3.0 Public Comment — June 25, 2007 Copyright © 1997-2007: ACC/HIMSS/RSNA
PCC Technical Framework V3.0, vol. 1 ________________________________________________________________________ 1370 1375 1380 1385 1390 1395 2. Patient consents to a policy 1. The Patient will be presented with the Affinity Domain – Patient Privacy Consent Policies. 2. The Patient will agree to one or more of the Privacy Consent Policies. In most regions the patient must be fully informed and acknowledge the privacy consent. In some regions there is implied consent, and thus there is no need to capture a patient's consent. 3. A system that captures patient privacy consents will capture this act in a BPPC Patient Privacy Consent Document. 1. XDS Metadata 1. authorPerson is the patient or legal guardian that is agreeing to the consent. 2. classCode indicates this is a consent document 3. confidentialityCode may indicate other consent OIDS that control this consent document 4. eventCodeList indicates the Privacy Consent Policy identifier (OID) 5. legalAuthenticator would be the digital signer if used, or the identity of the Affinity Domain representative that is confirming that the patient is agreeing. 6. serviceStartTime and serviceStopTime indicate when this consent is effective. 2. Patient Privacy Consent Document 1. template ID = "1.3.6.1.4.1.19376.1.5.3.1.1.7 " 2. The patient or legal guardian that is agreeing to the consent is identified as the author of the consent document. 3. Any witness to this consent may be captured (i.e. participant typeCode='WIT') 4. authorization indicates that this is a consent act 5. Effective time is set 1. When the privacy consent is first effective. This effective date may be retroactive based on the XDS Affinity Domain Policy. 2. If necessary, when the privacy consent is expected to elapse _____________________________________________________________________ 50 Revision 3.0 Public Comment — June 25, 2007 Copyright © 1997-2007: ACC/HIMSS/RSNA
Page 1 and 2: ACC, HIMSS and RSNA Integrating the
Page 3 and 4: PCC Technical Framework V3.0, vol.
Page 49: PCC Technical Framework V3.0, vol.
Page 101 and 102:
PCC Technical Framework V3.0, vol.
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
show all

IHE Patient Care Coordination Technical Framework Vol I

Create successful ePaper yourself

Delete template?

Save as template?