Vault MedInquiry is an application within Veeva Vault Medical. It handles the intake, management, and fulfillment of Medical Inquiries.
MedInquiry Features
Medical Inquiry customers benefit from support across the whole lifecycle of a medical information request. Handling the capture of the inquiry, the construction of a response package using the approved content stored within Vault Medical, and sending this directly to the requestor all within one application provides a simple platform for users and drives efficiency in responding to inquiries.
- Dedicated Medical Inquiry UI: Medical Inquiries can be captured by users via a dedicated user interface. This is configurable to ensure all the information about the case and any related information can all be entered on a single page.
- Integration with Veeva CRM: A standard, bi-directional connection to Veeva CRM allows inquiries captured by field users to be triaged to MedInquiry. Once a response has been sent, Vault MedInquiry pushes an update to Veeva CRM to close the inquiry there.
- Automated Email Intake: Requests for medical information made via email can be automatically ingested into Vault MedInquiry.
- Integrated: MedInquiry is a central part of your Medical Affairs ecosystem. In addition to cases captured via the dedicated user interface, email ingestion, and those triaged from field users using Veeva CRM, the Vault API can be used to integrate with other intake mechanisms.
- Case Contact Management: MedInquiry manages your case contact database. Contacts can be entered manually by the user, pulled from Veeva CRM, or pulled from Veeva Opendata.
- Veeva Network Connection: A standard connection to Veeva Network allows users to search Veeva OpenData for accurate, up to date HCP reference data. This is done from the Medical Inquiry user interface, so you don’t need to navigate away from the case intake to find the HCP’s contact information.
- Case Management: The lifecycle of the case is managed in MedInquiry. Once the case has been captured, it can be assigned to a case owner to manage and respond to the inquiry. Case SLAs can be defined to ensure responses are sent.
- Case Escalations: Cases can be escalated to other users, while requests for new content creation can be escalated to the appropriate user.
- Medical Information: The content used to respond to the inquiry is stored in Vault. If you also have the MedComms application in your Vault, this can also be used to review and approve the medical information content.
- Response Package: You can construct a package of fulfillment documents from the library of approved content stored in Vault. This response package is sent via email to the recipient.
- Case Response Emails: Email responses can be sent directly from MedInquiry. You can set the To, From and Reply To email fields. A template can be defined in Vault for the email Subject and Body, which users can preview and edit before sending. Emails sent from MedInquiry are tracked, so if it is not successfully delivered to the recipient, users are notified and can resend it to ensure the requestor receives the information they need. If the recipient has a follow up question, they can reply to the email and it will be ingested into Vault alongside the original inquiry.
- Case Response Approval: You can use a workflow to approve the Case Response before sending.
- Reporting: The full suite of Vault reporting functionality is available to MedInquiry users. Medical Information requests can yield fascinating insights into your medical information, and can drive new content creation.