Versions Compared

Version Old Version 11 New Version Current
Changes made by

Alistair Pringle

Former user

Saved on

Key

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

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

  • TIS-540
  • TIS-684
  • TIS-681
  • TIS-539
  • TIS-683
  • TIS-92
  • TIS-682
  • TIS-278 << NOT REQUIRED, REMOVED FROM JIRA
  • NEW STORY REQUIRED - support 
  • NEW STORY REQUIRED - form R, part A

Out of Scope:

  • TIS-193
  • TIS-196
  • TIS-200
  • TIS-20
  • TIS-171
  • TIS-174
  • TIS-319

...

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.

...

  1. user register a username
  2. user sets password
  3. user sets security
  4. user validates details
  5. 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.

...

Format of username? Email

Validation of password? None

What security should be implemented? There will be a trainee 'role' applied to all trainee users.

...

Will they be able to use their old details, or have to re-register?

I expect all trainees will require new login credentials but they will not have to interact with us 

They won't need to re register. I imagine we will setup all trainees with a profile in TIS and send out creds via email.

What about users transitioning from Synapse? What will happen to details there?

...

Trainee has been registered on system

Trainee has validated their registered details

...

  1. Traine enters username
  2. Trainee enters password
  3. System validates details
  4. System presents logged in view of system

...

T-17 Forgotten Username

T-18 Forgotten Password

T-19 Username / Password Error

...

  • Error: Invalid email entered
  • Error: Incorrect password

...

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)



Since the scope of the Trainee View is limited to current functionality of Intrepid (and to a lesser extent Synapse), the scope relating to Trainee JIRA tickets should be as follows: 

  • TIS-540
  • TIS-684
  • TIS-681
  • TIS-539
  • TIS-683
  • TIS-92
  • TIS-682
  • TIS-278 << NOT REQUIRED, REMOVED FROM JIRA
  • NEW STORY REQUIRED - support 
  • NEW STORY REQUIRED - form R, part A

Out of Scope:

  • TIS-193
  • TIS-196
  • TIS-200
  • TIS-20
  • TIS-171
  • TIS-174
  • TIS-319


Process NameT-1 New RegistrationComments MVP - move to Admin UM
DescriptionAdmin has the ability to register a user to use the TIS system

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.

ActorsAdmin 
Pre-ConditionsTrainee must have registered via Oriel to a particular region
Post-ConditionsTrainee has access to new TIS system - login / logout capability 
Process Steps
  1. Import trainees from Oriel
  2. Trigger welcome message send -  inform trainees of what TIS is about, support, login details to follow
  3. Trigger credentials send

Admins should be able to trigger welcome message, credentials message, oriel manual upload

User able to change their password once logged in for the first time. User name will be email address.

Alternative Flow

Non-oriel import (Dentists / Other Academic Trainees)

 
Rules
  • Username format: valid email address
  • No account validation
  • Password to be autogenerated
  • All users given appropriate access for "Trainee" role

JIRA ReferenceTIS-629
Monitoring

No need to report on this

 Oriel upload to be considered separately


Process NameT-2 Trainee Login Comments MVP
DescriptionTrainee has the ability to login using the details they were registered for the service with

I expect all trainees will require new login credentials but they will not have to 'register' as we will send out logins as and when we migrate trainees to TIS.

The process will be the same for Synapse users as they are transitioning from one system to another.

ActorsTrainee 
Pre-Conditions

Trainee has been registered on system


Post-ConditionsTrainee is able to view the login space 
Process Steps
  1. Trainee enters username
  2. Trainee enters password
  3. System validates details
  4. System presents logged in view of system
 
Alternative Flow

T-17 Forgotten Username

T-18 Forgotten Password

T-19 Username / Password Error

T-XX: update login details

 
Rules
  • Error: Invalid email/password entered

JIRA ReferenceN/A to be created 
Usage Monitoring

No users logging in

Further discussion required

 



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-4 View SummaryComments MVP
DescriptionTrainee has the ability to view the summary screen
Actors

Trainee

System

 
Pre-ConditionsTrainee is logged in
Post-Conditions

Summary details in view

Navigation menu available

 
Process Steps
  1. User logs in
  2. System presents summary
  3. User navigates through view

 Fields displayed

  • Current Placement End Date & Site (Steve to confirm)
  • Next Placement Start Date & Site (Steve to confirm)
Alternative FlowN/A 
Rules
  • Read only
 
