Challenge Overview
Project Overview
We are building a mobile app for use in the U.S. healthcare sector. A new federal law requires transparency in payments and transfers of value from the healthcare industry to healthcare providers. From now, each payment or transfer of value must be recorded. Please note the following terminology
- what is recorded: a payment or transfer of value
- who gives it: a physician or teaching hospital
- who receives it: an applicable manufacturer (AM) or group purchasing organization (GPO)
The U.S. government wants to provide an app that encourages compliance with the law by making it easy to record information while the transfer of value is taking place.
- data collection in this app must adhere to the CMS payment template (attached)
- Open Payments overall will have to comply with FISMA
- Open Payments overall will have to comply with the HIPAA Security Rule
The attached Conceptualization document describes the business requirements for the software system and outlines the user flows it must support. The overall system comprises a mobile app and a report host. This contest is concerned with system architecture for the mobile app. However, we expect you to be aware of the interaction with the report host. Your work in this contest will influence the architecture of the report host, which comes later.
System Requirements
You are responsible for the system architecture of an iOS mobile app. We are targeting the following platform parameters.
- iOS 6
- support for small screens: iPhone 5 in portrait mode
- support for large screens: iPad mini and iPad with Retina display
Each party in a transaction will use the same app, but each will see an interface that is tailored for its role in the transaction. The AM/GPO field agent will have an interface particular to the AM/GPO recording requirements, and the recipient will have an interface tailored to the recipient's needs.
The set of information to be recorded about a gift will be fully visible to both users. The required fields are listed in the attachment 508_CMS-10419_Non-Research_Payment_Template.pdf. Field numbers refer to this file.
The descriptions below, in conjunction with the attached wireframes, describe the expected behavior of the app.
Registration
- While registering, the AM/GPO field agent enters a code that will let the app communicate with the report host at the home office. This code is separate from the field agent's login password.
- The recipient has the option of entering some or all of fields 6 through 26 during registration. These fields may also be entered or updated later.
- Both users must be able to review and update their registration information.
Login/logout
Login authentication takes place on the app without any network connection. However, a network connection is required for password retrieval by email.
Recording gift information without the recipient's assistance
All interaction must be designed so that the AM/GPO field agent can record information even if the recipient is not using the app.
Transfer of information from the recipient to the AM/GPO field agent
The recipient's personal information is sent to the field agent to start the payment recording process. If this transfer does not take place due to lack of Bluetooth or lack of an app, the field agent enters the recipient's information manually.
Incomplete payment recording
Some information may not be immediately available, making the payment record incomplete. It will be reported as such to the home office and completed later.
Transfer of information from the AM/GPO field agent to the recipient
The Bluetooth connection is maintained during the transaction and used by the field agent to send the recorded information to the recipient. If the connection breaks and the app cannot make a new one, it informs both users.
Sending payment information to the report host
After the transaction, the field agent's app transmits the record to the AM/GPO home office. The transmission may be queued for later delivery if the mobile device is currently offline.
Updating the recipient's app by email
It is quite possible that the recipient was not using the mobile app at the time of the transaction. It is also possible that the field agent recorded incomplete information at the time of the transaction. In either case, the payment record must eventually be completed at the home office. It is also possible for an existing record to be edited at the home office. In these cases, the payment record will be sent to the field agent and the payment recipient
- the updated payment record is sent to the field agent's app by direct transmission
- the new or updated payment record is emailed to the recipient, who may import it into the app
Note that the recipient's app must have a feature to import a new or updated payment record that arrives by email.
Submission Deliverables
- standard deliverables are expected
- we will be going direct to assembly (no components, please)
Final Submission Guidelines
Submission deliverables are listed above.