08/01/2018


#
Discussion/Action
Responsible
Outcome

1

ARCP outcomes - queried values.

e.g. for academic outcomes there are more values than the three current agreed ones and for ARCP outcomes there instances of trainees having been given more than one outcome per ARCP event.

There are two possible solutions:

  1. Copy the values over as is but if a user viewed the record, they will see the legacy academic outcome BUT they won't be able to modify it and save it.
  2. Archive the legacy academic outcome and store it in another field then set the modern equivalent of that value to the academic outcome.

JW to find out when these ARCPs took place.

Data Leads to agree which of the two solutions to use.


Report has been provided, but requires further analysis - to be shared approx 20/12


James/David

  • display read only legacy fields

Been agreed on the Slack Channel. 

Pull the outcome and make as read-only.

Item closed.

2Some academic assessments have been orphaned as they were created when a separate ARCP event was recorded for Clinical and Academic

JW to ask the Assessment SMLs if the academic assessment should be its own event or it it should continue as being part of the overall clinical event.

For post TCS. 

SMLs happy with the overall process.

Put a ticket in Jira to look at post TCS and close.

TISDEV-3483 - Getting issue details... STATUS

Item closed

3

Reports requested by each region have been submitted to JT, Alice and James for writing up in SQL.

JT, AB and JH had a meeting on the 8/12 to identify themes in the reporting requirements to allow a suite of reports to be written but with filterable criteria to allow each local office/region to run the reports they need,

JW

AB and JW - to write the reports

JW provided the initial list of reports for creation

JH/AB: Pushed into Tableau as data sources. Completed 1 of the reports.

JT to publish for users to test.

Logins to be setup for users.

To present what's done so far on next week's meeting (Tuesday 16/01) with Reporting SMLs.

4Data stories to be tasked up to support Oriel integrationAR

Tasks created in next up and sumarised in the table here. Notified Data Leads on DQ channel.

Create an Oriel Integration Channel on Teams 

Tasks with AR to review and close

Confirm the mandatory fields on Recruitment Import and close.


5Review TISDEV-3335Data Leads to review the placement dates described in the ticket and report back in the next call

This investigation has been done and Jag is working on the fix for the next APP file. 

Item closed.

6
  • Programme names/numbers aren’t provided for Dental trainees, they’re created by Admins

Proposed Solution (JH)

  • 3 letter use the prefix of the local office + 3 digit acronym based on specialty
  • 3 digit specialty acronym should be consistent across all


Action: AP/IO to impact assess

JH: Done mapping and need to do some more work and send to AP.
7

ESR Integration Data Quality tasks. Some of the fields are mandatory for ESR to create records. 

IO: Discuss with Reubs on the next course of action.
8

Fields comparison/review between TIS and Intrepid. Fields removed from Intrepid when coming across to TIS

JW/AP/CL to review Next Monday (15/01).

JW/AP/CL