Challenge Overview
Project Overview
The client of this application is CPI (Center for Program Integrity) which is a part of CMS (Centers for Medicare and Medicaid Services). CPI wants to ensure transparency of payment giving from manufacturers to healthcare providers. This project will help to ensure that the rules for payment giving are followed and that there is a record keeping regarding the payments that have been given.
The purpose of this project is to create an iOS application and a report host web application that will make it easier for users to comply with the new transparency law. The iOS application will be used by payers (the manufacturer and its field agents) to record information about their payments and other transfers of value to payment recipients (physicians, teaching hospitals, and other healthcare providers).
In this contest we will focus on testing the report host web application
Contest Objective
The goal of this competition is to clearly identify the limitations of the provided web application and ensure the requirements as they were described have been met. You can find the UI prototype describing the applications in contest forum. You need to make sure the applicaiton is compliant with section 508.
Things to test in the current competition are:
- Report Host web application
Users
See the deployment guide for the user credentials.
Tip
You can simulate new payment records arriving from the iOS app by reusing the provided sql scripts to insert new records in the database.
Format
For each report of a limitation or bug, we need the following information:
1) A description detailing what the issue is.
2) What steps can be taken to reproduce the issue.
3) The expected result.
4) The actual result.
5) Your suggested priority level.
6) Make sure to set the component to "Data Host". Please take care of this step, all bugs which didn't set correct component will not be counted for winning places.
 |
If you do not properly document your bug reports, they will likely be rejected due to lack of information or documentation. Also, make sure your bug reports are reasonably general. If you submit the same bug that is seen in multiple screens, for instance, you will likely only get credit for the original bug report. The others will all be closed as duplicates. |
You will log your tickets here: https://apps.topcoder.com/bugs/browse/OPEN You must select the "Data Host" component for each logged issue or it may not get counted during review. if you cannot access that project please send an email to khochtaf.anass@gmail.com and rsial@appirio.com. we will give you access to the project.
|
For scoring, the submitter with the most accepted bugs will win. The submitter with the second most accepted bugs will receive second place. For submitters who submit but don't take first or second, if they submit bugs that aren't covered in the first or second place submission, they will receive $5 for each unique bug reported up to a maximum of the 2nd place prize If two submitters submit the same bug report, the submitter who submitted the report first into JIRA will get credit for the bug. The second submitter will not. |
Provided Resources
Documentation Provided
The following documentation will be available in the contest forum:
- UI Prototype
- Source code
- Deployment Guide
- Section 508
Final Submission Guidelines
Final Submission
You MUST submit a file with a list of your reported bugs into OR during the submission phase, for review purposes. If you do not do this, you will not get credit for any logged bugs!