Project

General

Profile

Actions

Gaps #93890

closed

ER Module > Primary Survey > Implement Audit Trail for Changes Made in Primary Survey

Added by Kierthini Nethi 5 months ago. Updated 2 months ago.

Status:
Closed
Priority:
High
Category:
CliniCare
Target version:
-
Start date:
03/06/2026
Due date:
% Done:

100%

Estimated time:
Spent time:
Dev Due date:
Release date to QA:
01/08/2026
Issue released on:
Dev
Function:
Standard

Description

Description:
Currently, there is no audit trail available to track modifications made within the Primary Survey section of the ER Module.
Enhance the system by implementing an Audit Trail feature to capture and display all changes made to the Primary Survey records.

Requirements:
  1. Create an audit trail table/view.
  2. The audit trail should record the following information:
    • Date & Time of the change
    • Username of the user who performed the action
    • Field/Section Modified
    • Previous Value
    • Updated Value
Expected Behaviour:
  • Every creation, update, or modification made within the Primary Survey should be logged automatically.
  • Users should be able to review the audit history to identify who made the change, when it was made and what information was changed.
  • Audit records must be displayed in chronological order, with the most recent changes appearing first.

Purpose/Business Justification:
To improve traceability, accountability and data integrity by providing visibility into all modifications made within the Primary Survey, allowing clinical and administrative users to review historical changes when required.

CURRENT UI

EXPECTED CHANGES


Files

clipboard-202606031410-e8xrw.png (145 KB) clipboard-202606031410-e8xrw.png Kierthini Nethi, 03/06/2026 02:10 PM
clipboard-202606031411-kesfj.png (161 KB) clipboard-202606031411-kesfj.png Kierthini Nethi, 03/06/2026 02:11 PM
clipboard-202606051043-axlys.png (234 KB) clipboard-202606051043-axlys.png Kierthini Nethi, 05/06/2026 10:43 AM
clipboard-202606051043-oveis.png (230 KB) clipboard-202606051043-oveis.png Kierthini Nethi, 05/06/2026 10:43 AM
clipboard-202606240011-y8arg.png (611 KB) clipboard-202606240011-y8arg.png Ahmad Ashfaq , 24/06/2026 03:11 AM
clipboard-202606262055-i11vq.png (224 KB) clipboard-202606262055-i11vq.png Harshada Dixit, 26/06/2026 08:55 PM
clipboard-202606262055-j12d0.png (216 KB) clipboard-202606262055-j12d0.png Harshada Dixit, 26/06/2026 08:55 PM
clipboard-202606262055-wjvzz.png (217 KB) clipboard-202606262055-wjvzz.png Harshada Dixit, 26/06/2026 08:55 PM
clipboard-202606262056-kvbml.png (211 KB) clipboard-202606262056-kvbml.png Harshada Dixit, 26/06/2026 08:56 PM
clipboard-202606262056-hmdw0.png (194 KB) clipboard-202606262056-hmdw0.png Harshada Dixit, 26/06/2026 08:56 PM
clipboard-202606262056-7jih6.png (200 KB) clipboard-202606262056-7jih6.png Harshada Dixit, 26/06/2026 08:56 PM
Actions #1

Updated by Sagar Pokale 5 months ago

  • % Done changed from 0 to 50

Hi @Ahmad,
Please use this API to get the history of respective tab

GET : /ipd-clinical/case/sheet?patientId=59573&encounterId=2de72e4b-69c9-4796-a4c6-fcc510e3144f&siteId=5&eventIdentifier=PUPILLARY_ASSESSMENT

Please replace the eventIdentifier for respective tab,

If anything let me know

Actions #2

Updated by Sagar Pokale 5 months ago

  • Assignee changed from Sagar Pokale to Ahmad Ashfaq

Updated by Kierthini Nethi 5 months ago

As per the discussion with the development team (@Sagar Pokale and @Ahmad Ashfaq ) on 4 June 2026, the previously proposed requirement to introduce a dedicated audit trail table for all Primary Survey sections has been reviewed and revised.

During the review, it was observed that in the Classic View of the Primary Survey, the GCS and Pupillary Assessment sections already contain a History tab that effectively displays the audit trail for the respective sections. This approach was agreed to be more user friendly, consistent and spaceefficient compared to displaying a separate audit trail box within each section.

Revised Requirement
  1. Introduce a History tab for all sections within the Primary Survey, following the existing implementation used in the GCS and Pupillary Assessment sections.
  2. The History tab shall display the audit trail of changes made to the respective section.
  3. The functionality and user interface should be consistent across all Primary Survey sections.
  4. This enhancement shall be implemented in both:
    • Single Form View
    • Classic View

Expected Outcome
Users should be able to view the modification history of each Primary Survey section through its respective History tab, allowing easy tracking of changes while maintaining a clean and consistent user interface throughout the Primary Survey module.


Actions #4

Updated by Ahmad Ashfaq 5 months ago

  • Status changed from New to Assigned
Actions #5

Updated by Ahmad Ashfaq 5 months ago

@Sagar Please update General Condition history API to return data.

Actions #6

Updated by Sagar Pokale 5 months ago

  • Assignee changed from Sagar Pokale to Ahmad Ashfaq

Hi,
Updated the GET API to return the General condition,
Please check

Actions #7

Updated by Ahmad Ashfaq 5 months ago

  • Status changed from Assigned to Coded
  • % Done changed from 50 to 100
  • Issue released on Dev added
  • Issue released on deleted (NA)
Actions #8

Updated by Mehdi Mehdi 5 months ago

  • Status changed from Coded to QA

Updated by Harshada Dixit 5 months ago · Edited

ER Module > Primary Survey > Implement Audit Trail for Changes Made in Primary Survey- PASS

As discussed with @Ahmad Ashfaq & @Sagar Pokale

Please find the details of the changes below:

- History Tab: A History tab has been added to all sections within the Primary Survey.

- Vitals: Please note that a History tab was not added to the Vitals section, as all vitals entries are already recorded and accessible under the "View All Vitals" feature.

- GCS Assessment: In the GCS assessment, entries are now recorded as "ADD" instead of "Update." Since every new value is added as a separate entry,
 
- single form view- there is no direct audit trail function as mentioned by the Dev team,
that any information added or updated under the single form view is being recorded under the respective function's history tab within the classic view.






Actions #10

Updated by Mangesh Pangrekar 4 months ago

  • Assignee changed from Mangesh Pangrekar to Kierthini Nethi
Actions #11

Updated by Kierthini Nethi 4 months ago

  • Assignee changed from Kierthini Nethi to Harshada Dixit
Actions #12

Updated by Harshada Dixit 4 months ago

  • Status changed from Tested to Re-open
  • Assignee changed from Harshada Dixit to Mehdi Mehdi

As per discussion with @Kierthini Nethi - This enhancement shall be implemented in both:
Single Form View- No enhancement
- please develop such function based on requirement.

Classic View -Enhancement done as per req. added history tab and all actions done by user recorded properly under this tab .

Actions #13

Updated by Mehdi Mehdi 4 months ago

  • Assignee changed from Mehdi Mehdi to Ahmad Ashfaq
Actions #14

Updated by Mehdi Mehdi 4 months ago

  • Release date to QA set to 01/08/2026
Actions #15

Updated by Ahmad Ashfaq 3 months ago

  • Assignee changed from Ahmad Ashfaq to Kierthini Nethi

@Kierthini Nethi As discussed in meeting that single form view history table will not align as all the data is different for each step. Please guide on that accordingly.

Actions #16

Updated by Kierthini Nethi 2 months ago

  • Status changed from Re-open to Closed
Actions

Also available in: Atom PDF