A maintenance release contains fixes for issues affecting customer Vaults in production environments. Maintenance releases can occasionally include enhancements, for example, a time-sensitive regulatory requirement. This page covers maintenance releases deployed to General Release Vaults only. We communicate 24 hours prior to a maintenance release. There may be a short service disruption during deployment.
This list only covers fixes for issues that impact 23R3 General Release versions of Safety Vaults. The list of fixed issues is subject to change until the release occurs. When we identify issues to fix in a maintenance release, we attempt to get them into the earliest release possible. Sometimes, we target a specific release but are not able to deliver a fix early enough for full testing. In situations like this, we postpone the fix for a later release and strike out the description in this list.
We number maintenance releases for Safety by appending the number of the Safety-specific maintenance release to the General Release number. The most recent Vault General Release is 23R3.0, so our maintenance releases for this version are 23R3.0.1, 23R3.0.2, and so on.
Vault frequently delivers Platform maintenance releases. Safety deploys these Platform maintenance releases at a later date, along with any required fixes to Safety. For details on Platform fixes in these maintenance releases, see 23R3 Maintenance Releases.
Last Updated: February 28, 2024
February 27, 2024
Release Number: 23R3.0.12 | Build Number: 300
|When creating Domestic Follow-up Cases for localizations other than Japan, if the number of Products on an Inbox Item and matched Case differ, an unequal number of global and localized Case Assessments and Case Assessment Results is generated.
|For Cases with a localization of Japan, a system error occurs when Inbox Items with new Products or Adverse Events are merged to In-flight Cases or promoted to Follow-up Cases.
|During import of custom E2B formats using SDK, some Parent Information is not imported.
|After Gateway or manual E2B import, Case Access Groups are not populated on Inbound Transmissions.
February 20, 2024
Release Number: 23R3.0.11 | Build Number: 296
Vault Safety now supports exporting International Medical Device Regulators Forum (IMDRF) device codes to section H6 - Event Problem and Evaluation Codes of FDA MedWatch 3500A forms. When Admins enable the IMDRF Dictionary feature, the system now exports codes from Annex E: Health Effects - Clinical signs and Symptoms or Conditions, Annex F: Health Effects - Health Impact to the Patient Code fields, and Annex G: Medical Device Component to the Device Code fields. This improves data quality and compliance when reporting to the FDA.
|When Strict Case Locking is enabled on a Case, users cannot create a Child Information Case from it even if the Case is locked to them.
|E2B import fails if the file includes a data element with more than 1,500 characters and the Case is Localized.
For Device-related Cases, the Device Report Type field now includes a Product Problem value, which is mapped to the B.1 - Product Problem field of FDA MedWatch 3500A forms.
|When E2B(R3) ACKs are generated on the Inbound Transmission record, Vault maps the ACK.B.r.3 ICSR Message ACK Receiver data element to the Destination ID field and the ACK.B.r.4 ICSR Message ACK Sender data element to the Origin ID field, instead of the reverse.
|When generating FDA MedWatch 3500A forms, Vault maps Company Product type products registered as a device in the country of its destination to section C. Suspect Products, instead of D. Suspect Medical Device and H. Device Manufacturers Only.
February 8, 2024
Release Number: 23R3.0.10 | Build Number: 287
|When Inbox Items with blinded Products are merged to In-flight Cases or promoted to Follow-up Cases through the Case Compare page, if the matched Case is unblinded, the Case-level Product field is set to the primary Case Product.
February 6, 2024
Release Number: 23R3.0.9 | Build Number: 283
|On newly created Vaults, MedDRA dictionary version 26.0 is not available.
|When coding MedDRA Conditions on Datasheets, Lowest Level Terms (LLTs) are now the only MedDRA level available. Previously, the system supported coding this field at any level of the MedDRA hierarchy, although the system matches MedDRA terms for Product Indications on Cases at the LLT level only.
|When an Inbox Item Products section includes unsaved changes, if Study Products are added through the Specify Study Product dialog, the unsaved changes are cleared.
|When the Localization value is defined, the Comments field on Case Medical History records and the Comments and Result (Text) fields on Case Test Result records are cleared upon saving.
|When importing custom E2B file formats, the G.k.4.r.10.1 Route of Administration (free text) data element is not mapped to the Patient RoA Text field on the Case Product Dosage.
|On the Case Compare page, in some instances, attempting to select a matching Case Product manually causes an error message to appear.
|When importing E2B file formats without an Inbound Format value, the G.k.4.r.10.1 Route of Administration (free text) data element is not imported to Inbox Items.
|When sending an ACK2 message from an AS2 Connection, the system sends the original E2B back to the destination.
January 30, 2024
Release Number: 23R3.0.8 | Build Number: 263
|When creating Product-Event Combinations, coding MedDRA terms at any level of the MedDRA hierarchy is not supported.
|When exporting custom E2B formats, the system runs Case-level validations for the custom format but not for the standard format that is the basis for the custom format.
|Combination Product device constituents are exported to CIOMS I forms.
|During E2B import, custom E2B tags mapped using SDK are not imported to the Case Assessment Result object.
January 23, 2024
Release Number: 23R3.0.7 | Build Number: 259
|On Follow-up Cases created from Inbox Items, Case Relatedness field values are missing.
|When Follow-up Cases that are reportable to the PMDA do not have Localized Case Assessments, the system prevents Case voiding.
|When creating a Follow-up Study Case with no change to Relatedness from the initial Case, in some instances the Case Tag is incorrectly updated.
|When Localization is added to a Case that was initially promoted as Global, the system prevents Follow-up Case creation from a Localized Inbox Item.
January 16, 2024
Release Number: 23R3.0.6 | Build Number: 255
|When generated from a Child Rule Set, Safety Rule Set Configuration reports do not include Rule Set Parameters for inherited Child Rules.
Devices can now be exported to sections D and H of FDA MedWatch 3500A forms regardless of Product Registration destination.
When the Retrieve Reportable Case Product Registrations action is run on a Localized Case and reportable Case Product Registrations are retrieved, if a marketing Case Product Registration is created for general reporting the system does not create another Case Product Registration for cross reporting.
The Date of Death field on Inbox Items now includes the following Reasons Omitted values: "Not Asked" and "Asked but Unknown". Previously, the only available Reason Omitted for this field was "Masked".
January 9, 2024
Release Number: 23R3.0.5 | Build Number: 238
|When sending Submissions to the Chinese Health Authority (NMPA CDE) through AS2 Connections, expected Acknowledgements (ACKs) are not received.
|After importing an E2B(R3) file, the system-generated CSV rendition is missing information in the Assessment Results section.
|In some instances, system performance is slower than expected when generating CSV renditions of imported E2B files, blocking subsequent E2B intake.
|When importing Cases through Safety Inbox Loader, the Action Taken field on Case Products is not populated.
|When the JDrug field is added to External Product page layouts, External Products cannot be viewed or created on Domestic Cases for Japan.
|For Vaults without PT Aggregation enabled, when generating a PBRER, the Summary Tabulation of Adverse Drug Reactions from Postmarketing Sources counts the same Adverse Event multiple times, once for each Product on a Case, instead of counting each Adverse Event only once.
|When an Inbox Item has more than 500 Assessments, the system prevents merge to In-flight Case and promote to Follow-up Case.
December 22, 2023
Release Number: 23R3.0.4 | Build Number: 223
This release includes only Platform fixes.
December 21, 2023
Release Number: 23R3.0.3 | Build Number: 221
This release includes only Platform fixes.
December 18, 2023
Release Number: 23R3.0.2 | Build Number: 220
|In some instances, merging Inbox Items to In-flight Cases is prevented and this error message appears: "Case creation is already in progress. Please wait for it to complete."
|The C.1.9.1 Other Case Identifiers in Previous Transmissions data element is populated as True when there are no E2B-transmittable Case Identifier objects associated with the Case, resulting in Negative Acknowledgement (NACK) messages.