JIRA ReferenceTIS-704 
Audit LogTBD 


Process NameT-5 View & Edit Personal DetailsComments MVP
DescriptionUser has the ability to view and update their own details
ActorsTrainee 
Pre-ConditionsTrainee
has been registered on systemTrainee has validated their registered details
is logged in to their own account
Post-Conditions

Trainee

leaves logged in view of system securely Process Steps
  1. User logs in
  2. System presents summary
  3. User navigates through view
 

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
  1. Trainee selects to logout
  2. System logs user out
  3. System presents logged out view
 Alternative FlowN/A RulesN/A JIRA ReferenceN/A Audit LogTBD Process NameT-4 View SummaryComments DescriptionTrainee has the ability to view the summary screen

AP - Not sure summary screen is required as information presented is not extensive.

IO - will there be anything to display?

MVP?

Actors

Trainee

System

 Pre-ConditionsTrainee is logged inPost-Conditions

Summary details in view

Navigation menu available

  
  1. User navigates to Personal Details space
  2. System presents personal details in editable view
  3. User makes changes to relevant fields
  4. System validates changes
  5. 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

Non-editable (editable by central admin team)
GMC / GDC Number
GMC / GDC Status
EEA Resident
Permit to Work
Settled
Visa Issued
Details/Number


Alternative FlowN/A 
Rules
Validation rules?
  • View & Edit select fields, see data table

JIRA Reference
TBD
TIS-540, TIS-278 
Audit LogTBD 


Process NameT-
5 View & Edit Personal DetailsComments
6 View ProgrammeComments MVP
DescriptionUser has the ability to view
and update
their
own details
Programme details 
ActorsTrainee 
Pre-Conditions
Trainee

User is logged in

to their own accountSystem updates personal details centrally

Not as such, the details of the Programme are the placements and assessments which we have considered.
Post-Conditions

Trainee can see currently stored details in an editable format

Trainee can make and save changes to specified details

