Skip to end of metadata
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 19 Next »

Page content:

User stories (BA's/PO)

This is what came out of a session between PO and BA’s to flesh out high-level stories off the back of the documented pages. These might need to be further refined and broken down on to smaller stories by devs.

Item no.

Feature

User Story

Acceptance Criteria

1.

Profile

As a Trainee
I want to receive my sign in details via email with clear instructions
So that I have access to TIS and know what to use it for

  • Login details created

  • Login details sent via email

  • Clear instructions on the email

  • What is TIS for, what sort of information they can access?

  • Consent to Cookie & Privacy Policy (TISNEW-3145)

As a Trainee
I want to be able to reset my password
So That I can access my account if I forget my password

As a Trainee
I want to have access to my personal details
So That I have one place to verify accuracy of my details.

Personal details:

Trainee UI - Field Validation#FieldValidation-1.PERSONALDETAILS

AA: *No NI in the list *???

AR: This is not training information although we store it in the BE for the sole purpose of sending and enriching ESR NI information. Need to question this as to why should we and whether we can make it visible on TIS Admin UI and eventually Trainee UI.

https://hee-tis.atlassian.net/browse/TISNEW-3670

https://hee-tis.atlassian.net/browse/TISNEW-3671

2.

Programme and Curricula

As a Trainee
I want to be able to see my current and future Programme and curriculum membership I am training on
So That I can ensure placement details against the programme are accurate

https://hee-tis.atlassian.net/wiki/spaces/NTCS/pages/713621525/Concept+design?preview=/713621525/1358037022/Screenshot%202019-10-25%20at%2010.43.19.png

https://hee-tis.atlassian.net/browse/TISNEW-3810?src=confmacro

3.

Placements

As a Trainee
I want to have visibility of my placements and rotations information
So That I can ensure placement details are accurate and I have a way of knowing where I am going to be training next

UX: Initial Discovery from 2017 (Steve)

TIS Trainee UI - Log in, Placements - Mobile & Desktop

https://hee-tis.atlassian.net/browse/TISNEW-3811

4.

Assessments

As a Trainee
I want to have visibility of my assessments including upcoming ones
So That I can ensure I have the essential documents for my next ARCP and track my progression.

5.

FormR

As a Trainee
I want to be able to complete my Form R Part A electronically
So that I can submit it easily and in time for registration purposes and reconfirm my details

As a Trainee
I want to be able to complete my Form R Part B electronically
So that I can submit it easily and in time for my Assessment

Acceptance criteria similar for both:

  • Form R Part A and B (and similar forms for non-medical trainees) available to complete and submit electronically

  • Available on mobile or computer

  • Pre-populated fields and options relating to trainee (e.g. should only be able to select placements relevant to their specialty - with override option for special cases)

    • Note: This information is not going to update TIS details initially but held separately for the trainee UI.

    • Where reference data is being updated, ensure drop-downs are provided

  • Electronic signature or validation via log in credentials

  • User can edit information on Trainee Record to update Form R details. Trainee-UI considerations - Will be overwritten by bi-directional ESR.

  • User can add, edit and save multiple declarations to a Form R before submission

  • User can review Form R before submitting, and go back and edit Form R information

  • Upon submitting Form R is not editable and a date stamp is added

Field validation:

UX: Initial Discovery from 2017 (Steve)

TIS Trainee UI - Form design, menu - Mobile & Desktop

Does the submitted Form Rs need to be kept as a record accessible to TIS admins?

If so in what format and how do they access it? (e.g. does it need to be PDF’d as a record within Documents or a Trainee?

Admin Side:

As an Admin
I want to be able to access submitted Form R's and unlock/unsubmit them
So that a trainee can make changes and re-submit their Form/s

  • Ability to access and unlock/unsubmit a Form-R for re-submission

  • Form R part b is linked to an Assessment

  • Form R part A is linked to a Programme membership

Look at Foundation Form R’s and align where possible.

Trigger:

  • Programme membership start date? - > Part A

  • Assessment dates? - >Part B

6.

Notifications

As a Trainee

I want to be able to flagging up if something is not correct or something has changed to TIS Admins

So that TIS/ESR admin can update with correct information

  • Profile Notification

  1. Links

  2. Prompt

  3. Acceptance/decline

  4. Interactive

As a TIS Admin

I want to be able to set Notifications to alert Trainees about there ARCP/forms

So that Trainees can be reminded about ARCP and scheduling this in Calendars

  • Assessment - Mandatory Notification?

  • Forms - Mandatory Notification?

  • general way of informing Trainees they need to contact their Administrator or have got Training courses, Core, Events, General information etc. - Mandatory/Non-mandatory Notifications?

As a TIS Admin

I want to be able to notify the trainee of the next placement (12 weeks) and (LET) + Option to raise a query via the notifications

So that Trainees can be reminded

  • Placement - Mandatory Notification?

The trainees must not be able to:

  1. Decline the notification

  2. Change anything because of the notification

  3. The admins need to know the Trainee has read the notification

  4. No calendar link as this may cause issues with other dates?

  5. This should then go back to the Admins for confirmation

  • Programme: current/future ….????

7.

Other Forms???

Leave request for future placements????

Jira Tickets

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

Architecture and Technical Level stories

These are technical stories created by the DEV team.

key summary type created updated due assignee reporter priority status resolution
Loading...
Refresh

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.