Open Payments - Data Host - UI Specification

Project overview

The Open Payments project aims to help the U.S. healthcare industry to comply with new federal laws about payment transparency. When a healthcare manufacturer makes a payment to a physician, the manufacturer is required to make a detailed record of the transaction. A mobile app used by the manufacturer's field agents to record payments is being developed in another set of contests. This contest is concerned with the report host, which is a web application installed at the manufacturer's home office. The report host lets users carry out the following functions.

• view, sort, and filter records
• edit records to complete or correct them
• send updated records to field agents and payment recipients
• export records to a spreadsheet

The manufacturer is not required to use this software to prepare its payment reports. Our goal is to make it user-friendly and fully compliant with government standards so that manufacturers will want to use it.

 

Task description

We are asking you to prepare a UI specification that will be used as input to a storyboard contest and a module architecture contest. You are responsible for documenting the application requirements according to the attached template. Use case diagrams and activity diagrams are also required.

The conceptualization document contains ideas that have since been modified and superseded by other contests. Wherever there is a conflict between the conceptualization document and another one of the attached documents, the other document takes precedence. Please note the following generalized terminology, which we are now using in preference to the earlier terminology.

• the transaction recorded by the software is a payment or transfer of value (this is more general than a gift)
• the party that is offering the payment or transfer of value is an applicable manufacturer or group purchasing organization
• you may also refer to the applicable manufacturer or group purchasing organization as the payer
• the party that is receiving the payment or transfer of value is a physician or teaching hospital
• you may also refer to the physician or teaching hospital as the recipient

The most complete definition of the report host UI is embodied by the wireframes. However, the UI is subject to modification in this contest in order to better comply with the requirements of the Centers for Medicare and Medicaid Services (CMS). You are free to specify changes and additions to the UI in your submission.

Please note the following consistency requirements for the wireframes.

• The detailed view of the payment form (click on the first row) and the advanced search form should have the same set of fields. This should currently be the case in the wireframes.
• The "Manage Field Selection" button, which controls the visible columns in the payment table, should have the same list of field names as the payment form. This is currently not the case in the wireframes.
• The most important requirement is for the payment form to comply with the CMS payment template.

The CMS payment template is found in the first sheet of "Open Payment Submission File Specs 04 21_draft 3.xls". It is crucial that we implement all of the form logic, data restrictions, input validation, and other requirements stated in the template.

Final Submission Guidelines

Input documents

• the overall Conceptualization document
• module architecture for the mobile app
• wireframes for the report host
• the CMS payment template: refer to the first sheet, titled "General Payments (Non-Research)"

For each document, please note the modifications summarized above and ask lots of questions in the forum to make sure that you understand the requirements for the report host.

 

Deliverables

• Application Requirement Specification (ARS)
• use case diagrams
• activity diagrams

The other document types listed in section 4.1 of the ARS (logical data model, site map, site definition, quality assurance plan) are not required.