Configuring Safety Link

Safety Link is an integration between Vault CDMS and Vault Safety or between Vault CDMS and any third party safety system via the CDMS AS2 Gateway. Enabling this integration automates the reporting of all serious adverse events (SAEs) to the chosen safety system. Organizations can configure a study to also send related (via form linking) case information, including concomitant medications, medical histories, and related adverse events, alongside the SAE, and optionally demographics items or an In Case of Death form, when that data is available. Any time a site completes or updates the SAE form, or any related forms, CDMS automatically generates a first-send or follow-up and sends it to the safety system.

The automated data transfer uses E2B in the R3 format. This provides a scalable way to send all required and complimentary case information that any safety system can parse and ingest accurately.

Safety administrators can configure this integration by mapping study design Items to the E2B R3 elements and setting the timing of the first-send and the frequency of any follow-ups. For third-party safety systems, you can provide other attributes, such as a URL and Certificate, to use with the integration.

E2BLink supports automated nullification via E2B in R3 format. Nullifications are generated if the SAE Term is changed to non-serious or the form is reset. E2BLink accepts acknowledgements from the safety system to confirm that data was received and parsed correctly, and also confirm the case status, message status, and provide error details, if any. All data is readily available in the Safety Cases and Safety Message reports to confirm integration status and health.

Connect to the Safety Vault

If you are using Vault Safety, a Vault Owner can follow the instructions below to connect your CDMS vault and your Safety vault. If your organization is using a third party safety system, see Connect to a 3rd Party Safety System.

Creating the Connections

First, you must connect your CDMS and Safety vaults with Vault-to-Vault Connections.

To perform the actions described below, you must be a Vault Owner in both the CDMS and Safety vaults.

Create the Connection in CDMS

1. Navigate to Admin > Business Admin > Safety Transmission Profiles.
2. Click + Create.
3. For Name, enter “{Organization}SafetyVault”, for example, “VerteoPharmaSafetyVault”. Note that whitespaces aren’t allowed.
4. For Batch Sender Identifier, enter “CDMS{CDMS Vault ID}”, for example, “CDMS50720”. You can find the Vault ID for your CDMS vault from Admin > Settings > General Settings in your CDMS vault.
5. For Batch Receiver Identifier, enter “SAFETY{Safety Vault ID}”, for example, “SAFETY57667”. You can find the Vault ID for your Safety vault from Admin > Settings > General Settings in your Safety vault.
6. Click Save.

7. Click the Connection. This opens the Details page for the Connection.

8. From the Actions menu, select Download Connection File.

9. In the confirmation dialog, click Download.
10. Save the connection file to a location of your choosing.

Create the Connection in Safety

1. Switch to your Safety vault.
2. Navigate to Admin > Connections.
3. Select CDMS to Safety Connection.

4. From the Actions menu, select Connect from File.

5. Select the connection file you downloaded in your CDMS vault.
6. Click Continue.
7. Click Workflow Timeline to expand that section.
8. In the Details panel, select Reassign from the Actions menu.
9. Select your User Name.
10. Click Save.
11. In the Review Connection banner, click Complete.
12. Select Approve Connection.
13. Click Complete.

Approve the Connection in CDMS

1. Switch to your CDMS vault.
2. Navigate to Admin > Connections.
3. Click Vault to Vault: CDMS to Safety Connection to open the connection.
4. Click Workflow Timeline to expand that section.
5. In the Details panel, select Reassign from the Actions menu.
6. Select your User Name.
7. Click Save.
8. In the Review Connection banner, click Complete.
9. Select Approve Connection.
10. Click Complete.

Safety Transmission Profile

Once you’ve connected your Safety vault to your CDMS vault, you can configure your Safety vault to accept safety cases from CDMS. To do so, you’ll create an Organization record and several supporting records. Then, you’ll create a Transmission Profile.

To perform the actions described below, you must be a Vault Owner in both the CDMS and Safety vaults.

Create an Organization, Study & Product

To create an Organization:

1. Switch to your Safety vault.
2. Navigate to Admin > Business Admin > Organizations.
3. Click + Create.
4. Select Sponsor for Type.
5. Click Create.
6. For Name, enter “{Organization} CDMS Vault”.
7. For Sender Type, select Pharmaceutical Company.
8. For Organization UID Code, enter a unique value to represent your organization.
9. Click Save.

To create the Product and Registration:

1. From the Organization record, click Products to expand that section.
2. Click + Create.
3. Select Drug for Type.
4. Click Continue.
5. Enter the Product Name.
6. Click Save.
7. Click to expand the Registrations section.
8. Click + Create.
9. Enter a Registration Date.
10. For Registration Type, select Investigational New Drug (IND).
11. For Country, select United States of America.
12. Click Save.

