Versions Compared

Version Old Version 14 New Version 15
Changes made by

TIS Surface Hub

TIS Surface Hub

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: ADD STEVE LIST EQUIVALENCE

...


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 
Audit LogTBD 

...

Process NameT-4 View SummaryComments Comments MVP
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?

Could be a judgement call from steve? I don't think we need it but i suppose that depends on the design. If we have historical and future information presented the summary could contain current details of placement, programme, assessment etc.

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
 
Alternative FlowN/A 
RulesValidation rules? 
JIRA ReferenceTBDActors

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 ReferenceNew story to be created 
Audit LogTBD 


Process NameT-5 View & Edit Personal DetailsComments MVP
DescriptionUser has the ability to view and update their own details
ActorsTrainee 
Pre-ConditionsTrainee 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
  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
  • View & Edit select fields, see data table

JIRA ReferenceTIS-540, TIS-278 
Audit LogTBD 

...

Process NameT-6 View ProgrammeComments MVP (Synapse equivalence?)
DescriptionUser has the ability to view their Programme details 
ActorsTrainee 
Pre-Conditions

User is logged in

Is there a need for detailed Programme view? Not as such, Not as such, the details of the Programme are the placements and assessments which we have considered.
Post-ConditionsSystem presents relevant detail 
Process Steps
  1. User navigates to summary programme view
  2. System presents summary information
  3. User selects to view detail
  4. System presents detail viewUser views Programme data
  5. User selects to leave Programme Detail view
  6. 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? 


Alternative FlowN/A 
Rules
  • View only
  • 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 FlowN/A 
Rules
  • View only
 
 
JIRA ReferenceTIS-684 
Audit LogTBD 

...

Process NameT-7 View PlacementComments MVP (Synapse equivalence)
DescriptionUser has the ability to view their Placement details 
ActorsTrainee 
Pre-ConditionsUser is logged in
Post-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 views Placement data
  6. User selects to leave Placement Detail viewSystem presents summary view << is this correct?

Fields

Start Date
End Date
Site
Grade
Specialty
Placement type


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

...

Process NameT-8 View AssessmentComments MVP
DescriptionUser has the ability to view their Assessment details 
ActorsTrainee 
Pre-ConditionsUser is logged in
Post-ConditionsSystem presents relevant detail 
Process Steps
  1. User navigates to summary Assessment view
  2. System presents summary information
  3. User selects to view detail
  4. System presents detail viewUser views assessment data 
  5. User selects to leave Assessment Detail viewSystem presents summary view 

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 assessments
 
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 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 Personal Details Form R, Part A space
  2. System presents personal details form in editable view
  3. User makes 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)
  8. User selects to submit Form-R (Part A)
  9. Form-R (Part A)
  10. 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.
  1. 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.

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 FURTHERA)
Rules
  • Autopopulation will be required from personal details and other sections, where appropriate.
 
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 GMC 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.

IO to check whether there is a trigger requirement in TIS for admins

Post-ConditionsForm-R (Part B) is submitted 
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 Form-R (Part B)
  7. Form-R (Part B) is sent to GMC
  8. 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.
Rules

Validation as per data table

 
  • Error message: cannot be edited once submitted, as no longer a draft
Rules around submission TBD
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 in
Post-ConditionsOOP 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-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?
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 space
  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 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 MVP - out 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-Conditions

Post-Conditions
 
Process Steps
  1. System User contacts HEE by telephone
  2. HEE tells them over the phone
 What's the best process here?
Alternative Flow
 
Rules
 
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 StepsTBD
  1. user selects password reminder
  2. new password sent to registered email address
  3. user logs in using password sent
 
Alternative FlowN/A 
RulesTBD
  • no validation
 
JIRA ReferenceTBD 
Audit LogTBD 

...