Feedback
- the name should be consistent with cases as is known now
- reporting is highly important
Cut Over from Intrepid - ConsderationsConsiderations
CPPS data will be part of the DR2 v2 data consolidation, so any cases currently sitting within the database will be available in the newly re-purposed Concerns Log
Russell Steel (Unlicensed) - do we have an up to date view on what's available re CPPS data?
| view-file | ||||
|---|---|---|---|---|
|
- Archiving of closed cases for former and newly created cases, how should these be managed?
- Handling of spreadsheet data for those who don't use intrepid currently - how can their cases be brought? Post MVP?
Concerns Log will need to change in the following ways
...
Concerns Log Screenshots
Suggested Scope of Change for Concerns Log is as follows:
- field labels & reference data - see field validation
- integrated reporting - see Reporting
- date of incident (non-mandatory) and date case raised (additional field)
- Add types - reference data tbc
- Source >> free text field
- employer at the time >> should be trust
- Trusts
- Non-hospital practices/sites
- Practices (NB: is this just another term for sites? Yes) Alistair Pringle (Unlicensed)
- Site >> remain as is
- Grade at the time >> remain as is
- Any other information required here? (see form templates) Alistair Pringle (Unlicensed) - please can you chase up sending the consolidated forms?
- detailed information >> no limit on free text
- contact person >> should be case manager name & email address
- submission of
- a request (front end) i.e needs to be accessible without login
- no validation required to confirm they are affiliated with the trainee in a meaningful way for HEE
- case related further information
Statuses of a case
- submitted, accepted, returned, under review, closed
- can the statuses trigger comms or suggest manual comms?
- Notifications sent where
- a new submission is received (HEE Cases Admin only)
- an update to a case is made (referrer)