To create the Study and Study Product:

1. Navigate to Admin > Business Admin > Organizations.
2. Click your organization’s Name to open it.
3. Click Studies to expand that section.
4. Click + Create.
5. Enter a Study Number.
6. Select Open Label for Masking. This is the only supported option in the current release.
7. Enter the Study Name. This must be an exact match to the Study Name in the CDMS vault (study__v.name__v).
8. Click Save.
9. In the Study Products section, click + Create.
10. For Type, select Drug.
11. Click Continue.
12. Enter a Name.
13. For Study Product Role, select Investigational.
14. The Product and Product Registration fields should have defaulted to the Product and Product Registration you created earlier. If not, select those.
15. Click Save.

Create a Transmission Profile

To create a Transmission Profile:

1. Navigate to Admin > Business Admin > Transmission Profiles.
2. Click + Create.
3. For Name, enter “{Organization} CDMS to {Organization} Safety”, for example, “VerteoPharma CDMS to VerteoPharma Safety”.
4. Select your Organization.
5. For Origin ID, enter “{Organization}{SafetyVaultID}” with no spaces, for example, “verteopharma57667”.
6. For Destination, select your Organization.
7. For Destination ID, enter “{Organization}{CDMSVaultID}” with no spaces, for example, “verteopharma50720”.
8. Click Save.

Now, your Safety and CDMS vaults are ready to use the E2BLink. Configure the link for your Study and map your data items to their E2B elements from EDC Tools > Safety Configuration.

Email Notifications

You can set your configuration so that up to five (5) users receive notifications when the following events occur:

• Transmission of a Safety Case or Safety Message fails via the Safety to CDMS Connector or via the AS2 Gateway to a third party safety system
• Safety to CDMS or AS2 Gateway connection becomes inactive
• Gateway Profile becomes inactive
• AS2 Gateway Encryption Certificate expires:
  • 3 months before expiration
  • 1 month before expiration
  • Day of expiration

To set up email notifications:

1. Navigate to Tools > System Tools > External Connections > Safety.
2. Locate your Connection in the list.
3. Click the Name to open the Edit Connection dialog.

4. Enter up to five (5) Notification Emails, separated by a semi-colon (;) or carriage return.

5. Click Save.

To stop sending notifications, clear the Notification Emails field.

General Settings for First Send & Follow Up

Before you can map your forms to their E2B elements, you must first configure the General Settings for your Study and the safety system.

Available Settings

Setting	Default	Description
Study Transmission Status	Inactive	Setting this field to Active enables E2BLink for your Study. Vault will not begin sending _Safety Cases until this is set to Yes, even if the other configuration is complete.
Safety System Connection Profile		Select the Safety System Connection Profile that you want to send your Safety Cases to. The available options are the configured Transmission profiles.
Reporter		Select None or Principal Investigator. If you choose Principal Investigator, Vault uses the Principal Investigator assigned to the Site. This is the value for the Reporter field on the Safety Case.
First Send E2B Schedule	3 hours	Select an Interval. The interval is the amount of time after form submission that Vault will send the collected data to the safety system.
Follow-up E2B Schedule	Once every 3 days	Select an Interval. The interval is the amount of time after a user saves changes to a form that CDMS will send a follow-up to the safety system.
Null Flavor for Coding	None	Select how to handle null values for coding: "None", "10067482", or "99999999". If you choose "None", Vault won't include the E2Bs below in the Safety Case. If you choose "99999999" or "10067482", CDMS sends that as the value for the E2Bs below. Coding E2Bs: SAE - E.i.2.1b: Reaction / Event (MedDRA code) AE - E.i.2.1b: Reaction / Event (MedDRA code) MH - D.7.1.r.1b: Medical History (disease / surgical procedure / etc.) (MedDRA code)
Mute Coding Follow-ups	No	When set to Yes, this setting stops Vault from sending follow-ups when the only change is the coding of the AE term (coded, uncoded, or a change to the dictionary version). When set to No, Vault sends follow-ups for all changes, including coding. If your study primarily performs coding in the safety system, Vault recommends setting this option to Yes to prevent unnecessary follow-ups to the safety system.
Alerting on Unsubmitted Forms	No	Select Yes to activate a job that will alert selected users about unsubmitted SAE forms. This option sends an alert when a site user creates a new SAE form, enters data to mark it as Serious, and doesn't submit the Form. This option also sends an alert if the user submits the Form but doesn't enter a value for the mapped AE term item. These scenarios prevent the initial sending of safety data. The reporting deadline will also be set when seriousness is set to Yes. You can choose alert recipients from Tools > Safety Integrations. From Safety Integrations, you can choose a specific list of users or email groups and limit recipients by country. Vault sends a notification to the selected users and to the site user one hour after form creation.

