Project

General

Profile

Actions

Gaps #87156

open

Check again: Any amendments made should be added as addendum, name and time stamp should be available for addendum.

Added by Vasuki Muniratnam over 1 year ago. Updated 3 months ago.

Status:
QA
Priority:
Critical
Category:
M Laboratory
Target version:
-
Start date:
07/08/2025
Due date:
08/05/2026 (about 6 months late)
% Done:

50%

Estimated time:
Spent time:
Dev Due date:
05/08/2026
Release date to QA:
06/05/2026
Issue released on:
HUMS SandBox
Function:
HUMS

Description

As a [Pathologist], I want to create an Addendum/Supplementary Report for an existing test report

1. Use Case

As a Pathologist, I want to create an Addendum Report (Supplementary Report) to append additional findings, clarifications, or amendments to an existing finalized test report without replacing or modifying the original content.
This ensures data integrity, traceability, and compliance with medical documentation and audit standards.

2. Visual UI

Refer to the attached screenshots.

The “Addendum” tab will be available in the Result Entry screen for relevant tests (e.g., Biopsy in Histopathology).
Within this section, users can:

  • Enter supplementary information in a free text box (rich text editor).
  • Select or type the Reason for Amendment using:
  • A dropdown containing predefined options (e.g., “Report Correction”, “Additional Findings”, “Clarification”).
  • A free text box for manual entry if the predefined options are insufficient.
  • Save the addendum to append it as a Supplementary Report linked to the original report.

3. Pre-condition

❏ The Result Entry screen must be accessible for the relevant department (e.g., Histopathology/Cytology).
❏ Only authorized users (Pathologists or designated roles) can add Addenda.
❏ The original report must be finalized before an Addendum can be created.
❏ The following metadata must be captured and stored for every Addendum:

Capture Username of the user making the amendment ✅

Capture Date and Time of the amendment ✅

Reason for amendment (Optional based on department policy) ✅
❏ The Addendum details will be displayed and traceable in the Phlebotomy Dashboard.
❏ The clinician/requester must be able to identify that a Supplementary Report has been added (via alert or visible indicator).

4. Acceptance Criteria

❏ Creating an Addendum should not trigger a new report version.
❏ The Addendum should appear as a Supplementary Report section appended to the existing report.
❏ The Addendum should not overwrite or alter any content in the original report.
❏ All addenda—whether corrections or new findings—will be categorized under Supplementary Reports.
❏ Each Addendum should include the label:
“Supplementary Report issued on DD/MM/YYYY by [Username]”
❏ Each Addendum must maintain complete traceability (username, timestamp, reason).
❏ Clinicians/requesters must be alerted or able to visually identify the presence of a supplementary report in the dashboard or patient record view.
❏ Multiple Addenda can be created for a single report, and all must be displayed chronologically.
❏ Once saved, Addenda cannot be edited or deleted — only new entries can be appended.

5. Technical Requirement

❏ Each Addendum should be stored as a child record linked to the parent report ID.
❏ The system must maintain complete version tracking and audit trail for every Addendum entry.
❏ Database table must include:

  • Parent Report ID
  • Addendum ID (unique)
  • Username / User ID
  • Date and Time
  • Reason (Dropdown/Text)
  • Addendum Text Content
    ❏ Addendum details should display in:
  • Result Entry Screen (under Addendum tab)
  • Report print view as “Supplementary Report”
  • Phlebotomy Dashboard (indicator or status)
    ❏ The predefined reasons should be configurable from the Master Configuration (Admin Setup) screen.
    ❏ Notification logic:
  • If enabled, the system should flag or alert the clinician/requester when a supplementary report is added.
  • The alert method (popup, dashboard highlight, or message) can be finalized with the client.

6. System + User Flow Diagram

Step 1: User Access

  • Pathologist opens the Result Entry screen for a finalized report.
  • Navigates to the Addendum tab.

Step 2: Data Entry

  • Pathologist types in supplementary findings or clarifications in the text box.
  • Selects a predefined reason from dropdown or enters a custom reason manually.

Step 3: Save Action

  • User clicks Save Addendum.
  • System validates user permission and report status.

System captures:

  • Username
  • Date & Time
  • Reason (if provided)
  • Addendum content

Step 4: System Processing

  • Addendum is saved as a new supplementary record linked to the original report.
  • Original report remains unchanged.
  • Addendum record is marked as “Supplementary Report”.
  • The entry is stored in the audit trail.

Step 5: Display and Notification

  • The Phlebotomy Dashboard updates with a Supplementary Report indicator.
  • Clinicians/requesters viewing the case are alerted or can see a visual marker that a supplementary report exists.
  • When the report is viewed or printed, the Addendum appears as:
    “Supplementary Report issued on DD/MM/YYYY by [Username].”

