Review of local teams' incident and concerns logging tools
THAMES VALLEY
- Access database to log GMC Concerns - manually entered by revalidation officer when they are alerted (by email correspondence from GMC to RO)
- Confidentiality a real concern. GMC investigations super-sensitive, so only revalidation officer and manager have access to this database
- Database built locally by keen colleague - therefore has not been developed since (e.g. to include Live Reporting)
- Employer reports - formerly Collective Exit Reports, now employer reporting done by exception - known as Live Reporting
- Trusts/GP practices submit information about Significant Incidents on a form that's emailed
- Logged by revalidation officer in Excel spreadsheet
- Form-R & Educational supervisor's reports - former on Intrepid, latter on ARCP checklist (paper form developed locally for ARCP panel to complete at time of ARCP as input to Intrepid can be delayed) - these both checked at time of Revalidation and details entered on revalidation spreadsheet if relevant
NORTH EAST
- Have a locally developed a tool in Sharepoint which they use to log all incidents and concerns (need to confirm is this is a Sharepoint list or a full database e.g. Access accessed on Sharepoint)
- Sketch of this created by Izzy during contextual enquiry visit is here
- Sketch of this created by Izzy during contextual enquiry visit is here
EAST MIDLANDS