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-268: Manage Patient History Req-767: Manage Structured Health Record Information
(Matches) Release Package: 2013 Format 2013 Format
(No Match) Title: Manage Patient History Manage Structured Health Record Information
(No Match) Description: STATEMENT: Capture and maintain medical, procedural/surgical, social and family history including the capture of pertinent positive and negative histories, patient-reported or externally available patient clinical history.
DESCRIPTION: The history of the current illness and patient historical data related to previous medical diagnoses, surgeries and other procedures performed on the patient, and relevant health conditions of family members is captured through such methods as patient reporting (for example interview, medical alert band) or electronic or non-electronic historical data. This data may take the form of a pertinent positive such as: "The patient/family member has had..." or a pertinent negative such as "The patient/family member has not had..." When first seen by a health care provider, patients typically bring with them clinical information from past encounters. This and similar information is captured and presented alongside locally captured documentation and notes wherever appropriate.
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): Birth Information, Child Abuse Reporting, Child Welfare, Genetic information, Parents and Guardians and Family Relationship Data, Patient Identifier, Prenatal Screening, Primary Care Management, Security and Confidentiality, Specialized Scales/Scoring, 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: S.2.2.1, S.3.5, IN.1.7, IN.2.5.1, IN.2.5.2, IN.4.1, IN.4.2, IN.4.3, IN.5.1, IN.5.2, IN.5.4
(No Match) Comments:
(Matches) Additional Information:
(Matches) Implementation Notes:
Scroll To Top