Verification of logs is a requirement for all healthcare providers. Logs are available for export in admin for transparency or if data needs to be verified in any way.

If you have access to admin and administration of logs, you can use this feature easily and safely.

The logs page stores both active and deleted users. The information is stored according to legal requirements, after which the logs are deleted.

Logs for users in the platform

Access log
Contains, for example, the user’s logins to different parts of the platform, which cases the user has accessed and when, and when the user accessed a patient’s medical report(s).

As access logs contain patient data, we recommend that the feature is used sparingly and that exported logs are deleted as soon as appropriate.

Changelog
Contains all changes that a user has made to other user accounts, their identifier (such as NHS number or memberID), and the value that the user has changed.

How to download a log

  1. Log into Admin.
  2. Select page “Logs”
  3. Select “User logs”
  4. Filter the user you want to check using: first name, last name and identifier (such as NHS number or memberID).
  5. Download logs by selecting “Download access log” or “Download changelog”, depending on which logs you want to check. Each file is saved on your computer.
  6. If you get no result, it means that there are no logs for that user.

Note! Logs are provided for the purpose of controlling what data users have had access to according to various data regulations.

Important to know
You can only export data for units for which you have permissions in Doctrin Admin. The log that is exported is filtered based on the permissions of the user exporting the file.

  • Users with permissions only on unit A, will be able to export a log containing recorded events for unit A, but not unit B. If recorded events are present on unit B, they will not be reported in the log file.
  • When users with multiple unit permissions export a log file, the log file will cover recorded events on all unit that the user’s permissions cover.

When a user acts as an external consultant within Doctrin Network, an event will be recorded both on the unit to which the case belongs, and on the unit that the user as consultant represents in the case. This is to provide a complete overview of the access to patient data that a user has had, while working in or representing the unit.

Data fields in the access log
Created – when event happened    
Patient unit – the unit where event happened    
HSA – owners HSA ID    
SSN – owners national identifier    
Caregiver unit – the unit where caregiver works, can be another one than the patient’s unit (regarding Doctrin Network)    
Patient identifier – patient’s national identifier    
System – describes in what part of the platform the event happened.Case, Medical history report, Caregiver, Attachment.    
Action & system action – describes the type of event. • case.get (case opened)• case.assign (case opened)• case.invitationComment.get (comment for invite read)• anamnesis.getReport (medical history report opened)• case.anamnesis.create (issued new medical history taking)• case.handoverComment.get (comment for handover read)• attachment.get (attachment opened)• login (logged in) Requested objectid – ID for the requested object
All case report In Doctrin admin it is possible to download a report (log) of all cases. This report includes several data points regarding a case such as state, time of creation, payment, owner, offboarding feedback etc. Users with the Log Manager permission profile will be able to access this page in admin. How to download all case report Log into Doctrin admin. Select “Logs” in the menu. Select “All case report” Select date range to download a file. The file will be saved directly to your computer. Note! This log contains very sensitive information and should be treated accordingly. Do not use this report for data anlytics purposes. Instead use the Analytics platform which has anonymzed data in a much more structured and presentale format. The caselog should only be used if you need to access specific data about a case that you can not get otherwise. Data points • Case: unique ID for the case• Registered at: unit where a patient is registered (if applicable)• Registered county: area where a patient is registered (if applicable) • Patient identifier: national identifier• Patient name: name of a patient• Updated: latest event in the case • Created: when case is created• State: status of a case• Closed: case closed • Expired: case has expired due to no response from patient• Chat: ongoing activity• Onboarding: patient is in the onboarding process • Offboarding: case is closed but patient has not yet been through offboarding process• Handover: case is pending handover• Reason for contact: what patient needs help with • Issue: reason for contact• Owner HSA: professional user’s HSAID• Owner (national) identifier: identifier for a user, depending on local adaptions • Owner name: professional user’s name• Sufficient information: shows if patient thinks they recieved enough information(True: yes, False: no, Blank: no answer given) • Recommend to others: shows if patient thinks they can recommend the service(True: yes, False: no, Blank: no answer given) • Compassion shown: shows if patient thinks they recieved campassion(True: yes, False: no, Blank: no answer given) • Rating: shows how patient rated the service (1-4, 4 = best)• Case viewer link: URL for static page with case information• Onboarding to offboarding (minutes): how long a case was ongoing for • Onboarding date: when onboarding started• Chat date: when chat started for a patient• Assigned date: when a professional user entered a case • Offboarding date: when offboarding ended• Close date: when case was closed• Patient email: email of patient • Patient phone: phone number of patient• Patient allows marketing: shows if patient want markering content/information• Switchboard: shows rules active or not for a case • Output method: shows to what flow the case has been triaged automatically• Time picked: shows when a booking for a healthcare centre has been done(face-to-face)• Healthcare centre: shows to what healthcare centre a booking has been made • Payment initiated: shows if paymen has started• Payment reserved: shows if paymen has been reserved• Payment completed: shows if paymen has been completed • Unit: what unit a case belongs to• Patient gender: gender of patient• Patient age: age of patient • Type of case – Feedback loop• Type of case (details) – Feedback loop • Handed over to unit – if a handover has been done, this is the receiving unit’s name• Handed over to user – if a handover has been done, this is the name of the professional user receiving the case • Handover received by unit – if a handover has been done, this is the original unit’s name• Handover received by user – if a handover has been done, this is the original owner of the case