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.

Results 1-17 of 17
remove Filtering Topic Area on Special Terminology and Information
MS Excel
Download as an MS Excel spreadsheet.
[Download Excel ReaderExit Disclaimer]
PDF
Download as a PDF file.
[Download PDF ReaderExit Disclaimer]
MS Word
Download as an MS Word document.
[Download Word ReaderExit Disclaimer]
Remove All Filters

sort Req ID
sort Title
sort Release Package
Release Package(s) Selected
sort Description
sort Topic Area
Topic Area(s) Selected
sort Type
Type(s) Selected
sort Critical/Core
Critical/Core(s) Selected
Req-542Multiple terminology versioning2013 FormatThe system SHALL provide the ability to use different versions of terminology standards, (e.g. a child-specific version, when it existsSpecial Terminology and InformationNormative Statementsno
Req-667Preserve concept interpretations across terminology versions2013 Format
Lorem, ipsum, dolor, sit, amet, consectetur, adipiscing, elit, Ut, egestas, dolor, nec, ipsum, luctus, non, varius, felis, blandit, Quisque, facilisis, pellentesque, nisi, Sed, rutrum, sodales, nisl, Duis, mattis, ipsum, a, laoreet, pharetra, quam, eros, porta, nisl, eget, pellentesque, augue, purus, eu, nunc
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.
Special Terminology and InformationNormative Statementsno
Req-1010Validate clinical terms against a standard terminology2013 FormatThe system MAY provide the ability to validate that clinical terms and coded clinical data exists in an accepted standard terminology for child health (if availableSpecial Terminology and InformationNormative Statementsno
Req-1011Standard child health terminology for system communication2013 FormatThe system SHALL provide the ability to use a standard terminology for child health (if available to communicate with other systems (internal or external to the EHR-SSpecial Terminology and InformationNormative Statementsno
Req-1012Standard terminology for diagnoses2013 FormatThe system SHOULD provide the ability to encode diagnoses using a terminology identified as an adequate standard for documenting diagnoses common in childhood.Special Terminology and InformationNormative Statementsno
Req-1013Standard terminology for medications and treatments2013 Format
The system SHOULD provide the ability to encode the names of medications and patient treatments commonly used for children using a terminology identified as a standard for documenting medication names.
Comment: EHR systems may use...
The system SHOULD provide the ability to encode the names of medications and patient treatments commonly used for children using a terminology identified as a standard for documenting medication names.
Comment: EHR systems may use existing terminologies that represent clinical medications, such as MediSpan, First Data Bank or Multum to support this function. However, EHR systems may also maintain their own proprietary medication terminology. In either case, the scope of the functionality for EHR systems relates to their ability to allow users to encode medications according to a standard representation.
Show Full Text
Medication Management, Special Terminology and InformationNormative Statementsno
Req-1014Standard terminology for signs, systems, and development2013 FormatThe system SHOULD provide the ability to encode pediatric signs, symptoms and development using a terminology identified as a standard for documenting signs and symptoms.Special Terminology and InformationNormative Statementsno
Req-1015Standard terminology for laboratory testing2013 Format
The system SHOULD provide the ability to encode laboratory and other testing names common to children using a terminology identified as a standard for documenting laboratory names .
Comment: In some cases, laboratory and other...
The system SHOULD provide the ability to encode laboratory and other testing names common to children using a terminology identified as a standard for documenting laboratory names .
Comment: In some cases, laboratory and other testing is managed by a laboratory information system that is either a component of or external to the EHR system. In those cases, the laboratory information system can use the terminology identified as a standard for documenting laboratory and testing names. In other cases, results from laboratory and other testing is entered directly into the EHR system by a healthcare provider. For example, office-based testing for streptococcus, pregnancy or infectious mononucleosis typically would not be documented in a laboratory information system. A user may prefer not to provide the terminology mapping to a specific vocabulary; however the EHR system may have this already linked in their system.
Show Full Text
Special Terminology and InformationNormative Statementsno
Req-1059Code status for children with special healthcare needs2013 FormatThe system MAY selectively include code status on the Health & Physical Evaluation template for a child designated as medically complex and/or with special health care needs.Children with Special Healthcare Needs, Special Terminology and InformationNormative Statementsno
Req-1057Use and search of pediatric diagnosis codes2013 FormatThe system SHALL support the use and search of a broad selection of pediatric diagnosis codes and code sets, when available, such as by specialty, subspecialty or organ system.Children with Special Healthcare Needs, Special Terminology and InformationNormative Statementsyes
Req-103Care Management2013 Format
Care Management functions are those directly used by providers as they deliver patient care and create an electronic health record. The Record Management (Req-106 functions address the mechanics of creating a...
Care Management functions are those directly used by providers as they deliver patient care and create an electronic health record. The Record Management (Req-106 functions address the mechanics of creating a health record and concepts such as a single logical health record, managing patient demographics, and managing externally generated (including patient originated health data. Thereafter, The additional Care Management functions follow a fairly typical flow of patient care activities and corresponding data, starting with managing the patient history and progressing through consents, assessments, care plans, orders, results etc.

Integral to these care management activities is an underlying system foundation that maintains the privacy, security, and integrity of the captured health information - the information infrastructure of the EHR-S. Throughout the DC functions, conformance criteria formalize the relationships to Information Infrastructure functions. Criteria that apply to all Care Management functions are listed in this header (see Conformance Clause page six for discussion of "inherited" conformance criteria

In the Direct Care functions there are times when actions/activities related to "patients" are also applicable to the patient representative. Therefore, in this section, the term "patient" could refer to the patient and/or the patient's personal representative (e.g. guardian, surrogate
Show Full Text
Activity Clearance, Birth Information, Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, EPSDT, Genetic information, Growth Data, Immunizations,...
Activity Clearance, Birth Information, Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, EPSDT, Genetic information, Growth Data, Immunizations, Medication Management, Newborn Screening, Parents and Guardians and Family Relationship Data, Patient Identifier, Patient Portals - PHR, Prenatal Screening, Primary Care Management, Quality Measures, Registry Linkages, Security and Confidentiality, Special Terminology and Information, Specialized Scales/Scoring, Well Child/Preventive Care
Show Full Text
Headerno
Req-287Preferences, Directives, Consents and Authorizations2013 FormatMaintain preferences, directives, consents and authorizations.
Children with Special Healthcare Needs, Parents and Guardians and Family Relationship Data, Primary Care Management, Security and Confidentiality, Special Terminology...
Children with Special Healthcare Needs, Parents and Guardians and Family Relationship Data, Primary Care Management, Security and Confidentiality, Special Terminology and Information
Show Full Text
Headerno
Req-296Standard Terminologies and Terminology Services2013 Format
STATEMENT: Support semantic interoperability through the use of standard terminologies, standard terminology models and standard terminology services.

DESCRIPTION: The purpose of supporting terminology standards and services is to enable semantic interoperability. Interoperability is demonstrated...
STATEMENT: Support semantic interoperability through the use of standard terminologies, standard terminology models and standard terminology services.

DESCRIPTION: The purpose of supporting terminology standards and services is to enable semantic interoperability. Interoperability is demonstrated by the consistency of human and machine interpretation of shared data and reports. It includes the capture and support of consistent data for templates and decision support logic.

Terminology standards pertain to concepts, representations, synonyms, relationships and computable (machine-readable definitions. Terminology services provide a common way for managing and retrieving these items.
Show Full Text
Medication Management, Special Terminology and InformationHeaderno
Req-254Manage Assessments2013 Format
STATEMENT: Create and maintain assessments.
DESCRIPTION: During an encounter with a patient, the provider will conduct an assessment that is germane to the age, gender, developmental or functional state, medical and behavioral condition of the...
STATEMENT: Create and maintain assessments.
DESCRIPTION: During an encounter with a patient, the provider will conduct an assessment that is germane to the age, gender, developmental or functional state, medical and behavioral condition of the patient, such as growth charts, developmental profiles, and disease specific assessments. Wherever possible, this assessment should follow industry standard protocols although, for example, an assessment for an infant will have different content than one for an elderly patient. When a specific standard assessment does not exist, a unique assessment can be created, using the format and data elements of similar standard assessments whenever possible.
Show Full Text
Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, EPSDT, Parents and Guardians and Family Relationship Data, Primary Care...
Child Abuse Reporting, Child Welfare, Children with Special Healthcare Needs, EPSDT, Parents and Guardians and Family Relationship Data, Primary Care Management, Registry Linkages, Special Terminology and Information, Well Child/Preventive Care
Show Full Text
Functionno
Req-276Maintenance and Versioning of Standard Terminologies2013 Format
STATEMENT: Enable version control according to customized policies to ensure maintenance of utilized standards.
This includes the ability to accommodate changes to terminology sets as the source terminology undergoes its natural update process (new codes,...
STATEMENT: Enable version control according to customized policies to ensure maintenance of utilized standards.
This includes the ability to accommodate changes to terminology sets as the source terminology undergoes its natural update process (new codes, retired codes, redirected codes Such changes need to be cascaded to clinical content embedded in templates, custom formularies, etc., as determined by local policy.
DESCRIPTION: Version control allows for multiple sets or versions of the same terminology to exist and be distinctly recognized over time.
Terminology standards are usually periodically updated, and concurrent use of different versions may be required. Since the meaning of a concept can change over time, it is important that retrospective analysis and research maintains the ability to relate changing conceptual meanings. If the terminology encoding for a concept changes over time, it is also important that retrospective analysis and research can correlate the different encodings to ensure the permanence of the concept. This does not necessarily imply that complete older versions of the terminology be kept in the EHR-S, only access to the changes needs to be maintained.
It should be possible to retire deprecated versions when applicable business cycles are completed while maintaining obsolescent code sets. An example use of this is for possible claims adjustment throughout the claim's lifecycle.
Show Full Text
Special Terminology and InformationFunctionno
Req-256Manage Consents and Authorizations2013 Format
STATEMENT: Create, maintain, and verify patient decisions such as informed consent for treatment and authorization/consent for disclosure when required.
DESCRIPTION: Decisions are documented and include the extent of information, verification levels and exposition of treatment...
STATEMENT: Create, maintain, and verify patient decisions such as informed consent for treatment and authorization/consent for disclosure when required.
DESCRIPTION: Decisions are documented and include the extent of information, verification levels and exposition of treatment options. This documentation helps ensure that decisions made at the discretion of the patient, family, or other responsible party govern the actual care that is delivered or withheld.
Show Full Text
Children with Special Healthcare Needs, Parents and Guardians and Family Relationship Data, Primary Care Management, Security and Confidentiality, Special Terminology...
Children with Special Healthcare Needs, Parents and Guardians and Family Relationship Data, Primary Care Management, Security and Confidentiality, Special Terminology and Information
Show Full Text
Functionno
Req-715Standard Terminologies and Terminology Models2013 Format
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...
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.
Show Full Text
Medication Management, Special Terminology and InformationFunctionno
Scroll To Top