Below are proposed use cases:
- An Individual User enters or edits data in a web or mobile app to store Financial Interest and other relationship or activity information in a central repository.
- An Individual User manages permissions for Designees who may read, enter or edit Financial Interest and other relationship or activity information in a central repository on his or her behalf.
- A Designee enters or edits data in a web or mobile app to store Financial Interest and other relationship or activity information in a central repository.
- An Individual User transfers Financial Interest and other relationship or activity information from an existing system into a Central Repository.
- A Requesting Organization creates or edits an organization profile in a Central Repository, including the criteria for the Financial Interest and other relationship or activity information it would like Individual Users to include in required disclosures.
- An Individual User or Designee sends a disclosure of Financial Interest and other relationship or activity information from the Central Repository to a requesting organization with a profile in the Central Repository.
- The Individual User manages permissions for Requesting organizations to pull a disclosure of a predefined set of data.
- An Individual User downloads a disclosure of Financial Interest and other relationship or activity information from the Central Repository.
- An Individual User reviews his or her Financial Interest and other relationship or activity information in the central repository and submits to a Requesting Organization an attestation to its accuracy.
- A Requesting Organization requests a disclosure of an individual's or group of individuals' Financial Interest and other relationship or activity information contained in a central repository in a manner consistent with the requesting organization's profile.
From Pam: Do we also need a use case for the repository to ingest data from other sources? For instance, if the Individual User had an ORCID account, when registering could he or she present the number and have all the personal data transfer over? Maybe this is covered in use case F1-10.
Glossary
| Central repository | In this context, a system that compiles data on financial interests and other relationship or activity information if individuals for the purpose of managing disclosures. |
| Designee | In this context, an individual who enters or edits Financial Interest and other relationship or activity information on behalf of another. |
| Existing system | In this context, a system for tracking financial interests and other relationship or activity information for the purpose of managing conflicts of interest within a single institution or organization. |
| Individual user | An individual using the central repository or an existing system. |
| Mobile app | An application designed to run on a mobile device. |
| Requesting Organization | An organization that requests financial interests and other relationship or activity information from the central repository. |
| Requesting System | A system used by the requesting organization to send requests to the central repository and receive data form the central repository. |
| Web app | An application rendered through a web browser. |
Use Cases
ID | FI-10 |
|---|---|
Title | An Individual User enters or edits data in a web or mobile app to store Financial Interest and other relationship or activity information in a central repository. |
Actors | Individual user Web app or mobile app Central repository |
Trigger event | An organization requests that the individual user enter or edit Financial Interest and other relationship or activity information in a central repository. OR The individual user proactively chooses to enter or edit Financial Interest and other relationship or activity information to a central repository. |
Success end condition | Financial Interest and other relationship or activity information that is Up-to-date as of the date of submission for the individual user exists in the central repository. |
Assumptions | The individual user has registered with the central repository and logged into the web or mobile app. |
Description | The individual user uses the web or mobile app to enter or edit their Financial Interest and other relationship or activity information. They submit the up-to-date data in the app, and it sends that data to the central repository. |
Transaction | The individual user accesses the web or mobile app. IF the individual user has existing data in the central repository, the app displays that data. The reporting individual enters Financial Interest and other relationship or activity information. AND/OR The reporting individual edits existing Financial Interest and other relationship or activity information. The web or mobile app sends the reporting individual's Financial Interest and other relationship or activity information to the central repository along with required identifying information. |
Exceptions | There are errors in the data transfer. The data is corrupt or contains errors. |
Potential Standards | Financial interest and relationship data MedBiquitous Professional Profile |
ID | FI-12 |
|---|---|
Title | An Individual User manages permissions for Designees who may read, enter or edit Financial Interest and other relationship or activity information in a central repository on his or her behalf. |
Actors | Individual User Web app or mobile app Central repository |
Trigger event | The Individual User wishes to change permissions for their Designees or grant Designee permissions. |
Sucess end condition | The Designee permissions reflect the wishes of the Individual User. |
Assumptions | The Individual User has registered with the central repository and logged into the web or mobile app. The Designee has registered with the central repository. |
Description | The individual user uses the web or mobile app to manage permissions for a Designee who may enter data, edit data, send disclosures, or read data on his or her behalf. |
Transaction | The individual user accesses the web or mobile app. The individual user identifies the user for which he or she would like to manage permissions. The individual user grants, removes, or modifies permissions for the Designee. Permissions may include the ability to read data, enter data, edit data , or send disclosures. The web or mobile app sends information on the reporting individual's Designee permissions and parameters to the central repository. |
Exceptions | If the Designee has not registered with the central repository, the permissions are not recorded in the central repository. If there is a problem sending data, the permissions are not recorded in the central repository. |
Potential Standards | Unsure |
ID | FI-16 |
|---|---|
Title | A Designee enters or edits data in a web or mobile app to store Financial Interest and other relationship or activity information in a central repository |
Actors | Designee Web app or mobile app Central repository |
Trigger event | The individual user asks the Designee to make updates to the central repository. |
Sucess end condition | Financial Interest and other relationship or activity information that is Up-to-date as of the date of submission for the individual user exists in the central repository. |
Assumptions | The Designee has registered with the central repository and logged into the web or mobile app. The individual user has granted permissions for the Designee to enter or edit data in the central repository (see FI-12) |
Description | The Designee uses the web or mobile app to enter or edit the individual user's Financial Interest and other relationship or activity information. They submit the up-to-date data in the app, and it sends that data to the central repository. |
Transaction | The Designee accesses the web or mobile app. The Designee selects the individual for whom he or she is entering or editing data. IF the individual user has existing data in the central repository, the app displays that data. The Designee enters Financial Interest and other relationship or activity information. AND/OR The Designee edits existing Financial Interest and other relationship or activity information. The web or mobile app sends the reporting individual's Financial Interest and other relationship or activity information to the central repository along with required identifying information. The individual is notified that the Designee has entered, edited, or disclosed data on his or her behalf. |
Exceptions | There are errors in the data transfer. The data is corrupt or contains errors. The Designee is denied access to view or update the individual user's information. |
Potential Standards | Financial interest and relationship data MedBiquitous Professional Profile |
space
ID | FI-20 |
|---|---|
Title | An Individual User transfers Financial Interest and other relationship or activity information from an existing system into a Central Repository. |
Actors | Individual user Existing system Central repository |
Trigger event | The organization licensing or owning the existing system requests or requires the individual user to send Financial Interest and other relationship or activity information to the Central Repository. AND The organization wishes to participate in centralized reporting of Financial Interest and other relationship or activity information OR The individual user requests the organization licensing or owning the existing system to send the data to central repository. AND The organization is willing to send data to the central repository. |
Success end condition | Financial Interest and other relationship or activity information for the reporting individual exists in the central repository. |
Assumptions | The organization licensing or owning the existing system has registered with the central repository and has implemented the services required to send data to the central repository. The individual user has registered with and logged into the existing system. |
Description | The individual user provides financial interest and relationship or activity information to a local system, which then sends that data to the central repository. |
Transaction | The individual user accesses the existing system and provides accurate Financial Interest and other relationship or activity information, including any information necessary to uniquely identify the individual to the central repository. The individual user selects an option within the existing system to send data to the central repository. The existing system sends the reporting individual user's Financial Interest and other relationship or activity information to the central repository along with required identifying information. |
Exceptions | There are errors in the data transfer. The data is corrupt or contains errors. |
Potential Standards | Financial interest and relationship data MedBiquitous Professional Profile WDSL/SOAP Authentication standards such as Shibboleth, Open Auth, Open ID, etc. |
space
ID | FI-30 |
|---|---|
Title | A Requesting Organization creates or edits an organization profile in a Central Repository, including the criteria for the Financial Interest and other relationship or activity information it would like Individual Users to include in required disclosures. |
Actors | Requesting organization Central repository |
Trigger event | The Requesting organization has a need to create or update an organization profile. |
Sucess end condition | The central repository has an organization profile for the requesting organization that indicates which data fields it would like to receive in disclosures. |
Assumptions | The central repository is available to requesting organizations for this purpose. The Requesting Organization has executed any legal agreements necessary to use the Central Repository. Requesting Organizations can have multiple profiles. |
Description | The requesting organization registers with the central repository, indicating what data fields it would like to receive. |
Transaction | The requesting organization accesses the central repository. IF the requesting organization has not registered, the requesting organization completes the registration process for the central repository. The requesting organization indicates the criteria for the Financial Interest and other relationship or activity information it would like Individual Users to include in required disclosures. |
Exceptions | The organization profile may not be saved within the central repository. The requesting organization may not be able to register for the central repository. The requesting organization may not be able to log into the central repository. |
Potential Standards | Financial interest and relationship data MedBiquitous Professional Profile |
space
ID | FI-40 |
|---|---|
Title | An Individual User or Designee sends a disclosure of Financial Interest and other relationship or activity information from the Central Repository to a requesting organization with a profile in the Central Repository. |
Actors | Individual user Central repository Requesting organization Requesting system Web app Mobile app |
Trigger event | The individual has a need to send a disclosure of Financial Interest and other relationship or activity information to an organization with a profile in the Central Repository. |
Sucess end condition | The requesting organization has relevant, up-to-date financial Interest and other relationship or activity information for the reporting individual aligned with the criteria in the organization's profile. |
Assumptions | The individual user has registered with the central repository. The individual user has logged into the web or mobile app. The requesting organization has registered with the central repository, has created a profile in the central repository, and has a requesting system that has implemented the services required to receive data from the central repository. The system may send the disclosure in real time or batch with other disclosures. |
Description | The individual user uses a web or mobile app to send a disclosure to the requesting organization via the central repository. The central repository sends a disclosure of Financial Interest and other relationship or activity information to the requesting system for the requesting organization. |
Transaction | The individual user accesses the web or mobile app. The individual user uses the web or mobile app to selects data to include in the disclosure and initiate sending the disclosure to the requesting organization. The central repository sends the disclosure to the requesting system for the requesting organization along with identifying information. |
Exceptions | There are errors in the data transfer. The data is corrupt or contains errors. |
Potential Standards | Financial interest and relationship data MedBiquitous Professional Profile WDSL/SOAP |
space
ID | FI-42 |
|---|---|
Title | The Individual User manages permissions for Requesting organizations to pull a disclosure of a predefined set of data. |
Actors | Individual User Web app or mobile app Central repository |
Trigger event | The individual user wishes to grant, remove, or change permissions for a requesting organization to pull a disclosure, |
Sucess end condition | The requesting organization(s) have data access permissions aligned with the individual user's wishes. |
Assumptions | The Individual User has registered with the central repository and logged into the web or mobile app. The Requesting Organization has registered with the central repository. |
Description | The individual user uses the web or mobile app to grant, remove, or change permission for the Requesting Organization to pull a disclosure. This may include changing the predefined set of data which the requesting Organization has permission to access. |
Transaction | The individual user accesses the web or mobile app. The individual user identifies the Requesting Organization for which he or she would like to manage permissions. The individual user grants, removes, or modifies permissions for the requesting organization, specifying the set of data to which they have access. The web or mobile app sends information on the permissions selection and parameters to the central repository. |
Exceptions | If the Designee has not registered with the central repository, the permissions are not recorded in the central repository. If there is a problem sending data, the permissions are not recorded in the central repository. |
Potential Standards | Unsure |
space
ID | FI-45 |
|---|---|
Title | An Individual User downloads a disclosure of Financial Interest and other relationship or activity information from the Central Repository. |
Actors | Individual user Central repository |
Trigger event | The individual user wishes to download a disclosure of Financial Interest and other relationship or activity information for their own use (ie record keeping, verification, to send to an individual or organization that is not registered with the central repository. |
Sucess end condition | The individual users has a downloaded copy of his or her disclosure of Financial Interest and other relationship or activity information. |
Assumptions | The individual user has registered with the central repository and logged into the web or mobile app. The individual user has Financial Interest and other relationship or activity information in the central repository. |
Description | The individual user uses a web or mobile app to download a disclosure. |
Transaction | The individual user accesses the web or mobile app. The individual user uses the web or mobile app to select data to include in the disclosure and download the disclosure from the central repository. |
Exceptions | The downloaded file is corrupt. The download fails. |
Potential Standards | Financial interest and relationship data MedBiquitous Professional Profile |
space
ID | FI-50 |
|---|---|
Title | An Individual User reviews his or her Financial Interest and other relationship or activity information in the central repository and submits to a Requesting Organization an attestation to its accuracy. |
Actors | Individual user Central repository Requesting organization requesting system |
Trigger event | The individual user's employer, grantor, or publisher may prompt the individual periodically to review his or her data and attest as to its accuracy. A Requesting Organization establishes a reminder schedule and tracking for individual attestation of compliance with the Requesting Organization’s disclosure requirements. |
Sucess end condition | The requesting organization receives an individual user's attestation of accuracy for data in the central repository |
Assumptions | The individual user has registered with the central repository and logged into the web or mobile app. The requesting organization has registered with the central repository, has created a profile in the central repository, and has a requesting system that has implemented the services required to receive data from the central repository. |
Description | An Individual User reviews his or her Financial Interest and other relationship or activity information in the central repository and submits to a Requesting Organization an attestation of compliance with the Requesting Organization’s disclosure requirements. |
Transaction | The individual user uses a web or mobile app to view his or her data in the central repository. If necessary, the individual user enters or edits data in the central repository (see FI-10). The individual user initiates sending an attestation of compliance with the Requesting Organization’s disclosure requirements to the requesting organization. The central repository sends the attestation to the requesting system for the requesting organization. |
Exceptions | The attestation does not get saved to the repository. The attestation is not sent to the requesting organization. |
Potential Standards | Financial interest and relationship data |
space
ID | FI-60 |
|---|---|
Title | A Requesting Organization requests a disclosure of an individual's or group of individuals' Financial Interest and other relationship or activity information contained in a central repository in a manner consistent with the Requesting Organization's profile. |
Actors | Central repository Requesting organization Requesting system
|
Trigger event | An organization has a need for the individual's disclosure of Financial Interest and other relationship or activity information. For example, a journal may be considering an article for publication and need to review the disclosure; a provider of continuing education may need to review the disclosure of a faculty member; an institution government agency, professional organization, or professional committee may require a disclosure. |
Success end condition | The requesting organization has up-to-date financial Interest and other relationship or activity information for the individual user. |
Assumptions | The individual user has registered with the central repository. The individual user has granted permission for the requesting organization to receive disclosures of Financial Interest and other relationship or activity information, indicating any limits or parameters for that permission. The requesting organization has registered with the central repository, has created a profile in the central repository, and has a requesting system capable of requesting and receiving data from the central repository. The system may send the disclosure in real time or batch with other disclosures. |
Description | The requesting organization uses a requesting system to indicate that it wishes to pull a disclosure for the reporting individual. The requesting system obtains the disclosure from the central repository. |
Transaction | The requesting organization uses a requesting system to indicate that it wishes to pull a disclosure for the reporting individual. OR The requesting organization uses a requesting system to indicate that it wishes to pull disclosure information for a set of reporting individuals. The requesting system contacts the central repository and provides the disclosure request. The central repository provides the disclosure(s) of Financial Interest and other relationship or activity information to the requesting system. The central repository sends a notification to the reporting individual in cases where the individual has requested notification. The central repository logs the disclosure provision. |
Exceptions | The reporting individual has not granted permission for the requesting organization to receives disclosures; no data is sent. The requesting system is unable to authenticate to the central repository. There are errors in the data transfer. The data is corrupt or contains errors. |
Potential Standards | Financial interest and relationship data MedBiquitous Professional Profile WDSL/SOAP |