Name: Basic Patient Privacy Consents (IHE BPPC)
Identifier: IHE BPPC
Issuing Organisation: Integrating the Healthcare Enterprise (IHE)
Organization website (opens in new window): https://www.ihe.net/
Link to standard (opens in new window): https://wiki.ihe.net/index.php/Basic_Patient_Privacy_Consents
Availability: Free to Access
Type: IHE Profile
Issue Year: unknown
Forward Review Date: Not known
Intended Audiences: Private Sector Bodies, Professional and Trade Bodies, and Governmental and Public Sector Bodies
Basic Patient Privacy Consents profile provide mechanisms to:
– Record the patient privacy consent(s),
– Enforce the privacy consent appropriate to the use.
First: The Affinity Domain organizers create a set of policies. Each of the policies are each given an OID. This OID now is an Affinity Domain specific vocabulary. Each OID can clearly identify one of the policies defined by the HIE. There are examples of how one might build these policies in a way that allows the patient to select appropriately the type of sharing they agree to. This was important as it allows the Affinity Domain to define their own policies in as clear of language as was necessary for the patients, providers, and systems to understand. This level of policy writing is necessary before one can even hope to commit the logic to computer encoding.
Second: The BPPC profile shows how to capture a patient’s acknowledgment and/or signature of one or more of these policies. This is captured using an CDA document with optionally a scanned copy or optionally a digitally signature. The scanned copy might be the patient’s ink on paper acknowledgment. This capability has been very well received as providers like to see that ink was put to paper. I suspect that this step will never be replaced. Patients have a need to know what they are consenting to. They can understand human text, but not many can understand computer logic.
Third: When a document is used, the document consumer Actors are obligated to enforce the acceptable use. The document consumer Actor is required to block access to documents that are not authorized. Any OIDs that are not understood by the document consumer Actor must not be used to enable access.
Relevance to Active and Healthy Ageing: Medium
Older Person Specific: No
Usage / Adoption status: IHE Profile endorsed by European Commission for Public Procurement
This IHE Profile is an essential building block in establishing interoperable digital tools in support of healthcare, thereby supporting seamless integrated healthcare for all generations incl. the elderly. This IHE Profile is mentioned in COMMISSION DECISION (EU) 2015/1302 of 28 July 2015 on the identification of ‘Integrating the Healthcare Enterprise’ profiles for referencing in public procurement (see Official Journal of the European Union, L199/43): (7) On 2 October 2014, the European multi-stakeholder platform on ICT standardisation evaluated 27 ‘Integrating the Healthcare Enterprise’ (IHE) profiles against the requirements set out in Annex II to Regulation (EU) No 1025/2012 and gave a positive advice to their identification for referencing in public procurement. The evaluation of the 27 IHE profiles was subsequently submitted to consultation of the eHealth network established by Article 14 of Directive 2011/24/EU of the European Parliament and of the Council (2) that confirmed the positive advice to their identification. (8) IHE develops ICT technical specifications in the field of healthcare information technology. The 27 IHE profiles are detailed specifications developed over a period of 15 years within the committees of IHE that optimise the selection of well-established standards describing the different layers of interoperability (i.e. protocol communication, technical, syntactical, semantic and application levels) with a view to find interoperability solutions for exchanging or sharing medical data. (9) The 27 IHE profiles have the potential to increase interoperability of eHealth services and applications to the benefit of patients and medical community. The 27 IHE profiles should therefore be identified as ICT technical specifications eligible for referencing in public procurement.
We are sorry that this content was not useful for you!
Let us improve this content!
Tell us how we can improve this content?