Versions Compared

Version Old Version 8 New Version 9
Changes made by

Alistair Pringle (Unlicensed)

Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Process NamePL2 - SearchComments
DescriptionUser should be able to find placement details by searching for a person or post number
ActorsHEE Admin
Pre-Conditions

Logged in

Security allows access to Posts, People or Placement Manager 


Post-Conditions

User is able to find specified data around a Placement

User is told there are no details related to their particular search


Process Steps
  1. User navigates to either Person, Posts areas
  2. User enters search criteria (First Name, Last Name, GMC Number, GDC Number, Healthcare Number, Programme Name, Programme Number)
  3. User confirms search
  4. System presents results as list

Alternative FlowN/A
RulesUsual search rules apply
JIRA Reference

Audit Log


Process NamePL3 - Create Placement from Person RecordComments
DescriptionUser can create placement related to an individual person
ActorsHEE Admins
Pre-Conditions

Logged in

Security allows access to Posts, People or Placement Manager 

Person search completed
Post-Conditions

Placement created for a single individual

Placement confirmed to relevant Trust


Process Steps
  1. select person
  2. system presents form with the following details: first name, last name, address, past/current/future placements (if applicable), programme name, curricula names, curricula start date, curricula end date
  3. user completes relevant fields
    1. post number
    2. post details  
    3. placement start date
    4. placement end date
    5. placement type
    6. honorary << TBC by Alistair Pringle (Unlicensed)
    7. WTE 
    8. clinical supervisor name
    9. educational supervisor name
    10. MIP
  4. User saves record
  5. Confirmation of placement is recorded against Trainee record
  6. Confirmation of placement is sent to relevant Trust (i.e. where the placement will be completed)

Placement record to include:

  • start date
  • end date
  • site
  • grade
  • specialty
  • placement type
  • status

Post Details to be pre-populated:

  • site,
  • managing deanery,
  • grade,
  • specialty,
  • local post number,
  • training description
Alternative Flow

PL4 - Create Bulk Placements

PL6 - Manage Multiple Placements


Rules

WTE default is 1

WTE - warn user that if the role is a slot share, they should add 10%

MIP default 0 on create


JIRA Reference

Audit Log

...

Process NamePL4 - Create Bulk PlacementsComments
DescriptionUser can create placement related to a group of people
ActorsHEE Admin
Pre-conditions

Logged in

Security allows access to Placement Manager 


Post-conditions

Placement created for a group of individuals

Placement confirmed to relevant Trust


Process steps
  1. Access bulk upload screen
  2. Download spreadsheet
  3. User completes spreadsheet
  4. Upload completed spreadsheet
  5. User saves record
  6. Confirmation message is displayed on screen
  7. Confirmation of placement is recorded against Trainee record
  8. Confirmation of placement is sent to relevant Trust (i.e. where the placement will be completed)

Column headers on spreadsheet

= PL3, step 3

  • post number
  • post details  
  • placement start date
  • placement end date
  • placement type
  • honorary << TBC by Alistair Pringle (Unlicensed)
  • WTE 
  • clinical supervisor name
  • educational supervisor name
  • MIP
Alternative flowPL10 - Upload Errors
Rules

Only template spreadsheet can be used

All fields must be completed with a valid response


JIRA Reference

Audit Log

...

Process NamePL6 - Manage Multiple PlacementsComments
DescriptionUser can link / unlink posts for multiple trainees to create multiple placements in one view
ActorsHEE Admin
Pre-conditions

Logged in

Security allows access to Placement Manager 


Post-conditions

Placement created for a group of individuals

Placement confirmed to relevant Trust


Process steps
  1. Navigate to Placement Manager
  2. View List of Posts & List of Trainees
  3. Select Programme (optional)
  4. Select Rotation(s) (optional)
  5. Add Posts to manage to shortlist
  6. Add Trainees to manage to shortlist
  7. Link Trainee to Post = Placement
  8. Go into detail view of Placement
  9. Edit placement detail (as in PL3, step 3)

Rotations can be created in Person Programme TBC


Posts detail in view

  • post name
  • site
  • specialty

Person detail in view

  • First name
  • Last name
  • GMC/GDC/Healthcare Number
  • In Post / Not in Post
Alternative flow

Rules

Trainees and Posts avaiable should be constrained to the local view only

Filter out "trainees in post"

IO - Is this true?

AP - it's likely that admins will want only to view the posts that they are responsible for making placements in.

JIRA Reference

Audit Log



Process NamePL7 - Unlink PlacementComments
DescriptionUser is able to remove Person from a Placement with immediate effect
ActorsHEE Admin
Pre-conditions

Logged in

Security allows access to People, Posts, Placement Manager 


Post-conditionsUser is removed from Placement
Process steps
  1. User navigates to Person record
  2. User selects to unlink placement record
  3. Placement is terminated
  4. Post becomes available again
  5. Trainee becomes available to be placed again
  6. Trust is sent a message to confirm that the Trainee has been removed from Post

all this detail is specified in the ESR guide I believe. We do not have jurisdiction over the data transfer as I believe it was agreed with trusts. their change process is basically non-existent.



Alternative flowPL9 - Placement Ends
Rules

JIRA Reference

Audit Log

...

Process NamePL8 - Manage Placements with Slot ShareComments
DescriptionUser can view and edit current/future placement data already created; specifially related to Slot Share details

Not sure we need this as a separate scenario. Unless we go down the route of outlining every possible type of placement etc? 

IO: It was so that the detail around the timing could be highlighted - it will still sit within create / edit stories

ActorsHEE Admin
Pre-conditions

Logged in

Security allows access to People, Posts, Placement Manager 


Post-conditionsUser edits slot share information in placement detail (current / future)
Process steps
  1. Begin Create or Edit journey (PL4 or PL5)
  2. Mark WTE as 0.6
  3. Continue Create or Edit journey

Alternative flowN/A
Rules

Slot share must always be 0.5 + 0.1 for both trainees sharing a single slot (to account for handover time)

System prevents user from editing past placement detail


JIRA Reference

Audit Log

...