Provide a Medical Utility or Practice Related Item (ex-US)
Written by Michelle Henley
Updated at January 22nd, 2024
Table of Contents
Use Case
- Provide a Medical Utility or Practice Related Item requests are used to seek pre-approval to provide a practice related item/item of medical utility to a HCP or GO. This request type is used by companies where such items are allowed to be given in specific countries and circumstances.
- Typically involves providing only two types of support: Medical Utility or Promotional aid.
- This request is typically used to get approval for a planned activity, where the types and amount of support are either known upfront or can be estimated.
Key Features
-
Provide a Medical Utility or Practice Related Item requests are separated into two sections:
- Activity Details section to capture the details related to the event.
- Recipients Details section to capture the details of the recipients and type of support requested for them.
Things to Note
• Submitting
- Multiple recipients can be added to a single engagement request.
- Additional recipients can be added, even after the initial submission. Added recipients are still subject for review and approval based on the approval workflow configuration.
- Spending can be monitored at a more granular level by adding different Support Categories and assigning them to different recipients within a single engagement.
- Integrate with Veeva or Reltio (IQVIA) Master Data Management Providers (MDM) to allow search and selection of HCPs from those MDM databases.
- Ability to adjust the overall Support Category amount above and/or below the default Support Category amount within the request.
- Changes can be made after the request is approved. However, that will require the request to be re-approved by all approvers based on the workflow configuration.
- Initially selected approvers can not be changed at the time of re-submitting the activity or the consultants.
- The recipient or HCP does not need to be profiled for this request as service fee is not a type of support category available in this request type.
- Spend Amounts can be entered in any currency. However, the totals are calculated in the default currency set for the application.
• Approving
- In order to enable more dynamic and faster approvals, separate approval processes for the activity and recipients can be configured. For example, if the activity and 5 out of 6 HCPs are approved, the 6th HCP can remain under review. This means the business can start contracting and other logistics without compliance being a bottlenecked by the 6th HCP.
- Approvers can approve or reject the activity or recipients. Once an activity is rejected, it moves all recipients to canceled status. A Rejected request can not be re-submitted.
- Approver needs to approve the activity and recipients separately. Activity must be approved first by an approver before taking approved action on the recipients.
- Approvers have the ability to request for more information from the submitter on the activity and/or on individual recipients during the approval process. In such instances, the activity or recipient needs to be re-submitted by the submitter after the updates have been made. Depending on the approval workflow configuration, the request will go back to the same approver for review or the approval workflow can be initiated from the beginning.
• Spending
- Aggregate Spend and Count analysis at support category and request level. Data is aggregated across recipients to provide a total request value.
• Oversight
- In-request screening using either Refintiv or RDC to compare individual and organization names against watchlist data.
• Request Features
Key Features
- Editor Collaboration allows different users to collaborate on filling details of the engagement.
- Approver Collaboration allows one of many approver collaborators to approve in any one approval step.
- Automated Approver Collaboration is used to automatically assign approver collaborators.
- Assign tasks to yourself, other users, or even third-parties.
- Easy-to-follow Request History tracks a complete audit trail of the changes and actions taken on the request throughout the approval process.
- Request Version Comparison allows for the ability to compare between different versions of the request if updates are made to the request before, during, and after the approval process.
- Business Owner configuration allows for requests to be submitted on behalf of someone else or to identify the actual business owner of the request.
Configurable Components
|
Request Configurations |