Configure Static Values (Contact Veeva Support to enable these options in your vault)
Subject ID E2B Location (D.1.-)	Patient Name or Initials	The Subject ID in CDMS is used in an E2B location, which may vary by sponsor or study. You can choose from one of the following options: Patient Name or Initials, E2B D.1 (Default behavior prior to 23R1) GP Medical Record Number, E2B D.1.1 Specialist Record Number, E2B D.1.2 Hospital Record Number, E2B D.1.3 Investigational Number, E2B D.1.4
Subject ID Format in E2B	Subject Only	Choose which format Vault uses to transfer the CDMS Subject ID to the safety system. Country ISO-Site-Subject (Default behavior prior to 23R1) Site-Subject (Site Number-Subject ID) Subject Only (value "as is" in EDC)
Sender Type E2B Value (C.3.1)	Pharmaceutical Company	Choose which type of organization is sending the safety case from CDMS to the safety system. This value is passed via C.3.1. You can choose from the following organization types: Pharmaceutical Company (Default behavior prior to 23R1) Health Professional Patient/Consumer Other Organization
Primary Source Qualification E2B Value (C.2.r.4)	Physician	C.2.r.4 yields the Classification of the person assessing the study drug or treatment, as it relates to each Adverse Event of a Safety Case. You can choose from the following classification types: Physician Pharmacist Other Health Professional (Default behavior prior to 23R1) Lawyer Consumer or Other Non Health Professional

Configure General Settings

To configure your general settings:

1. Navigate to your Study in Studio >Safety Settings. 2, Click Edit.
2. Select Active for Study Transmission Status.
3. Select your Safety System Connection Profile.
4. Select None or Principal Investigator for Reporter. This is the value sent for Reporter to the safety system.
5. For First Send E2B Schedule, select an Interval. This is the amount of time after form submission that CDMS will send the collected data to the safety system.
6. For Follow-up E2B Schedule, select an Interval. This is the amount of time after a user saves changes to a form that CDMS will send a follow-up to the safety system.
7. Click Save.

Duration Based Inclusion of Related Forms

You can choose to include a related Form based on it’s date in relation to the SAE form.

General Notes

1. Allows site linking for inclusion. This is an option for any section except Study Drug.
2. Compare dates - SAE Start / End to the related form Start / End
3. Both date comparison and allowance of site linking can be configured within a section, i.e. any are true, the form data is included in the safety case / transfer.
4. For fields where date only field is compared to full datetime, both are considered date for the comparison purpose
5. For datetime to datetime comparison where one of the time values is set unknown, both are considered date for the comparison purpose
6. Study Drug is a special section that contains several options that are specific only to that section.
7. When a start date is not set on a related form (or the primary SAE), duration inclusion rules are ignored
8. For forms with no end date (yet, or ongoing), the end date is considered far in the future for comparison purposes of the two durations. As such, those forms are included as the conservative default.
9. For partial dates (e.g. unknown day), comparisons are done with respect to the year first, then month.
10. When a form has no end date map (common with study drug or external labs), then the end date is considered equal to the start date.

Key Fields by Related Section

For a form to be included into the safety case, it must match the duration rules (or be linked to a site) and have specific fields with data within that form (i.e. considered ‘complete’).

Section	Required Field	E2B Mapping	Notes
Adverse Events	Reaction/Event as reported by the Primary Source in native language	E.i.1.1a	Event description is required on a related AE in order to be included
Concomitant Medications	Medicinal Product Name as Reported by the Primary Source	G.k.2.2	The name of the medication/treatment is required on a related CM in order to be included
Medical History	Comments	D.7.1.r.5	Medical history description is required on a related MH in order to be included
External Labs	Test Name	F.r.2.1	Must specify what test was done in order to be included
Study Drug	Date and Time of Start of Drug	G.k.4.r.4	Because all study drug inclusion is regarding data comparisons, a form must have a start date for consideration

Options / Related Section Availability

X = ‘Can be used in the section’

