HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1-ballot - Normative Ballot 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-ballot 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: CPS.9.4 Standard Report Generation (Function)

Page standards status: Informative
Statement N:

Provide report generation features using tools internal or external to the system, for the generation of standard reports.

 Description I:

Providers and administrators need access to data in the EHR-S for clinical, administrative, financial decision-making, audit trail and metadata reporting, as well as to create reports for patients. Many systems may use internal or external reporting tools to accomplish this. Reports may be based on structured data, and/or unstructured text from the patient's health record.

Users need to be able to sort, and/or filter reports. For example:

  • the user may wish to view only the diabetic patients on a report listing patients and diagnoses-the user may wish to view only male patients over 35 with a complaint of chest pain.
 Criteria N:
CPS.9.4#01 SHOULD

The system SHOULD provide the ability to render reports of structured clinical and administrative data using either internal or external reporting tools.
CPS.9.4#02 MAY

The system MAY provide the ability to extract unstructured clinical and administrative data for inclusion in the report generation process, using internal or external tools.
CPS.9.4#03 SHOULD

The system SHOULD provide the ability to extract and transmit reports generated.
CPS.9.4#04 SHOULD

The system SHOULD provide the ability to capture and maintain report parameters, based on patient demographic, and/or clinical data, which would allow sorting, and/or filtering of the data.
CPS.9.4#05 MAY

The system MAY provide the ability to save report parameters for generating subsequent reports either as integrated component of the system, or an external application, using data from the system.
CPS.9.4#06 MAY

The system MAY provide the ability to edit one or more parameters of a saved report specification when generating a report using that specification either as an integrated component of the system, or an external application, using data from the system.
CPS.9.4#07 SHOULD

The system SHOULD provide the ability to render automated reports as required by industry and regulatory bodies.
CPS.9.4#08 SHOULD

The system SHOULD provide the ability to extract facility level data at an organizational level in support of organizational initiatives.
CPS.9.4#09 MAY

The system MAY provide the ability to render a cumulative directory of all personnel who use or access the data.