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

This page is part of the HL7 Personal Health Record System Functional Model, Release 2 (v2.0.1-ballot: Normative 1 Ballot 1) based on FHIR (HL7® FHIR® Standard) v5.0.0. No current official version has been published yet. For a full list of available versions, see the Directory of published versions

Requirements: S.2.4 Manage Ad Hoc Reporting (Function)

Page standards status: Informative
Statement N:

Allow PHR Account Holders or authorized designees to request and read ad hoc reports of PHR information.

Description I:

PHR Account Holders may request ad hoc, non-standard reports. The purpose is not for PHR interchange but rather for PHR Account Holder’s analysis of his/her health related financial and administrative data, and for sharing (if desired).

Actors:
ehr
Criteria N:
S.2.4#01 SHOULD

The system SHOULD provide the ability for the authorized PHR Account Holder to render ad hoc reports of the PHR.

Satisfied by:
  1. https://www.hl7.org/fhir/measure.html
S.2.4#02 SHOULD

The system SHOULD provide the ability for the authorized PHR Account Holder to render customized reports of summarized information based on sort and filter controls for date or data range, problem, or other clinical data element or categories (e.g., medications or providers).

S.2.4#03 SHOULD

The system SHOULD provide the ability to maintain ad hoc reports for future retrieval and use.

S.2.4#04 SHOULD

The system SHOULD provide the ability to maintain summarized information through customized reports based on prioritization of chronology, problem or other pertinent information of importance to the authorized PHR Account Holder.

S.2.4#05 SHALL

The system SHALL manage data visibility for PHR Account Holder Proxies using confidentiality-related preferences that were previously established by the PHR Account Holder for all ad hoc reporting capabilities.

S.2.4#06 MAY

The system MAY provide the ability to render consolidated reports across family members (e.g., children).

S.2.4#07 SHOULD

The system SHOULD conform to TI.1.1 (Entity Authorization).

S.2.4#08 SHALL

The system SHALL conform to TI.2 (Auditable Records).

S.2.4#09 MAY

The system (or an external application using data from the PHR-S) MAY provide the ability to capture and maintain parameters for ad hoc reports.