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-264: Manage Results Req-767: Manage Structured Health Record Information
(Matches) Release Package: 2013 Format 2013 Format
(No Match) Title: Manage Results Manage Structured Health Record Information
(No Match) Description: STATEMENT: Present, annotate, and route current and historical test results to appropriate providers or patients for review. Provide the ability to filter and compare results.
DESCRIPTION: Results of tests are presented in an easily accessible manner to the appropriate providers. Flow sheets, graphs, or other tools allow care providers to view or uncover trends in test data over time. In addition to making results viewable, it is often necessary to send results to appropriate providers using electronic messaging systems, pagers, or other mechanisms. Documentation of notification is accommodated. Results may also be routed to patients electronically or by letter.
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): Primary Care Management, Records Management 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.2.4.3, S.2.2.1, S.3.7.1, IN.1.6, IN.1.7, IN.2.4, IN.2.5.1, IN.2.5.2, IN.6
(No Match) Comments:
(Matches) Additional Information:
(Matches) Implementation Notes:
Scroll To Top