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-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-489Support interoperability between various systems2013 FormatThe system MAY be interoperable between the juvenile justice system, medical facilities, probation department, schools, and each state's human services agency.Parents and Guardians and Family Relationship DataNormative Statementsno
Req-506Capture both presence and absence of conditions in history2013 FormatThe system SHALL provide the ability to capture patient history as both a presence and absence of conditions, i.e., the specification of the absence of a personal or family history of a specific diagnosis, procedure or health risk behavior.Parents and Guardians and Family Relationship Data, Primary Care ManagementNormative Statementsno
Req-507Import / export data with Surgeon General’s Family Health History Tool2013 Format
The system MAY import and export a family health history from and to the Surgeon General's Family Health History Tool using the HITSP IS08 / C90 Clinical Genomics Decision Support Tool based on the HL7...
The system MAY import and export a family health history from and to the Surgeon General's Family Health History Tool using the HITSP IS08 / C90 Clinical Genomics Decision Support Tool based on the HL7 v3 clinical genomics model with data mapping to the family history section of the HITSP C83 CCD content module for family history.
Show Full Text
Genetic information, Parents and Guardians and Family Relationship Data, Primary Care Management, Well Child/Preventive CareNormative Statementsno
Req-512Support communication with national, state, and local Child Protective Services, and more2013 FormatThe system MAY communicate with national, state, and local Child Protective Services, law enforcement, care physicians, prosecutor, medical examiner, Medicaid, and Insurance companies.Child Abuse ReportingNormative Statementsno
Req-513Retrieve, capture, store, and display information regarding age of menarche, past sexual activity of the victim, teen pregnancy and births.2013 FormatIn cases of child abuse the system SHOULD provide the ability to retrieve, capture, store, and display information regarding age of menarche, past sexual activity of the patient, teen pregnancy and births.Child Abuse Reporting, Well Child/Preventive CareNormative Statementsno
Req-515Ability to retrieve, capture, store, and display information regarding the child's response, demeanor, and appearance2013 FormatThe system SHALL provide the ability to retrieve, capture, store, and display information regarding the child's response, demeanor, and appearance.Child Abuse Reporting, Primary Care Management, Well Child/Preventive CareNormative Statementsno
Req-517Ability to access family history, including all parents2013 FormatThe system SHALL provide the ability to access family history, including all parents (biological, foster, adoptive, guardian, surrogate, and custody siblings, and case workers; with contact information for each.Child Abuse ReportingNormative Statementsno
Req-518Ability to retrieve, capture, store, and display information regarding forensic evaluations2013 FormatThe system SHOULD provide the ability to retrieve, capture, store, and display information regarding forensic evaluations.Child Abuse ReportingNormative Statementsno
Req-519Ability to access, store, and retrieve the date, time, and place of the occurrence2013 FormatThe system SHALL provide the ability to access, store, and retrieve the date, time, and place of the occurrence of alleged abuse.Child Abuse ReportingNormative Statementsno
Req-520Ability to access, store, and retrieve a detailed description of the genital examination, photographs or drawings of findings2013 FormatThe system SHALL provide the ability to access, store, and retrieve a detailed description of the genital examination, photographs or drawings of findings (both sexual and physical documentation of laboratory studies, and radiographic studies.Child Abuse ReportingNormative Statementsno
Req-522Ability to retrieve, capture, store, and display service plans, progress summaries, and assessments2013 FormatThe system SHOULD provide the ability to retrieve, capture, store, and display service plans, progress summaries, and assessments.Child Abuse ReportingNormative Statementsno
Req-523Measures to verify identity of parent/guardian2013 FormatThe system SHOULD incorporate measures that confirm/verify the identity of the parent/s or guardian/s and their relationship to a child.Patient Portals - PHRNormative Statementsno
Req-524Incorporate and adhere to legal local and national laws in regards to patient EHR access2013 FormatThe system SHALL incorporate and adhere to local, state, and national laws in regards to patient EHR access (e.g. children under 12 cannot sign up for access to their own accountPatient Portals - PHRNormative Statementsno
Req-525Ability to allow parents/legal guardians and children add any relevant additional health information2013 FormatThe system SHOULD allow parents/legal guardians and children of appropriate age to add any relevant additional health information and fill in gaps in their EHR.Patient Portals - PHRNormative Statementsno
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-544Ability to comply with registry sharing/linking regulations and standards2013 FormatThe system SHALL comply with registry sharing/linking regulations and standards (HIPAA, HITECH, CHIPRA, etc.Registry LinkagesNormative Statementsno
Req-545Ability to comply with industry standards for interfaces and services2013 FormatThe system SHALL comply with industry standards for interfaces and services within the limitations of currently accepted standardsRegistry LinkagesNormative Statementsno
Req-546Support ability to export data for non-interfaced registries2013 FormatThe system SHALL provide user controlled export features such as protected text or data files for registries that can't or won't accept interfaced or service fed data.Registry LinkagesNormative Statementsno
Req-547Support the tracking of the release of information to outside registries through linkage mechanisms2013 Format
The system SHALL provide data elements that support the tracking of the release of information to outside registries through linkage mechanisms. Release tracking must cascade to the patient level (X patient's data linked to Y...
The system SHALL provide data elements that support the tracking of the release of information to outside registries through linkage mechanisms. Release tracking must cascade to the patient level (X patient's data linked to Y registry. Data elements: Releasing System, Receiving System, Date and Time of Release, Releasing Agent, Reason for Release, Trust Relationship, Release Mechanism.
Show Full Text
Registry LinkagesNormative 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-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-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-553Assign parts of the EHR to another patient identifier2013 FormatThe system SHOULD provide the ability to assign parts of the electronic health record to another patient identifier and delete them permanently from the former according to organizational policy or jurisdictional law relating to protections of birth records of adoptees.Patient Identifier, Security and ConfidentialityNormative Statementsno
Req-556Document authority for consent on behalf of minors2013 FormatThe system SHALL allow for documentation of authority of foster parents or custodians to give consent on behalf of a minor patient, including unlimited number of different foster parents or custodians.Parents and Guardians and Family Relationship Data, Security and ConfidentialityNormative Statementsno
Scroll To Top