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-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-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-550Support patient consent requirements based on law2013 FormatThe system SHOULD determine the need for minor patient consent based on determination of age of majority based on jurisdictional law.Security and ConfidentialityNormative Statementsno
Req-549Define context for principal authorization2013 FormatThe system MAY provide the ability to define context for the purpose of principal authorization based on identity, role, work assignment, present condition, location, patient consent, or patient's present conditionSecurity and ConfidentialityNormative Statementsno
Req-558Ability to document limitations on the patient's parents' level of authority2013 FormatThe system SHALL provide the ability to document limitations on the patient's parents' level of authority to make decisions on behalf of the patient or access health information about the patient.Security and ConfidentialityNormative Statementsno
Req-559Ability to document parental (guardian) notification or permission2013 FormatThe 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 ConfidentialityNormative Statementsno
Req-552Determine need for minor patient consent for outside access to content2013 FormatThe system MAY determine the need for minor patient consent to permit outside access to content based on determination of age of majority within a legal jurisdiction, possibly in combination with record content to be accessed.Security and ConfidentialityNormative Statementsno
Req-573Entity Authorization.2013 Format
STATEMENT: Manage the sets of access-control permissions granted to entities that use an EHR-S (EHR-S Users
Enable EHR-S security administrators to grant authorizations to users, for roles, and within contexts. A combination of these authorization...
STATEMENT: Manage the sets of access-control permissions granted to entities that use an EHR-S (EHR-S Users
Enable EHR-S security administrators to grant authorizations to users, for roles, and within contexts. A combination of these authorization categories may be applied to control access to EHR-S functions or data within an EHR-S, including at the application or the operating system level.

DESCRIPTION: EHR S Users are authorized to use the components of an EHR-S according to their identity, role, work-assignment, location and/or the patient's present condition and the EHR S User's scope of practice within a legal jurisdiction.
- User based authorization refers to the permissions granted or denied based on the identity of an individual. An example of User based authorization is a patient defined denial of access to all or part of a record to a particular party for privacy related reasons. Another user based authorization is for a tele-monitor device or robotic access to an EHR-S for prescribed directions and other input.
- Role based authorization refers to the responsibility or function performed in a particular operation or process. Example roles include: an application or device (tele-monitor or robotic or a nurse, dietician, administrator, legal guardian, and auditor.
- Context-based Authorization is defined by ISO 10181-3 Technical Framework for Access Control Standard as security-relevant properties of the context in which an access request occurs, explicitly time, location, route of access, and quality of authentication. For example, an EHR-S might only allow supervising providers' context authorization to attest to entries proposed by residents under their supervision.
In addition to the ISO standard, context authorization for an EHR-S is extended to satisfy special circumstances such as, work assignment, patient consents and authorizations, or other healthcare-related factors. A context-based example is a patient-granted authorization to a specific third party for a limited period to view specific EHR records.
Another example is a right granted for a limited period to view those, and only those, EHR records connected to a specific topic of investigation.
Show Full Text
Security and ConfidentialityFunctionno
Req-590Document assent for patients unable to consent2013 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-671Define formal health record2013 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-665Mask selected EHR data2013 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 Statementsyes
Req-1244Legal confidentiality requirements for minors2013 FormatThe system SHALL enable users to implement all applicable confidentiality rules regarding health information of minors; note that these rules exist at more than one level, e.g., National and StateSecurity and ConfidentialityNormative Statementsno
Req-1245Multiple and flexible models of consent2013 FormatMultiple and flexible models of consentSecurity and ConfidentialityFunctionno
Req-1246Separate consent, assent and permission2013 FormatThe system SHALL support the recording of consent, assent, and permission as separate artifacts.Security and ConfidentialityNormative Statementsno
Req-1247Emergency consent documentation2013 FormatThe system SHALL record/document the appropriate data associated with emergency consent, i.e., consent when consent from parents or legal guardians cannot be obtained.Security and ConfidentialityNormative Statementsno
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
Scroll To Top