BPPC
E208065
BPPC (Basic Patient Privacy Consents) is an IHE IT Infrastructure profile that defines how healthcare systems capture, manage, and enforce patients’ privacy consent directives in electronic health information exchange.
All labels observed (1)
| Label | Occurrences |
|---|---|
| BPPC canonical | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1869357 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: BPPC Context triple: [IHE IT Infrastructure profiles, includesProfile, BPPC]
-
A.
BEP
BEP is a United States government agency responsible for designing and producing paper currency and other secure documents.
-
B.
PPS
PPS is the commonly used abbreviation for Parliamentary Private Secretaries, who are junior MPs acting as unpaid assistants and political aides to government ministers in the UK.
-
C.
PAPPG
PAPPG is the National Science Foundation’s comprehensive guide outlining the policies, procedures, and requirements for preparing and managing NSF grant proposals and awards.
-
D.
DBAP
DBAP is the commonly used abbreviation for Durham Bulls Athletic Park, a minor league baseball stadium in Durham, North Carolina.
-
E.
PBAP
PBAP (Phone Book Access Profile) is a Bluetooth profile that enables devices like car kits and headsets to access and manage a phone’s contacts and call history wirelessly.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: BPPC Target entity description: BPPC (Basic Patient Privacy Consents) is an IHE IT Infrastructure profile that defines how healthcare systems capture, manage, and enforce patients’ privacy consent directives in electronic health information exchange.
-
A.
BEP
BEP is a United States government agency responsible for designing and producing paper currency and other secure documents.
-
B.
PPS
PPS is the commonly used abbreviation for Parliamentary Private Secretaries, who are junior MPs acting as unpaid assistants and political aides to government ministers in the UK.
-
C.
PAPPG
PAPPG is the National Science Foundation’s comprehensive guide outlining the policies, procedures, and requirements for preparing and managing NSF grant proposals and awards.
-
D.
DBAP
DBAP is the commonly used abbreviation for Durham Bulls Athletic Park, a minor league baseball stadium in Durham, North Carolina.
-
E.
PBAP
PBAP (Phone Book Access Profile) is a Bluetooth profile that enables devices like car kits and headsets to access and manage a phone’s contacts and call history wirelessly.
- F. None of above. chosen
Statements (46)
| Predicate | Object |
|---|---|
| instanceOf |
IHE IT Infrastructure profile
ⓘ
privacy consent profile ⓘ |
| abbreviationFor | Basic Patient Privacy Consents ⓘ |
| addresses |
patient privacy requirements
ⓘ
regulatory compliance for consent ⓘ |
| appliesTo |
electronic health records
ⓘ
health information exchange networks ⓘ |
| category | health IT interoperability profile ⓘ |
| concerns | protected health information ⓘ |
| constrains |
access control decisions based on consent
ⓘ
how systems share protected health information ⓘ |
| definedByOrganization | Integrating the Healthcare Enterprise ⓘ |
| defines |
methods to capture patient privacy consents
ⓘ
methods to enforce patient privacy consents ⓘ methods to manage patient privacy consents ⓘ |
| domain | healthcare privacy and security ⓘ |
| enables |
automated enforcement of consent rules
ⓘ
exchange of consent information between organizations ⓘ |
| focusesOn |
electronic health information exchange
ⓘ
patient privacy consent directives ⓘ |
| fullName | Basic Patient Privacy Consents ⓘ |
| goal |
enable interoperable representation of patient privacy consents
ⓘ
ensure that access to health data respects patient choices ⓘ standardize consent communication between systems ⓘ |
| mayBeExtendedBy | more advanced consent profiles ⓘ |
| partOfDomain |
IHE IT Infrastructure profiles
ⓘ
surface form:
IHE IT Infrastructure Technical Framework
|
| relatedTo |
IHE ATNA
ⓘ
surface form:
IHE ATNA profile
IHE XDS profile ⓘ IHE profile XUA ⓘ
surface form:
IHE XUA profile
|
| represents | patient consent as structured electronic artifacts ⓘ |
| requires |
patient identification
ⓘ
policy identification ⓘ |
| status | published IHE profile ⓘ |
| supports | granular control of data sharing based on consent ⓘ |
| supportsProcess |
querying consent status
ⓘ
recording patient consent decisions ⓘ revoking patient consent decisions ⓘ updating patient consent decisions ⓘ |
| usedBy |
EHR systems
ⓘ
health information exchange platforms ⓘ regional health information organizations ⓘ |
| usedIn | cross-enterprise document sharing environments ⓘ |
| usesConcept |
authorizing provider identifiers
ⓘ
consent document ⓘ patient identifiers ⓘ policy identifiers ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: BPPC Description of subject: BPPC (Basic Patient Privacy Consents) is an IHE IT Infrastructure profile that defines how healthcare systems capture, manage, and enforce patients’ privacy consent directives in electronic health information exchange.
Referenced by (1)
Full triples — surface form annotated when it differs from this entity's canonical label.