Patient Context Validation at Report Signing
Overview
OmegaAI now includes enhanced validation at the point of report signing to help ensure that a finalized report is always associated with the correct patient, study and content. When a radiologist clicks Done or Done & Next, the system validates three things: that the patient identifiers match the currently loaded study, that the report's header and footer are present, and that bookmark values (such as patient name, demographics, and accession number) reflect the most current data. If any of these checks fail, the system pauses and prompts the radiologist to reload before proceeding.
Note: This validation is triggered when a report is signed using Done or Done & Next, regardless of whether the report was created in Document Viewer, Md.ai, or another supported editor. The feature is enabled by default for all users and requires no configuration.
Why This Matters
In a busy imaging environment, patient data can be updated or refreshed while a report is being authored. Without validation at signing, a report can be finalized based on patient information, demographics, or report content that no longer matches what is currently on record. This update addresses that risk by introducing an automatic safety check that runs every time a report is signed.
No action is required from administrators or radiologists to enable this behaviour — it is built into the signing flow and runs in the background.
What Gets Validated
When a radiologist clicks Done or Done & Next, the system validates three checks:
• Patient–study match — The system confirms that the Patient ID matches the Study ID for the currently loaded study. A mismatch here is a direct indicator of a wrong-patient or outdated/wrong-context situation.
• Report header and footer — The system checks that the required header and footer content is present in the report. If either is missing, the system attempts to fill it in automatically, first from the study’s own template, then from the organization’s default header/footer, before reloading.
• Bookmark values — Confirms that bookmark-driven fields (such as patient name, date of birth/age, gender, and accession number) match the current data on record. If a mismatch is found, the values are refreshed automatically.
If all checks pass, signing proceeds without interruption. If any check fails, the same shared notice appears; it does not indicate which specific check failed.
How It Works
The validation runs automatically when a radiologist initiates signing. All checks execute together in the background — there is nothing to trigger manually.
To access this feature: open a report in Document Viewer, then click Done or Done & Next — the validation runs automatically at the point of signing.
The Pre-Sign Notice
When any of the checks fail, the following notice appears:
Title: Unable to Sign Report
Message: “The patient information must match the loaded study, and the report must include its required header and footer. These checks must pass before the report can be signed. Click ‘Reload’ to update the report with the current patient data; your report content is preserved.”
Buttons: Close - Reload
The same notice appears regardless of which check failed; it doesn’t identify the specific field or component that triggered it. This is by design, to prompt a quick corrective action rather than require the radiologist to diagnose the issue manually.
From the notice, the radiologist can choose one of two actions:
• Reload- Reloads the study and refreshes the report with current patient, header/footer, and bookmark data before signing proceeds. Report content already entered is preserved.
• Close- Signing is cancelled and the radiologist returns to the report. No changes are made. The system does not automatically reassign or correct patient identity. The decision to proceed always remains with the radiologist.
What Users Will Notice
For most reports — where patient data, header/footer content, and bookmark values are all current- the signing experience is unchanged. The validation runs silently, and signing completes as normal.
The notice appears only when one of the three checks fails. This is expected to occur infrequently, typically when patient information was updated while the report was being drafted, or when a report component is missing. It presents a single clear action (Reload) so radiologists can resolve the issue quickly and continue their workflow with minimal interruption.
Notes for Administrators
• This feature is automatically active for all users in the Document Viewer signing flow. There is no configuration required.
• Patient data is not modified automatically at any point by user action. Automatic corrections that do occur (header/footer fill-in, bookmark refresh) draw from existing study/organization data, not manual edits.
• If you observe unexpected behaviour related to the pre-sign notice, contact OmegaAI support for assistance.