People - Bulk import scenarios

Scope

Ability to bulk import people via spreadsheet
Ability to manage oriel import of trainees before bulk creating/committing them into TIS

Bulk import scenarios

Process Name	PP6 - Bulk Upload of People	Comments
Description	A user should be able to add a list of individuals to create multiple person records in one go
Actors	Local office admin
Pre-conditions	Logged in Authorised User
Post-conditions	Searched for person in entire database
Process steps	Upload spreadsheet System validates spreadsheet System creates new records based on spreadsheet values 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) Fields People - Field Validation has a spreadsheet (bottom of page) that shows the fields
Alternative flow	PP5 - 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.
JIRA Reference	TIS-642
Audit Log	Who created the people record and when	Log changes to any of the field values and when and who made the changes. Visually presented to all

Process Name	PP7 - Manage Oriel Import of Trainees	Comments
Description	Users should be able to view a summary of recently imported trainee person records and edit the contents of each one	Note of caution - the reference data in Oriel does not always match the values in Intrepid. i.e. For the specialty if the Oriel value is "General Medicine" and the Intrepid value is "General (internal) Medicine", this data will not be updated automatically. This is the same for all reference data such as Title, Country, Grade, NTN, Nationality, etc. Trainees may already exist on the Intrepid and therefore the existing record will be update
Actors	Local office admin
Pre-conditions	Logged in Authorised User
Post-conditions
Process steps	Validate that the trainees on the list are new starters in the local office Add mandatory fields Add additional required data (if available) e.g. NTN Authorise import of trainee details from Oriel into TIS Confirmation received of successful import	How do you currently view/edit import errors? Joanne Watson (Unlicensed) Need to check this with colleagues who use the Oriel import
Alternative flow	PP6-Bulk upload of People
Rules	Update (do not create) when a person's record already exists in the database	Where mandatory fields are not completed at time of import suggest a quality dashboard/data extract be produced to indicate the missing values in each person record
JIRA Reference	TIS-715
Audit Log	Who created the people record and when	Log changes to any of the field values and when and who made the changes. Visually presented to all

For discussion and assumptions

#	Question	Comments
1	Where do you envisage the Oriel Bulk import navigation to be?
2	How do you envisage the data manipulation page of the oriel import to be like before creating them on TIS and what fields Should be made available on that page?
3	What are the necessary validation rules for bulk import?
4	Should TIS allow more than one trainees with the same GMC/GDC/PH number to be created within TIS? If not, then editing of 2 records on TIS to have the same GMC number should also not be allowed.
5	Should the interface where you do the data manipulation allow records/rows that pass validation to be created even though the lot may have rows that fail validation?
6	What are the filters that should be available on the import interface to facilitate the import? E.g. improt by Local Office, or Programme.
7	Are the programmes created on intrepid ahead of the trainees being imported from Oriel?	So that the admin can then choose a Programme to import trainees against.
8	When do recruitment admins on Oriel enable the ‘extract trainees to intrepid’?	Is it at the end of the recruitment process when offers end?