Versions Compared

Version Old Version 20 New Version 21
Changes made by

Former user

Former user

Saved on

Key

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

Description

The Trainee User Interface (UI) is the web application HEE Trainees use to interact with TIS. It will be designed to prioritise mobile use ('mobile first design') and will function on larger screens.

This component includes stories covering generic elements, but doesn't include UI functions which are specific to a single component, e.g. Menus and Navigation stories can be found here, but the FormR self assessment would be found in the Assessments component.


Summary Page 
N/A MVP

Details
Personal Details
Programmes & Curricula
Placements 
Assessment Reviews
Form R (A / B)

...


T-3 Trainee LogoutComments MVP
DescriptionTrainee has the ability to logout of the system
ActorsTrainee 
Pre-Conditions

Trainee has been registered on system

Trainee has validated their registered details


Post-ConditionsTrainee leaves logged in view of system securely 
Process Steps
  1. Trainee selects to logout
  2. System logs user out
  3. System presents logged out view
 
Alternative FlowN/A 
RulesN/A 
JIRA ReferenceN/A 
Usage MonitoringTBD 

...

Process NameT-10 Submit Form-R (Part A)Comments MVP
DescriptionUser is able to submit the form that will update their personal details with the GMC
ActorsTrainee 
Pre-Conditions

User is logged in

Available to medical trainees only


Post-Conditions

User personal details are updated in TIS across all systems

User personal details are updated with GMC

 
Process Steps
  1. User navigates to Form R, Part A space
  2. System presents form in editable view
  3. System autopopulates relevant fields
  4. User makes changes to relevant fields
  5. System validates changes
  6. System saves changes
  7. User signs the form (to be confirmed whether this needs to be wet signed / digitally signed - AP)
  8. User selects to submit Form-R (Part A)
  9. Form-R (Part A) is sent to GMC

Manual Trigger perhaps more appropriate dependent on design.

Fields

  • forename
  • GMC registered surname
  • GMC number
  • Deanery / HEE local team
  • DOB
  • gender
  • immigration status
  • primary quaification
  • date awarded
  • Medical Scool
  • Home Add
  • Contact Tel
  • Contact Mob
  • Preferred email
  • Prog Spec
  • Spc 1 for Award of CCT (non-mand)
  • Spec 2 for Award pf CCT (opt)
  • Royal College/Faculty assessing training for the award of CCT
  • Anticiapted completion date f curr prog if known
  • Options - confirmations x6 (see data table
  • declaration of programme
Alternative FlowT-20 No submission of Form R (Part A)
Rules
  • Autopopulation will be required from personal details and other sections, where appropriate
  • Must be submitted for new trainees
 What's the deadline for submission by new trainees? Alistair Pringle (Unlicensed)
JIRA ReferenceN/A 
Audit LogTBD 


Process NameT-11 Submit Form-R (Part B)Comments MVP
DescriptionUser is able to submit the form to the GMC at the appropriate time annually
Actors

Trainee

GMC

 
Pre-Conditions

User is logged in

Form-R submission is imminent

Cannot be submitted at anytime, it is usually requested by the local office prior to the ARCP, I think the timescales differ in different local offices.

To be confirmed whether there is a trigger requirement in TIS for admins - IO

Post-ConditionsForm-R (Part B) is submitted 
Process Steps
  1. User navigates to Form R Part B space
  2. System presents form details in editable view
  3. User completes relevant fields
  4. System validates fields
  5. System saves changes
  6. User signs form (tbc as with Part A)
  7. User selects to submit Form-R (Part B)
  8. Form-R (Part B) is sent to GMC
  9. Historical view of submitted Form's updated

Unsure. May be best to keep both parts A&B together in their own space. Steve to confirm

Alternative FlowT-16 Save as draft before submissionYes i think the trainee should be able to save the form as they go or autosave as with other areas of the system.
Rules

Validation as per data table

  • Error message: cannot be edited once submitted, as no longer a draft
Rules around submission TBD - AP
JIRA ReferenceTIS-539 & TIS-92, story for save drafts 
Audit LogTBD 

...

Process NameT-16 Save as draft before submissionComments MVP 
DescriptionUser is able to draft and save the form, to come back to later
ActorsTrainee 
Pre-ConditionsLogged in
Post-ConditionsDraft saved and accessible to be completed later 
Process Steps
  1. User navigates to relevant form
  2. System presents form details in editable view
  3. User completes relevant fields
  4. System validates fields
  5. System saves changes
  6. User leaves relevant space without submitting the form
  7. System stores draft
 
Alternative FlowT-11, T10 
RulesTBD 
JIRA ReferenceTIS-539 & TIS-92 
Audit LogTBD 


Process NameT-17 Forgotten UsernameComments Out of scope, manual process
DescriptionUser has ability to login after they have forgotten their username
ActorsTrainee 
Pre-ConditionsUser is registered user
Post-ConditionsUser has a reminder of their username Not secure
Process Steps
  1. System User contacts HEE by telephone / email
  2. HEE provides username

Alternative FlowN/A 
RulesN/A 
JIRA ReferenceTBD 
Audit Log
 

...