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-256: Manage Consents and Authorizations Req-767: Manage Structured Health Record Information
(Matches) Release Package: 2013 Format 2013 Format
(No Match) Title: Manage Consents and Authorizations Manage Structured Health Record Information
(No Match) Description: STATEMENT: Create, maintain, and verify patient decisions such as informed consent for treatment and authorization/consent for disclosure when required.
DESCRIPTION: Decisions are documented and include the extent of information, verification levels and exposition of treatment options. This documentation helps ensure that decisions made at the discretion of the patient, family, or other responsible party govern the actual care that is delivered or withheld.
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): Children with Special Healthcare Needs, Parents and Guardians and Family Relationship Data, Primary Care Management, Records Management, Security and Confidentiality, Special Terminology and Information 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.3, S.2.2.2, S.3.5.1, S.3.5.4, IN.1.5, IN.1.8, IN.1.9, IN.2.2, 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