HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1 - International flag

HL7 Electronic Health Record System Functional Model, Release 2.1.1, published by HL7 International / Electronic Health Records. This guide is not an authorized publication; it is the continuous build for version 2.1.1 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/mvdzel/ehrsfm-fhir-r5/ and changes regularly. See the Directory of published versions

Requirements: CP.9.2 Capture Health Service Report Information (Function)

Official URL: http://hl7.org/ehrs/uv/ehrsfmr2/Requirements/EHRSFMR2-CP.9.2 Version: 2.1.1
Standards status: Normative Active as of 2025-10-31 Computable Name: CP_9_2_Capture_Health_Service_Report_Information

Support the creation of health service reports to authorized health entities that a provider may be required to generate (e.g., the creation of an oncologist's report that must be submitted to a national cancer registry).

Statement N:

Support the creation of health service reports to authorized health entities that a provider may be required to generate (e.g., the creation of an oncologist's report that must be submitted to a national cancer registry).

Description I:

Providers are prompted to collect sufficient information in the course of care to avoid duplicate, retrospective or other additional data entry as part of supporting health management programs and reporting, for example public health, such as notifiable condition reports, immunization, cancer registry and discharge data.

Criteria N:
CP.9.2#01
MAY

The system MAY render a notification that prompts providers on the data needed for end of encounter reporting during the continuum of care to streamline end of care data collection.
CP.9.2#02
SHOULD

The system SHOULD provide the ability to render service reports at the completion of an episode of care (e.g., discharge summaries or public health reports) using data collected during the encounter.
CP.9.2#03
 conditional
MAY

IF the patient is tagged as deceased, THEN the system MAY provide the ability to capture (i.e., trigger) and render the collection of death certificate data.
CP.9.2#04
SHOULD

The system SHOULD provide the ability to capture and render the acknowledgement that health service reports have been received.
CP.9.2#05
SHALL

The system SHALL conform to function CP.9.1 (Produce a Summary Record of Care).
CP.9.2#06
SHOULD

The system SHOULD render a notification that prompts providers on the information needed for regulatory safety reporting.