Page Comparison

Make mandatory. Make Add/Matching Criteria as per rules suggested by Claire.

If Review date along with the rest of the matching criteria match exactly to a Person Assessment record on TIS then update the rest of the fields.

If review date differs, then act as a create.

Ashley Ransoo This field is the Review Date (not the Portfolio review date) from the TIS pages. But is indeed one of the matching criteria

AR:Made it 'Review Date* and added a separate non-mandatory 'Portfolio review date'.

Data leads to confirm behaviour?

AB: This field should be a calculated field based on Portfolio Review Date. As such, this field should not be included on the assessment import template as it should automatically calculate once the record has been imported.

JH: How can this be calculated for the statuses of Appealed and Completed???

CL: I don’t know how this field works. Do we actually need it?

Made an Add following last review.

12/02: 

This field has been removed from UI and Bulk following PAG

Accepted values are those from the Outcome Reference table i.e.:

Not Assessed
1
2
3
4
4W
4VR
5
6
6C
6R
7
8
9
10.1
10.2

Only Mandatory if Outcome is one of the following:

Not Assessessed
2
3
4
5

10.1

10.2

Accepted values should be one of those from the Outcome Reason reference table. e.g. 'N1 Trainee sick leave' etc. 

Allows multiple comma separated.

Unsatisfactory Outcome/Not Assessed Reason (Other)

Should be  mandatory if  'N13 Other reason (please specify)' is chosen as 'Not Assessed Reason' OR if 'U8 Other reason (please specify) is chosen as 'Unsatisfactory Outcome Reason'

Should be mandatory if 'Other reason (please specify)' is chosen as 'Not Assessed Reason' OR as 'Unsatisfactory Outcome Reason'

If you enter Other reason (please specify) in the field Reason(s) for unsatisfactory outcome, enter the Other reason into this field. The reason must be less than 60 characters

If you enter 'Other issues related to Covid-19 (please describe), enter the Other reason into this field. The reason must be less than 60 characters

Make mandatory if  'N13 Other reason (please specify)' is chosen as 'Not Assessed Reason' OR if 'U8 Other reason (please specify) is chosen as 'Unsatisfactory Outcome Reason'

Naming the column  as 'Unsatisfactory Outcome/Not Assessed Reason (Other)'.

Ashley Ransoo we don't have a field on TIS called 'Reason for unsatisfactory outcome - other' 

AR: Field has been added, therefore confirmed to include for bullk

AB: Should not be mandatory as only a small number of trainees are academic trainees so the vast majority of trainees will not receive academic outcomes. There also needs to be a field added for Academic Curriculum Name.

Joanne Watson (Unlicensed) 'Academic curriculum name'? Does the field exist on TIS? If not should it and how is it going to be used on the template? E.g. as a Update/Add/Matching Criteria.

AR 02/05: There is a 'Curriculum name' under Pre-assessment detail. Is this used for both Academic and non-academic curriculum?

Ashley Ransoo the Curriculum Name is always the name of the clinical curriculum. If the trainee has been following an academic curriculum in the assessment period the name of the academic curriculum will appear in the 'Academic Curriculum assessed' field in Post-assessment.

Remove from template. But populate in the same way as the Front End currently does. 

This is autopopulated from the trainee's placement grade on the Review Date

12/02: 

This field has been removed from UI and Bulk following PAG

Mandatory in an update scenario.

Matching Criteria

Pre-populate based on Curriculum name entered. Similar behaviour as the Front end is expected in an Add Scenario. It is expected this be left blank on the template in an Add scenario.

In an update scenario, this should be used as a matching criteria.

Keep on template but pre-populate based on Curriculum name entered. Similar behaviour as the Front end is expected in an Add Scenario. It is expected this be left blank on the template in an Add scenario.

In an update scenario, this should be used as a matching criteria.

Update

Add

02/05: CL confirmed for this to be included as non-mandatory 'Update' type.

Made an Add as template is for Create only.

Update

Add

Update

Add

Update

Add

Update

Add

Freetext

Data leads for other regions to confirm?

AR 02/05: Assessment Field Validation:
1. LEP report
2. Form R Part B
3. Supervisors report
4. Other
In which case, should we consider adding the above to the template instead as non-mandatory 'Update' type?
Back with Claire to confirm, the field if not currently on TIS.

Joanne Watson (Unlicensed) - can we remove this form the template for now?

Ashley Ransoo see no. 25

Data leads for other regions to confirm?

AR 02/05: Assessment Field Validation:
1. LEP report
2. Form R Part B
3. Supervisors report
4. Other
In which case, should we consider adding the above to the template instead as non-mandatory 'Update' type?
Back with Claire to confirm, the field if not currently on TIS.

