Context/Purpose (along with Use cases):

As part of other stories in this feature we have captured the actions of the user in logging into the system, opening/closing a visit etc. We would also like to capture any actions that a user does in editing clinical data. In this story we will track all the actions where the user edits an encounter.

This is could be point of care in the Consultation tab, when the providers fills in obs. forms or prescribes medicines. Or it could be a retrospective entry either through a CSV upload or through the dashboard.

Event:Edit encounter,

Message: <Username > edited an <encounter type> of <Patient ID>

​The encounter type and UUID must also be captured as part of the event to enable detailed investigation if required.

In Scope:

Consultation Tab
Retrospective mode
Upload through encounter.csv
Registration
Out Of scope:

We are not differentiating between creation of encounters and editing encounters. They are tracked as one activity of activity of editing clinical data of a patient.

Acceptance Criteria :

Regular Consultation Mode:
When a user edits any data in any of the tabs and saves it : Observation, Diagnosis, Disposition, Bacteriology, Orders, medication etc, an event should be logged in the audit log table.
The encounter type and UUID must also be captured in the event. This will help the admin in tracking more details about the edits made to the encounter and its observations’.
Retrospective Consultation mode:
When a user enters data in the retrospective mode from the dashboard, the encounter that is created as a part of either an existing visit or a new visit in the past, it must be logged in the Audit Log table.
The encounter type and UUID must also be captured as part of the event to enable detailed investigation if required.
Encounter Upload through CSVs
When a user uploads encounter information through a CSV – the encounter that is created ,as a part of either an existing Visit or a new visit, must be captured in the audit log table.
The encounter type and UUID must also be captured as part of the event to enable detailed investigation if required.
Registration:​
When a patient is registered & a visit is started, a Registration encounter is created. As a part of this encounter we capture Vitals etc. This event will also be in the audit log table.
Other Encounter Types: ADT, Patient doc Upload and Radiology Upload , Lab Results, Investigation, validation Notes encounter. Edit forms through dashboard