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-249: Health Record Output Req-767: Manage Structured Health Record Information
(Matches) Release Package: 2013 Format 2013 Format
(No Match) Title: Health Record Output Manage Structured Health Record Information
(No Match) Description: STATEMENT: Support the definition of the formal health record, a partial record for referral purposes, or sets of records for other necessary disclosure purposes.
DESCRIPTION: Provide hardcopy and electronic output that fully chronicles the healthcare process, supports selection of specific sections of the health record, and allows healthcare organizations to define the report and/or documents that will comprise the formal health record for disclosure purposes. A mechanism should be provided for both chronological and specified record element output. This may include defined reporting groups (i.e. print sets). For example: Print Set A = Patient Demographics, History & Physical, Consultation Reports, and Discharge Summaries. Print Set B = all information created by one caregiver. Print Set C = all information from a specified encounter. An auditable record of these requests and associated exports may be maintained by the system. This record could be implemented in any way that would allow the who, what, why and when of a request and export to be recoverable for review. The system has the capability of providing a report or accounting of disclosures by patient that meets in accordance with scope of practice, organizational policy and jurisdictional law.
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): Immunizations, Patient Identifier, Records Management, Registry Linkages, Security and Confidentiality, 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: DC.1.1.4, DC.1.4, IN.1.2, IN.2.5.1, IN.2.5.2, IN.4.1, IN.4.3, IN.5.1, IN.5.4, IN.6
(No Match) Comments:
(Matches) Additional Information:
(Matches) Implementation Notes:
Scroll To Top