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-268: Manage Patient History||Req-715: Standard Terminologies and Terminology Models|
|Release Package:||2013 Format||2013 Format|
|Title:||Manage Patient History||Standard Terminologies and Terminology Models|
|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: 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):||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||Medication Management, Special Terminology and Information|
|Provenance:||HL7 EHR FM R1||HL7 EHR FM R1|
|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|