Options	AE	CM	MH	Labs	Study Drug	Notes
All	X	X	X	X	X	Disables any other option in that section
Linked by Site User	X	X	X	X		When this option is used, Form to Form or Item to Form linking must be configured and site must perform the link
Duration overlaps any part of SAE	X	X	X	X	X	The start to end range of the related form overlaps the start to end date range of the primary SAE
Duration overlaps X days on/before SAE start	X	X	X	X	X	The start to end range of the related form overlaps the following range: SAE Start - X days → SAE Start
Duration overlaps X days on/after SAE start	X	X	X	X	X	The start to end range of the related form overlaps the following range: SAE Start → SAE Start + X days
Duration overlaps any X days on/before SAE end	X	X	X	X	X	The start to end range of the related form overlaps the following range: SAE End - X days → End Start
Duration overlaps any X days on/after SAE end	X	X	X	X	X	The start to end range of the related form overlaps the following range: SAE End → SAE End + X days
Duration ends before the SAE start	X	X	X	X	X	The end date of the related form is before the SAE start
Study drug start date prior to the SAE start					X	The start date of the study drug form is before the SAE start
Closest On Before SAE Start					X	This is a special option only for Study Drug. When set, no other option can be used. This option includes one dispense of the study drug that is closest to the SAE start (on/before)

Duration Rule Examples

Here are some common examples for use of duration rules:

Section	Intent	Configuration	Include/Exclude Examples
Adverse Events	Include any other Adverse Event, serious or not, that occurred within 2 days of the start of the serious adverse event.	Select Duration overlaps X days on/before SAE Start and enter "2" for Value. Select Duration overlaps X days on/after SAE Start and enter "2" for Value. Multiple Cases: This example creates multiple cases in the safety system with the same events. Use the safety system to mark one closed as duplicate and work with the other.	If the primary SAE form's SAE Start Date and End Date is January 15th: SAE #1, start date January 14th: Included SAE #2, start date January 17th: Included SAE #3, start date January 19th: Excluded
Concomitant Medications	Include any Concomitant Medication form that is ongoing at the SAE Start or that has ended within 3 days of the SAE Start.	Select Duration overlaps X days on/before SAE Start and enter "3" for Value. Select Duration overlaps any part of SAE	If the primary SAE form's SAE Start Date is January 15th and its SAE End Date is also January 15th: CM #1, start date January 10th, no end date (ongoing): Included CM #2, start date January 17th: Excluded CM #3, start date January 5th, end date January 13th: Included

Send Multiple SAEs per Safety Case

You can configure E2BLink to send multiple SAEs in a single Safety Case. For example, if a Subject was hospitalized for a heart attack, and then they had a stroke while in the hospital, you can send the SAE data for both the heart attack and the stroke in the same Safety Case.

In Data Entry, if the AE is marked as Serious, Vault generates a Safety Case. If the E2B IDs for the Term are inside a repeating Item Group, then every instance of that repeating Item Group is treated as a unique SAE within one Safety Case.

To send multiple SAEs, ensure that your Form meets the design requirements, then set Repeating Item Groups for Events to Yes in the Serious Adverse Events section.

Study Design Requirements

To send multiple SAEs in one Safety Case, you must use a repeating Item Group for your AE Term item and the related Items. Site users can create an instance of the repeating Item Group for each SAE to be included in the Safety Case.

All Items except for those listed below must be within the repeating Item Group. The following E2B Items can reside in another, non-repeating Item Group:

• G.k.8: Action(s) Taken with Drug
• H.1: Case Narrative Including Clinical Course, Therapeutic Measures, Outcome and Additional Relevant Information
• H.2: Reporter’s Comments

E2B Mapping

Once you’ve finished the General Settings, you can configure which Forms you want to use. For each E2B element, you’ll select an Item from your study to map it to. For codelist-type Items, you can map Codelist Items (options) to text values for the E2B.

Except for Serious Adverse Event, you can create multiple Form Configurations for each type.

Translate Values for E2B XML

If you choose a codelist-type Item, you can map Codelist Items (options) to text values to send in the E2B XML file.

1. Locate the E2B Element that you want to map in the list.
2. Click in the Translate Values for E2B XML column. This opens the Translate Values for E2B XML dialog.
3. For each Codelist Item, enter an E2B XML Value in the free text field.
4. When finished, click Save.
5. Repeat this for each mapped codelist Item.

Serious Adverse Events

To map your Serious Adverse Event form for E2B:

1. Navigate to Studio > Form Configurations for your Study.
2. Click + New Form Configuration.
3. Select Serious Adverse Events for Safety Form Type.
4. Select the Form.
5. For Each Entry In, select which method to determine individual SAEs:
   • Form: Select this option to treat each instance of the Form as its own SAE
   • Repeating item group in form: Select this option to treat each instance of the repeating Item Group as its own SAE. (To allow the sending of multiple SAEs)
