Personal Health Record System Functional Model, Release 2
0.1.0 - CI Build

Personal Health Record System Functional Model, Release 2 - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

## Example Requirements: PH.1.2 Manage PHR Account Holder Demographic Information (Function)

Active as of 2024-01-31

PH.1.2#01 | SHALL | The system SHALL capture the PHR Account Holder's demographic information. Satisfied by: https://www.hl7.org/fhir/patient.html
PH.1.2#02 | SHALL | The system SHALL store and retrieve the PHR Account Holder's demographic information as discrete data.
PH.1.2#03 | SHALL | The system SHALL provide the ability to import and/or receive the PHR Account Holder's demographic data from existing digital sources (including, for example, from a provider's EHR-S or a health plan system).
PH.1.2#04 | SHOULD | The system SHOULD provide the ability to enter or update demographic data that has not been synchronized with other source systems.
PH.1.2#05 | SHALL | The system SHALL provide the ability to render a PHR Account Holder's demographic data according to user preference and/or consent, organizational policy, and/or jurisdictional law.
PH.1.2#06 | SHOULD | The system SHOULD store historical values of demographic data (e.g., various residence addresses, or marital status changes).
PH.1.2#07 | SHALL | The system SHALL present identifying information with any presentation of the PHR Account Holder's data (unless the information has been tagged as needing to be de-identified) according to organizational policy and/or jurisdictional law. For example, the PHR Account Holder's name ought to appear on each screen to help a mother distinguish the screen displays of the PHRs for each of her minor children. Another example is that the PHR Account Holder's name should not appear -- and the information should be de-identified -- when the information is being shared with a research organization.
PH.1.2#08 | SHOULD | IF one PHR Account Holder has certain information in common with a second PHR Account Holder, THEN the system SHOULD provide the ability to auto-populate the second PHR Account Holder's information with certain common information from the first PHR Account Holder's account according to user role, organizational policy, and/or jurisdictional law. For example, a mother may auto-populate her infant's resident address information using her own resident address information.
PH.1.2#09 | SHOULD | The system SHOULD provide the ability for the PHR Account Holder to annotate demographic data with text comments.
PH.1.2#10 | SHOULD | The system SHOULD provide the ability for the PHR Account Holder to control access to demographic information.