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-266: Present Ad Hoc Views of the Health Record Req-715: Standard Terminologies and Terminology Models
(Matches) Release Package: 2013 Format 2013 Format
(No Match) Title: Present Ad Hoc Views of the Health Record Standard Terminologies and Terminology Models
(No Match) Description: STATEMENT: Subject to jurisdictional laws and organizational policies related to privacy and confidentiality, present customized views and summarized information from a patient's comprehensive EHR. The view may be arranged chronologically, by problem, or other parameters, and may be filtered or sorted.
DESCRIPTION: A key feature of an electronic health record is its ability to support the delivery of care by enabling prior information to be found and meaningfully displayed. EHR systems should facilitate search, filtering, summarization, and presentation of available data needed for patient care. Systems should enable views to be customized, for example, specific data may be organized chronologically, by clinical category, or by consultant, depending on need. Jurisdictional laws and organizational policies that prohibit certain users from accessing certain patient information must be supported.
STATEMENT: Employ standard terminologies to ensure data correctness and to enable semantic interoperability (both within an enterprise and externally).
Support a formal standard terminology model.

DESCRIPTION: Semantic interoperability requires standard terminologies combined with a formal standard information model. An example of an information model is the HL7 Reference Information model.
Examples of terminologies that an EHR-S may support include: LOINC, SNOMED, ICD-9, ICD-10, and CPT-4.
A terminology provides semantic and computable identity to its concepts.
Terminologies are use-case dependent and may or may not be realm dependent. For example, terminologies for public health interoperability may differ from those for healthcare quality, administrative reporting, research, etc.
Formal standard terminology models enable common semantic representations by describing relationships that exist between concepts within a terminology or in different terminologies, such as exemplified in the model descriptions contained in the HL7 Common Terminology Services specification.
The clinical use of standard terminologies is greatly enhanced with the ability to perform hierarchical inference searches across coded concepts. Hierarchical Inference enables searches to be conducted across sets of coded concepts stored in an EHR-S.
Relationships between concepts in the terminology are used in the search to recognize child concepts of a common parent. For example, there may be a parent concept, "penicillin containing preparations" which has numerous child concepts, each of which represents a preparation containing a specific form of penicillin (Penicillin V, Penicillin G, etc.). Therefore, a search may be conducted to find all patients taking any form of penicillin preparation.
Clinical and other terminologies may be provided through a terminology service internal or external to an EHR-S. An example of a terminology service is described in the HL7 Common Terminology Services specification.
(No Match) Topic Area(s): Immunizations, Patient Portals - PHR, Primary Care Management, Well Child/Preventive Care Medication Management, Special Terminology and Information
(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.1.8, S.2.2.3, S.3.1.1, IN.1.3, IN.1.6, IN.1.7, IN.1.9, IN.2.4, 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, IN.6
(Matches) Comments:
(Matches) Additional Information:
(Matches) Implementation Notes:
Scroll To Top