/
Concerns log specification

Concerns log specification

Draft for UI design purposes only

  • Input interface - form based
  • Need audit trail - who logged incident and when
  • Should enable search on GMC number, name, date, site, source, type, poss free text (details field)
  • Need ability to upload and store documents e.g. original emails, images
  • Should enable reports on all fields
  • East Mids include health concerns (also declared on Form-R) here, but leave it out for now (we are dealing with Form-R separately at the moment)

Field nameTypeComment
Date of logAutomatic data stampĀ 
Logged byAutomatic based on userĀ 
GMC Number7 digit numberĀ 
First nameĀ Pre-populated according to GMC number?
SurnameĀ "
SpecialtyĀ Ā 
Grade at time of incidentĀ Ā 
SourceĀ 

Options:

Employer report

ARCP Panel

Form-R

GMC

Other (please specify)

Ā 

Date reportedĀ 

This is date incident reported to HEE

Date of concern or incidentĀ 

May not be known so may need to allow empty field

'Concern' doesn't work as well as 'Incident' here - but log could include a complaints as well as incidents, etc - so to discuss

(Set rules so this date cannot be after date reported)

Concern typeĀ 

Options:

Complaint

Conduct and capability

Serious Untoward Incident

Significant Event

Level of trainee involvementĀ 

Not sure about this, and only relates to incidents (so maybe only opens if that type of concern selected?) but could be options:

Present

Contact during incident

Main actor

(None of wording right, but basis for discussion with users - and provides some structure? May be too complicated at this stage)

LEPĀ Would hope could have drop down for Trusts, although may be 10s of GP practices - maybe have one of options 'GP Practice' and then further drop down if that selected?
SiteĀ As above - could be e.g. Princess Elizabeth Children's Hospital, Nantwich (as part of Royal Cheshire NHS Hospitals Trust - names made up by me!) Might want to flip these tow fields, as the Trust could auto-populate once site is entered (assuming unique site names)
DescriptionFree textThis is the detail of the incident, so may need to put guidance on what to include?
StatusĀ Resolved/Unresolved (may wish to use 'Open/Closed')
Anticipated date of resolutionĀ 

Not right wording for field

Should only appear if 'Open'

This is where can put date when investigation likely to be completed, e.g. could be date of Coroner's court etc. Probably need a notes box to describe why particular date selected

UpdateĀ Not sure what this will be, but need somewhere to add notes as more details known, e.g. progress of investigation

Closure information:

Closed by

Actions

Date

Ā 

Record of when incident is closed

May include details of ARCP review of incident and whether it can be archived or not

Additional informationLink to docs or description of where they are storedSomewhere to put link to original docs/attachments etc) - in v1 we won't be able to upload documents (see Reuben's message in Slack)

Related content

Case Management - CPPS User | Concerns Log Feedback
Case Management - CPPS User | Concerns Log Feedback
More like this
Existing tools and systems
Existing tools and systems
More like this
Case Management
Case Management
More like this
Incidents and concerns logging
Incidents and concerns logging
More like this
18/12/2017
More like this
Case Management - Existing Process | Background - East of England Case Study
Case Management - Existing Process | Background - East of England Case Study
More like this