Posted By: Department of Health and Human Services
Category: Software/Apps Submission Dates: 12 a.m. ET, Nov 19, 2016 - 11:59 p.m. ET, Jan 12, 2017 Judging Dates: Jan 30, 2017 - Feb 22, 2017 Winners Announced: Feb 23, 2017
***Thanks to all who entered the Move Health Data Forward Challenge! We’ve completed our review for Phase 1, and our list of winners can be found here: http://www.hhs.gov/about/news/2016/11/02/hhs-announces-phase-1-winners-move-health-data-forward-challenge.html.
Join us for a live webinar showcasing the winning entries on 11/30 at 3pm ET / 12pm PT. Register here to join: https://attendee.gotowebinar.com/register/350576362580662274.***
The Move Health Data Forward Challenge encourages participants to create an application programming interface (API) solution that uses the implementation specifications created by the HEART Workgroup (Heart WG) to allow people to securely authorize the movement of their health data to destinations they choose.
The HEART WG was developed to advance the process of gathering representatives from many different health-related technical communities worldwide (private-sector, government and non-governmental organizations) working in areas such as patient authentication, authorization, and consent – to collaborate on developing open-source specifications.
The HEART WG has created a set of privacy and security specifications (HEART implementation specifications) using the following open standards: OAUTH 2.0, OpenID Connect and User Managed Access (UMA). These specifications empower people to control the authorization of access to health-related data sharing APIs.
Participants are expected to engage people to test the implementation of the Solution and make possible processes that need consumers to authorize the release of their health data to a destination they choose. Participants must recruit individuals and obtain their authorizations to test the implementation of the Solution using their health data. The data for the API and Solution should be provided by Phase 2 finalists.
The Challenge will have three phases and two finalists each winning $75,000. Phase 1 will award $5,000 for up 10 finalists each based on the proposals they submit to the Challenge. Phase 1 winners will move to Phase 2, which will award $20,000 for up to 5 finalists each based on the prototype of their Solution. Phase 2 winners will move to Phase 3, which will award $50,000 for up to two winners each based on the participant’s ability to implement their Solution.
This multi-phased approach allows participants to assemble, implement and test their Solutions. The final phase of the Challenge will require finalists to show a consumer-facing Solution that incorporates the HEART implementation specifications and uses an API that empowers consumers to control the movement of their health data.
This Challenge encourages participants to apply independently or team with others including health IT developers, health care providers and other entities with the appropriate expertise related to this Solution. Lessons learned and the Challenge’s results will be shared in order to support other organizations implementing solutions that make possible consumer-mediated exchange.
Questions about the Move Health Data Forward Challenge can be posted to the Discussion section and will be regularly monitored.
Challenge Participation Requirements
Phase 1 – Proposals
The Proposal Phase allows participants to present Solutions that increase consumers’ access to and sharing of their information within electronic health record systems. In this phase, participants should describe the technical, operational, financial and business aspects of their proposed Solution. The main goal of Phase 1 is for participants to show feasible and executable plans for innovative Solutions and prove its impact potential.
Phase 1 Submission Requirements
- Application should be in English and all documents uploaded in PDF format
- Submit by the deadline of September 8, 2016 using the online platform: https://www.challenge.gov/?post_type=challenge&p=137291
- The submission should be made up of, minimally, a Title and two uploaded .pdf files. The two files are described in more detail below. You may also optionally include a picture/logo (for instance a logo), and a URL (for instance to a non-profit site).
- Business Case (5-page maximum)
- Include an executive summary stating the value proposition:
- Describe how the proposed Solution will improve the exchange and accessibility of consumer health data
- Describe the target consumer population and/or target health care providers
- Describe the specific problem being solved
- Describe the methods and technologies used to develop the Solution:
- Specify the HEART implementation specifications for data exchange that will be used by the proposed Solution
- Show a financial overview that includes cost structure, projected revenue and expense budget, current funders and description of how funds will be used/allocated
- Development plan and timeline
- Describe key activities and resources required to employ the Solution
- Plan to make the Solution readily available to consumers. For example, to be used on existing mobile platforms or deployed on a public-facing website
- Define metrics for success (i.e. Number of users of the Solution, money saved by using the Solution, time saved, increases in number of data exchanges between consumers and providers)
- Show potential risks and mitigation strategies, including security constraints
- Describe participant roles, responsibilities and capabilities
- Include an executive summary stating the value proposition:
- Include brief deck presentation PDF of the Solution and use case(s) to visually present the Project (10 slides maximum)
- Briefly describe the proposed Solution and how the participants will use the HEART implementation specifications for consumer-mediated exchange of health information
- Explain the competitive advantage of the approach
- Give an example use case
- Show proposed workflow and deliverables
- The above documents should discuss how you will comply with the Health Insurance Portability and Accountability Act (HIPAA) if applicable
Phase 2 – Prototype & Pilot
Phase 1 finalists will advance to a second phase focused on prototyping the Solution and demonstrating the effectiveness of the Solution and impact on consumer or provider health records accessibility and data exchange. The goal of Phase 2 is to present a viable Solution with high technological value and potential to improve the quality of healthcare.
Phase 2 Submission Requirements
- Submit by the deadline of January 12, 2017
- Submit application in PDF
- Develop prototype using test data provided by participant
- Provide an Implementation plan (up to 10 pages)
- Describe key activities and resources required
- Describe the pilot Project and budget
- Provide timeline to go into production
- Video demonstration of the Solution and test results with live webinar
- Demonstration of the Solution’s data security, accessibility, ease of data movement and HIPAA compliance if applicable
Phase 3 – Scale & Implement
The final phase will involve testing the Solution in “real-life” situations. The goal of Phase 3 is to accelerate the best Solutions in the health IT marketplace. This phase will also test the scalability of the Solution, the feasibility of implementation, and the impact of the intended outcomes.
Phase 3 Submission Requirements
- Submit by the deadline of May 1, 2017
- Provide a description of the plan for engaging individuals in testing implementation of the Solution and the processes for requiring individuals to authorize the release of their health data to a destination they choose
- Submissions must be in PDF and should be no more than 10 pages
- Provide a narrative for the value proposition for the Solution and use case
- Report on progress in developing the Solution
- Demonstrate achievement of objectives set forth in the Business Case from Phase 1
- Describe lessons learned
- Provide concrete next steps for commercialization and/or broadened use, including how to attract consumers and/or providers to adopt and use the Solution
- Live demonstration of the Solution and results via webinar. Participants will not need to travel.
- Demonstrate the capability to go live, scalability, HIPAA compliance if applicable, and an interface optimized for consumers and/or providers
For further information on the Move Health Data Forward Challenge, please review the Federal Register Notice.
Phase 1 - Participant Capabilities
Is there appropriate expertise and capability to bring the idea to the testing stage?
Does the participant have the resources available to carry out proposed work?
Phase 1 - Impact Potential
Does the proposed Solution have potential to improve the quality of health care?
Is the proposed Solution using the HEART implementation specifications?
Does the Submission describe how the Solution can be optimized for the greater population of consumers and/or providers?
Is there a clear plan to make the Solution readily available to consumers on existing mobile platforms or a public-facing website?
Is the Solution relevant to ONC priorities of improving the quality of health care?
Phase 1 - Executability
Does the Solution show its HIPAA compliance? Does the Solution use the HEART implementation specifications?
Does the Submission present a reasonable and credible approach to accomplish the proposed objectives, tasks, outcomes and deliverable?
Does the Submission address a pathway or timeline to broad use?
Does the Submission clearly define potential risks?
Does the Submission include a thorough description for the use of funds?
Phase 2 - Technical Merit
Does the Solution use privacy and security specifications/regulations?
o Does the Solution comply with HIPAA if applicable?
o Does the Solution enable people to control the authorization of access to data sharing APIs, using the HEART (HEART) implementation specifications?
Does the Solution support consumer-mediated exchange?
Is the consumer’s health information easy to find, retrieve and access (data-accessibility)?
Is the Solution easy to manage (ease of use, ease of data movement, user friendly)?
Phase 2 - Viability
Does the Solution present a deep understanding of the market for the Solution?
Is there a clear advantage that differentiates this Solution from others?
Is the Solution a model for real-world implementation practical?
Is the Solution economically viable and scalable/replicable?
Are consumers and/or providers already participating (e.g. have signed up to test the Solution)?
Phase 2 - Impact
Does the participant present a theory or explanation of how the proposed Solution would improve the future of consumer-mediated health information sharing?
Is there clear evidence of a health care need based on research for a specific consumer population, and is there evidence that Solution impacts this population?
Could the Solution improve the experience of information sharing between consumers and their health care providers?
Is the Solution’s design human-centered so that it allows consumers to understand and manage their health?
Phase 3 - Impact
Do the results indicate how the Solution will enable consumers share data in a “real-life” setting?
Does the Solution improve the experience of information sharing between consumers and their health care providers?
Phase 3 - Deployability
Is the Solution readily available to consumers to be used on existing mobile platforms or a public-facing website?
Is the Solution designed for ease of learning and ease of use by the target user population?
Phase 3 - Scalability
How scalable is the Solution in a real-world setting? How likely are cost efficiencies for delivery at greater scale?
Is the user experience optimized for the greater population of consumers and/or providers?
Is there a plan for getting consumers and/or providers to adopt and use the Solution?
Participants can register by visiting https://www.challenge.gov/?post_type=challenge&p=137291 and click “Submit Solution” anytime during the proposal submission period stated above. Instructions and Challenge information will be provided on the Challenge website.
If potential participants are interested in finding team members for the Challenge, they may visit https://www.challenge.gov/?post_type=challenge&p=137291 to browse ONC events and register online anytime during the proposal submission period stated above.
Add to the Discussion
My Electronic Health Information MyEHI.co with Patient Centered Health Information Technology PCHIT
Standardized Electronic Two-Way Data Transfer Healthcare (SETH) Form™ (Patent Pending)
Docket – Organize and Communicate Your Health Data
The IHT Medical Hub®
My Health Hub powered by Aidbox from Health Samurai
To be eligible to win a prize under this Challenge, an individual or entity:
- Shall have registered to participate in the Challenge under the rules promulgated by the Office of the National Coordinator for Health Information Technology.
- Shall have complied with all the stated requirements of the Move Health Data Forward Challenge (parentheses above).
- 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 Information Technology.
- 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.
- No HHS or ONC logo – The product must not use HHS’ or ONC’s logos or official seals and must not claim endorsement.
- 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.
- The proposed Solution must be HIPAA compliant if applicable to be eligible for entry into the Challenge.
- All individual members of a team must meet the eligibility requirements.
An individual or entity shall not be deemed ineligible because the individual or entity used Federal facilities or consulted with Federal employees during a Challenge if the facilities and employees are made available to all individuals and entities participating in the Challenge on an equitable basis.
Participants 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. Participants are required to obtain liability insurance or demonstrate financial responsibility in the amount of $500,000, for claims by a third party for death, bodily injury, or property damage, or loss resulting from an activity carried out in connection with participation in a Challenge.
Participants must also agree to indemnify the Federal Government against third party claims for damages arising from or related to Challenge activities.
General 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 Solution must not use HHS or ONC logos or official seals and must not claim endorsement.
- Functionality/Accuracy – A Solution may be disqualified if it fails to function as expressed in the description provided by the participant, or if it provides inaccurate or incomplete information.
- Security – Submissions must be free of malware. Participant agrees that ONC may conduct testing on the API(s) to determine whether malware or other security threats may be present. ONC may disqualify the API(s) if, in ONC’s judgment, the app may damage government or others’ equipment or operating environment.