Document

Announcement of Requirements and Registration for “EHIgnite Challenge”

The EHIgnite Challenge addresses data usability challenges in single patient electronic health information (EHI) exports. This challenge seeks to incentivize the development of ...

Department of Health and Human Services

AGENCY:

Office of the National Coordinator for Health Information Technology, Department of Health and Human Services.

ACTION:

Notice.

SUMMARY:

The EHIgnite Challenge addresses data usability challenges in single patient electronic health information (EHI) exports. This challenge seeks to incentivize the development of tools, platforms, and workflows that transform single patient EHI exports into usable, readable, and actionable information that supports clinical care, patient engagement, and informed decision-making.

DATES:

This challenge includes two phases. Only the participants selected to receive a Phase 1 prize may participate in Phase 2.

Phase 1: Concept & Design

Submission period begins: February 23, 2026, 10:00 a.m. EST.

Submission period ends: May 20, 2026, 11:59 p.m. PST.

Phase 1 Announcement of Winners: June 2026.

Phase 2: Prototype Development

Submission period begins: June 23, 2026, 10:00 a.m. EST.

Submission period ends: March 24, 2027, 11:59 p.m. PST.

Phase 2 Announcement of Winners: May 2027.

FOR FURTHER INFORMATION CONTACT:

Adam Wong, (preferred), 202-664-4396.

SUPPLEMENTARY INFORMATION:

Award Approving Official

Dr. Thomas Keane, National Coordinator for Health Information Technology.

Subject of Challenge

The EHIgnite Challenge, a program managed by the Office of the National Coordinator for Health Information Technology (ONC), addresses data usability challenges in single patient electronic health information (EHI) exports. This challenge seeks to incentivize the development of tools, platforms, and workflows that transform single patient EHI exports into usable, readable, and actionable information that supports clinical care, patient engagement, and informed decision-making.

While health IT developers of a certified Health IT Module that is part of a health IT product that electronically stores EHI (“health IT developers of certified health IT”) are required to provide EHI export functionality, variability in implementation and the sheer volume of data have made these exports difficult for clinicians and patients to effectively use. Although the ONC Health IT Certification Program specifies functional requirements as part of the certification criteria at 45 CFR 170.315(b)(10), it does not mandate specific transport methods, data standards, or implementation strategies. The EHI export file required for Health IT Modules certified to that criterion must be in an electronic and computable format and accessible via hyperlink.

These requirements are designed to offer health IT developers of certified health IT flexibility in their approach to conformance with the certification criterion and to foster innovation, transparency, and best practices for data sharing. While beneficial for innovation, this has created inconsistencies in how exports are structured, formatted, and made accessible. Clinicians, patients, and other stakeholders have reported that EHI exports are often overwhelming, difficult to interpret, and challenging to integrate into existing workflows.

These challenges limit the ability of healthcare teams to provide seamless care, particularly in care transitions ( e.g., hospital to rehab), or for patients seeking to manage their own health data. Moreover, current tools do not consistently support critical use cases such as summarizing information for care teams, integrating multiple sources of patient data, or providing patient-facing interactive tools.

EHIgnite Challenge participants are asked to develop solutions that leverage single patient EHI exports to improve data usability and value. To incentivize wide adoption, submissions are encouraged to make use of standards adopted as part of the ONC Health IT Certification Program. Such standards could include FHIR Release 4, US Core Implementation Guide v6, and SMART App Launch Framework 2.0.

Submissions must create a usable, readable summary of relevant health information based on the user and/or a particular scenario. For example, if a patient is being transferred to a rehab or acute care facility after a complex surgery, what information does the place of care and care team need to know to provide the best possible care to this patient? If an individual is moving out of state, what information does their new primary care provider need before their first visit?

Submissions must additionally address at least one of the following five scenarios:

1. Interactive Patient Tools: Enable patients to ask questions about their health data and receive understandable responses. Participants can assess an EHI export and make an interactive tool that allows patients to ask questions about their own health and care instructions. For example, if I am a patient, can I use a chatbot to review my own EHI and help me understand post-surgical instructions, or my provider notes to help modify diet or other behaviors? ( printed page 29501)

2. Customization for Clinical Domains: Build tools that allow customized queries and organizing exports by relevant domains.