6. Optional: Enter a Description.
7. Select the Safety Key Item. This is typically the Item that indicates seriousness.
8. Define the Safety Key Item Value:
   • Select Specify value and enter a specific value to match on.
   • Select Any non empty value to consider any non-empty value a match.
9. Click Save and Next.
10. Select Required for First Send to require that a value be entered on that Item for CDMS to send the SAE to the safety system.
11. Click Save and Next.
12. To define Inclusion Criteria, select Yes for Include Related Adverse Event Forms in Safety Case.Otherwise, leave this set to No.
13. Select your inclusion method: * Include Related Adverse Event Forms Linked by Site Users: Select Yes to include related Adverse Events that are linked by sit4 users in the Safety Case. Otherwise, leave this set to No. * Include Related Adverse Event Forms by Date Matching: Select Yes to include related Adverse Events by date matching in the Safety Case. Otherwise, leave this set to No.
14. If you selected Yes for Include Related Adverse Event Forms by Date Matching, enter your date ranges.
15. Click Save.

If you selected Repeating item group in form for Each Entry In, you must select an Item for E.i.1.1a (Reaction / Event as Reported by the Primary Source in Native Language) E2B first. Vault will only enable the other E2Bs (except for those listed below) for item selection after you select an item for E.i.1.1a. Both E.i.1.a and the other E2Bs must be inside a repeating Item Group.

The following E2Bs remain enabled, as they do not need to be in a repeating Item Group for multiple SAEs:

• G.k.8: Action(s) Taken with Drug
• H.1: Case Narrative Including Clinical Course, Therapeutic Measures, Outcome and Additional Relevant Information
• H.2: Reporter’s Comments

However, if you don’t have E.i.1.1a mapped to an Item, Vault disables these rows.

If H.1 and H.2 are in a repeating Item Group, and there is more than one instance of that Item Group for the SAE, Vault concatenates the values for each, separating them with a space. The concatenation order is based on the item group Sequence Number, in ascending order. The character limits apply to the concatenated text, not individual items.

E2B ID	E2B Element	Data Type
E.i.1.1a	Reaction / Event as Reported by the Primary Source in Native Language	Text (250)
E.i.1.2	Reaction / Event as Reported by the Primary Source for Translation	Text (250)
E.i.3.1	Term Highlighted by the Reporter	Number (1)
E.i.3.2a	Results in Death	Boolean
E.i.3.2b	Life Threatening	Boolean
E.i.3.2c	Caused / Prolonged Hospitalization	Boolean
E.i.3.2d	Disabling / Incapacitating	Boolean
E.i.3.2e	Congenital Anomaly / Birth Defect	Boolean
E.i.3.2f	Other Medically Important Condition	Boolean
E.i.4	Date of Start of Reaction/Event (value)	Datetime
E.i.5	Date of End of Reaction/Event (value)	Datetime
E.i.6a	Duration of reaction/event (value)	Number (5)
E.i.6b	Duration of reaction/event (unit)	Text (50)
E.i.7	Outcome of Reaction/Event at the Time of Last Observation	Number (1)
E.i.9	Identification of the Country Where the Event Occurred	Text (2)
D.2.2a	Age at time of onset of reaction/event (number)	Number (5)
D.2.2b	Age at time of onset of reaction/event (unit)	Text (50)
D.3	Body Weight (kg)	Number (6)
D.4	Height (cm)	Number (3)
D.6	Last Menstrual Period Date	Datetime
G.k.8	Action(s) Taken with Drug	Number (1)
G.k.9.i.2.r.3	Result of Assessment	Text (60)
G.k.9.i.4	Did Reaction Recur on Re-administration?	Number (1)
H.1	Case Narrative Including Clinical Course, Therapeutic Measures, Outcome and Additional Relevant Information	Text (100,000)
H.2	Reporter's Comments	Text (20,000)
H.4	Sender's Comments	Text (20,000)
C.1.11.2	Reason for Nullification / Amendment	Text (2000)

Concomitant Medications

To include Concomitant Medications:

1. Navigate to Studio > Form Configurations for your Study.
2. Click + New Form Configuration.
3. Select Concomitant Medication for Safety Form Type.
4. For Each Entry In, select which method to determine individual ConMeds:
   • Form: Select this option to treat each instance of the Form as its own ConMed.
   • Repeating item group in form: Select this option to treat each instance of the repeating Item Group as its own ConMed.
