follow us on facebook follow us on twitter email us

Move Health Data Forward Challenge

About the Challenge
Create an API solution that allows people to authorize the movement of their health data.

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:
    • 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 brief deck presentation PDF of the Solution and use case(s) to visually present the Project (10 slides maximum)
    • Content:
      • 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.

Judging Criteria

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?

How to Enter

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.

Prizes
Total Phase 1 Prize Amount $50,000.00 Phase 1 will award up to 10 winners each receive $5,000
Total Phase 2 Prize Amount $100,000.00 Phase 2 will award up to 5 winners each receive $20,000
Total Phase 3 Prize Amount $100,000.00 Phase 3 will award up to 2 winners each receive $50,000

63 Discussions for "Move Health Data Forward Challenge"

  • Show Replies [+]
    jrodriguez
    All - The MHDF Challenge is now closed. Thanks to those who submitted! We'll be in touch soon regarding next steps. Please note that if you submitted a solution as "hidden," it will not display in the public Solutions tab. Only those submitted as "unhidden" are displayed on the public page. Upon submission, you should have received a confirmation email. If you did not receive one, you may contact us at sensischallenges@sensisagency.com.

    • Reply
      Thomas Bell
      Hi, I never received a confirmation email, but I did receive a confirmation page from the website after I submitted. I was looking to get the confirmation email or some other confirmation that my submission went through. I wrote an email to sensischallenges@sensisagency.com and didn't hear back. Is there any way to additionally confirm that our submissions have been successful.

  • Jose Macion
    My company, MHC, Inc., is willing and able to partner with any hospital and healthcare provider, in Southern California's Inland Empire. I would also like a list from the Department of Health and Human Services, for any hospital and healthcare provider, in Southern California's Inland Empire, that would like to partner with my company in this challenge. Please contact me, Jose Macion, CEO of MHC, Inc., 11362 Sewell Street, Fontana, CA 92337, Phone: (818) 903-9133, e-mail: jose.macion@gmail.com

  • Show Replies [+]
    Raj Sharma
    I tried to submit our response last night before the deadline Before I hit the submit button I noticed that the two PDF files were listed as 0KB in length. It was nearing the deadline so I hit the submit button anyway. Now I do not see my submission on the list :( I have reached out to https://www.challenge.gov/contact/ and sent an email to sensischallenges@sensisagency.com last night, but haven't heard anything.

    • Reply
      James MacDougall
      Try going to your profile and at the bottom checking "My Solutions". If it's there I think you're good.

    • Reply
      Raj Sharma
      I do not see my submission in the list. When I submitted just before the deadline the two PDF files to the challenge, they were listed as 0KB in length.

    • Reply
      John S
      I ran into the same issue. I had to go to the bottom of my profile to find my submission, then it showed up on the page after I unchecked the box "Hide the contents of my submission from all others on Challenge.gov"

    • Reply
      jrodriguez
      Hi, Jocelyn - Sorry to hear you're having trouble with the site. Please contact our help desk at https://www.challenge.gov/contact/; they'll be able to address the technical issue. If you still have problems submitting your solution, please contact our team at sensischallenges@sensisagency.com for an alternate option to send your submission.

    • Reply
      lozeran
      I had the same issue, but clicking on the displayed links showed them on the challenge.gov website, so you might see if the links work for you.

    • Reply
      jrodriguez
      We've heard from some folks that this is happening, and after checking on our end, it seems that despite a 0KB notice, the files are making their way to us. If you open your entry after submitting, you should be able to access your files as links to verify that they uploaded correctly. However, please don't hesitate to reach us at sensischallenges@sensisagency.com if you have any issues uploading your solutions.

    • Reply
      jrodriguez
      Hi, Debra - The upload feature should be working correctly now, so kindly try uploading your solution again. Please contact us at sensischallenges@sensisagency.com if you have any additional tech issues.

    • Reply
      jrodriguez
      Hi, the upload feature should be working correctly now, so kindly try uploading your solution again. Please contact us at sensischallenges@sensisagency.com if you have any additional tech issues.

  • Show Replies [+]
    jrodriguez
    Hi, all -- we received another question via email that we wanted to share with everyone. Q: We are planning on partnering with organization types on this project. Are we required to have our partnering relationships finalized prior to submitting on the Sept 8th deadline?

    • Reply
      jrodriguez
      A: The 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. Applications should include descriptions of the technical, operational, financial, and business aspects of their proposed Solution. This should include a list of partners. We strongly encourage applicants to only list partnerships that are finalized or far along in the process and to list the status of these partnerships. This will allow our review panel to accurately assess the teams that will be developing and implementing the Solution.

  • Show Replies [+]
    Venkata Phani Anne
    1) How funds will be used? (Q) To submit proposal for PHASE 1; Are we not doing it at our own expense? If we are selected, (one among 10 winners) we get 5 K. (Q) This 5 K is not good enough for developing PROTOTYPE. (Phase product) Are you saying 5 K could be used to reimburse for developing preliminary plans for phase 1? 2) Similarly we are the winners for PROTOTYPE then we reimburse ourselves $ 20 K? It looks like we are walking backwards every time when you are a winner. Is the correct? 3) Like wise, we don't understand how to project cost structure for Prototype or Demo when the money awarded is small and caped off? Without any advance of money we are asked to develop and take our chances. Then where is the question of projecting cost structure when the budget is already set at every phase? 4) PROJECTED REVENUE AND EXPENSE BUDGET: (Q) Are you asking us how would we sustain the operations of maintaining / managing Consumer-Mediated Exchange (CME) going forward? 5) Development plan and Timeline & Resources required: You have already set in 3 phases. Looking forward to hearing from you. Thanks

    • Reply
      jrodriguez
      Hi, thanks for your questions. ONC hosts prize competitions to stimulate market innovation and incentivize development of new technology for health care. The use of any prize money received from this challenge is at the discretion of the winner. The proposal for Phase 1 will be submitted at the applicant’s expense. At the conclusion of Phase 1, up to 10 winners will be selected and they will each win $5000. It is up to the winners how they choose to spend the $5000. It is not required to put it towards Phase 2, but many choose to do so in order to work towards the $20,000 Phase 2 prize. Applicants should project their costs and budget requirements for each phase of the challenge in order to accurately scope their projects based on the availability of resources and personnel for their team. Since it is unlikely that all participants who enter the challenge will be winners, potential participants should consider the cost to their organization for developing proposals and solutions. While applicants are not required to do so, some teams may choose to provide their own funding to support their participation in the challenge. The projected revenue and expense budget should refer to the projected revenue and expenses for the activities outlined in the proposal submitted for the Challenge. While the timeline for each Phase of the challenge has been set, it is anticipated that numerous additional tasks will need to be taken by participants in order to implement and test their solutions during the time period specified. Participants should detail their timeline for these tasks in order to present a comprehensive project plan to the review panel. A description of resources, such as technical infrastructure and personnel, will be helpful to the review panel in order to assess the applicant’s ability to complete all necessary project work on time.

  • jrodriguez
    Hello, all - you may now view recordings for both the June 7 and August 18 webinars here: https://www.healthit.gov/techlab/innovation/move-health-data-forward-challenge.

  • Show Replies [+]
    jrodriguez
    Hi, all - We received another question following our recent webinar. Please see below for both the question and answer: Q: Thank you for a helpful webinar. Should the submitted materials focus on the API component or on the application? Should the focus be on how we support the connectivity needs of the consumer (describe the application) or how our technology enables movement of data per consumer wishes among different applications (describe the API)?

    • Reply
      jrodriguez
      A: Thanks for participating in the webinar. It is up to the applicant to decide the focus of their submitted materials based on the submission requirements for the MHDF Challenge. In general, our primary interest is the development of applications that enable consumer-mediated exchange via the use of APIs implementing standards from the HEART Work Group. Applicants should describe the consumer-mediated exchange use case that will be demonstrated and tested as part of their proposal. This should include a description of the application and how it incorporates the API, as well as more information about the target population and how data will be shared by consumers.

  • Show Replies [+]
    Nitin
    This is an interesting challenge. I am interested in joining a team of passionate individuals to participate in this contest. I've an extensive business and health IT related experience (government and private HIEs) relevant for this competition. Ping me if you have a slot in your team.

    • Reply
      Christian
      Where are you located? Can you send me contact information? Currently lacking in Industry specialized members, but have Technical.

  • jrodriguez
    Hi, all - we received a question following our recent webinar and wanted to share with everyone: Q: On the webinar you mentioned there were templates for the plan and the deck, but I do not see links anywhere. I checked both healthit.gov and challenge.gov Where might they be found? Also, will a notice go out to the webinar participants where to find the slides from that 18 August presentation? A: Thanks for reaching out. The reference to templates for the plan and deck was a general one, saying that applicants could find example templates online. We are not providing templates as part of the MHDF Challenge. We anticipate that the slides and webinar recording will be posted by early next week and we will do our best to notify participants when they become available.

  • Show Replies [+]
    Ravi Ada
    I am wondering if patient is giving access to a provider to get their health records directly from source system(typically EHR or patient portal) or from PHR vendor (man in the middle). I am looking at HEART WG and UMA specs, they talk about managing cross domain access privileges, does it mean data resides in source system and the provider who is given access will get it directly from source system? Does this challenge specifically calls for an API to manage access privileges or API to choose and send parts of PHR data (they already have it, both clinical and patient generated) directly to destination provider? Please clarify.

    • Reply
      jrodriguez
      Thanks for your question. The overall goal of the challenge is to demonstrate that APIs can be used to facilitate the exchange of data on behalf of a patient. This could include a push or pull/get or post between a client and source server, and depending on the role the systems could provide both functions. A few example scenarios include: 1) a source system sends data to a client chosen by the patient 2) an authorization method that permits a provider to gather information about a patient from a source system using the client of their choice 3) a patient sends data from their client (such as a PHR) to an EHR or donates it for research. It is up to the applicant’s discretion to choose the HEART profiles that make sense for their use case and it is necessary to adhere to the constraints contained within the profiles of choice. Testing the HEART profiles will help to provide feedback to the HEART Work Group and enable them to further refine the profiles as needed.

  • Show Replies [+]
    John Williams
    Are these dates correct (from top of this page) Submission Dates: 12 a.m. ET, May 10, 2016 - 11:59 p.m. ET, Sep 08, 2016 Judging Dates: Sep 09, 2016 - Oct 14, 2016 Winners Announced: Oct 31, 2016

  • Show Replies [+]
    Rich
    In the section entitled Rules, you reference the need for liability insurance, "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." As we are a non-profit organization and don't carry liability insurance, how do we instead "demonstrate financial responsibility?"

    • Reply
      jrodriguez
      Thanks for your question, Rich. The high-level goal of this Challenge is to identify an entity that can endure beyond the submission period, both by supporting the winning API, and by continuing to innovate. To achieve this, it is important that the winning team have the right framework in place to handle the degrees of risk inherent in any business venture. Insurance is an important part of the longevity and risk mitigation framework. We realize that those participating in this Challenge will be at various stages in the business lifecycle. In Phase 1, it would be acceptable for the business-plan portion of the submission to discuss how insurance and financial responsibility in the amount of $500,000 would be accounted for in later phases. For Phase 1 winners, demonstration of financial responsibility in the amount of $500,000 or insurance for the same amount must be acquired prior to any work commencing for later Phases in order to protect both the product being created, and those using it.

  • Show Replies [+]
    apeschard1
    We would like to incorporate in the US in order to participate to the Challenge. As you know, this is a process that can take a few weeks. We would like to do this with sufficient advance time to allow for a timely submission of our project proposal. We'd be of course grateful if you could clarify if this will be enough to ensure eligibility.

    • Reply
      apeschard1
      Thank you for your interest in the Move Health Data Forward Challenge. Please review the Federal Register Notice (https://www.federalregister.gov/articles/2016/05/11/2016-11102/office-of-the-national-coordinator-for-health-information-technology-announcement-of-requirements#h-17) for the Move Health Data Forward Challenge, specifically the “Eligibility Rules for Participating in the Challenge” section (https://www.federalregister.gov/articles/2016/05/11/2016-11102/office-of-the-national-coordinator-for-health-information-technology-announcement-of-requirements#p-72). To be eligible to win a prize under this Challenge, 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.

  • Show Replies [+]
    Rich
    Is there a max page limit for this Solution? In the Phase 1 Submission Requirements section, the Business Case is limited to 5 pages, and the slide presentation is limited to 10 slides. But is there a limit to the entirety of the Solution submission? Thanks

    • Reply
      apeschard1
      Thanks for verifying. Aside from the submission form, applicants are expected to submit two deliverables: a Business Case and a Solution Briefing Presentation. The Business Case has a 5 page limit and the Solution Briefing Presentation is limited to 10 slides. Both deliverables should be in PDF format.

  • Show Replies [+]
    Rich
    Is there a total submission page limit? I see in the Phase 1 Submission Requirements, reference to a Business Case limit of 5 pages and a presentation deck limit of 10 slides, but no reference to a page limit for the complete submission. Thanks

    • Reply
      apeschard1
      Thanks for verifying. Aside from the submission form, applicants are expected to submit two deliverables: a Business Case and a Solution Briefing Presentation. The Business Case has a 5 page limit and the Solution Briefing Presentation is limited to 10 slides. Both deliverables should be in PDF format.

  • Show Replies [+]
    Rich
    Just to confirm, there is no pre-registration for this Challenge. As I read the Rules section, registration occurs at the time of proposal submission. Is this correct? Thanks very much.

    • Reply
      apeschard1
      You are correct – there is no pre-registration required for this specific challenge. However, in order to submit your solution, you will need to be logged into your account on the Challenge.gov website.

  • Show Replies [+]
    Sai Vinnakota
    Hi, This is an interesting challenge but I was able to google and find lot of organizations that have developed APIs to securely transfer data between Providers to consumer health mobile applications. So I'm not able to understand what is the uniqueness about the challenge that we need to solve that existing companies in Health API space have not yet solved? Please advise

    • Reply
      apeschard1
      While many organizations have generated potential solutions to enable patients to view data via a patient portal hosted on the web or via a mobile app managed by a provider, we have seen little evidence that this functionally is currently available for consumer/patient applications of choice. This challenge specifically tasks applicants to use the HEART profiles and underlying standards enable secure and trusted patient mediated exchange for easier and more robust data flow. To support that goal, first round winners will also need to test their API with actual patient data. This iterative, user-centered approach should lead to a solution that can be widely adopted and accepted by both consumers and providers alike.

  • apeschard1
    Register for the June 7 Informational Webinar here: https://attendee.gotowebinar.com/register/9090076417523027716

Add to the Discussion

Rules

To be eligible to win a prize under this Challenge, an individual or entity:

  1. Shall have registered to participate in the Challenge under the rules promulgated by the Office of the National Coordinator for Health Information Technology.
  2. Shall have complied with all the stated requirements of the Move Health Data Forward Challenge (parentheses above).
  3. 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.
  4. May not be a Federal entity or Federal employee acting within the scope of their employment.
  5. Shall not be an HHS employee working on their applications or Submissions during assigned duty hours.
  6. Shall not be an employee of the Office of the National Coordinator for Health Information Technology.
  7. Federal grantees may not use Federal funds to develop COMPETES Act challenge applications unless consistent with the purpose of their grant award.
  8. 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.
  9. No HHS or ONC logo – The product must not use HHS’ or ONC’s logos or official seals and must not claim endorsement.
  10. 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.
  11. The proposed Solution must be HIPAA compliant if applicable to be eligible for entry into the Challenge.
  12. 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:

  1. No HHS or ONC logo – The Solution must not use HHS or ONC logos or official seals and must not claim endorsement.
  2. 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.
  3. 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.
Submit Solution
Challenge Followers
Public Profile: 3
Private Profile: 43