System presents relevant detail 
Process Steps
  1. 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
    1. programme view
    2. User views Programme data
    3. User selects to leave Programme Detail view
    4. System presents summary view 

    Fields

    • Programme Name
    • Curriculum
    • Start Date
    • End Date
    • Managing Deanery


    Alternative FlowN/A 
    Rules
    • View only
    • View will show historical programmes, current and future programmes if applicable
    		 
    Rules
    • View & Edit select fields, see data table
    JIRA ReferenceTIS-
    540, TIS-278
    684 
    Audit LogTBD 


    Process NameT-
    6
    7 View
    Programme
    Placement
    Comments 
    Comments MVP
    (Synapse equivalence?)
    DescriptionUser has the ability to view their
    Programme
    Placement details 
    ActorsTrainee 
    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.
    User is logged in
    Post-ConditionsSystem presents relevant detail 
    Process Steps
    1. User navigates to summary view
  • System presents summary information
  • User selects to view detail
  • System presents detail view
    1. User views Placement data
    2. User selects to leave
    Programme
    1. Placement 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

    Date
    Site
    Grade
    Specialty
    Placement type


    Alternative FlowN/A 
    Rules
    • View only
    • Detailed view should present historical, current and future placements
    		 
    JIRA ReferenceTIS-
    684
    681 
    Audit LogTBD 


    Process NameT-
    7
    8 View
    Placement
    AssessmentComments
    MVP (Synapse equivalence)
    MVP
    DescriptionUser has the ability to view their
    Placement
    Assessment details 
    ActorsTrainee 
    Pre-ConditionsUser is logged in
    Post-ConditionsSystem presents relevant detail 
    Process Steps
    1. User navigates to
    summary
    1. Assessment view
  • System presents summary information
  • User selects to view detail
  • System presents detail view
    1. User views assessment data 
    2. User selects to leave
    Placement
    1. Assessment Detail view
  • System presents summary view << is this correct?
    • Start Date
    End Date
    Site
    Grade
    Specialty
    Placement type

    Fields

    Review (date)
    Curriculum Assessed
    Outcome
    Grade at Time
    Period From
    Period To


    Alternative FlowN/A 
    Rules
    • View only
    • Detailed view should present historical, current and future
    placements
    • assessments
    		 
    JIRA ReferenceTIS-
    681
    705 
    Audit LogTBD 


    Process NameT-
    8 View AssessmentCommentsDescriptionUser has the ability to view their Assessment details ActorsTrainee Pre-ConditionsUser is logged inPost-ConditionsSystem presents relevant detail Process Steps
    1. User navigates to summary view
    2. System presents summary information
    3. User selects to view detail
    4. System presents detail view
    5. User selects to leave Assessment Detail view
    6. System presents summary view 

    Review (date)
    Curriculum Assessed
    Outcome
    Grade at Time
    Period From
    Period To

    Alternative FlowN/A Rules
    • View only
    • Detailed view should present historical, current and future assessments
     JIRA ReferenceTBD Audit LogTBD Process NameT-9 View CoursesCommentsDescriptionUser has the ability to view their Course details Do we need this as part of the MVP? Joanne Watson (Unlicensed)ActorsTrainee Pre-ConditionsUser is logged inPost-ConditionsSystem presents relevant detail What details can be seen?Process Steps
    1. User navigates to summary view
    2. System presents summary information
    3. User selects to view detail
    4. System presents detail view
    5. User selects to leave Course Detail view
    6. System presents summary view 
     Should there be a summary view of courses?Alternative FlowT-19 Book Course Is this necessary for MVP?RulesView Only JIRA ReferenceTBD Audit LogTBD Process NameT-10 Submit Form-R (Part A)Comments MVP (Synapse equivalence)DescriptionUser is able to submit the form that will update their personal details with the GMCActorsTrainee Pre-ConditionsUser is logged inPost-Conditions

    User personal details are updated in TIS across all systems

    User personal details are updated with GMC

     Process Steps
    1. User navigates to Personal Details space
    2. System presents personal details in editable view
    3. User makes changes to relevant fields
    4. System validates changes
    5. System saves changes
    6. User selects to submit Form-R (Part A)
    7. Form-R (Part A) is sent to GMC
    Should this be a manual trigger or automated whenever personal details are updated? Manual Trigger perhaps more appropriate dependent on design.
    9 View CoursesComments
    DescriptionUser has the ability to view their Course details Do we need this as part of the MVP? Joanne Watson (Unlicensed)
    ActorsTrainee 
    Pre-ConditionsUser is logged in
    Post-ConditionsSystem presents relevant detail What details can be seen?
    Process Steps
    1. User navigates to summary view
    2. System presents summary information
    3. User selects to view detail
    4. System presents detail view
    5. User selects to leave Course Detail view
    6. System presents summary view 
    		 Should there be a summary view of courses?
    Alternative FlowT-19 Book Course Is this necessary for MVP?
    RulesView Only 
    JIRA ReferenceTBD 
    Audit LogTBD 


    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 HEE Admins

    		 
    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 
    8. User selects to submit Form-R (Part A)
    9. Form-R (Part A) is sent to HEE Admins
    10. Historical view of submissions is updated

    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)Only relevant if the Part A submission is automated - TO BE DISCUSSED FURTHER
    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 (Synapse equivalence)
    DescriptionUser is able to submit the form that will XYZto the Admins at the appropriate time annually
    Actors

    Trainee

    GMC

    		 
    Pre-Conditions

    User is logged in

    Form-R submission is imminent

    		Can this

    Cannot be submitted at anytime

    ? No

    , 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 XXX space 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. fields
    7. System saves changes
    8. User signs form (tbc as with Part A)
    9. User selects to submit Form-R (Part B)
    10. Form-R (Part B) is sent to GMCAdmin UI
    11. Historical view of submitted Form's updated
    Where should this be located? Alongside Assessments, or in it's own area?

    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 submissionAre drafts possible? Yes i think the trainee should be able to save the form as they go or autosave as with other areas of the system.RulesValidation as per data table 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-12 Submit OOPComments
    DescriptionUser is able to submit their OOP request digitally from end to end
    ActorsTrainee 
    Pre-ConditionsLogged inAny others?
    Post-ConditionsOOP form submitted Where is the result sent?OOP form submitted

     Where is the result sent?

    Administrator will need to receive the form in order for it the details to be checked and the application either accepted or denied by the designated authority (Dean or deputy)

    Process Steps
    1. User navigates to XXX space
    2. System presents form details in editable view
    3. User completes relevant fields
    4. System validates fields
    5. System saves changes
    6. User selects to submit OOP request
    7. OOP request is sent to XXX
    8. Historical view of submitted Form's updated
    		 
    Alternative FlowSave draft

    Is this necessary? 

    Yes

    RulesTBD 
    JIRA ReferenceTBD 
    Audit LogTBD 

    ...

    Process NameT-13 Submit LTFTComments
    DescriptionUser is able to submit their LTFT request digitally from end to end
    ActorsTrainee 
    Pre-ConditionsLogged in
    Post-ConditionsLTFT request sent

    Where is the result

    sent? 

    sent? 

    Administrator will need to receive the form in order for it the details to be checked and the application either accepted or denied by the designated authority (Dean or deputy)

    Process Steps
    1. User navigates to XXX space
    2. System presents form details in editable view
    3. User completes relevant fields
    4. System validates fields
    5. System saves changes
    6. User selects to submit LTFT request
    7. LTFT is sent to XXX
    8. Historical view of submitted Forms updated
    		 
    Alternative FlowN/A 
    RulesTBD 
    JIRA ReferenceTBD 
    Audit LogTBD 

    ...

    Process NameT-14 Submit ExpensesComments
    DescriptionUser is able to submit their Expenses request digitally from end to end
    ActorsTraineeAny others? 
    Pre-ConditionsLogged in
    Post-ConditionsExpenses form submittedWhere do they receive outcome / follow up? 
    Process Steps
    1. User navigates to XXX space
    2. System presents form details in editable view
    3. User completes relevant fields
    4. System validates fields
    5. System saves changes
    6. User selects to submit expenses request
    7. Expenses are sent to XXX
    8. Historical view of submitted Forms updated
    		 
    Alternative FlowN/A 
    RulesTBD
    • can be edited any number of times
    • Error message: cannot be edited once submitted, as no longer a draft
    		 
    JIRA ReferenceTBD 
    Audit LogTBD 

    ...

    Process NameT-15 Access Help & Support - TO BE DISCUSSED FURTHERComments MVP?
    DescriptionUser is able to access technical and administrative support for their journey through the applicationThe extent to which this occurs is down to scope considerations - how is it done now, what plans are there for future?is able to access technical and administrative support for their journey through the application
    ActorsTrainee 
    Pre-ConditionsTBD
    Post-ConditionsTBD 
    Process StepsTBD  Display phone number & email address
    Alternative FlowTBD 
    RulesTBD
    • display contact details as per local office where they were registered OR
    • display central contact details (if available)
    		 
    JIRA ReferenceTBD 
    Audit LogTBD 

    ...

    Process NameT-16 Save as draft before submissionComments MVP 
    DescriptionUser is able to draft and save the form that will XYZConfirm purpose of 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 XXX spacerelevant 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 XXX 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 MVPOut of scope, manual process
    DescriptionUser has ability to login after they have forgotten their usernameIs there an admin process to support where this does not work?
    ActorsTrainee 
    Pre-ConditionsUser is registered user
    Post-Conditions User has a reminder of their username Not secure
    Process Steps What's the best process here?
    1. System User contacts HEE by telephone / email
    2. HEE provides username

    Alternative FlowN/A 
    RulesN/A 
    JIRA ReferenceTBD 
    Audit Log
    		 

    ...

    Process NameT-18 Forgotten PasswordComments MVP
    DescriptionUser has ability to login after they have forgotten their passwordHow is this to be achieved? Password reminder v password change? Additional security required?
    ActorsTrainee 
    Pre-ConditionsUsername recognisedIs this valid? Or should email be sent regardless - (a) warn that an attempt was made and (b) prompt password reset?
    Post-ConditionsView Posts landing page Process StepsTBDUser is able to login succesfullyNot secure
    Process Steps
    1. User selects password reminder
    2. New password is autogenerated
    3. New password is sent to registered email address
    4. User logs in using password sent
    		 
    Alternative FlowN/A 
    RulesTBD
    • no validation
    		 
    JIRA ReferenceTBD - new story 
    Audit LogTBD 


    Process NameT-19 Book CoursesComments
    DescriptionUser has the ability to book new Courses Do we need this as part of the MVP? Joanne Watson (Unlicensed)
    ActorsTrainee 
    Pre-ConditionsUser is logged in
    Post-ConditionsSystem presents relevant detail What details can be seen?
    Process Steps
    1. User navigates to summary view
    2. System presents summary information
    3. User selects to view detail
    4. System presents detail view
    5. User selects to book Course
    6. System presents Booking view 
    		 
    Alternative FlowT-9 - View Course ??
    RulesValidation Rules? 
    JIRA ReferenceTBD 
    Audit logTBD


    **New SCENARIO - manual completion & submission of form R**