Review and update Case data.
Note: Depending on your Admin’s configuration, object, field, and section labels, lifecycle states, and workflows may differ from the general information on this page. Refer to your organization’s business processes for guidance.
Case Data Entry Considerations
After running the Promote to Case action, all data entered on the source Inbox Item copies to the appropriate fields on the Case and child records. Consider the following when processing Cases:
- If your Admin has configured your Vault to isolate blinded Product information on Clinical Trial Study Cases, see Isolate Blinded Clinical Trial Information for additional considerations during Case processing.
- Cases involving pregnancy, parents, and children include additional sections and fields. For more information, see Process Pregnancy, Child Information, and Parent Information Cases.
- When processing Cases that may be reportable to the PMDA, see Complete Intake and Process Cases for the PMDA for regionally specific features in Vault.
- When entering data, picklist field values are accent-sensitive. Entering a value with an accent prioritizes results with accents.
Within many sections of a Case record, you can select Create to manually add related records. For information on specific Case fields, including in sections not described on this page, see Case Field Reference.
Prerequisites
Some capabilities described on this page require Admin configuration, including:
- For the Device Details section to appear for Cases with Combination Products, see Enable the Combination Products.
- To enter Remedial Actions and Malfunction data at the Case Product Device level, see Enable Remedial Actions and Malfunction for Combination Products.
- To manually lock Cases to prevent changes, see Enable Manual Case Locking: User Check In and Check Out.
- For Vault to consider Case Products with a Drug Role of Drug Not Administered as suspect, see Enable Extend Definition of Suspect to Drug Not Administered.
- To code device-specific adverse events using the International Medical Device Regulators Forum (IMDRF) dictionary, see Enable the IMDRF Dictionary for Maintenance, Case Processing, and Submissions.
- For clearer study product blinding labels, see Enable Product Masking Selection for Study Products.
- To capture substance data for EMA E2B(R3) section D.8.r.EU, update the Case Drug History Substance layout.
Device Details Section
For the Device Details section to appear, the Case must have a Case Product that is a Combination Product. Use this section to specify the report type and add details about device-type Case Products.
When you enter Remedial Actions and Malfunction at the Case Product Device level, Vault syncs device-specific information to this section at the Case level. This is useful for Cases that involve multiple Combination Products or Combination Products with multiple device constituents.
This Case is Locked Section
The This Case is Locked section appears when a user manually locks a Case. When a Case is locked, Vault prevents other users from saving changes to the Case and child records until you unlock the Case. All Case child records (such as Case Assessment and Case Product) are locked, with the exception of Parental Case and Case Number records. This section provides details on the date the case was locked and the user who locked it.
Contacts Section
When you promote an Inbox Item to a Case, Vault copies the reporter and patient information to create Case Contacts.
Types of Case Contacts
The following list describes the types of Case Contacts:
- Reporter: Captures information about the person who reported the Case. A Reporter type of contact is created for patients or health care professionals who are also the reporter.
- Patient: Captures information about the patient.
- Health Care Professional: Captures information about the health care professional who treated the patient for the adverse event that resulted in hospitalization or treatment.
- Base Case Contact: Captures information about contacts who are not reporters, patients, or health care professionals who have information relevant to the adverse event.
- Facility: Captures information about the facility where a vaccine dosage was administered. A Case Product Dosage can then reference a Facility record using the Administration Facility field.
- From Inbox Item promotion, the Facility type of Case Contacts are created only through the Intake Vault API from JSON files.
When imported Inbox Items include sender information, Vault adds those details to the Inbound Transmission.
How Vault Creates and Updates Case Contacts
On each new Case, Vault creates a Reporter type of Case Contact, using data from the Inbox Item contact information. Vault also copies patient information to the Reporter type of contact when the patient is also the reporter. If the patient was not the reporter, Vault creates a separate Patient type of Case Contact. Vault determines whether the patient is also the reporter using the Patient value specified in the Reporter Qualification field on the Inbox Item.
Note: Each Case must have a primary Reporter type of Case Contact. As such, you cannot delete a primary Reporter record. If a primary Reporter must be deleted, you can designate a different Reporter as primary using the Rank field, and then delete the non-primary Reporter.
When the Patient is the Reporter
Note: If the Qualification controlled vocabulary record corresponding to Patient is inactive, contact your Admin to make this Qualification option available.
If the Reporter Qualification is Patient, Vault:
- Considers the patient the primary reporter.
- Does not create a Patient type of Case Contact.
- Populates the patient information fields on the primary Reporter Case Contact.
- Updates the corresponding fields on the primary Reporter Case Contact any time the Patient name fields are updated on the Case.
When the Patient is Not the Reporter
If the Reporter Qualification is not Patient, Vault:
- Creates a Patient type of Case Contact record in addition to the Reporter Case Contact.
- Populates the patient information fields on the Patient Case Contact
- Updates the corresponding fields on the Patient Contact any time the Patient name fields are updated on the Case. You can have only one Patient Contact per Case.
If the Inbox Item did not specify these fields and they are later added to the Case directly, Vault copies the patient name fields from the Inbox Item to create a new Patient Contact.
Pregnancy Information Section
For pregnancy cases, enter information about the pregnancy and outcome in the Pregnancy Information section. For guidance on adding pregnancy Cases, see Process Pregnancy, Child Information, and Parent Information Cases.
Child Information Section
Use the Child Information section to capture details about an infant born from a tracked pregnancy case when there was no adverse event in the infant. The Pregnancy checkbox must be selected to make this section appear on the layout. For guidance on adding different birth outcomes associated with pregnancy cases, see Process Pregnancy, Child Information, and Parent Information Cases.
Products Section
Use the Products section to enter information about suspect and concomitant medications, including products suspected to have an interaction. For Cases under a Study, this section label appears as Products (Study). When you promote an Inbox Item to a Case, Vault copies the product information to create the primary Case Product record using the appropriate product type:
- Company Product (Drug, Biologic, Device, Vaccine, or Company Product): If a Product from the company library was selected on the source Inbox Item, then Vault creates the Case Product of that type.
- Study Product: If the Inbox Item specified a Study, then Vault copies the Study Products to the Case.
- External Product: If the Inbox Item does not link to a preconfigured Product, Vault adds the product details as an External Product.
- Combination Product: If a Combination Product was selected on the Inbox Item, its constituents are automatically downloaded and added as separate Case Products when the Case is promoted. Each constituent Product inherits the Combination Product Drug Role.
Note: If the Inbox Item was promoted with a constituent product in error, you can edit the Combination Product field of the Product. The related constituent products are automatically downloaded and added as separate Case Products.
When you add a Product that is configured in the Product Library, Vault populates the Product details on the Case. For information on coding products based on the reported Product, see Auto-Code and Browse Products.
About Company Products
The Company Product type of Company Product is used when a product has multiple Product Type registrations to meet agency reporting requirements. When Company Product is selected, the Transmission Product Type on the Registered As field from the Product Registration is copied to the Product Globally Registered As field. Available Transmission Product Types include the following:
- Drug
- Biologic
- Device
- Vaccine
- Nutritional
- Cosmetic
- OTC Drug
- OTC Device
- Combination Product
Note: Your Vault may not be configured to display the Globally Registered As field, which is intended for Admin use only.
When you create a Company Product record, the sections and fields included are based on the Product Types in the associated Product Registrations. For example, the Device Information section appears only when the Company Product is registered as a device in at least one jurisdiction.
Delete a Case Product
When you delete individual Case Products, Vault also deletes the following related records:
- Case Product Dosage
- Case Product Indication
- Case Product Device Code
- Case Product Similar Incident
- Case Product Substance
- Case Assessment
- Case Assessment Result
- Case Assessment Expectedness
- Signal Individual Case Review (applies only to Safety Signal)
Each Case must have a primary Case Product. As such, you cannot delete a primary Case Product. If you have to delete a primary Case Product, you can designate a different Case Product as primary using the Rank field, and then delete the non-primary Case Product.
If configured by your Admin, when you delete a Case Product on a Case with a Localized Case, Vault deletes the related Localized Case Product and its related records. For Japan Localized Cases, Vault follows the same process as when deleting Case Product Registrations and the related records.
Note: You cannot delete Case Products and their related records using bulk delete or Vault Loader. You must delete Case Products individually.
Dosages Section
Use the Dosages section to add, edit, or delete dosage and route of administration regimens for a Case Product. By default, this section does not display for Device type of Case Products or Study Products associated with a double-blinded Study. When there are no Dosage records, the Case Product Dosage section appears blank. To create a Dosage, select Edit on the Case Product page.
To create additional dosages for a Case Product, select the Add Dosages button. After saving the page, Vault displays dosages in order of the earliest to latest First Admin Date. You can also copy a Dosage record and any inputted data by selecting the Copy () icon. To mark a Dosage record for deletion, select the Delete (
) icon.
Note: After adding 10 dosage entries, Vault disables the Add Dosages and Copy buttons. You must save the page if you want to add more Dosage records. When there are 11 or more dosages, use the left and right arrows to move through the pages.
Case Product Similar Incident Section
When generating reports in the EU MIR format, the Case Product Similar Incident section captures information about similar incidents based on region and time period. Depending on your Admin’s configuration, Case Product Similar Incident records may be generated automatically or manually. To generate them manually, from the All Actions menu, select Generate Similar Incident Records.
If no other Case Product Similar Incident records exist, after running the action, Vault generates twelve records, one for each region and time period pair. After record generation, you can enter the market and similar incident data on each record.
Device Problem and Evaluation Codes Section
The Device Problem and Evaluation Codes section captures FDA device codes for a Device type of combination product constituent. By default, this section displays only for External Products and Device types of Products.
Note: If your Vault is configured for IMDRF coding, the Case Product Device Code section has replaced the Device Problem and Evaluation Codes section.
Blinding Details Section
The Blinding Details section describes the blinding settings active on a Case Product. This section is informational and read-only. By default, this section appears only if the Study associated with the Case is double-blinded. Manage Case Blinding provides information about unblinding Cases.
Registration Section
Use the Registration section to add license and registration details for a Case Product. By default, this section does not appear for blinded Study Products.
If the registration details are already configured in the Product library and you select that Product Registration in the Case Product Details section, Vault automatically populates data in the Registration section.
The following related sections are available only for processing Cases that may be reportable to the PMDA:
- Case Product Registrations
- Local Reporting Details
- PMDA Reportable Products
- Case Comments
For information on these sections, see Complete Intake and Process Cases for the PMDA.
Substances Section
Use the Substances section to add Substances under a Case Product. Substance records specify the active substance and strength in the product. By default, this section appears only for External Products and open or single-blinded Study Products.
Adverse Events Section
Use the Adverse Events section to add Case Adverse Events with details of each adverse event. For Cases with SAEs transferred from the Safety-EDC Connection, you can run the Add Relevant Subject Information action to add the applicable subject information to the Case.
Delete a Case Adverse Event
When you delete individual Case Adverse Events, Vault also deletes the following related records:
- Case Assessment
- Case Assessment Result
- Case Assessment Expectedness
Each Case must have a primary Case Adverse Event. As such, you cannot delete a primary Case Adverse Event. If you must delete a primary Case Adverse Event, you can designate a different Case Adverse Event as primary using the Rank field, and then delete the non-primary Case Adverse Event.
If configured by your Admin, when you delete a Case Adverse Event on a Case with a Localized Case, Vault deletes the related Localized Case Adverse Event and its related records.
Note: You cannot delete Case Adverse Events and their related records using bulk delete or Vault Loader. You must delete Case Adverse Events individually.
Diagnoses Section
Use the Diagnoses section to combine signs and symptoms that were reported into a single Case Diagnosis, if required.
By default, the Diagnoses section does not appear until the Case is in the Medical Review state.
Medical Assessments Section
The Medical Assessments section provides a centralized view of all assessment data for a Case. Use this section to review and update:
- Case Assessment fields: Display the assessed relationship between Case Adverse Events and Case Products with an eligible Drug Role.
- Case Assessment Result fields: Support entering the assessed relationship between the adverse event and product pair from individual sources.
- You can enter additional comments about the assessment in the Company Comments field in the Narrative section.
- Case Assessment Expectedness fields: Display the evaluated expectedness of Case Adverse Events.
Note: If an E2B-imported case contains an assessment for an adverse event or suspect product with an unknown link, Vault labels the assessment with UNK
.
For more information on Case Assessments, Case Assessment Results, and Case Assessment Expectedness, see Generate Assessments.
Causes of Death Section
Use the Causes of Death section to enter the details about the reported and autopsy-determined causes of death. The Causes of Death section appears if at least one of the following conditions are met:
- The Date of Death field has a value
- A Seriousness field value on a Case Adverse Event for the Case contains Results in Death
Study Section
When the Report Type of the Case is Study, the Study section appears on the layout for entering information about the Study the patient is enrolled in. If a Study was selected on the initial Inbox Item, the Study section fields are automatically populated with any available Study data configured in Business Admin.
Note: You cannot change a Study Arm on a Case once it has been promoted from an Inbox Item.
Study Registrations Section
When the Report Type of the Case is Study, the Study Registrations section appears on the layout for entering registration information about the Study the patient is enrolled in. When you select a Study in the Study section and save the page, Vault adds each registration configured under the associated Study in Business Admin.
Vault may update or populate Case Study Registration data in the following scenarios:
- When you create a follow-up Case from a Case or non-E2B-imported Inbox Item, Vault populates the Study Registrations section on the follow-up Case with the latest registration data from the Study library.
- When you merge an E2B-imported Inbox Item to an in-flight Case or promote it to a follow-up Case, Vault maps the Inbox Item’s Study registration data to the Study Registrations section on the in-flight Case.
- After automated Case promotion for Inbox Items imported from E2B or JSON, Vault populates the Study Registrations section on the follow-up Case with the Inbox Item Study registration data.
Documents Section
Use the Documents section to add and manage documents linked to the Case, including the source report, narrative, attachments, literature, and other relevant documents.
E2B Transmission Document Setup
To be included in E2B transmissions, Case documents must:
- Be classified with the Case › Source › Attachment or Case › Source › Literature document type.
- Include Yes in the Retransmit field.
When sending FDA E2B(R2) or FDA E2B(R3) transmissions through an AS2 Connection for Cases with over-the-counter (OTC) drugs, you can also attach OTC carton images. To include images, files must:
- Be classified with the Case › Source › Attachment document type.
- Include FDA Carton Attachment in the Attachment Type field.
Add a Case Attachment or Literature Document
When adding a Case Attachment or Literature Document, classify the document type with either of the following options, as appropriate:
- Case › Source › Attachment
- Case › Source › Literature
During E2B generation, included documents map to the:
- C.1.6 and C.4.r sections of E2B(R3) files.
- A.1.8.1-2 and A.2.2 sections of E2B(R2) files.