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.

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]

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-1254Segmented access to information2013 FormatThe system SHALL have the ability to segment health care data and provide views of the record that correspond to granular authorizations as to data-type, user, and/or purpose, as provided by the parent/guardian and/or the minor, as relevant.Security and ConfidentialityNormative Statementsno
Req-1253Adolescent permission for parental information access2013 FormatThe system SHOULD support the documentation of adolescent patient permission to release information to parents and/or guardians.Security and ConfidentialityNormative Statementsno
Req-1252User guidance based on age of consent2013 FormatThe system MAY provide user guidance based on patient age for consent and assent according to organizational policy or jurisdictional law.Security and ConfidentialityNormative Statementsno
Req-1251Education of adolescents regarding legal protections2013 FormatThe system SHOULD support documentation of adolescent's education regarding legal protections of health data for adolescents.Security and ConfidentialityNormative Statementsno
Req-1250Age of emancipation2013 FormatThe system SHOULD record the patient's age of emancipation.Security and ConfidentialityNormative Statementsno
Req-1249Problem-specific age of consent2013 FormatThe system SHALL record the age of consent for specific problems and/or diagnosis.Security and ConfidentialityNormative Statementsno
Req-1248Time stamp consent to guardianship2013 FormatThe system SHOULD record the date and time of consent to guardianship when transferred from biological relationship, e.g., mother, father, or kinships, foster or custodial care, or proxy.Security and ConfidentialityNormative Statementsno
Req-1212Document decision-making authority of patient representative2013 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.
Security and ConfidentialityNormative Statementsno
Req-2030Document decision-making authority of patient representative2015 Priority List
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.
Security and ConfidentialityNormative Statementyes
Req-2039Problem-specific age of consent2015 Priority ListThe system shall provide the ability to access legal guidelines on consent requirements for reference, where available, and to record the age of consent for a specific treatment when these differ based on legal guidelines.Security and ConfidentialityNormative Statementyes
Req-2040Age of emancipation2015 Priority ListThe system shall provide the ability to record the patient's emancipated minor status.Security and ConfidentialityNormative Statementyes
Req-2041Segmented access to information2015 Priority ListThe system shall provide users the ability to segment health care data in order to keep information about minor consent services private and distinct from other content of the record, such that it is not exposed to parents/guardians without the minor’s authorization.Security and ConfidentialityNormative Statementyes
Req-2008Ability to document parental (guardian) notification or permission2015 Priority ListThe system shall provide the ability to document parental (guardian notification or permission for consenting minors to receive some treatments as required by institutional policy or jurisdictional law.Security and Confidentiality, Parents and Guardians and Family Relationship DataNormative Statementyes
Req-2038Separate consent, assent and permission2015 Priority ListThe system shall support the recording of consent, assent, and permission as separate artifacts.Security and Confidentiality, Parents and Guardians and Family Relationship DataNormative Statementyes
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-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-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-488Incorporate scale and score tools2013 FormatThe system SHOULD incorporate scale and score tools that can often be quickly performed and easily recalled, especially in critical care areas.Specialized Scales/ScoringNormative Statementsno
Req-486Ability to prompt for frequent monitoring of specific scales and scores2013 FormatThe system SHALL prompt for frequent monitoring of specific scales and scores that have a dynamic nature, including step-wise scales that assess the response to increasingly noxious stimuli to define levels of consciousness.Specialized Scales/ScoringNormative Statementsno
Req-701Encounter Specific Functionality2013 Format
STATEMENT: Provide assistance in assembling appropriate data, supporting data collection and processing output from a specific encounter.
DESCRIPTION: Workflows, based on the encounter management settings, will assist (with triggers alerts and other means in determining...
STATEMENT: Provide assistance in assembling appropriate data, supporting data collection and processing output from a specific encounter.
DESCRIPTION: Workflows, based on the encounter management settings, will assist (with triggers alerts and other means in determining and supporting the appropriate data collection, import, export, extraction, linkages and transformation. As an example, a pediatrician is presented with diagnostic and procedure codes specific to pediatrics. Business rules enable automatic collection of necessary data from the patient's health record and patient registry. As the provider enters data, workflow processes are triggered to populate appropriate transactions and documents. For example, data entry might populate an eligibility verification transaction or query the immunization registry.
Show Full Text
Specialized Scales/ScoringFunctionno
Scroll To Top