Challenge Overview
Overview
We are building a pair of applications that implement the same payment form. It is critical for the payment form to comply with a payment template issued by the Centers for Medicare and Medicaid Services (CMS). Your task in this contest is to find discrepancies between our web app wireframes and the CMS payment template.
Instructions
The attached document Open Payment Submission File Specs 04 21_draft 3.xlsx contains three payment templates. This contest is concerned only with the first one, "General Payments (Non-Research)". Fields 1 through 5 are out of scope. We are verifying fields 6 through 46.
The attached HTML wireframes report.host.zip contain features that are out of scope. We are only concerned with the payment editing interface. To see the payment fields that you must verify, follow these steps:
- Open the index.html file in a web browser.
- Click on "Payments or transfers of value" in the left frame.
- In the payment list, click on the first row. The recipient is "John Lee" and the row will be highlighted when you mouse over it.
- The resulting editor has five tabs. We are ignoring the first tab and verifying the other four.
- Click on the second tab, "Recipient". Now click on the "Edit" link at right. You will have to click "Edit" in each of the four tabs.
After completing the above steps, you will be able to compare the web form to the CMS template. Tabs 2 through 5 in the web form should correspond to groups 2 through 5 in the CMS template.
- web tab 2, "Recipient" = template group 2, "Recipient Demographic Information"
- web tab 3, "Medical Supply" = template group 3, "Associated Drug, Device, Biological, or Medical Supply Information"
- web tab 4, "Payment" = template group 4, "Transfer of Value (Payment) Information"
- web tab 5, "General Info" = template group 5, "General Record Information"
You are responsible for checking columns A through F of the CMS template. Columns G and H are not in scope because field size and validation will be enforced by software. Note that column I does not apply to us. Our web form must include all fields, including those that are not to be publicly displayed.
Prizes
First place: $400
Second place: $200
The top two places will be determined by the greatest number of valid bugs reported per contestant. If there is a tie, the placement will be decided by the copilot's assessment of the quality of the bug reports.
Contestants who do not win one of the top two prizes will be paid $5 per bug for a maximum of 40 bugs.
Final Submission Guidelines
To start filing tickets in the JIRA project, post a request in the contest forum. Look for the thread "permission to create tickets".
While you are waiting for your JIRA permissions, you can file bug reports in the same thread in the contest forum.