Skip to end of metadata
  • Created by Former user , last modified on 01 Aug 2017
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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
Process NameT-1 New Registration - FURTHER DISCUSSION REQUIRED, maybe make this a sub-story of TIS-629Comments MVP
DescriptionUser 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.

ActorsTrainee 
Pre-ConditionsTBC
Post-ConditionsTrainee has access to new TIS system - login / logout capability 
Process Steps
  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.

Alternative FlowUser is registered from <another system> 
RulesTBC

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 ReferenceTIS-629Wider discussion necessary on whether this is a valid story, before writing a JIRA ticket
Audit LogTBC 


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

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

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?

ActorsTrainee 
Pre-Conditions

Trainee has been registered on system

Trainee has validated their registered details


Post-ConditionsTrainee is able to view the space 
Process Steps
  1. Traine 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

 
Rules
  • Error: Invalid email entered
  • Error: Incorrect password

JIRA ReferenceN/A 
Audit LogTBD 



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 
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 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 ReferenceTBD 
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
GMC Number
GMC 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, 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 view
  2. System presents summary information
  3. User selects to view detail
  4. System presents detail view
  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? 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 selects to leave Placement Detail view
  6. System presents summary view << is this correct?

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
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 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 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 (Synapse equivalence)
DescriptionUser is able to submit the form that will update their personal details with the GMC
ActorsTrainee 
Pre-ConditionsUser is logged in
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 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.

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.
 
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 XYZ
Actors

Trainee

GMC

 
Pre-Conditions

User is logged in

Form-R submission is imminent

Can this be submitted anytime? No it is usually requested by the local office prior to the ARCP, I think the timescales differ in different local offices.
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 together in their own space.

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 
JIRA ReferenceTIS-539 & TIS-92 
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?
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 draftIs this necessary? 
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 sentWhere is the result sent? 
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 
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 
Alternative FlowTBD 
RulesTBD 
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
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
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
 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 
Alternative FlowN/A 
RulesTBD 
JIRA ReferenceTBD 
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
  • No labels

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213