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.
|Requirement ID:||Req-278: Standard Report Generation||Req-715: Standard Terminologies and Terminology Models|
|Release Package:||2013 Format||2013 Format|
|Title:||Standard Report Generation||Standard Terminologies and Terminology Models|
|Description:||STATEMENT: Provide report generation features using tools internal or external to the system, for the generation of standard reports.
DESCRIPTION: Providers and administrators need access to data in the EHR-S for clinical, administrative, financial decision-making, audit trail and metadata reporting, as well as to create reports for patients. Many systems may use internal or external reporting tools to accomplish this (such as Crystal Report).
Reports may be based on structured data and/or unstructured text from the patient's health record.
Users need to be able to sort and/or filter reports. For example, the user may wish to view only the diabetic patients on a report listing patients and diagnoses.
|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.
|Topic Area(s):||Activity Clearance, Birth Information, EPSDT, Records Management, Well Child/Preventive Care||Medication Management, Special Terminology and Information|
|Provenance:||HL7 EHR FM R1||HL7 EHR FM R1|
|See Also:||IN.1.9, IN.2.5.1, IN.2.5.2, IN.4.1, IN.4.3|