Judging Criteria
Suggested Judging Framework
Know what the judges are looking for:
- Design and Ease of Use (20 points)
The primary audience for CMS data are the Medicare beneficiaries. How intuitive is the experience? Would the intended end user find the app easy to use and understand?
- Benefit for Users (15 Points)
Would a Medicare beneficiary use this app? What would end users gain from their experience using the app? Does this address a fundamental problem in adult or geriatric care in a reasonable manner?
- Creativity and Innovation (15 Points)
Is this a new idea? Does technology like this already exist? How innovative is the concept for Medicare beneficiaries?
- Scaling/Standards (15 Points)
Does this idea make use of FHIR APIs? To what degree can the app connect with any FHIR server without requiring custom integration services work?
- Overall Quality (20 Points)
Does the solution address issues and goals for Medicare beneficiaries? Is the app practical and useful to beneficiaries? Does the app enable information sharing? - Integration (15 Points)
To what extent does the solution make use of other data sources to complement the CMS Blue Button on FHIR API?
What form can your solution take?
Teams will be expected to create applications that allow Medicare beneficiaries to use and share their data. These applications can have a number of different purposes including, but not limited to:
- Helping beneficiaries manage their health
- Allowing beneficiaries to share their data with their providers or caregivers
- Allowing beneficiaries to donate their data for research purposes (e.g., for patient-centered comparative effectiveness research)
Teams should create either web/mobile applications or mockups of applications using tools such as Invision or Balsamiq.
- Any form of web or smartphone application is acceptable
- Teams that choose to create a mockup should provide examples of how actual data from the APIs is mashed up in the application