TIS - ESR interface meetings

Number

Description

Issue Reference in Log

TIS Ticket

Priority Assigned

Impact assessment of issue

1

Duplicate applicant records

Issue 8

TISNEW230- Now TISNEW-2062 - Applicants being exported in Duplicate for some positions triggered by ESR

 04/04/2019

Should be TISDEV-6342. Chris already started work on this. ESR working on getting email notification sent to TIS on duplicates

1

This is a long running issue that was first raised on 4/10/2018.  Duplicates were created on ESR causing confusion to the users on which application to progress.
ESR Workaround is in place which quarantines duplicates based on set parameters. But this is a temp fix- not a complete soution. There is a risk that parameters used to idnetify duplicates may not be correct or may not consider all scenarios or deduce legitimate repetition of applications. Genuine applictaions may be getting quarantined. Hence this needs to be nipped / corrected at the source.

2

Missing Applicant records
Wye valley - 30 missing
County Darlington- Missing in Host
West Suffolk -50 Missing New

Issue 11

1. TISNEW-2826 - ESR - Host positions with status of IMPORTED_AND_EXCLUDED to be amended
   (Added to Sprint -27 March 2019) COMPLETED on 2 April 2019- what does Completed mean ?Has this status been done away with.

 04/04/2019

Completed and already in live environment. Ade emailed the examples used in the investigation to ESR to  check from their end and get back to us if any issue

2. TISNEW-2485-ESR Investigation - Missing applicants - not exported from TIS to ESR
(Added to Sprint -27 March 2019).

4/04/2019

In the current sprint and TIS team looking at this.

On Wye Valley list of missing applicants: Ade to give the call ID - 168441 to Anita/Naz to check if the list was added to the incident number

1

Long running issue identified in 7/11/2018.
For every ocurrence of missing applicants this should be assigned priority 1 as this is affecting end user experience . It is a failure of the interface in performing its fundamental function of loading applicants.
Type 1: missing host applications . Lead applications exist.
Type 2: Imported and Excluded status -
Type 3: Misisng because of failed validation at ESR end hence rejected (Postcode issue)
Type 4: Others ?

New! West Suffolk - 50 Missing- reported on 2/04/2019. These applications are misisng - April rotation -high priority

3

manual export of applicants on TIS

Issue 7

TISNEW1311 now TISNEW-2871 -Add interface for manual export of users to ESR

04/04/2019

Ade: This is not an issue but an enhancement which still needs to be refined with the Product Owners and users. Ashley had re-purposed the ticket now – TISDEV – 5561 : “As a Local Office Admin I Want to manually export Applicants to ESR So That I can reconcile applicants that have not been received by ESR”

The idea is to help an incorrect application on TIS to be corrected and then to be marked for export by the end user but the user journey/s for this is yet to be refined. This is not an alternative/workaround to the problem that currently exist on ESR where loading of applicant fails on ESR for some reasons which is not with TIS.

PAV/Craig: To prioritise and also see if they can send us some examples.

?

Ash please provide more detail about this ticket and why it was raised.??
??On the face of it this is a functionality that could help an incorrect application to be corrected and then to be marked for export by the end user (this is over and above the automated  batch process that runs and batches the applicantions to be exported to ESR)- But this is my guess? Can you explain what the outcome of this ticket was supposed tobe?

4

reporting on DNC exceptions

Issue 33

TISNEW-2698- Confirmation of Notification success/failure Records received from ESR to be captured and made reportable

04/04/2019

In the backlog

2

This should have been built into the TIS exception reporting process. The DCC file or confirmation carries the issues - feedback on the DNC/ DNF. However TIS  exception reporting does not look at this currently and hence the exception reporting is incomplete or provides only a partial picture.
This is necessary for end users / local offices to be able to resolve issues as one of the big problems we have is that end users feel helpless or constrained by the lack of information to resolve issues.

5

DNF files

Issue 33

1. TISNEW-2778-  Produce Full Notification Files (DNF) for all Local Offices after 14/03.

04/04/2019

For refinement

 2. TISNEW-2872 - Investigation - DNC outdated records- updated in Log

05/04/2019 

In the backlog

3

This is needed to refresh the information on the MEDROT. But first TIS need to review the DNF/DNC processes.

There is a batch of incorrect / outdated information coming through in the DNC files. TIS needs to send us delete indicators for the records that are outdated or to be removed but that is not observed. Hence ESR Medical rotation report (MEDROT)  has accumulated old outdated records from rotations in 2018, 2017 etc which are confusing to the end user. These MEDROT  reports - ESR notifications are fundmaental to workforce staff managaing the rotations but they are based on the information and the quality of information on the DNC and DNF.
Issue 1: outdated information
issue 2: incorrect information on the DNC
Issue 3: misisng notiifcation for Host trusts-while notification for lead trusts exists.

6

Job share tickets

issue 32

TISNEW-2774 - Investigation on handling multiple applicants per deanery number in the DNF/C Files

 04/04/2019

In the Backlog

3

Medical Rotation report is not showing the information for the trainees in a job share. This is because the DNC/ DNF that underpins the production of the Medrot does not provide information for job share trainees as a set. Again this is a gap in the medical rotation spreadsheet and needs to be addressed as London and other trusts will rely on these reports and notiifcations and will raise issue if this is incomplete.

7

New !NINO missing and the Data quality of the GMC and the DOB is poor.
Payroll affecting

Issue 42

04/04/2019

Ade: If this is what the user has entered, it is not a problem with TIS or the Interface, it is just how the data has been entered on TIS. The interface could not have made that decision for them.

Actions:

Naz/Anita/ESR: To follow up with Cathy who is the Oriel Project Manager in order to find solution to NINO

Other aspect to the issue:

Hi Pav ,Craig and Anita/Naz:

I forgot to state that, don’t you think the GMC/ DOB/First name/ Surname issue should also be raised with Cathy instead of TIS team? These are information that comes from Oriel

1

Matching issue:
In some cases there is an old employee record and a new employee record in ESR. For payroll purposes the application from TIS should match with the new employee record. It isnt matching correctly because of data quality issues, misisng NINO orother issues.
Application from TIS has associated with the old employee record when it should have associated with the new record in ESR.NUTH: Nottingham University Hospital Trust :
Matching with old employee record because the applicant from TIS does not contain the NINO. Hence ESR-IBM unable to match. It looks for the GMC reg but doenst find that in the new employe erecord either. Hence it cant match therefore it matches with the next best which is the Ex employee record where the GMC reg is there or it creates a new applicant.
No NINOs have been sent for  8 records and the DOB observed is erroneous(18000101) that has caused issues at ESR end where the applications haven’t matched with the employee and new applicant record created in ESR. This has caused issues for the Trust users.
(email sent on 01/04/2019 -2019 April rotation issues)