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

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 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.7 Manage New, Additional, or Other Use Request (Function)

Official URL: http://hl7.org/ehrs/uv/phrsfmr2/Requirements/PHRSFMR2-S.3.7 Version: 2.0.1
Standards status: Normative Computable Name: S_3_7_Manage_New__Additional__or_Other_Use_Request

Support the formal and routine request for PHR Account Holder health record information for new, additional, or other uses.

Description I: Provide hardcopy and electronic output that supports the needs of a variety of new, additional, or other uses such as: annual immunization requests from schools/camps, application processing for disability requests, validation of compliance with treatment regimens. This mechanism should be provided for both chronological and specified record element output. An auditable record of these requests and associated exports may be maintained by the system. The system has the capability of providing a report of accounting of disclosures of the secondary PHR Account Holders in accordance with user role, organizational policy and/or jurisdictional law.
Criteria N:
S.3.7#01 SHOULD The system SHOULD provide the ability to capture information regarding the new, additional, or other use data-requestor (including the identity of the requestor, the requestor's intended use of the data, date of the request, and the date of the PHR Account Holder's response to that request) according to user role, organizational policy, and/or jurisdictional law.
S.3.7#02 MAY The system MAY provide the ability for the PHR Account Holder to control access by adding password protection to PHR Account Holder-defined exported information.
S.3.7#03 SHOULD The system SHOULD provide the ability to tag specific PHR information to be reviewed and acted upon by the authorized PHR Account Holder for the purpose of deactivation, destruction, or retention.
S.3.7#04 SHALL The system SHALL provide the ability to render PHR Account Holder identifying information on each page of the reports generated.
S.3.7#05 SHOULD The system SHOULD provide the ability to export PHR records to a variety of PHR Account Holders using various platforms without needing special viewing software.