Skip to main content

Who on my team should use Request?

  • Updated

Covered entities (CEs) can invite up to three (3) other users to join their teams at their discretion using the Team Management feature. We recommend inviting members of your team who may be responsible for submitting discount requests, reviewing remittance advice or tracking payments. 

Each team member can be assigned one of four different roles.

  • Admin
    • Recommended Users:
      Authorizing Official (if a very small organization)
      HRSA database primary contact
      Pharmacy Director/VP Pharmacy
      340B Program Manager (for very large org)
      **This person should not be a TPA/consultant in most cases**
  • Submitter

    • Recommended Users:
      340B Administrator, Program Manager, and/or Analysts
      Pharmacy Directors/Managers
      TPA/Consultant (depending on scope of engagement)

  • Viewer
    • Recommended Users:
      Senior leaders/managers looking for oversight or insight into the data
      Consultants/TPA
  • Payment
    • Recommended Users:
      Financial Representative

 

For covered entities (CEs), up to three (3) individuals can be involved in the initial sign up process. Step-by-step details are provided in this help desk article.

  • The process begins with the Authorizing Official (AO), whose email must match the AO listed in the OPAIS database for the specified 340B ID. 
  • The AO can choose to also be the Account Admin, or they may choose to invite another representative from their team. The Account Admin will be responsible for the remaining portion of onboarding and remain as the primary contact for that CE when communicating with the Kalderos support team in Request. This role will be the contact person on the Dwolla account for the Health System. 
  • Lastly, the Account Admin may choose to invite a third person, the Financial Representative, from their team to complete the remaining setup that includes linking of a bank account to receive payments.

Once onboarding is complete, the Account Admin can then proceed to invite additional team members to use the application. Each team member can be assigned one of four different roles.

  • Admin
  • Submitter
  • Viewer
  • Payment

By default, the AO and Account Admin receive the ‘Admin’ user role, and the Financial Representative receives the ‘Payment’ role.

1) Admin

The Admin user will have the broadest set of permissions for a Covered Entity. By default, the AO and Account Admin will be assigned this role, but new users can also be invited with this role.

Recommended Users

  • Authorizing Official (if a very small organization)
  • HRSA database primary contact 
  • Pharmacy Director/VP Pharmacy
  • 340B Program Manager (for very large org) 
    **This person should not be a TPA/consultant in most cases**

Permissions

  • User Management
    • Add, edit, remove users
    • Change user roles
    • Assign/unassign access to CEs
  • Request Center
    • View requests
    • Submit new discount requests
    • Reverse requests
    • Correct and resubmit requests
  • Payments & Remittance Advice
    • View Payments and Remittance Advice
    • View or edit Bank Info
    • View outstanding credits

 

2) Submitter

The Submitter role is intended for members of your team who will be submitting or uploading requests for 340B rebates, but should not have full admin privileges. 

Recommended Users

  • 340B Administrator, Program Manager, and/or Analysts
  • Pharmacy Directors/Managers
  • TPA/Consultant (depending on scope of engagement)

Access

  • User Management
    • View assigned users to a CE
    • Edit their own information
  • Request Center
    • View requests
    • Submit new discount requests
    • Reverse requests
    • Correct and resubmit requests
  • Payments & Remittance Advice
    • View Payments and Remittance Advice
    • View Bank Name
    • View outstanding credits



3) Viewer

The Viewer role is intended for users who require read-only access to the data in Request.

Recommended Users

  • Senior leaders/managers looking for oversight or insight into the data
  • Consultants/TPA

Access

  • User Management
    • View assigned users to a CE
    • Edit their own information
  • Request Center
    • View requests
  • Payments & Remittance Advice
    • View Payments and Remittance Advice
    • View Bank Name
    • View outstanding credits

 

4) Payment

The Payment user role is similar to the Viewer but also has edit privileges to maintain banking information. Some organizations may not utilize this role if an Admin user also maintains the banking setup.

  • User Management
    • View assigned users to a CE
    • Edit their own information
  • Request Center
    • View requests
  • Payments & Remittance Advice
    • Edit Bank Information
    • View Payments and Remittance Advice
    • View outstanding credits

Related articles