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.3.6 Manage PHR Data Import and Export (Function)

Page standards status: Informative
Statement N:

Allow the PHR Account Holder to manage the import to and export of data from a PHR-S.

 Description I:

A PHR Account Holder needs to prescribe how data is exchanged with other systems including how data is imported to the PHR-S, and the parameters for data export (e.g., who, when, or the extent of data). Some import and export functions may be one-time events; other exchanges, for example, may occur at regular intervals (such as via a subscription service). The PHR Account Holder should be able to determine the information or data that he/she will accept into the PHR. The system should record the acknowledgement or refusal of data sent to the Account Holder’s PHR-S. Use of exported data should be constrained according its intended and permitted purpose of use (e.g., as described in the PHR-S manufacturer's Terms of Service and Terms of Use agreements).

Example(s): The PHR Account Holder may desire to inform her General Practitioner that the PHR Account Holder has received a proposed dietary regimen from a Registered Dietitian / Nutrition specialist. The PHR Account Holder may also desire to send a copy of the proposed nutrition care plan to the General Practitioner.

 Criteria N:
S.3.6#01 SHOULD

The system SHOULD provide the ability to exchange PHR Account Holder data content with another PHR system.

 Satisfied by:
  1. https://hl7.org/fhir/uv/bulkdata/
S.3.6#02 SHOULD

The system SHOULD provide the ability to exchange PHR Account Holder data content with other systems.
S.3.6#03 SHOULD

The system SHOULD provide the ability to exchange PHR Account Holder data content with other systems.
S.3.6#04 SHOULD

The system SHOULD provide the ability for the PHR Account Holder to determine entities from which data may be imported into the PHR-S.
S.3.6#05 SHOULD

The system SHOULD provide the ability for the PHR Account Holder to determine entities to which data may be exported from the PHR-S.
S.3.6#06 SHOULD

The system SHOULD provide the ability for the PHR Account Holder to exchange information with an entity on a one-time basis.
S.3.6#07 SHOULD

The system SHOULD provide the ability for the PHR Account Holder to exchange information with an entity on a recurring basis.
S.3.6#08 SHOULD

The system SHOULD provide the ability for the PHR Account Holder to annotate incoming information.
S.3.6#09 SHOULD

The system SHOULD provide the ability for the PHR Account Holder to render a notification (i.e., an acknowledgment) of the receipt or the refusal to receive information that was sent from another system.
S.3.6#10 SHALL

The system SHALL conform to TI.1.5 (Non-Repudiation) to promote provenance regarding professionally-sourced clinical information.