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-923Amphetamine use during pregnancy2013 FormatThe system SHALL record amphetamine use during pregnancy as Positive, Negative, or Unknown, as well as the type and average amount of amphetamine used per day.Birth InformationNormative Statementsno
Req-1121Annotate immunization record2013 FormatThe system SHOULD provide the ability to annotate a patient immunization record.ImmunizationsNormative Statementsno
Req-872Anthropometric prescribing support2013 FormatMost pediatric drug dosing is weight-based. Sometimes drug dosing is based on body surface area or other anthropometric measures (e.g., oncology drugsGrowth DataHeaderno
Req-1069Anticipatory guidance based on preventive Service Guidelines2013 FormatThe system SHALL display or print age/gender-specific anticipatory guidance based on preventive service guidelines (such as Bright Futures (e.g. sleep, development, injury prevention, behavior, and nutrition and document the completion of specific services.Well Child/Preventive CareNormative 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-2021Associate mother's demographics with newborn2015 Priority ListThe system shall provide the ability to associate multiple identifying parent or guardian demographic information, such as relationship to child, street address, telephone number, and/or email address for each individual child.Patient Identifier, Parents and Guardians and Family Relationship DataNormative Statementyes
Req-992Associate mother’s demographics with newborn2013 FormatThe system SHALL provide the ability to associate elements of the mother's demographic information, aside from name and other personal identifiers, with each baby in the single or multiple birth situation.
Example: Street address, telephone number, email address but NOT mother's date of birth, driver's license, etc.
Patient IdentifierNormative Statementsno
Req-1032Asthma Severity Scoring2013 FormatThe system SHALL support Asthma Severity Scoring.Specialized Scales/ScoringNormative Statementsno
Req-666Audit trails2013 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.
Growth DataNormative Statementsno
Req-275Auditable Records2013 Format
STATEMENT: Provide audit capabilities for system access and usage indicating the author, the modification (where pertinent and the date and time at which a record was created, modified, viewed, extracted, or deleted. Date and Time...
STATEMENT: Provide audit capabilities for system access and usage indicating the author, the modification (where pertinent and the date and time at which a record was created, modified, viewed, extracted, or deleted. Date and Time stamping implies the ability to indicate the time zone where it was recorded (time zones are described in ISO 8601 Standard Time Reference Auditable records extend to information exchange, to audit of consent status management (to support Req-256 (HL7 ID: DC.1.3.3 and to entity authentication attempts. Audit functionality includes the ability to generate audit reports and to interactively view change history for individual health records or for an EHR-S.
DESCRIPTION: Audit functionality extends to security audits, data audits, audits of data exchange, and the ability to generate audit reports. Audit capability settings should be configurable to meet the needs of local policies. Examples of audited areas include:
- Security audit, which logs access attempts and resource usage including user login, file access, other various activities, and whether any actual or attempted security violations occurred
- Data audit, which records who, when, and by which system an EHR record was created, updated, translated, viewed, extracted, or (if local policy permits deleted. Audit-data may refer to system setup data or to clinical and patient management data
- Information exchange audit, which records data exchanges between EHR-S applications (for example, sending application; the nature, history, and content of the information exchanged and information about data transformations (for example, vocabulary translations, reception event details, etc.
- Audit reports should be flexible and address various users' needs. For example, a legal authority may want to know how many patients a given healthcare provider treated while the provider's license was suspended. Similarly, in some cases a report detailing all those who modified or viewed a certain patient record
- Security audit trails and data audit trails are used to verify enforcement of business, data integrity, security, and access-control rules
-There is a requirement for system audit trails for the following events:
>Loading new versions of, or changes to, the clinical system;
>Loading new versions of codes and knowledge bases;
>Taking and restoring of backup;
>Changing the date and time where the clinical system allows this to be done;
>Archiving any data;
>Re-activating of an archived patient record;
>Entry to and exiting from the clinical system;
>Remote access connections including those for system support and maintenance activities
Show Full Text
Growth DataFunctionno
Scroll To Top