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-715: Standard Terminologies and Terminology Models
(Matches) Release Package: 2013 Format 2013 Format
(No Match) Title: Health Record Output Standard Terminologies and Terminology Models
(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: 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 Identifier, Records Management, Registry Linkages, Security and Confidentiality, 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: 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
(Matches) Comments:
(Matches) Additional Information:
(Matches) Implementation Notes:
Scroll To Top