Recipient Types
Written by Michelle Henley
Updated at January 17th, 2024
Use Case
Different organizations engage with different types of individuals as part of their ongoing operations. In our system, we offer different recipient type categories to help companies classify recipients for purposes of payment restrictions and to support their policies and procedures related to the type of individual or organization being engaged.
In our Approvals & Disclosures product, recipient type selection allows the user and approvers to identify the type of recipient being engaged in the request and enables the use of other key features in the application. (E.g. Limits feature, build approval workflow triggers, recipient search, etc.)
Recipient Types
When a submitter adds a recipient to a multi-recipient request, the submitter will be required to choose the type of recipient from the list highlighted in the screenshot below.
Each recipient type corresponds with Master Data flags that allow recipients to be stored in the backend based on the associated flags. For example, an GO = True flag is applied to any new recipients added to the system as a GO (Government Official).
The list of recipient types can be changed to add, remove, or edit the names within the list. However, master data flags associated with recipient types cannot be changed.
Associated master data flags cannot be changed because if a new recipient (not used in a previous request) is added to a request, the recipient will be stored in Master Data → Individuals → Other (at the time the request is submitted) along with any flags associated with the recipient type they have chosen. (i.e., GO or HCP flag).
Lextegrity offers a wide variety of recipient types to choose from. The table below outlines the types of recipients that are available in the system along with their associated master data flags:
| Recipient Type | Search/Select Parameters | Master Data Parameters |
| Life Sciences | ||
|
HCP-Government Official |
Is HCP = true and Is GO = true |
Is HCP = true; Is GO = true |
|
HCP-Non Government Official |
Is HCP = true and is GO = false | HCP = true; GO = false |
|
Non-HCP Government Official |
Is HCP = false and is GO = true |
HCP = false; GO = true |
|
Other |
Is HCP = false and is GO = false |
HCP = false; GO = false |
|
Life Sciences - Additional Types | ||
|
Patient |
Is HCP = false and is GO = false |
HCP = false and is GO = false |
| Non-Life Sciences | ||
| Government Official |
Is GO = true and is HCP = true or false |
HCP = false; GO = true |
| Non-Government Official | Is GO = false and is HCP = true or false | HCP = false; GO = false |
- The flags associated with recipient types listed above cannot be changed, however, the names of the recipient types can be changed in the system. (For example, Government Official can be Public Official. Master data will still flag this recipient as HCP = false; GO = true.)
- New recipient types can be added to the application. If new types are added, master data parameters will need to be defined for each new recipient type.
- New master data parameters cannot be created in the master data. New recipients must adhere to current master data parameters.
Further information on how recipient types and master data work together can be found here.
Things to Note
- Additional recipients can be added to a request, even after the initial submission. Added recipients are still subject for review and approval based on the approval workflow configuration.
Additional Configurations
- Multi-recipient requests can be configured to allow for submission with or without recipients. More information can be found here: Submit Multi-Recipient Request Configurations