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

HL7 Personal Health Record System Functional Model, Release 2, published by EHR WG. This guide is not an authorized publication; it is the continuous build for version 2.0.1-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phrsfm-ig/ and changes regularly. See the Directory of published versions

Requirements: S.4.2 Registry Notification and Management (Function)

Page standards status: Informative
Statement N:

Enable data sharing and communication with registries and manage the related information shared.

 Description I:

Support the automated transfer of formatted demographic and clinical information to disease-specific registries (and other notifiable registries) to enable PHR Account Holder to participate, if and as desired, in provider and public health monitoring and subsequent epidemiological analysis.

The PHR Account Holder can export personal health information to disease-specific registries, other notifiable registries such as immunization registries, through standard data transfer protocols or messages. The PHR Account Holder can update and configure communication for new registries, or delete communication with an existing registry.

 Criteria N:
S.4.2#01 SHALL

The system SHALL conform to function TI.1.1 (Entity Authentication).
S.4.2#02 SHALL

The system SHALL conform to function TI.1.3 (Entity Access Control).
S.4.2#03 SHOULD

The system SHOULD provide the ability to manage information exchange and communication with registries.
S.4.2#04 dependent MAY

The system MAY provide the ability to exchange demographic and clinical information with disease-specific registries (and other notifiable registries) according to PHR Account Holder's preferences and/or consents, organizational policy, and/or jurisdictional law.
S.4.2#05 dependent MAY

The system MAY provide the ability to manage a pointer to PHR Account Holder registry information that might exist in a registry according to PHR Account Holder's preferences and/or consents, organizational policy, and/or jurisdictional law.