HL7 Personal Health Record System Functional Model, Release 2
2.0.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## Requirements: PH.2.5.8 Maintain Family History (Function)

Page standards status: Informative

Statement N:

Manage the PHR Account Holder's Family Health History.

Description I:

The family history traditionally imparts the PHR Account Holder with certain risks and probabilities of illnesses that have a familial component. The major illnesses and cause of death of primary family members should be captured and displayed. For some illnesses of the PHR Account Holder a negative family history is also pertinent such as for cancer.

Actors:
ehr Criteria N:

PH.2.5.8#01 | dependent SHALL | The system SHALL provide the ability to manage family history according to organizational policy and/or jurisdictional law. Satisfied by: https://www.hl7.org/fhir/familymemberhistory.html
PH.2.5.8#02 | SHOULD | The system SHOULD provide the ability to capture, maintain, and transmit a request-for-correction to family history that was captured from an external source. Note: There could be multiple types of errors, both unintentional and intentional; the errors could also reside in multiple storage locations (primary, secondary, and intermediary); the errors could also reside in current records or in archived records; there could also be multiple sources (author, custodian-of-record, transcriptionist).
PH.2.5.8#03 | SHOULD | The system SHOULD provide the ability for the PHR Account Holder to annotate the family history with text comments (e.g., "Great-grandmother Alice was lost at sea” and that "Uncle Robert disagrees with the cause-of-death attributed to great-grandmother Alice".)
PH.2.5.8#04 | SHALL | The system SHALL provide the ability to enter missing information regarding the family history.
PH.2.5.8#05 | dependent MAY | The system MAY provide the ability to exchange family history entries with the PHR Accounts of other family members according to user preference and/or consent, user role, organizational policy, and/or jurisdictional law.