Versions Compared

Key

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

...

Process NamePP6 - Bulk Upload of PeopleComments
DescriptionA user should be able to add a list of individuals to create multiple person records in one go
ActorsLocal office admin
Pre-conditionsLogged in
Authorised User

Post-conditionsSearched for person in entire database
Process steps
  1. Upload spreadsheet
  2. System validates spreadsheet
  3. System creates new records based on spreadsheet values
  4. System presents a list of newly created records for review/update

From People - Field Validation  (when creating a person record only the fields in Personal and Contact and (for a trainee) Programme are required)Which fields are required in spreadsheet?

Fields

People - Field Validation has a spreadsheet (bottom of page) that shows the fields How should upload errors be handled? 


Alternative flowPP5 - Create person (single)
Rules

Error: this GMC/GDC/Public Health number is already held by a person on this database

Error: mandatory fields not completed

Error message appears to let the operator know what the reasons for non import are. The errors should be corrected on the import spreadsheet before the import function is tried again.  It is possible to select records to be imported if some of the records are correct but the best course of action is to correct all inaccuracies and import the entire spreadsheet in one go.

The total number of records that have been imported is shown to the operator.

Mandatory fields should be defined on the import spreadsheet to avoid the non import of records.

Alternative flowPP5 - Create person (single)Rules

Error: this GMC/GDC/Public Health number is already held by a person on this database

Error: mandatory fields not completedrecords.

JIRA ReferenceTIS-642
Audit LogWho created the people record and whenLog changes to any of the field values and when and who made
the changes.
Visually presented to all

...

Process NamePP9 - Leaver process - Need to agree process for making records inactive - with SMLsComments
DescriptionUsers are able to reflect in a trainee's record that they have left their training programme (non-completion of programme and completion of programme)Question for SMLs is 'how can we show that a trainee has left their training programme without completing/achieving their CCT?. 
ActorsLocal office and trust admins (depending on the local office arrangements for managing FP trainees)
Pre-conditionsLogged in
Authorised User

Post-conditionsNavigated to trainee record
Process steps
  1. Follow process for 'remove person from programme'
  2. Automate function to allow a record to be set to 'inactive' wef the Programme End date.
Need to agree this with SMLs
Alternative flowN/A
Rules

JIRA ReferenceTIS-211, TIS-216
Audit LogLog changes to any of the field values and when and who made
the changes.
Visually presented to all

...

Process NamePP10 - Reporting  Need to agree reporting functionsComments
DescriptionUsers should be able to configure and pull a report directly from TIS relating to specific requirements
  • Aggregated Trainee Data - TIS-363
  • Trainee Attrition - TIS-298  (a subset of TIS-363)
  • Trainees per Discipline - TIS-362 (a subset of TIS-363)

Dependency on Workshop to be held with Joanne, Ray & Rob

ActorsAdmins
Pre-conditionsLogged in
Authorised User

Post-conditions

Process steps

Alternative flow

Rules

JIRA Reference

Audit Log


Process NamePP-11 Review Trainee HR Details
Comments
DescriptionAdmin access to Trainee HR details to support Related to TIS-37 however this may be an information sharing requirement, rather than a functional requirement for TIS - TO BE DISCUSSED

Actors

Pre-Conditions

Post Conditions

Process Steps

Alternative Flow

Rules

JIRA Reference

Audit Log

...