5. Optional: Enter a Description.
6. Click Save and Next.
7. Select the Item for each CM Field that you include in your form. Note that the Item must have the correct data type. See the table below for a list of Items and their expected Data Type.
8. Optional: (If enabled) By Default, CDMS uses Always Interacting for G.k.1 (Study Drug Classify when ConMed Suspect) when classifying a Concomitant Medication via an Item to Form Link, in which a user chose Subject. You can choose instead to use Always Suspect.
9. Click Save and Next.
10. To include all Forms in the Safety Case, select Yes for Include All Forms in Safety Case. Otherwise, leave this set to No and define inclusion criteria.
11. Select your inclusion method:
    • Include Forms Linked by Site Users: Select Yes to include related Adverse Events that are linked by sit4 users in the Safety Case. Otherwise, leave this set to No.
    • Include Forms by Date Matching: Select Yes to include related Adverse Events by date matching in the Safety Case. Otherwise, leave this set to No.
12. If you selected Yes for Include Forms by Date Matching, enter your date ranges.
13. Click Save.

E2B ID	E2B Element	Data Type
G.k.1	Characterization of Drug Role	Number (1)
G.k.11	Additional Information on Drug (free text)	Text (2000)
G.k.2.2	Medicinal Product Name as Reported by the Primary Source	Text (250)
G.k.2.3.r.3a	Strength (number)	Number (10)
G.k.2.3.r.3b	Strength (unit)	Text (50)
G.k.2.4	Identification of the Country Where the Drug Was Obtained	Text (2)
G.k.4.r.10.1	Route of Administration (free text)	Text (60)
G.k.4.r.1a	Dose (number)	Number (8)
G.k.4.r.1b	Dose (unit)	Text (50)
G.k.4.r.2	Number of Units in the Interval	Number (4)
G.k.4.r.3	Definition of the Time Interval Unit	Text (50)
G.k.4.r.4	Date and Time of Start of Drug	Datetime
G.k.4.r.5	Date and Time of Last Administration	Datetime
G.k.4.r.7	Batch / Lot Number	Text (35)
G.k.4.9.1	Pharmaceutical Dose Form (free text)	Text (60)
G.k.7.r.1	Indication as Reported by the Primary Source	Text (250)

Characterization of Drug Role

If this Concomitant Medication is suspected to have caused the related Serious Adverse Event, this element captures the relationship between the ConMed and SAE. Map this element to the Item that indicates the drug role. This is typically a codelist-type Item. Then, you can translate the codelist to the appropriate coded values for the E2B element.

Codelist Item	Translated Value
Suspect	1
Concomitant	2
Interacting	3
Drug Not Administered	4

To use this element, your Study must have a configured Item to Form linking relationship between the appropriate Item on the Concomitant Medication form and the Serious Adverse Event form.

Medical History

To include Medical History:

To include Concomitant Medications:

1. Navigate to Studio > Form Configurations for your Study.
2. Click + New Form Configuration.
3. Select Medical History* for **Safety Form Type.
4. For Each Entry In, select which method to determine individual medical history events:
   • Form: Select this option to treat each instance of the Form as its own history
   • Repeating item group in form: Select this option to treat each instance of the repeating Item Group as its own history.
5. Optional: Enter a Description.
6. Click Save and Next.
7. Select the Item for each MH Field that you include in your form. Note that the Item must have the correct data type. See the table below for a list of Items and their expected Data Type.
8. Click Save and Next.
9. To include all Forms in the Safety Case, select Yes for Include All Forms in Safety Case. Otherwise, leave this set to No and define inclusion criteria.
10. Select your inclusion method:
    • Include Forms Linked by Site Users: Select Yes to include related Adverse Events that are linked by site users in the Safety Case. Otherwise, leave this set to No.
    • Include Forms by Date Matching: Select Yes to include related Adverse Events by date matching in the Safety Case. Otherwise, leave this set to No.
11. If you selected Yes for Include Forms by Date Matching, enter your date ranges.
12. Click Save.

E2B ID	E2B Element	Data Type
D.7.1.r.1a / D.7.1.r.1b	Medical History MedDRA Coding and Version	(Coding / Version)
D.7.1.r.2	Start Date	Datetime
D.7.1.r.3	Continuing	Boolean
D.7.1.r.4	End Date (value)	Datetime
D.7.1.r.5	Comments	Text (2000)
D.7.1.r.6	Family History	Boolean
D.7.2	Text for Relevant Medical History and Concurrent Conditions (not including reaction / event)	Text (10,000)

Patient Characteristics

To include Patient Characteristics:

