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-673Report summaries: hard copy and electronic2013 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.
Immunizations, Registry LinkagesNormative Statementsno
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-1134Transmit data on vaccine refusals to IIS2013 FormatThe system SHALL provide the ability to transmit data on vaccine refusals to Immunization Information Systems (IISs using an established and agreed upon messaging standard.Immunizations, Registry LinkagesNormative Statementsno
Req-1147IIS query responses in real-time2013 FormatThe system SHOULD provide the ability to receive real-time electronic query responses from IISs.Immunizations, Registry LinkagesNormative Statementsno
Req-1145Report adverse immunization events per legal requirements2013 FormatIF the system has the capacity to prepare reports of patient adverse events due to immunizations, THEN the system SHALL prepare the report according to the requirements of local, state and federal agencies as specified by law.Immunizations, Registry LinkagesNormative Statementsno
Req-1141Access to registries2013 FormatThe system SHOULD provide the ability to add, change, or remove access to registriesImmunizations, Registry LinkagesNormative Statementsno
Req-1140Send real-time queries on patients to IIS2013 FormatThe system SHALL provide the ability to send standard queries in real-time for immunization data regarding individual patients to Immunization Information Systems (IISsImmunizations, Registry LinkagesNormative Statementsno
Req-1139Use established immunization messaging standards2013 FormatThe system SHALL provide the ability to use established and agreed upon messaging standards to transmit and receive data from Immunization Information Systems (IISs and other Health Information Exchanges (HIEsImmunizations, Registry LinkagesNormative Statementsno
Req-1196Registry support for alerts2013 FormatThe system MAY access registry information (e.g. date of immunization, demographics of subject, name of vaccine to issue alerts within the EHR for specific patient cases.Immunizations, Registry LinkagesNormative Statementsno
Req-107Standards Based Interoperability2013 Format
Provide automated health care delivery processes and seamless exchange of clinical, administrative, and financial information through standards-based solutions.
Interoperability standards enable an EHR-S to operate as a set of applications. This results in a unified...
Provide automated health care delivery processes and seamless exchange of clinical, administrative, and financial information through standards-based solutions.
Interoperability standards enable an EHR-S to operate as a set of applications. This results in a unified view of the system where the reality is that several disparate systems may be coming together.
Interoperability standards also enable the sharing of information between EHR systems, including the participation in regional, national, or international information exchanges.
Timely and efficient access to information and capture of information is promoted with minimal impact to the user.
Show Full Text
Immunizations, Prenatal Screening, Registry Linkages, School-Based LinkagesHeaderno
Req-266Present Ad Hoc Views of the Health Record2013 Format
STATEMENT: Subject to jurisdictional laws and organizational policies related to privacy and confidentiality, present customized views and summarized information from a patient's comprehensive EHR. The view may be arranged chronologically, by problem, or other parameters,...
STATEMENT: Subject to jurisdictional laws and organizational policies related to privacy and confidentiality, present customized views and summarized information from a patient's comprehensive EHR. The view may be arranged chronologically, by problem, or other parameters, and may be filtered or sorted.
DESCRIPTION: A key feature of an electronic health record is its ability to support the delivery of care by enabling prior information to be found and meaningfully displayed. EHR systems should facilitate search, filtering, summarization, and presentation of available data needed for patient care. Systems should enable views to be customized, for example, specific data may be organized chronologically, by clinical category, or by consultant, depending on need. Jurisdictional laws and organizational policies that prohibit certain users from accessing certain patient information must be supported.
Show Full Text
Immunizations, Patient Portals - PHR, Primary Care Management, Well Child/Preventive CareFunctionno
Req-1102Controlled access to registries data2013 FormatThe system MAY enable controlled access to and display of data contained in registries such as immunizations.Immunizations, Patient Portals - PHRNormative Statementsno
Req-1097Patient and Caregiver Views2013 FormatThe child's clinical information should be accessible by the child, parents, guardians, caregivers and other consumers to enable assessment of compliance with school or leisure activity requirements. In addition, it should be usable by caregivers to assure care appropriateness and quality.Immunizations, Patient Portals - PHRFunctionno
Req-249Health Record Output2013 Format
STATEMENT: Support the definition of the formal health record, a partial record for referral purposes, or sets of records for other necessary disclosure purposes.
DESCRIPTION: Provide hardcopy and electronic output that fully chronicles the healthcare...
STATEMENT: Support the definition of the formal health record, a partial record for referral purposes, or sets of records for other necessary disclosure purposes.
DESCRIPTION: Provide hardcopy and electronic output that fully chronicles the healthcare process, supports selection of specific sections of the health record, and allows healthcare organizations to define the report and/or documents that will comprise the formal health record for disclosure purposes. A mechanism should be provided for both chronological and specified record element output. This may include defined reporting groups (i.e. print sets For example: Print Set A = Patient Demographics, History & Physical, Consultation Reports, and Discharge Summaries. Print Set B = all information created by one caregiver. Print Set C = all information from a specified encounter. An auditable record of these requests and associated exports may be maintained by the system. This record could be implemented in any way that would allow the who, what, why and when of a request and export to be recoverable for review. The system has the capability of providing a report or accounting of disclosures by patient that meets in accordance with scope of practice, organizational policy and jurisdictional law.
Show Full Text
Immunizations, Patient Identifier, Registry Linkages, Security and Confidentiality, Well Child/Preventive CareFunctionno
Req-273Support for Medication and Immunization Administration2013 Format
STATEMENT: Alert providers to potential administration errors (such as wrong patient, wrong drug, wrong dose, wrong route and wrong time in support of safe and accurate medication administration and support medication administration workflow.
DESCRIPTION: To...
STATEMENT: Alert providers to potential administration errors (such as wrong patient, wrong drug, wrong dose, wrong route and wrong time in support of safe and accurate medication administration and support medication administration workflow.
DESCRIPTION: To reduce medication errors at the time of administration of a medication, the patient is positively identified; checks on the drug, the dose, the route and the time are facilitated. Documentation is a by-product of this checking; administration details and additional patient information, such as injection site, vital signs, and pain assessments, are captured.
Access to drug monograph information may be provided to allow providers to check details about a drug and enhance patient education. Workflow for medication administration is supported through prompts and reminders regarding the "window" for timely administration of medications.
Show Full Text
Immunizations, Medication Management, Registry LinkagesFunctionno
Req-293Medication and Immunization Management2013 FormatSystem manages Medications and ImmunizationsImmunizations, Medication Management, Registry LinkagesHeaderno
Req-272Support for Patient Specific Dosing and Warnings2013 Format
STATEMENT: Identify and present appropriate dose recommendations based on known patient- conditions and characteristics at the time of medication ordering.
DESCRIPTION: The clinician is alerted to drug-condition interactions and patient specific contraindications and warnings e.g....
STATEMENT: Identify and present appropriate dose recommendations based on known patient- conditions and characteristics at the time of medication ordering.
DESCRIPTION: The clinician is alerted to drug-condition interactions and patient specific contraindications and warnings e.g. pregnancy, breast-feeding or occupational risks, hepatic or renal insufficiency. The preferences of the patient may also be presented e.g. reluctance to use an antibiotic. Additional patient parameters, such as age, gestation, height, weight, and body surface area (BSA shall also be incorporated.
Show Full Text
Immunizations, Medication ManagementFunctionno
Req-292Support for Medication and Immunization Ordering2013 FormatSystem supports Medication and Immunization Ordering.Immunizations, Medication ManagementHeaderno
Req-1116Vaccine administration messages to billing system2013 FormatThe system SHOULD send standard messages to the practice management/billing system that include vaccine-specific administration codes.Immunizations, Medication ManagementNormative Statementsno
Req-1115EHR communication with medication management system2013 FormatIF vaccines doses are managed by a vaccine/medication management system, THEN the EHR system SHOULD exchange standard messages with the medication management system.Immunizations, Medication ManagementNormative Statementsno
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-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-609Data pertinent to immunization administration2013 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-612Update immunization schedule on demand2013 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-599Discrete immunization 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.
ImmunizationsNormative Statementsyes
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-657Record vaccine refusal reasons2013 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-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-1119Multiple views of the immunization record2013 FormatThe system SHOULD provide the ability to display different views of a patient's immunization records, allowing users to specify data fields in the view.ImmunizationsNormative Statementsno
Req-1118Manage immunization data for quality measures2013 FormatThe system SHALL provide the ability to manage (search, retrieve, display, sort/filter, calculate immunization data to determine immunization rates (and other quality measures for practices and subsets (by provider, by care group, by patient population, age groups, etc.ImmunizationsNormative Statementsno
Req-1113Capture vaccine administration data from multiple input tools2013 FormatThe system SHOULD provide the ability to capture vaccine administration data from multiple input tools such as keyboard, bar-coding and radio-frequency identification devices.ImmunizationsNormative Statementsno
Req-1112Update immunization inventory on vaccine dose administration2013 FormatIF the system links to a vaccine inventory (formulary THEN the system SHOULD update the inventory/formulary when a vaccine dose is administered and documented.ImmunizationsNormative Statementsno
Req-1109Manage immunization inventory2013 FormatManage immunization inventoryImmunizationsFunctionno
Req-1108Capture and document overrides of immunization notifications2013 Format
IF a provider overrides an immunization notification THEN the system MAY prompt the prescriber for documentation and attestation supporting the override, comprised of: a vaccine dose identifiers, b the patient for whom the dose was...
IF a provider overrides an immunization notification THEN the system MAY prompt the prescriber for documentation and attestation supporting the override, comprised of: a vaccine dose identifiers, b the patient for whom the dose was originally intended, c the patient who received the dose, d the current prescriber (if different from the original provider ordering the dose e the reason for the override and f signature.
Show Full Text
ImmunizationsNormative Statementsno
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-1110Predict practice-level immunization needs2013 FormatThe system MAY provide the ability to estimate/determine the number of types and doses of immunizations that will be required by a practice over a given period of time going forward (1 month, 3 months, etc. based on patient lists and demographics.ImmunizationsNormative Statementsno
Req-1105Link vaccine doses to specific patients2013 FormatLink vaccine doses to specific patientsImmunizationsFunctionno
Req-1104Immunization procurement and inventory management2013 FormatImmunization procurement and inventory managementImmunizationsHeaderno
Req-1107Alert for identical vaccine dose order2013 FormatIF a vaccine dose/identifier is linked to a specific patient record AND a provider orders/prescribes that dose for a different patient, THEN the system SHALL notify the prescriber for order cancellation or override/documentation.ImmunizationsNormative 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-1135Alert for ordered immunizations not forecasted2013 FormatIF a vaccine dose order is not indicated in the immunization forecast for a patient, THEN the system SHALL provide an alert to the provider ordering the dose and to the nurse administering the dose.ImmunizationsNormative Statementsno
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-1133Document reason for non-vaccination2013 FormatThe system SHALL provide the ability to document reasons for non-vaccination that MAY include: the prescriber, the patient, and the reason the vaccine dose was not given.ImmunizationsNormative Statementsno
Req-1130Guideline based decision support for immunization ordering2013 FormatThe system SHALL provide real-time decision support for ordering immunizations for treatment and prophylaxis (such as tetanus, rabies and hepatitis A/B, etc. based on guidelines.ImmunizationsNormative Statementsno
Req-1131Vaccine reminders2013 FormatThe system MAY provide the ability to link to (and display vaccine dose reminders from recognized health maintenance standards.ImmunizationsNormative Statementsno
Req-1128Decision support for options on specific vaccine products2013 FormatIF the system recommends a list of antigens for which a patient is eligible THEN the system SHALL provide the ability to give real-time decision support as to options on specific vaccine products (including combination vaccines according to what vaccine products are available.ImmunizationsNormative 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-1126Timely decision support when ordering vaccines2013 Format
The system SHALL enable timely decision support (recommendations for specific antigens when ordering vaccine dose(s for an individual patient, based on a current child health immunization schedules, which may include the patient's immunization history (age,...
The system SHALL enable timely decision support (recommendations for specific antigens when ordering vaccine dose(s for an individual patient, based on a current child health immunization schedules, which may include the patient's immunization history (age, vaccines received, including date of last previous vaccination b the patient's demographics (date of birth and clinical history (current weight, allergies, medications, problem lists, and laboratory test results including contraindications to vaccine components, and c an entered date (default date is the time the vaccine is ordered, i.e. Now
Show Full Text
ImmunizationsNormative Statementsyes
Req-1127Show available dose options for recommended antigens2013 FormatThe system SHOULD provide the ability to display vaccine dose (brand/product/price options for recommended antigens, including combination vaccines given a patient's immunization history and demographic and clinical data.ImmunizationsNormative Statementsno
Scroll To Top