Joanne Watson (Unlicensed) - can we remove this form the template for now?

Ashley Ransoo see no. 25

Data leads for other regions to confirm?

AR 02/05: Assessment Field Validation:
1. LEP report
2. Form R Part B
3. Supervisors report
4. Other
In which case, should we consider adding the above to the template instead as non-mandatory 'Update' type?
Back with Claire to confirm, the field if not currently on TIS.

Joanne Watson (Unlicensed) - can we remove this form the template for now?

Ashley Ransoo see no. 25

Data leads for other regions to confirm?

AR 02/05: Assessment Field Validation:
1. LEP report
2. Form R Part B
3. Supervisors report
4. Other
In which case, should we consider adding the above to the template instead as non-mandatory 'Update' type?
Back with Claire to confirm, the field if not currently on TIS.

Joanne Watson (Unlicensed) - can we remove this form the template for now?

Ashley Ransoo see no. 25

Update

Add

Corrected.

Ashley Ransoo also need to include in this dropdown the fields from the GMC ARCP list of allowed values. Will find this and go through it with you.

AR 02/05: 'Curriculum end date' is a readonly field in TIS Assessment record on the Front end however is editable within the Programme Membership record. 'Curriculum start date' can be added via the people bulk uload currently but there is no bulk facility for updating this, is there a requirement to be able to bulk update curriculum end dates?

Assuming this only needs to be populated on the template when updating curriculumn end dates, what should be the rules to be able to update this field, apart from the 'Curriculum name*' should match?

The is also the complexity of automatically updating the Programme end date based on the last curriculumn end date + grace period. Do we need to factor this in?

Update

Add

Update

Add

Update

Add

Update

Add

Update

Add

Additional comments from the panel

Update

Add

Keep on template as non-mandatory.

Ashley Ransoo added this - on TIS now

AR: Have now included on the template.

Update

Add

Update

Add

Update

Add

Keep on template as non-mandatory.

12/02: 

This field has been removed from UI and Bulk following PAG

Must match exactly the TIS Assessment ID of a current or soft deleted Assessment record on TIS

13/02: Allow both Current and Soft deleted to be entered on the template

Could TIS programme membership ID be an alternative and is this something that the people having access to this tool would have visibility of 

Yes - Go for Programme Membership ID attached to the Assessment instead of Programme name and number

Must match exactly to one of the curricula against the Programme Membership ID entered in the Programme Membership ID column.

Curriculum ID in Programme Membership.

14/10: This is not required on the template after discussing with the devs as it can be determined by programme membership ID.

• Accepted format is dd/mm/yyyy
• 'Period covered from' cannot be before 'curriculum start date'

• Accepted format is dd/mm/yyyy
• 'Period covered to' cannot be before 'Period covered from'

Is this required to be updated via bulk? This is normally pulled automatically if there is one at the time of updating/creating the assessment record else set to Not Provided. But can be overridden. 

13/02: Yes, include on template.

Accepted values are those from the Outcome Reference table i.e.:

Not Assessed
1
2
3
4
4W
4VR
5
6
6R
6C
7
8
9
10.1
10.2

Only Mandatory if Outcome is being updated to one of the following in #Outcome column :

• Not Assessed
• 2
• 3
• 4
• 10.1
• 10.2

• Accepted values should be one of those from the Outcome Reason reference table. e.g. 'N1 Trainee sick leave' etc. 

• Allows for multiple semicolon ( ; ) separated values.

Unsatisfactory Outcome/Not Assessed Reason (Other)

Should be mandatory if 'Other reason (please specify)' is chosen as 'Not Assessed Reason' OR as 'Unsatisfactory Outcome Reason'

• If you enter Other reason (please specify) in the field Reason(s) for unsatisfactory outcome, enter the Other reason into this field. The reason must be less than 60 characters

• If you enter 'Other issues related to Covid-19 (please describe), enter the Other reason into this field. The reason must be less than 60 characters

Overwrite existing comments with the comments from the template

Update

Update and replace

Freetext

Only Accepted value is 'YES' or left blank for no action.

Entering 'YES' will result in the assessment record being marked as soft deleted, removed from the UI but can be accessed from the Backend, similar to the TIS FE behaviour trashcan interaction against Assessment.  

To avoid this field being incorrectly used, suggest that the only fields required for a soft-delete are the TIS_Assessemt_IDs and Soft Delete from UI? on the template and all other columns should be left unfilled.

P.S: The option of undoing soft-deletion was considered, but no one has demonstrated a need for this yet.