Multi Author

Multi Author

Control which report actions are available to users based on their privilege level and authorship.

Overview

Define the actions that will be available to users under the actions menu when working with reports. This setting determines how users can manage report drafts and submissions, particularly when multiple authors or reviewers are involved in the reporting workflow.

Allowed Report Actions

Select the actions that will be available to users under the actions menu.

Discard Changes

Allow users to discard unsaved changes and revert to the last saved version of a report.

When enabled:

• Users can abandon their current edits

• Report reverts to the most recent saved state

• Useful for backing out of unwanted modifications

When disabled:

• Users must manually undo changes or save over previous work

• Reduces risk of accidental data loss for inexperienced users

Discard Report

This allows users to discard recent changes made to the report, which reverts the report to the previous state (e.g. a Save, Discard, or Complete Discard, Ownership Change)

When enabled:

• Users can discard report drafts entirely

• Unassisngs the report from the user

• Cannot be undone once executed

When disabled:

• Report drafts must be kept or processed through standard workflows

• Prevents accidental discards of work in progress

Reject Changes (by Lower Privileged Users)

Allow higher privileged users to reject submissions from users with lower privilege levels and send reports back to their previous status.

When enabled:

• The Reject button appears under the Actions menu for users with higher roles

• A Radiologist can reject a report submitted by a Resident

• A Resident can reject a report submitted by a Report Drafter

• Button remains visible but disabled when reject conditions are not met

When disabled:

• The Reject button is hidden from the Actions menu

• Reports cannot be sent back through rejection workflow

• Review must happen through other mechanisms

How the Reject workflow works:

When a user rejects a report submission:

1. Status reversion:

   • If the status was Draft → remains Draft

   • If the status was Preliminary Signed → returns to Draft

2. Reassignment:

   • Report is automatically reassigned to the user who last saved it

3. Edits and feedback:

   • Any edits made by the rejecting user are saved

   • The rejecting user can leave messages or feedback for the drafter

4. System tracking:

   • A rejection event is emitted for audit purposes

Use case: This is particularly useful in teaching environments where attending physicians review resident reports, or in quality assurance workflows where senior reviewers can provide feedback while rejecting submissions that need revision.