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.

remove Filtering Release Package on 2013 Format
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-1132Identify patients underinsured for immunizations2013 FormatThe system SHOULD provide the ability to identify patients who are uninsured or underinsured for immunizations, such as those that are eligible for Vaccines for Children (VFC and S-CHIP/Medicaid.ImmunizationsNormative Statementsno
Req-664Identify recipient-appropriate educational material2013 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.
Primary Care Management, Well Child/Preventive CareNormative Statementsno
Req-924Illicit drug use during pregnancy2013 FormatThe system SHALL record other illicit drugs used during pregnancy (Positive, Negative, or Unknown IF positive THEN the system SHALL record the name, dose and frequency of use.Birth InformationNormative Statementsno
Req-120Immediate alerts for abnormal growth values2013 FormatThe system SHALL support alerting at the time of value entry for values outside of the probable range and heights less than previous measures.Growth DataNormative Statementsno
Req-1129Immunity data as vaccine contraindication2013 FormatThe system SHALL provide the ability to link to historical and/or laboratory data that documents a patient's immunity as a contraindication to ordering/administering a vaccine dose.ImmunizationsNormative Statementsno
Req-601Immunization consent status2013 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.
ImmunizationsNormative Statementsno
Req-1104Immunization procurement and inventory management2013 FormatImmunization procurement and inventory managementImmunizationsHeaderno
Req-1148Immunization prompts for patients weighing less than 2 kg2013 FormatIF the patient's weight is below 2 kg, THEN the system SHALL provide the ability to generate a prompt for the immunization prescriber.
ImmunizationsNormative Statementsno
Req-608Immunizations based on risk factors2013 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.
ImmunizationsNormative Statementsno
Req-835Implement age rounding rules2013 Format
The system SHOULD implement age rounding rules that conform to social conventions of age representation
- Age in years, months, weeks, and days should be incremented at the 'day' level of precision, and rounded down...
The system SHOULD implement age rounding rules that conform to social conventions of age representation
- Age in years, months, weeks, and days should be incremented at the 'day' level of precision, and rounded down to an integer
- Age in months should be calculated as though dates that do not exist in a particular month are equivalent to the 1st day of the following month.
- Age in hours and minutes should be incremented at the 'minute' level of precision, and rounded down to an integer
Show Full Text
Well Child/Preventive CareNormative 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-1275Import and manage compendia of resources2013 FormatThe system SHOULD have the ability to import and manage compendia of resources for non-medical psychosocial problemsWell Child/Preventive CareNormative Statementsno
Req-1260Import questionnaire results in computable format2013 FormatThe system SHALL be able to import results of questionnaire into a computable format (to the degree that the original responses are computableWell Child/Preventive CareNormative Statementsno
Req-1205Import/export family member demographics2013 FormatThe system SHOULD offer a utility to copy or import and export demographic information between records of parents, guardians, and siblings (including foster siblings within the same home.Parents and Guardians and Family Relationship DataNormative Statementsno
Req-1204Import/export family member medical data2013 FormatThe system MAY offer a utility to copy or import and export common medical information, such as family history information, from medical records of biological family members.Parents and Guardians and Family Relationship DataNormative 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-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-485Incorporate scanned documents2013 FormatThe system SHALL provide the ability to incorporate and index scanned documents from internal and external providers or agencies into the patient record.Primary Care ManagementNormative Statementsno
Req-890Indicate common side effects2013 FormatThe system MAY provide the ability to indicate common side effects, including those unique to or more common in children, and inform the user during ordering.Medication ManagementNormative Statementsno
Req-655Indicate formulae for drug dose recommendations2013 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.
Medication ManagementNormative Statementsno
Req-113Indicate information collected at Point of Care2013 FormatThe system SHOULD indicate point of care of collected measures and/or allow filtering of values by point(s of care.Growth DataNormative Statementsno
Req-582Indicate unknown patient gender2013 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.
Birth Information, Genetic information, Prenatal ScreeningNormative Statementsno
Req-902Infant size relative to gestational age2013 FormatThe system SHALL provide the ability to capture, record and store the birth weight, length and head circumference of the infant relative to normal values for its captured and/or assigned gestational age (SGA=Small for Gestational Age, AGA=Appropriate for Gestational Age, LGA=Large for Gestational AgeBirth InformationNormative Statementsno
Req-781Information View2013 Format
STATEMENT: Support user-defined information views.

DESCRIPTION: Views of the information can be tailored for or by the user (or department or "job classification" for their presentation preferences, within local or facility established rules. For...
STATEMENT: Support user-defined information views.

DESCRIPTION: Views of the information can be tailored for or by the user (or department or "job classification" for their presentation preferences, within local or facility established rules. For example, a nursing supervisor may elect or prefer to see summary data on all patients as the default view.
Show Full Text
Immunizations, Well Child/Preventive CareFunctionno
Req-938Initial Infant Data2013 FormatData recorded in the first hour of life will guide care in the initial neonatal period.Birth Information, Specialized Scales/ScoringFunctionno
Req-1114Integrate vaccine administration with other systems2013 FormatThe system MAY integrate vaccine dose administration with vaccine/medication management systems and practice management/billing systems.Immunizations, Medication ManagementNormative Statementsno
Req-443Integrated immunizations reporting2013 FormatThe EHR SHOULD allow an integrated view of what immunizations are due or past due.ImmunizationsNormative Statementsno
Req-719Interchange Agreements2013 Format
STATEMENT: Support interactions with entity directories to determine the address, profile and data exchange requirements of known and/or potential partners.
Use the rules of interaction specified in the partner's interchange agreement when exchanging information.
DESCRIPTION:...
STATEMENT: Support interactions with entity directories to determine the address, profile and data exchange requirements of known and/or potential partners.
Use the rules of interaction specified in the partner's interchange agreement when exchanging information.
DESCRIPTION: Systems that wish to communicate with each other, must agree on the parameters associated with that information exchange. Interchange Agreements allow an EHR-S to describe those parameters/criteria.
An EHR-S can use the entity registries to determine the security, addressing, and reliability requirements between partners.
An EHR-S can use this information to define how data will be exchanged between the sender and the receiver.
Discovery of interchange services and capabilities can be automatic.
For example:
- A new application can automatically determine a patient demographics source using a Universal Description and Discovery Integration (UDDI for source discovery, and retrieve the Web Services Description Language (WSDL specification for binding details.
- Good Health Hospital is a member of AnyCounty LabNet, for sharing laboratory results with other partners. Good Health Hospital periodically queries LabNet's directory (UDDI to determine if additional information providers have joined LabNet. When new information providers are discovered, the Good Health IT establishes the appropriate service connections based upon the Service Description (WSDL
Show Full Text
ImmunizationsFunctionno
Req-772Interchange Standards Versioning and Maintenance2013 Format
STATEMENT: Enable version control according to local policies to ensure maintenance of utilized interchange standards.
Version control of an interchange standard implementation includes the ability to accommodate changes as the source interchange standard undergoes its...
STATEMENT: Enable version control according to local policies to ensure maintenance of utilized interchange standards.
Version control of an interchange standard implementation includes the ability to accommodate changes as the source interchange standard undergoes its natural update process.

DESCRIPTION:
The life cycle of any given standard results in changes to its requirements. It is critical that an organization know the version of any given standard it uses and what its requirements and capabilities are.

For example, if the organization migrates to an HL7 v2.5 messaging standard, it may choose to take advantage of new capabilities such as specimen or blood bank information. The organization may find that certain fields have been retained for backwards compatibility only or withdrawn altogether. The EHR-S needs to be able to handle all of these possibilities.

Standards typically evolve in such a way as to protect backwards compatibility. On the other hand, sometimes there is little, or no, backwards compatibility when an organization may need to replace an entire standard with a new methodology. An example of this is migrating from HL7 v2 to HL7 v3.

Interchange standards that are backward compatible support exchange among senders and receivers who are using different versions. Version control ensures that those sending information in a later version of a standard consider the difference in information content that can be interchanged effectively with receivers, who are capable of processing only earlier versions. That is, senders need to be aware of the information that receivers are unable to capture and adjust their business processes accordingly.
Version control enables multiple versions of the same interchange standard to exist and be distinctly recognized over time.
Since interchange standards are usually periodically updated, concurrent use of different versions may be required.
Large (and/or federated organizations typically need to use different versions of an interchange standard to meet internal organizational interoperability requirements.
For example, the enterprise-wide standard might use HL7 v2.5 for Lab messages, but some regions of the enterprise might be at a lower level.
It should be possible to retire deprecated interchange standards versions when applicable business cycles are completed while maintaining obsolete versions. An example use of this is for possible claims adjustment throughout the claim's life cycle.
When interchange standards change over time, it is important that retrospective analysis and research correlate and note gaps between the different versions' information structures to support the permanence of concepts over time. An example use of this is the calculation of outcome or performance measures from persisted data stores where one version of a relevant interchange standard, e.g., CDA Release 1 captures the relevant data, e.g., discharge data, differently than CDA Release 2.
Show Full Text
Immunizations, Registry LinkagesFunctionno
Req-1031International Classification for (VUR)2013 FormatThe system SHALL support the International Classification for Vesico-ureteral Reflux (VUR - Grades 1-5.Specialized Scales/ScoringNormative Statementsno
Req-1025International classification of retinopathy of prematurity (ICROP)2013 FormatThe system SHALL support the international classification of retinopathy of prematurity (ICROPSpecialized Scales/ScoringNormative Statementsno
Req-1023Intra-ventricular hemorrhage scoring2013 FormatThe system SHALL support intra-ventricular hemorrhage scoring.Specialized Scales/ScoringNormative Statementsno
Req-932Labor and Delivery2013 FormatThe method and circumstances of labor and delivery are critical to adequate care for a newborn infant.Birth InformationFunctionno
Req-933Labor: spontaneous or induced2013 FormatThe system SHALL record if labor was spontaneous or induced.Birth InformationNormative Statementsno
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-1149Legal constraints on importing maternal data2013 FormatThe system SHALL follow applicable state or federal privacy laws regarding the importation of maternal information into the child's record.Prenatal ScreeningNormative Statementsno
Req-1227Legal history2013 FormatThe system SHOULD have access to the legal history (e.g., first-time offender versus repeat offender, multiple incarcerations when available.Child WelfareNormative Statementsno
Req-1046Leiter International Performance scale2013 FormatThe system SHALL support the Leiter International Performance Scale.Specialized Scales/ScoringNormative Statementsno
Req-851Length/Height2013 FormatLength is typically measured in newborns and then at every well-child visit through 36 months of life. Afterwards, height is typically recorded. Length/height may also be measured at other times based on clinician concern.Growth Data, Primary Care Management, Well Child/Preventive CareFunctionno
Req-1270Library of patient/caregiver questionnaires2013 FormatThe system SHOULD have a library of patient/caregiver questionnaires from which clinicians can choose.

Well Child/Preventive CareNormative Statementsno
Req-95Link maternal and birth data to child health record2013 FormatThe system SHALL provide for the linking or recording of maternal and birth data to the child health record. Examples: maternal social history, maternal prenatal results, and gravida/para (GPBirth InformationNormative Statementsno
Req-1005Link maternal and birth data to child health record2013 FormatThe system SHALL provide for the linking of maternal and birth data to the child health record for quality measures. Examples: linkage of frequency of prenatal care to birth weight.Quality MeasuresNormative Statementsyes
Req-1111Link patient record to immunization inventory2013 FormatThe system SHOULD provide the ability to link to a vaccine inventory (formulary for information about (immediately available vaccine doses (including brands, products, number of doses, dates of acquisition, and dates of expirationImmunizationsNormative Statementsno
Req-1193Link to Child Welfare registries2013 FormatThe system SHOULD provide an interface or link to child welfare registries to be searchable by name (either child or parent placement, service categories provided, and/or jurisdiction.Child Abuse Reporting, Child Welfare, Registry LinkagesNormative Statementsno
Req-1106Link vaccine dose to patient record2013 FormatThe system SHOULD provide the ability to link each individual vaccine dose/identifier to a specific patient record by patient ID, prescribing provider, planned date of administration, patient insurance , and vaccine identifiers, including type (antigen combination brand, lot number, and dose number.ImmunizationsNormative Statementsno
Req-1105Link vaccine doses to specific patients2013 FormatLink vaccine doses to specific patientsImmunizationsFunctionno
Req-886Liquid drug prescriptions2013 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.
Medication ManagementNormative Statementsno
Req-578Locate records based on previous names2013 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.
Parents and Guardians and Family Relationship DataNormative Statementsno
Req-1177Maintain unsubstantiated instances of abuse or neglect2013 Format
The system SHOULD provide the ability to maintain indicated unsubstantiated instances of abuse or neglect consistent with the prevailing law (which may be state, federal, tribal or local depending on situational factors with the ability...
The system SHOULD provide the ability to maintain indicated unsubstantiated instances of abuse or neglect consistent with the prevailing law (which may be state, federal, tribal or local depending on situational factors with the ability to expunge or limit communication to certain external systems unsubstantiated instances of abuse or neglect when required by the prevailing law.
Show Full Text
Child Abuse ReportingNormative Statementsno
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
Scroll To Top