3. Integration Across Settings: Create a solution that makes EHI exports more consumable and allows for integration of EHI exports from multiple places of care. For example, create a solution that allows patients to import their EHI export(s) across settings into a third-party application which enables searching, parsing, filtering, and viewing.

4. Streamlined Payer Use Cases: Create a solution that allows for easier and more streamlined sharing of information for insurance coverage using payer APIs. For example, create a solution that processes and incorporates the USCDI data elements contained in the Health Insurance Information data class that enhances data sharing for prior authorization.

5. Participant-Defined Use Case: Participants may propose a unique solution that leverages single patient EHI exports to improve data usability and value in a different manner than the outlined scenarios. This option allows teams to identify a critical challenge or opportunity not already specified, and to design a tool, application, or workflow addressing that challenge or opportunity.

Use of AI is encouraged but must be transparent, explainable, and compliant with all applicable civil rights and privacy and security laws and policies.

Background

As defined in 45 CFR 170.102, EHI (electronic health information) includes individually identifiable health information that is stored or transmitted electronically and would be included in a designated record set, but excludes psychotherapy notes and certain other information as specified in regulation. Health IT developers of certified Health IT are required to support two use cases as set forth in 45 CFR 170.315(b)(10):

Single Patient EHI Export:

—Export EHI for a single patient at any time the user (or user's representative) chooses without Developer assistance

—The export must be created in a timely fashion

—Must include all EHI for a single patient

—Must be electronic and in a computable format

—Must include a publicly accessible hyperlink of the export's format

—Certified Health IT Module must be able to limit users who can perform an EHI export

Patient Population EHI Export:

—Must include all EHI for a patient population

—Must be electronic and in a computable format

—Must include a publicly accessible hyperlink of the export's format

Judging

Phase 1 (Concept and Design) Judging Criteria

Relevance and Problem Alignment (Up to 25 pts)

Interpretability and Ease of Use (Up to 40 pts)

Potential for Integration and Scaling (Up to 20 pts)

Privacy and Security Compliance (Up to 15 pts)

Use of AI (Phase 1: Optional, Up to 20 Bonus pts; Phase 2: Award for Most Innovative Use of AI)

Phase 2 (Prototype Development) Judging Criteria

Phase 2 judging criteria will reflect the Phase 1 judging criteria, adapted for judging of Phase 2 submissions.

How To Enter

To enter this Challenge, participants must:

(1) register by completing the “Challenge Registration Form” found on the challenge website at https://ehignitechallenge.org/​phase-1-challenge-registration/​; and

(2) submit your Challenge submission on the challenge website, https://ehignitechallenge.org/​. Once the participant has registered using the “Challenge Registration Form” and is logged in on the website, the submission link becomes available.

Additional Information Regarding Registration

Registration is required to be eligible to win a cash prize. When you register using the “Challenge Registration Form,” you will need to decide whether you are registering as:

(1) an individual (on behalf of yourself);

(2) a team (on behalf of a group of individuals competing together, but not on behalf of an established organization, institution, or corporation). If registering as a team, each participating Team is required to designate an eligible Team Leader who will register and submit on behalf of the Team members. The Team Leader is responsible for all communications with HHS; or

(3) an entity (on behalf of a legally established organization, institution, or corporation).

Your decision to register as an individual, team, or entity on the “Challenge Registration Form” will determine who HHS pays any winning prize money from this Challenge. Please see “Prize Payment Rules” in the “Rules” section. Before registering, you may wish to consider any potential tax consequences of registering as an individual, team, or entity.

HHS reserves the right, in its sole discretion, to grant or deny any request to update registration information on the “Challenge Registration Form.” ( printed page 29502)

Additional Information Regarding Submissions

Phase 1 Submission Requirements

The following components are requirements for a complete submission package:

[FR Doc. 2026-10068 Filed 5-18-26; 11:15 am]

BILLING CODE 4150-28-P

Legal Citation

Federal Register Citation

Use this for formal legal and research references to the published document.

91 FR 29500

Web Citation

Suggested Web Citation

Use this when citing the archival web version of the document.

“Announcement of Requirements and Registration for “EHIgnite Challenge”,” thefederalregister.org (May 20, 2026), https://thefederalregister.org/documents/2026-10068/announcement-of-requirements-and-registration-for-ehignite-challenge.