Vault uses strict Case locking to prevent users from editing a Case and certain related records unless they are specified in the Locked By field on the Case. This capability enforces restrictions on Case editing permissions for organizations requiring heightened security. For more information, see Lock and Unlock a Case.

Prerequisites

To use this feature, you must enable Manual Case Locking and define Case Locking security settings.

Objects Affected by Strict Case Locking

Strict Case locking protects the following objects:

  • Case (case_version__v)
    • Applies to the Case (case__v) and Parent Information (parental_case__v) object types
  • Case Adverse Event (case_adverse_event__v)
  • Case Assessment (case_assessment__v)
  • Case Assessment Expectedness (case_assessment_expectedness__v)
  • Case Assessment Result (case_assessment_result__v)
  • Case Cause of Death (case_cause_of_death__v)
  • Case Contact (case_contact__v)
  • Case Drug History (case_drug_history__v)
  • Case Diagnosis (case_diagnosis__v)
  • Case Identifier (case_identifier__v)
  • Case Medical History (case_medical_history__v)
  • Case Product (case_product__v)
  • Case Product Dosage (case_product_dosage__v)
  • Case Product Indication (case_product_indication__v)
  • Case Product Substance (case_product_substance__v)
  • Case Relationship (case_relationship__v)
  • Case Study Registration (case_study_registration__v)
  • Case Test Result (case_test_result__v)

Actions Affected by Strict Case Locking

Strict Case locking protects the following actions:

  • Generate CIOMS I
  • Generate E2B (R3)
  • Generate FDA3500A
  • Re-generate Domestic Case
  • Re-render Case Narrative
  • Void Case

User Actions That Lock Cases

Vault prevents conflicting Case edits in the following user-initiated scenarios by locking the Case to the initiating user and setting the Locked By value to System:

When the action completes, Vault unlocks the Case and clears the Locked By value.