This challenge is no longer accepting new submissions.
Provider User-Experience Challenge
Create health provider apps that sync consumers' data using open APIs.
Department of Health and Human Services
Type of Challenge: Software/Apps
Submission Start: 06/02/2016 12:00 AM ET
Submission End: 2016/11/07 02:00 PM ET
Read the press release announcing the final, Phase 2 winners! Congratulations to them all! The Provider User-Experience (UX) Challenge incents the development of applications that use open, standardized APIs to enable innovative ways for providers to interact with patient health data. This challenge will focus on demonstrating how data made accessible to apps through APIs can positively impact providers’ experience with EHRs by making clinical workflows more intuitive, specific to clinical specialty, and actionable. The lack of interoperability between electronic health record (EHR) systems remains a significant barrier to the modernization of health IT. Fast Healthcare Interoperability Resources (FHIR), developed by HL7, is a standard designed to increase the liquidity of granular patient data. The FHIR API allows data to move between vendor systems both within and across different providers, not to mention through third-party applications for direct use by both clinicians and consumers. Among several opportunities now enabled by this interoperability standard are the new channels being opened up for improving a provider’s user experience when interacting with EHRs and the “consumability” of interrelated health data. ***Watch the recording of the March 31 Informational Webinar*** The challenge has two phases. Phase 1 requires the submission of technical and business plans for the application (app) while Phase 2 requires that a working app be available for consumers. Phase 2 of the competition will not be limited to only those who won Phase 1 – all Phase 1 competitors, and those who did not participate in Phase 1, can submit a final app at the end of Phase 2. The final application must meet the following requirements:
Phase 2 Participation Requirements The second phase, to run from June 2 to November 7, will entail the actual development of the apps, verification of technical capabilities, user testing/piloting, and public release of the apps. This will include remote testing with providers and health IT developers to test the technical abilities of the apps to connect to in-production systems. Participants will submit:
The grand prize winner will receive $50,000 and a second place winner will receive $25,000. There will be an additional $25,000 prize for the app that connects to the greatest number of unique health IT developer systems implemented in production settings (the "Ultimate Connector"), which can be won by any entry, including the grand prize or 2nd place winner. Phase 1 Participation RequirementsParticipants interested in competing for Phase 1 awards will need to submit an app development plan that must include:
To augment technical development and enhance the likelihood of a successful app that will continue to exist beyond the end of the challenge, a progress update/matchmaking event will be held that will seek to connect participants with provider partners. In Phase 1, up to five app proposals will be recognized as winners and awarded up to $15,000 each.
Phase 2 First Prize - Herald Health
Its solution helps clinicians manage the overwhelming flow of alerts and information by allowing them to create highly customizable push notifications. These can be tailored to both individual patients and groups and exported to fellow users.
Phase 2 Second Prize and Connector Award - University of Utah Health Care / Intermountain Healthcare / Duke Health System
Their solution is a clinical decision support tool that can provide recommendations for the treatment of babies with jaundice detected at birth based on the level of liver waste products found in their blood.
Phase 2 Honorable Mention - PHRASE Health
This solution uses clinical decision support to help clinicians align with priorities such as public health alerts.
Phase 1 Winner - Herald Health
The Herald platform leverages FHIR to surface the patient information that clinicians need the most. It’s integration of FHIR will help enable highly customizable, IFTTT-like (“if this, then that”) alerts based on real-time EHR data.
Phase 1 Winner - PHRASE Health
PHRASE (Population Health Risk Assessment Support Engine) Health aims to create a clinical decision support platform, compatible with the SMART on FHIR platform, to bridge the gap between public health and clinicians by intuitively creating rules to identify at-risk populations. This would help better manage emerging illnesses, incorporate more external data sources into the identification of at-risk patients, and allow for the two-way exchange of data and knowledge between public health and frontline providers.
Phase 1 Winner - University of Utah Health Care / Intermountain Healthcare / Duke Health System
A multi-institutional, collaborative effort to redevelop a SMART on FHIR application to provide clinical decision support for timely diagnosis of newborn bilirubin and management according to evidence-based best practices. The collaboration intends to integrate the app across each member’s EHR platform.
Phase 1 Winner - WellSheet
WellSheet’s web application seeks to utilize machine learning and natural language processing to prioritize relevant information during a patient visit. Its algorithm simplifies workflows that must incorporate multiple data sources, including those enabled by FHIR, and presents information in a single screen.
The statutory authority for this challenge competition is Section 105 of the America COMPETES Reauthorization Act of 2010 (Public L. No 111-358). Eligibility Rules for Participating in the Competition: To be eligible to win a prize under this challenge, an individual or entity:
- Shall have registered to participate in the competition under the rules promulgated by the Office of the National Coordinator for Health Information Technology.
- Shall have complied with all the requirements under this section.
- In the case of a private entity, shall be incorporated in and maintain a primary place of business in the United States, and in the case of an individual, whether participating singly or in a group, shall be a citizen or permanent resident of the United States.
- May not be a Federal entity or Federal employee acting within the scope of their employment.
- Shall not be an HHS employee working on their applications or submissions during assigned duty hours.
- Shall not be an employee of the Office of the National Coordinator for Health IT.
- Federal grantees may not use Federal funds to develop COMPETES Act challenge applications unless consistent with the purpose of their grant award.
- Federal contractors may not use Federal funds from a contract to develop COMPETES Act challenge applications or to fund efforts in support of a COMPETES Act challenge submission.
An individual or entity shall not be deemed ineligible because the individual or entity used Federal facilities or consulted with Federal employees during a competition if the facilities and employees are made available to all individuals and entities participating in the competition on an equitable basis. Entrants must agree to assume any and all risks and waive claims against the Federal Government and its related entities, except in the case of willful misconduct, for any injury, death, damage, or loss of property, revenue, or profits, whether direct, indirect, or consequential, arising from my participation in this prize contest, whether the injury, death, damage, or loss arises through negligence or otherwise. Entrants must also agree to indemnify the Federal Government against third party claims for damages arising from or related to competition activities. Submission Requirements In order for a submission to be eligible to win this Challenge, it must meet the following requirements:
- No HHS or ONC logo – The product must not use HHS’ or ONC’s logos or official seals and must not claim endorsement.
- Functionality/Accuracy – A product may be disqualified if it fails to function as expressed in the description provided by the user, or if it provides inaccurate or incomplete information.
- Security – Submissions must be free of malware. Contestant agrees that ONC may conduct testing on the product to determine whether malware or other security threats may be present. ONC may disqualify the product if, in ONC’s judgment, the app may damage government or others’ equipment or operating environment.
Additional Information: General Conditions: ONC reserves the right to cancel, suspend, and/or modify the Contest, or any part of it, for any reason, at ONC's sole discretion. Intellectual Property: Each entrant retains title and full ownership in and to their submission. Entrants expressly reserve all intellectual property rights not expressly granted under the challenge agreement. By participating in the challenge, each entrant hereby irrevocably grants to Sponsor and Administrator a limited, non-exclusive, royalty-free, worldwide license and right to reproduce, publically perform, publically display, and use the Submission to the extent necessary to administer the challenge, and to publically perform and publically display the Submission, including, without limitation, for advertising and promotional purposes relating to the challenge. Authority: 15 U.S.C. 3719.
Phase 2 - Number, sources, and types of data aggregation using FHIR
Success in achieving the technical requirements for the challenge
Phase 2 - Functionality and quality of data aggregation
Assessment will include how well the app aggregates data pulled from different sources into a presentation that is usable and coherent
Phase 2 - Privacy and security of patient data
Submission must demonstrate how the app functionality and structure safeguard patient health data
Phase 2 - Impact potential in clinical setting
To what extent does the app improve on the status quo, such as through time saved, convenience, completeness/thoroughness of patient information, ease of integration into current workflows, and integration with their current health IT
Phase 2 - User experience and visual appeal
Assessment will include whether the app follows best practices in conveying information online, how intuitive is its navigation, and overall user-friendliness
Phase 1 - Technical feasibility of plan, including number of EHR sources targeted
Includes number of EHR sources targeted and how realistic those plans are (i.e., don’t list every single EHR in existence without having done any due diligence about whether it’s possible).
Phase 1 - Adherence to data privacy and security best practices and applicable law (including HIPAA)
Apps must demonstrate they will adhere to the provisions, as applicable, of the Privacy Rule and Security Rule of the Health Insurance Portability and Accountability Act of 1996 (HIPAA), in addition to best practices for safeguarding patient health data.
Phase 1 - Strength of business/sustainability plan
Assessment will include how well the submitter understands the issues underlying the challenge, how well the proposed solution addresses them, and rigor, methodology, and reality of the plan.
Phase 1 - Impact potential in clinical setting
How would the proposed solution address clinician needs in the clinical setting, including utility, usability, integration into current workflows, and integration with their existing health IT.
Phase 1 - Provider and/or health IT developer partnerships
Extent to which submitter has partnered or come to agreements with stakeholders to, for example, co-design, develop, or test the app.
How To Enter
Participants will submit:
- Working app
- Provide the url to download/access the app.
- Video demonstrating the app (maximum of 5 minutes)
- Provide the url of the video on YouTube or Vimeo.
- The video must highlight the use of FHIR to integrate with EHR vendor systems, including demonstration of data exchange with each system. The rest of the video should address the remaining evaluation criteria: functionality and quality of data aggregation, privacy and security of patient data, impact potential in a clinical setting, and user experience and visual appeal.
- Slide deck describing app (maximum of 15 slides)
- Overall, the slide deck should complement the video demonstration. It should include a list of the active FHIR integrations with EHRs at provider settings, as demonstrated in the video. It should describe other functionality pertaining to the review criteria, particularly anything that was not covered in the video.