1. Navigate to Studio > Form Configurations for your Study.
2. Click + New Form Configuration.
3. Select Patient Characteristics for Safety Form Type.
4. Optional: Enter a Description.
5. Click Save and Next.
6. Select the Item for each CM Field that you include in your form. Note that the Item must have the correct data type. See the table below for a list of Items and their expected Data Type.
7. Click Save and Next.
8. For Patient Characteristics, Include All Forms in Safety Case is automatically enabled.
9. Click Save.

E2B ID	E2B Element	Data Type
D.2.1	Date of Birth (value)	Datetime
D.2.2a	Age at time of onset of reaction/event (number)	Number (5)
D.2.2b	Age at time of onset of reaction/event (unit)	Text (50)
D.5	Sex	Number (1)

In Case of Death

To include data from an In Case of Death form:

1. Navigate to Studio > Form Configurations for your Study.
2. Click + New Form Configuration.
3. Select In Case of Death for Safety Form Type.
4. Optional: Enter a Description.
5. Click Save and Next.
6. Select the Item for each Field that you include in your form. Note that the Item must have the correct data type. See the table below for a list of Items and their expected Data Type.
7. Click Save and Next.
8. For In Case of Death, Include All Forms in Safety Case is automatically enabled.
9. Click Save.

E2B ID	E2B Element	Data Type
D.9.1	Date of Death	Datetime
D.9.2.r.2	Reported Cause(s) of Death	Text (250)
D.9.3	Was Autopsy Done?	Boolean
D.9.4.r.2	Autopsy-determined Cause(s) of Death	Text (250)

External Labs

To include data from External Labs:

1. Click Edit if you aren’t already in Edit mode.
2. Click External Labs to expand that section.
3. For Include External Labs, select Yes.
4. Select the External Labs Form.
5. Select the Item for each field that you include in your form. Note that the Item must have the correct data type. See the table below for a list of Items and their expected Data Type.
6. Click Save.

E2B ID	E2B Element	Data Type
F.r.1	Test Date	Datetime
F.r.2.1	Test Name	Text (250)
F.r.3.1	Test Result (code)	Number (1)
F.r.3.2	Test Result (value / qualifier)	Number (50)
F.r.3.3	Test Result (unit)	Text (50)
F.r.3.4	Result Unstructured Data (free text)	Text (2000)
F.r.4	Normal Low Value	Text (50)
F.r.5	Normal High Value	Text (50)
F.r.6	Comments (free text)	Text (2000)
F.r.7	More Information Available	Boolean

Study Drug

To include data from a Study Drug form (formerly labeled Treatment):

1. Navigate to Studio > Form Configurations for your Study.
2. Click + New Form Configuration.
3. Select Study Drug for Safety Form Type.
4. For Each Entry In, select which method to determine individual study drugs:
   • Form: Select this option to treat each instance of the Form as its own study drug.
   • Repeating item group in form: Select this option to treat each instance of the repeating Item Group as its own study drug.
5. Enter the Study Drug Name.
6. Select Yes or No for Blinding.
7. Optional: Enter a Description.
8. Select the Safety Key Item. This is typically the Item indicating that the dispense was performed.
9. Define the Safety Key Item Value:
   • Select Specify value and enter a specific value to match on.
   • Select Any non empty value to consider any non-empty value a match.
10. Click Save and Next.
11. Select the Item for each Field that you include in your form. Note that the Item must have the correct data type. See the table below for a list of Items and their expected Data Type.
12. Click Save and Next. 13.. To include all Forms in the Safety Case, select Yes for Include All Forms in Safety Case. Otherwise, leave this set to No and define inclusion criteria.
13. Select your inclusion method:
    • All: Include all Forms in the Safety Case.
    • Closest dispense on/before SAE start
    • Advanced date matching
14. If you selected Advanced date matching, enter your date ranges.
15. Click Save.

