What are "concerns" in Horus?
Assessors/supervisors can raise concerns ("some concern" or "major concern") about a foundation doctor in the 7 assessment forms on Horus: Core Procedures; Self-TAB; TAB feedback form; PSG feedback form; CS end of placement report; ES end of placement report; ES end of year report
Foundation doctors, supervisors and administrators (as appropriate in each individual case) need to review any concerns raised and deal with them as required. In January 2019 a "concerns management" feature was added to Horus, to allow users to easily spot any forms where concerns have been raised and thereby support the relevant foundation doctor in a timely manner.
NOTE: Concerns raised in PSG feedback forms will not be labelled/'manageable' until later on in 2019.
How are "concerns" displayed in Horus?
Concerns are displayed on a number of Horus pages (visible to users with the relevant permission(s)):
- Admin menu > Foundation Doctors - next to the FD doctor's/NTG's name
- Trainer menu > Supervising - next to the FD's/NTG's name
- Portfolio > Contents - next to the form that contains the concern(s)
- Portfolio > Concerns - each concern is listed individually, grouped against the form in which it was raised
What should happen if a foundation doctor receives a "concern" in Horus?
The FP Curriculum 2016 and Foundation Operational Guide 2019, describe in detail how to manage foundation doctors (FDs) about whom concerns are raised. This section describes the administrative actions that can be taken in Horus if concerns are raised about a foundation doctor in one of the seven assessment forms.
IMPORTANT NOTE: The information below is not intended to be an educational support guide to managing concerns.
When a concern is raised in Horus, it will be visible to the FD/NTG, their supervisor(s), foundation programme director(s) and administration team (in the local postgraduate centre and in the local HEE office). See how concerns are displayed in Horus.
Once concerns have been discussed with the relevant FD/NTG and an action plan/resolution is agreed, the relevant supervisor or administrator should 'follow up' the concern(s) in the concerns management page.
- FD's/NTG's portfolio > Concerns (second option from the bottom)
- Select "View/Update" next to the relevant concern
- Enter notes (mandatory) - could be to describe the discussion, the action plan, the outcome; whatever is most useful to the individuals involved.
- Decide on a new status for the concern - your options are
To leave the concern as unresolved, don't check the box or enter a date to defer until - just select "Save Changes".
To resolve the concern, check the box next "Resolve this concern" and select "Save Changes".
To defer the concern, select a date from date widget next to "defer this concern until" and select "Save Changes".
Each 'follow up' is recorded as a separate entry against the concern. The latest follow up overrides the previous ones.
Who can 'manage' concerns in Horus?
Concerns can be managed by any user (except FDs/NTGs themselves) who has access to the portfolio item in which the concern was raised.
In effect this means any previous or current supervisor, foundation programme director or administrator (trust or foundation school).
All concerns management activity is logged in the FD/NTG's portfolio and can be viewed by all with authorised access (see above).
Is there a time limit to 'manage' concerns in Horus?
No, concerns can be 'managed' (that is, their status changed by adding a 'follow up') at any time.
Can a concern follow up be edited or deleted?
Currently, no - once you submit a concern 'follow up' it cannot be changed. It can always be overridden by a new follow up though.
April 2019: We are working on a process to manage submitted follow ups with significant errors (eg problematic typos) in them.
Why are some concerns marked as "auto-resolved"?
Concerns labelling and management functionality became available in HEE Horus in December 2018. All concerns raised since the launch of HEE Horus are now labelled, including any raised during the 2017-18 training year. To reduce administration time, we have marked all concerns raised in rotations ending before August 2018 as "auto-resolved". If required, these concerns can be 'opened' again.
Note that any rotations that started during 2017-18 but end during 2018-19 have not had their concerns auto-resolved.