Configure the Medical-Safety connection to sync Adverse Event data between Medical and Pharmacovigilance systems.

About the Medical-Safety Vault Connection

Using the Medical-Safety Vault Connection, organizations with both MedInquiry and a Safety Vault can exchange Adverse Event data. MedInquiry transfers data, such as patient details, reporter information, product details, and event information to Vault Safety. For more information see About the Medical-Safety Vault Connection.


In addition to the configuration on this page, to use this feature you must configure the following:

Medical-Safety Connection Components

The components below support the standard Medical-Safety Vault Connection.


The following Connection records are available in Admin > Connections:

  • Medical-Safety Connection (medical_safety__v) is available in your Medical Vault
  • Medical Safety Connection (medical_safety__v) is available in your Safety Vault

Integration & Integration Points

The Integration and Integration Point objects enable Vault Safety to manage the message queues and define what data the connection maps from MedInquiry to Vault Safety. These records are read-only and are used by Vault Safety to manage the connection and track any connection errors.

The Medical Safety Connection record includes the default Adverse Event Integration record with the following standard Integration Point records in your Safety Vault:

  • Adverse Event Integration Point (adverse_event_oip__v)
    The outbound integration point for sharing Adverse Event information.
  • Adverse Event Integration Point (adverse_event_iip__v)
    The inbound integration point for sharing Adverse Event information.

Integration Rules

To support the Medical-Safety Connection, it may be necessary to transform data from the source Vault’s data model to fit within the target Vault’s data model. You can use Integration Rules to incorporate configurable rules for mapping object and document fields between two Vaults.


This feature includes four (4) standard message processing queues. You can access and manage these queues from Admin > Connections > Spark Queues.

In your Medical Vault, you have:

  • Safety to Medical Adverse Event inbound queue (safety_to_medical_ae_inbound_queue__v)
  • Medical to Safety Adverse Event outbound queue (medical_to_safety_ae_outbound_queue__v)

In your Safety Vault, you have:

  • Medical to Safety Adverse Event inbound queue (medical_to_safety_ae_inbound_queue__v)
  • Safety Outbound Messaging Queue (safety_to_medical_outbound__v)

User Exception Objects

Vault Safety includes the User Exception Message object and its child object, User Exception Item, to help you track and resolve any errors that occur with your Medical-Safety Connection. If the Vault Safety side of the integration can’t process an incoming message, Vault Safety creates a User Exception Message record to capture the failure.

You can view and manage these messages from Admin > Connections > User Exception Messages.

Vault Safety also creates individual User Exception Item records for each Inbox Item or related document that failed on the related Integration Point record in your Safety Vault. The User Exception Item’s Error Message field contains the reason for the error.

A User Exception Message means you need to update your configuration. After you update the configuration, Vault Safety attempts to resolve any errors the next time the connection runs. You can also select the Reprocess Request action on the User Exception Message record to run the connection and resolve errors.

When the connection job runs, Vault Safety processes all User Exception Messages in the Active state. Any new errors result in new User Exception Messages in the Active state. Once the connections on both the Safety and Medical side run, previously Active User Exception Messages are inactivated.