[1] Pathologist Opens Finalized Report
│
▼
[2] Navigates to “Addendum” Tab in Result Entry
│
▼
[3] Enters Addendum Text + Selects/Enters Reason
│
▼
[4] Clicks “Save Addendum”
│
▼
[5] System Validates User Permission & Report Status
│
▼
[6] System Records:
- Username
- Date & Time
- Reason (Optional)
- Addendum Content
│
▼
[7] Addendum Stored as Child Record (Linked to Report ID)
│
▼
[8] Original Report Remains Unchanged
│
▼
[9] Supplementary Report Appears:
“Supplementary Report issued on DD/MM/YYYY by [Username]”
│
▼
[10] Phlebotomy Dashboard Updated → Supplementary Indicator Visible
│
▼
[11] Clinician/Requester Alerted or Sees Visual Indicator

7. Outcome

❏ The system successfully appends supplementary information to the existing report without replacing or modifying the original data.
❏ All Addenda are traceable with full metadata and appear in chronological order.
❏ The clinician/requester can easily identify and access the supplementary report.
❏ The overall process supports full audit compliance and data integrity standards.

Attachment:


Files

clipboard-202508111330-y2frs.png (74.8 KB) clipboard-202508111330-y2frs.png Thivakaran Maniam, 11/08/2025 01:30 PM
clipboard-202510171106-yx5rk.png (72.9 KB) clipboard-202510171106-yx5rk.png Vasuki Muniratnam, 17/10/2025 11:06 AM
clipboard-202510171107-5usiu.png (67.7 KB) clipboard-202510171107-5usiu.png Vasuki Muniratnam, 17/10/2025 11:07 AM
Screenshot 2026-05-05 182222.png (217 KB) Screenshot 2026-05-05 182222.png Kunal Yelne , 05/05/2026 06:26 PM
Screenshot 2026-05-05 182204.png (327 KB) Screenshot 2026-05-05 182204.png Kunal Yelne , 05/05/2026 06:26 PM
clipboard-202605111157-kuasz.png (219 KB) clipboard-202605111157-kuasz.png Yaswanth Sai Thirumalasetty, 11/05/2026 02:27 PM
clipboard-202605111158-oiwgd.png (160 KB) clipboard-202605111158-oiwgd.png Yaswanth Sai Thirumalasetty, 11/05/2026 02:28 PM
clipboard-202605151736-49stl.png (269 KB) clipboard-202605151736-49stl.png Kunal Yelne , 15/05/2026 05:36 PM
clipboard-202605291302-7aesc.png (281 KB) clipboard-202605291302-7aesc.png Yaswanth Sai Thirumalasetty, 29/05/2026 03:32 PM
clipboard-202605291303-blj8v.png (361 KB) clipboard-202605291303-blj8v.png Yaswanth Sai Thirumalasetty, 29/05/2026 03:33 PM
clipboard-202606111624-0kppi.png (248 KB) clipboard-202606111624-0kppi.png Vasuki Muniratnam, 11/06/2026 04:24 PM
clipboard-202606111642-gljdp.png (154 KB) clipboard-202606111642-gljdp.png Vasuki Muniratnam, 11/06/2026 04:42 PM
clipboard-202606301507-7sl8g.png (278 KB) clipboard-202606301507-7sl8g.png Nurfarisha Izani, 30/06/2026 03:07 PM
clipboard-202606301510-rcn3e.png (314 KB) clipboard-202606301510-rcn3e.png Nurfarisha Izani, 30/06/2026 03:10 PM
clipboard-202606301510-la6zk.png (263 KB) clipboard-202606301510-la6zk.png Nurfarisha Izani, 30/06/2026 03:10 PM
clipboard-202606301511-nfsz4.png (271 KB) clipboard-202606301511-nfsz4.png Nurfarisha Izani, 30/06/2026 03:11 PM
clipboard-202607081600-k3zve.png (178 KB) clipboard-202607081600-k3zve.png Shweta Bhoyar, 08/07/2026 06:30 PM
clipboard-202607081600-ky3wi.png (165 KB) clipboard-202607081600-ky3wi.png Shweta Bhoyar, 08/07/2026 06:30 PM
clipboard-202607081600-nucjz.png (213 KB) clipboard-202607081600-nucjz.png Shweta Bhoyar, 08/07/2026 06:30 PM
clipboard-202607141112-a2ov0.png (357 KB) clipboard-202607141112-a2ov0.png Nurfarisha Izani, 14/07/2026 11:12 AM
clipboard-202607141114-8xaat.png (447 KB) clipboard-202607141114-8xaat.png Nurfarisha Izani, 14/07/2026 11:14 AM
clipboard-202607141114-wznwo.png (446 KB) clipboard-202607141114-wznwo.png Nurfarisha Izani, 14/07/2026 11:14 AM
Actions

Also available in: Atom PDF