Versions Compared

Old Version 15

changes.mady.by.user Former user

Saved on

compared with

New Version 16

changes.mady.by.user Former user

Saved on

Key

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

...

Process NamePP3 - View People ListComments
DescriptionUser can view a summary list of all people and be able to constrain/sort that view by certain filters; they should also be able to enter into a person record
ActorsAdmins (Local office and Trusts)
Pre-conditions

Logged in

Security allows access to people records 


Post-conditionsView all or searched people in a list
Process steps1. View table with column headers defined
2. Click into single line to view detail on a particular person
3. System presents detailed post view
  • Forename
  • Surname
  • GMCnumber/GDC number/Public Health Number
  • Programme
  • NTN
  • Current placement details (placement grade, placement specialty)
  • Current placement site 
  • Placement type
  • Role
  • Status
Alternative flowPP2 - Search Person
Rules
  • Error: page unavailable
  • filter on by default: user's local office
  • Other validation available on field validation table

JIRA ReferenceTIS-636
Audit LogN/A

...

Process NamePP4 - View / Edit PersonComments
DescriptionUser should be able to view a person record and edit as their permission allows
ActorsLocal office admins
Pre-conditions

Logged in 

Authorised user


Post-conditionsView all or filtered/searched people in a list
Process steps1. Click through from list view
2. View detail
3. Edit detail in field (including changing status to 'inactive')
4. Save
5. Close

From People - Field Validation 


Alternative flowPP3 - View people list
Rules
  • NEW allow some users access to only certain parts of the person record e.g. all apart from the sensitive data (See Admin User Management - Roles & Permissions DRAFT (WIP))
  • NEW activate all 3rd level navigation items on edit journey
  • NEW display tool tip to notify user that they can edit full record
  • NEW ineditable/blank Assessments if no Placements set - user can navigate to page, but cannot do anything on it (see here AS-1 Assessments - Scenarios)
  • Error message: only one user to edit a single person record at any one time
  • Rule: Must save before closing
  • Error: this GMC/GDC/Public Health number is already held by a person on this database

JIRA ReferenceTIS-636, TIS-207, TIS 130
Audit LogChange made - was/is
When
Who		Log changes to any of the field values and when and who made
the changes.
Visually presented to all

...

Process NamePP5 - Create Person (single)Comments
DescriptionUsers should be able to manually add an individual person record
ActorsLocal office admin
Pre-conditionsLogged in
Authorised User
Post-conditionsSearched for person in entire database (searched based on GMC, GDC, Public Health number or Surname)
Process steps

1. Select to add new person
2. Enter relevant field data (see order of field completion
on validation table)data 

3. User selects whether to assign a DRN or NTN
3. System autosaves details as they progress
4. User saves

From People - Field Validation (when creating a person record only the fields in Personal and Contact and (for a trainee) Programme are required)


(IO) How do we differentiate between a medical trainee or other?

Alternative flowPP6 - Bulk upload of people
RulesMandatory fields must be completed.
  • Error: Mandatory fields not completed
  • NTN cannot be generated if the following fields are incomplete - local office, specialty, GMC no, suffx option*
  • DRN cannot be generated if the following fields are incomplete - TBC
  • NTN/DRN must be unique - to a trainee within a single programme and assigned to a local office
  • NTN/DRN cannot be transferred
  • NTN/DRN is only mandatory for doctors

    • Suffix option TBC 

    • CCT  = C
    • CESR = L
    • CESP = ?
    • CEGPR = L
    • CEGCP  ?
    Joanne Watson (Unlicensed) - we need to discuss how to select one of the options that allows the suffix to be appended to the NTN/DRN
    • NEW Personal & Contact + Manage Record Fields must be populated to enable other sections (see below)
      • NEW Display tool tip notifying them that all fields must be completed in order to be able to complete the others
    • NEW hide all other 3rd level navigation items on create
    • NEW Activating save - on save click:
      • nok: present error message on save click
      • ok: display successful save message
      • keep user on record (they can decide to go back to list or not)

    (IO) When should save button be made available? Discussed here but needs to be revisited (People - Field Validation | Activating Save & Errors)


    (IO) what if there is unknown information, do we need to reduce the number of mandatory fields?


    JIRA Reference

    		TIS 629
    Audit LogWho created the people record and whenLog changes to any of the field values and when and who made
    the changes.
    Visually presented to all

    ...