Page Comparison

Since the scope of the Trainee View is limited to current functionality, the scope relating to Trainee JIRA tickets should be as follows:

Out of Scope:

Process Name	T-1 New Registration - FURTHER DISCUSSION REQUIRED, maybe make this a sub-story of TIS-629	Comments MVP
Description	User has the ability to register to use the TIS system directly	Is this a necessary story? Do trainees have the ability to request Intrepid access? Do we need same/separate login details for new TIS, so migration consideration? Trainees will not be requesting access we will send creds out as part of the onboarding process. We will have to consider how we migrate the current trainees onto TIS.
Actors	Trainee
Pre-Conditions	TBC
Post-Conditions	Trainee has access to new TIS system - login / logout capability
Process Steps	user register a username user sets password user sets security user validates details system shares	What interaction should this have with Admin UI? What are the back end implications? User able to change their password once logged in for the first time. User name will be email address. Processes to be done by the admins/system not the trainee.
Alternative Flow	User is registered from <another system>
Rules	TBC	Format of username? Email Validation of password? None What security should be implemented? There will be a trainee 'role' applied to all trainee users.
JIRA Reference	TIS-629	Wider discussion necessary on whether this is a valid story, before writing a JIRA ticket
Audit Log	TBC

...

	T-3 Trainee Logout	Comments MVP
Description	Trainee has the ability to logout of the system
Actors	Trainee
Pre-Conditions	Trainee has been registered on system Trainee has validated their registered details
Post-Conditions	Trainee leaves logged in view of system securely
Process Steps	Trainee selects to logout System logs user out System presents logged out view
Alternative Flow	N/A
Rules	N/A
JIRA Reference	N/A
Audit Log	TBD

...

Process Name	T-5 View & Edit Personal Details	Comments MVP
Description	User has the ability to view and update their own details
Actors	Trainee
Pre-Conditions	Trainee is logged in to their own account
Post-Conditions	Trainee can see currently stored details in an editable format Trainee can make and save changes to specified details System updates personal details centrally
Process Steps	User navigates to Personal Details space System presents personal details in editable view User makes changes to relevant fields System validates changes System saves changes	Relevant Fields: Surname Forenames Known As Maiden Name Title Telephone Mobile Email Address Address 1 Address 2 Address 3 Address 4 Post Code GMC Number GMC Status EEA Resident Permit to Work Settled Visa Issued Details/Number
Alternative Flow	N/A
Rules	View & Edit select fields, see data table
JIRA Reference	TIS-540, TIS-278
Audit Log	TBD

Process Name	T-6 View Programme	Comments MVP (Synapse equivalence?)
Description	User has the ability to view their Programme details
Actors	Trainee
Pre-Conditions	User is logged in	Is there a need for detailed Programme view? Not as such, the details of the Programme are the placements and assessments which we have considered.
Post-Conditions	System presents relevant detail
Process Steps	User navigates to summary view System presents summary information User selects to view detail System presents detail view User selects to leave Programme Detail view System presents summary view	Summary Fields Programme Name Curriculum Start Date End Date Managing Deanery Should user be presented with previous view or summary screen? View will show historical programmes, current and future programmes if applicable IO - this could be deemed as detailed information, rather than summary, but we should discuss it further with Steve & Alex
Alternative Flow	N/A
Rules	View only
JIRA Reference	TIS-684
Audit Log	TBD

...

Versions Compared