United States Health Information Knowledgebase

 

You are viewing the Abridged Children's EHR Format.
To view the Full Children's EHR Format, you must first agree to the HL7 License Agreement.

Children's EHR Format Requirement Comparison

(No Match) Requirement ID: Req-278: Standard Report Generation Req-767: Manage Structured Health Record Information
(Matches) Release Package: 2013 Format 2013 Format
(No Match) Title: Standard Report Generation Manage Structured Health Record Information
(No Match) Description: STATEMENT: Provide report generation features using tools internal or external to the system, for the generation of standard reports.
DESCRIPTION: 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 (such as Crystal Report).
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.
STATEMENT: Create, capture, and maintain structured health record information.

DESCRIPTION: Structured health record information is divided into discrete fields, and may be enumerated, numeric or codified.

Examples of structured health information include:
- patient address (non-codified, but discrete field)
- diastolic blood pressure (numeric)
- coded result observation
- coded diagnosis
- patient risk assessment questionnaire with multiple-choice answers

Context may determine whether or not data are unstructured, e.g., a progress note might be standardized and structured in some EHRS (e.g., Subjective/Objective/Assessment/Plan) but unstructured in others.
(No Match) Topic Area(s): Activity Clearance, Birth Information, EPSDT, Records Management, Well Child/Preventive Care Well Child/Preventive Care
(Matches) Provenance: HL7 EHR FM R1 HL7 EHR FM R1
(Matches) Achievability:
(Matches) Requirement Type: Function Function
(Matches) Shall/Should/May:
(Matches) Critical/Core: no no
(Matches) Status: Released Released
(Matches) Links:
(No Match) See Also: IN.1.9, IN.2.5.1, IN.2.5.2, IN.4.1, IN.4.3
(No Match) Comments:
(Matches) Additional Information:
(Matches) Implementation Notes:
Scroll To Top