Generate case narratives based on Admin-defined templates and edit them on your local machine or directly in your browser with Microsoft 365. Vault may automatically generate narratives when you create a Case or move a Case to a specific lifecycle state. If configured by your Admin, you may also be able to manually generate and update a narrative. You can review all versions of the narrative document and, if applicable, edit the document in your Library. In Vaults using Veeva AI for Safety, you can use the Narrative Agent to proofread and rewrite the narrative content.
Depending on your Admin’s configuration, Vault may generate narrative documents in the following ways:
Prerequisites
Depending on your business needs, your Admin may need to complete the following:
About Narrative Generation
The content included in generated narrative documents depends on your Admin’s configuration. Upon generation, Vault populates certain fields on the Case and document. You can access the generated DOCX narrative file in your Library and directly from the Narrative section of the Case or Localized Case.
Whenever you bulk unblind all Cases in a Study, Vault generates two minor document versions. The first copies the previous Case’s narrative. The second appends the Narrative Text value to the end of the document.
Case Fields
Upon narrative generation, Vault populates fields in the Narrative section of the Case. Vault populates the Narrative Preview field on the Case with a plain text preview of the narrative document. This preview shows how the narrative will be exported in generated regulatory reports, such as CIOMS I, FDA 3500A, and E2B. This field can contain up to 32,000 characters. If the content includes a table, Vault replaces the table dividers with commas in the preview. If your Admin has configured blind protection on narrative documents, does not display any sensitive information.
Note: Vault does not generate a value for the Narrative Preview field if the narrative document contains invalid characters that do not render. If applicable, we recommend updating or removing invalid characters in your narrative document so Vault populates this field.
Document Fields
Upon narrative generation, Vault populates the following fields on the generated document, which you can review in the the Case section of the Document Information panel on the Doc Info pane:
- Narrative Content Source: This field specifies the content source. Vault updates this field with every version check-in:
- Imported from Source: Content copied from the source by importing or promoting an Inbox Item or creating a follow-up Case.
- Rules Based Narrative: Content generated by running the Generate Narrative from Outline action on a Case.
- Narrative Agent: Content generated by Veeva AI by running the Generate Text with Narrative Agent action on a narrative document.
- Blank: Content generated from a narrative template or manually added by a Vault user from uploading or checking in a new document version.
- Case Access Group: If your Admin has configured Case Access Group Security, Vault populates this field based on the corresponding value of the associated Case. You cannot modify this field value.
- Blind Protection: If your Admin has configured blind protection on narrative documents, Vault populates this field with On and unauthorized users cannot view the narrative. When Vault generates a narrative for a follow-up Case, the new narrative document inherits the Blind Protection value from the narrative of the previous Case version unless the follow-up Case was unblinded during processing. In this scenario, Vault always sets the Blind Protection field to On. You can adjust blind protection for the narrative by updating this field value.
Rules Based Narratives
When you run the Generate Narrative from Outline action on a Case, Vault generates a narrative based on Admin-defined outlines that include specific elements of a Case. These narratives are grammatically correct, logical, orderly, and complete, while requiring minimal editing. Your Admin can configure outline templates for different types of Cases and optionally for different locations and organizations. Depending on your Admin’s configuration, this action may run automatically when you create a Case or move a Case to a specific lifecycle state. If configured, you can manually run this action by selecting it from the All Actions menu of a Case. In Vaults using Veeva AI for Safety, the Narrative Agent may run automatically, or you can run it manually, depending on your Admin’s configuration.
When the Generate Narrative from Outline action runs, Vault generates a narrative document. Whenever you run the action on a Case that already has an associated narrative document, Vault re-renders and upversions the existing narrative document based on the applicable outline template. You can review any changes to follow-up statements on the Case Version Compare page. The upversioned narrative includes a summary of any changes to the Case between major versions, including updates to the following:
- Patient details
- Added studies
- Adverse events and changes to seriousness
- Suspect product details
- Assessment results
- Drug histories
- Treatment drugs
- Medical histories
- Narrative text for unblinded studies
In Vaults configured to isolate blinded clinical trial information, follow-up statements for Case Products and Case Assessment Results on the summary of changes do not include Case Products with Unblinded as the Blinding Type.
Note: Vault does not include a summary of changes in narrative documents for Cases generated using the override merge method for automated Case promotion.
The following behavior applies to generating rules based narratives:
- For Cases promoted from imported Inbox Items with E2B narrative content, you can review the source E2B narrative in the previous version.
- When you create a follow-up Case, Vault generates a new minor narrative document version by copying the previous Case’s narrative. If the previous Case does not have a narrative, Vault generates a new narrative document for the follow-up Case.
- When configured by your Admin, Vault also generates a new minor document version of the narrative for the follow-up Case based on the applicable outline template.
Types of Cases
Vault matches the appropriate Admin-defined outline template to Case data for the following types:
- Post-Market Non-Serious: Applies to the following Cases:
- Postmarket Cases (do not have Studies)
- Non-clinical trial study Cases (Study Type is Other) with a Serious value of No or blank
- Post-Market Serious: Applies to the following types of Cases:
- Postmarket Cases (do not have Studies)
- Non-clinical trial study Cases (Study Type is Other) with a Serious value of Yes
- Clinical: Applies to clinical trial study Cases (Study Type is not Other)
Limitations
Vault can reference up to 15,000 child Case Products and 15,000 Case Medical Histories per Admin-defined Narrative Statement Option. If executing a particular record would exceed this amount, Vault ignores that option when generating the narrative and sends you a notification with details about which record would have exceeded this limitation.
Narrative Templates
When you promote an Inbox Item to a Case, Vault generates a narrative based on Admin-defined controlled document templates using merge fields that generate values based on token resolution. Your Admin can configure custom templates for any combination of Organization, Report Type, Study Type, Study, and Localization.
The following behavior applies to generating narratives from narrative templates:
- For Cases promoted from imported Inbox Items with E2B narrative content, the generated narrative includes imported narrative text and translations.
- When you create a follow-up Case, Vault re-renders the narrative from the initial Case, creating a new follow-up narrative document version for the follow-up Case. If the previous Case does not have a narrative, Vault generates a new narrative document for the follow-up Case.
- For follow-up Cases with imported E2B content, Vault appends the content in the H.1 Case Narrative Including Clinical Course, Therapeutic Measures, Outcome and Additional Relevant Information data element to the end of the narrative.
- If you merge a local Inbox Item to a follow-up Case and the language for the Inbox Item’s narrative content and initial Case are the same, Vault copies the narrative content from the initial Case to the new narrative document and appends any localized narrative content to the new document.
- In Vaults using Veeva AI for Safety, you can manually run the Narrative Agent on generated narratives after medical review and QA, if configured by your Admin.
Follow-Up Narratives
When you open a follow-up Case, Vault copies over the most recent version of the narrative document from the initial Case. If the most recent version contains merge fields, Vault updates the field values in the newest version using the information in the follow-up Case. To include the initial Case narrative without regenerating merge field values, perform the following steps:
- Navigate to the initial Case narrative document.
- Copy the text from the initial narrative.
- Paste the contents into the narrative document for the follow-up Case using plain text without formatting. You must paste with plain text to ensure Vault does not regenerate merge field values.
Localized Narratives
Vault generates narrative documents for the translation of Localized Cases, which includes the English narrative that exists for the related Case when you generate the Localized Case. You can review these details and access the narrative document in the Narrative section.
You can override a Localized Case’s narrative content by selecting the Sync Global Narrative to Local Narrative action from the record’s All Actions menu. This updates the narrative document, preview, and language with the most-recent version from the related global or domestic Case.
For follow-up domestic Cases generated through the Inbox Item to Case Compare page, if the previous Case version doesn’t include a Localized Case Narrative or the Localization of the Case has changed, Vault generates a narrative and attaches it to the Localized Case. To generate the narrative, Vault uses the local narrative template for the Localization. If no local template exists, Vault generates the narrative from the default narrative template.
Re-Render the Narrative Document
After adding or changing Case details, you can run the Re-render Case Narrative action to update merge fields on the narrative. To do this:
- Navigate to the Case.
- From the All Actions menu, select Re-render Case Narrative.
- In the Re-render Document dialog, select OK.
When you re-render the narrative document, Vault does not create a new document version. Instead, Vault updates merge fields in the most-current version of the document to reflect the new details.
Lock Merge Fields
Before you distribute a Case to health authorities, we recommend moving the narrative document to a steady-state to save the narrative to a specific version in time. This prevents Vault from updating merge field values in the narrative document if any of the associated fields on the Case change, such as non-significant follow-ups or amendments. If you need to update the narrative document after distribution to partners or health authorities, you can create a new version of the document.
Use the narrative document’s workflow to move it to a steady state, such as Approved.
Narrative Agent
In Vaults using Veeva AI for Safety, use the Narrative Agent to refine narrative content. The agent can fix spelling and grammar and improve the narrative’s readability by updating the overall flow, style, and voice. The Narrative Agent actions can:
- Proofread: Corrects spelling and grammar issues while preserving the narrative’s original structure and details.
- Rewrite: Refines flow, style, and voice. This may adjust the document structure but should not modify the clinical course of the narrative.
Depending on your Admin’s configuration, Vault may run these actions automatically during rules based narrative creation for initial Cases, follow-up Cases, or both. If configured by your Admin, you can also run these actions from any narrative document’s All Actions menu.
Note: For content generated by narrative templates with merge fields, narrative documents generated by the Narrative Agent do not maintain any merge field tokens inherited from the template, so you cannot re-render the narrative after running the agent to update the data points. We recommend waiting to run the agent until later in the Case’s lifecycle, after medical review and QA.
To manually run the Narrative Agent on a document:
- Navigate to the most recent version of the narrative document classified as Case > Summary > Narrative.
- From the All Actions menu, select Generate Text with Narrative Agent.
- In the dialog, select Proofread (
) or Rewrite (
). The dialog indicates that Vault is working on your selection. - You can select Close or wait for the dialog to close when the action completes. Closing the dialog does not stop the selected action from executing.
When the action completes, Vault upversions the document to the next minor version, which contains the AI-generated content. Review the generated content to verify accuracy. If applicable, edit the document as needed. When the action completes, Vault also does the following:
- Updates the Narrative Generation Status field on the Case to indicate the current status.
- Updates Narrative Content Source document field value to Narrative Agent.
- Preserves the previous narrative content in the document’s previous minor version.
- For follow-up Cases, includes a change summary in the narrative content for each version.
- If Vault encounters any errors, updates the document’s lifecycle to Generation Error state.
Note: Always review the generated narrative content after running the Narrative Agent.
Edit the Narrative Document
You can edit generated narrative documents using collaborative authoring.
Recommendations and Best Practices
We recommend the following best practices when editing a narrative document:
- Do not add information that should be blinded to the narrative document.
- Do not add comments or track changes in the document. If you need to use these review tools for draft purposes, ensure you remove them for the final version.
- To copy-paste content with merge field tokens, paste without formatting. If you paste with formatting, the tokens will regenerate if there are changes to the associated field.
- Do not insert images into the document.
- If you must insert tables, only use single-column tables. Multi-column tables cannot be exported to transmission documents. When tables are exported, they are flattened to comma-separated text values.
- Do not archive narrative documents for any Cases that may receive follow-ups. Vault cannot transmit archived documents.
Note: If you see merge field queries in the narrative, contact your Veeva Representative or your Admin. There may be a configuration issue on the narrative template.
Add a Narrative Translation
For Cases based on imported E2B files, Vault imports all narrative translations from the E2B file. To manually add a narrative translation:
- Navigate to the applicable Case.
- In the Documents section, select Add.
- In the Search: Documents window, select Create.
- In the Create Document dialog, select Upload, then Continue.
- On the Upload Files (Step 1) page, upload the applicable DOCX file and classify the document as Case › Summary › Narrative.
- Select Next.
- On the Upload Files (Step 2) page, populate the following fields:
- Language (ISO)
- Organization
- Select Save.
- In the Narrative section of the Case, select the document to which you want to add this translation to navigate to the document’s Doc Info pane.
- Add the narrative translation you saved to the Supporting Documents section of the Relationships panel.