E2B ID	E2B Element	Data Type
G.k.10.r	Additional Information on Drug (coded) (repeat as necessary)	Number (2)
G.k.11	Additional Information on Drug (free text)	Text (2000)
G.k.2.3.r.3a	Strength (number)	Number (10)
G.k.2.3.r.3b	Strength (unit)	Text (50)
G.k.2.4	Identification of the Country Where the Drug Was Obtained	Text (2)
G.k.4.r.10.1	Route of Administration (free text)	Text (60)
G.k.4.r.10.2a	Route of Administration TermID Version Date / Number	As per ISO DMP
G.k.4.r.10.2b	Route of Administration TermID	Number (3)
G.k.4.r.1a	Dose (number)	Number (8)
G.k.4.r.1b	Dose (unit)	Text (50)
G.k.4.r.2	Number of Units in the Interval	Number (4)
G.k.4.r.3	Definition of the Time Interval Unit	Text (50)
G.k.4.r.4	Date and Time of Start of Drug	Datetime
G.k.4.r.5	Date and Time of Last Administration	Datetime
G.k.4.r.6a	Duration of Drug Administration (number)	Number (5)
G.k.4.r.6b	Duration of Drug Administration (unit)	Text (50)
G.k.4.r.7	Batch / Lot Number	Text (35)
G.k.4.r.8	Dosage Text	Text (2000)
G.k.4.r.9.1	Pharmaceutical Dose Form (free text)	Text (60)
G.k.4.r.9.2a	Pharmaceutical Dose Form TermID Version Date / Number	As per ISO IDMP
G.k.4.r.9.2b	Pharmaceutical Dose Form TermID	As per ISO DMP
G.k.5a	Cumulative Dose to First Reaction (number)	Number (10)
G.k.5b	Cumulative Dose to First Reaction (unit)	Text (50)
G.k.6a	Gestation Period at Time of Exposure (number)	Number (3)
G.k.6b	Gestation Period at TIme of Exposure (unit)	Text (50)
G.k.7.r.1	Indication as Reported by the Primary Source	Text (250)
G.k.8	Action(s) Taken with Drug	Number (1)
G.k.9.i.2.r.3	Result of Assessment	Text (60)
G.k.9.i.3.1a	Time Interval between Beginning of Drug Administration and Start of Reaction / Event (number)	Number (5)
G.k.9.i.3.1b	Time Interval between Beginning of Drug Administration and Start of Reaction / Event (unit)	Text (50)
G.k.9.i.3.2a	Time Interval between Last Dose of Drug and Start of Reaction / Event (number)	Number (5)
G.k.9.i.3.2b	Time Interval between Last Dose of Drug and Start of Reaction / Event (unit)	Text (50)
G.k.9.i.4	Did Reaction Recur on Re-administration?	Number (1)

Drug History

To include data from a Drug History form:

1. Navigate to Studio > Form Configurations for your Study.
2. Click + New Form Configuration.
3. Select Drug History for Safety Form Type.
4. For Each Entry In, select which method to determine individual drug histories:
   • Form: Select this option to treat each instance of the Form as its own drug history.
   • Repeating item group in form: Select this option to treat each instance of the repeating Item Group as its own drug history.
5. Optional: Enter a Description.
6. Click Save and Next.
7. Select the Item for each Field that you include in your form. Note that the Item must have the correct data type. See the table below for a list of Items and their expected Data Type.
8. Click Save and Next. 9 To include all Forms in the Safety Case, select Yes for Include All Forms in Safety Case. Otherwise, leave this set to No and define inclusion criteria.
9. Select your inclusion method:
   • All: Include all Forms in the Safety Case.
   • Closest dispense on/before SAE start
   • Advanced date matching
10. If you selected Advanced date matching, enter your date ranges.
11. Click Save.

E2B ID	E2B Element	Data Type
D.8.r.1	Name of Drug as Reported	Text (250)
D.8.r.2	Start Date	Datetime
D.8.r.5	End Date	Datetime
D.8.r.6a/D.8.r.6b	MedDRA Coding and Version (Indication)	(Coding / Version)
D.8.r.7a/D.8.r.7b	MedDRA Coding and Version (Reaction)	(Coding / Version)

Remove Form Configurations

You can remove a single Form Configuration or remove all Form Configurations at once to start over. If you have Safety Cases associated with a Form Configuration, Vault disables the delete option.

To remove a single Form Configuration:

1. Navigate to Studio > Form Configurations for your Study.
2. Hover over the Form Configuration Name to show the Actions menu**.
3. Select Delete.
4. In the confirmation dialog, click Delete.

To remove all Form Configurations:

1. Navigate to Studio > Safety Settings for your Study.
2. From the Actions menu, select Delete All Safety Configurations.
3. In the confirmation dialog, click Delete.

Download Specifications

You can download your safety configuration via the All CRFs PDF export.

Deploying your Safety Configuration

Once you finish your configuration in your study’s DEV environment, you can deploy it to TST for testing, then onward into your training and production environments.

Your E2B Link configuration is automatically included in your study’s deployment package. When you deploy your study, Vault includes the current configuration in the package.

Because this configuration is managed as part of study deployments, you can only make changes in DEV type environment. To make changes, make them in the DEV environment and then deploy those changes to your other environments. This configuration is validated as part of casebook version publication. While validation is in progress, editing is disabled. A list of possible errors and warnings is available here.

Learn how to deploy a study.