12/02/2018

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 JH - 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 (Tuesday 16/01) with Reporting SMLs.

JW/JT to coordinate the access to Tableau  for the SMLs to test the reports.  - In Progress with JT

List of names sent to JW

Quick guide to send to SMLs

Oriel Integration:

Tasks created and summarised in the table here. 

Create an Oriel Integration Channel on Teams  - Done

To schedule a quick presentation of the Oriel trainees import process. - People SMLs, a message on General

05/02 AR: Will schedule on my return.

12/02 AR: Scheduled for 16/02 @ 11a.m, will be emailing People SMLs. 

• 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.

AP has received James ssheet.

More generally, we should look to standardise naming conventions around programmes (not just Dental) to be discussed separately

Next to put on Microsoft Teams and get SMLs feedback - AP

JH/AP - Setup call to briefly explain next week. - 

IO/AP: Recommendation: show a concatenated display of the programme name in the dropdown list with the Local Office name? To check with DEV on the possible solutions. (P1)  TISDEV-3767 - Getting issue details... STATUS

• Discuss with Reubs on the next course of action.
• All tickets clarified, require the report to be looked at again to confirm there are still issues pending

3322:

DS: Duplicate issues to be fixed to reduce the numbers of missing details. - Update?

DS: Checking 120 items manually. To be completed asap. Follow up with Hicom.  

CL/IO: To identify which of those are current trainees records; who is in a current/future programme/placement?

AB: Which of those have self-service access?

IO to confirm - check whether there is a trainee is in a current or future programme membership or placement and re-do reports, update data leads

TISDEV - 3620 - Done

JH:

Assumption: Dental trainees to be any person record that has a GDC number which is not Null, N/A or blank

Total Number of Person Records: 13376
Number with a Start and Expiry Date: 622
Number with a Null Start or Expiry Date: 12754

% with valid dates: 4.65%
% without valid dates: 95.35%

TISDEV - 3363 - In Progress

JH/AB/CL/DS -

To get rid of the N/A for records that have a valid other registration number. We can only remove it for all if we are definitely not going to have person records which would not have an applicable reference number

I think the validation rule should stay the same

But what are we going to do with the practice manager records?

AR: To find out with ESR how they handle a GMC/GDC number of 'N/A' -

05/02: If the professional body detail is provided in the applicant file, then ESR would expect to see the registration number and the expiry date in the subsequent fields. Where a value of N/A is being passed, the assumption is no professional body is being passed therefore does not represent an issue for ESR. 

Next Steps:

CL/JH: To be written down of what each means and share with SMLs? - to be documented: Trainnees should have at least 1 registration number populated, if that is not known at the time the record is created, then populate one of the relevant registration numbers with 'Unknown' and the rest as 'N/A'. 

AB: PH numbers - what is the standard format? Not consistent across LOs.

JH: 2 PH schools for assigning the numbers, also not mandatory to have one - make this a non-mandatory field? - Ashley Ransoo Joanne Watson (Unlicensed) - to verify this on TIS.

AR/CL: To discuss and feed into the design work for Absence.

05/02: Matt/Ashley/Claire have met and discussed on the templates for recording Study leave and costs/expenses which will feed into the solution design for TIS.

Claire - any update from Martyn Clarke (Lead BM for absence) with regards to the national process?

Trusts access to Intrepid and how they are currently recording study leave not necessarily the way forward for TIS. - To be clarified with Rob

If you want to create a single row per person in the person table coontaining roles, this (or something like it) will need to be the case. The alternative would be to export person role as a separate table / view (this would be my preference). I would imagine that TIS stored person role as a separate table.
The ETL into the warehouse can setup the data more or less however we like. I would separate out role, as it gets messy packing lots of them into one field and it is tricky for users to handle.
John Thompson

Considerations for reports changes - Post on Data_Warehouse channel on slack to get clarification.

Audit data needs to be reportable - add as a NFR

Add story for comments box - add ticket

TISDEV-3810 - Getting issue details... STATUS

These dates will be displayed within the record, also should be possible to extract it for reporting purpose from the data warehouse, but this is TBC (IO)

See example in #9

Yes it has been removed - TBC is required, check Teams

No further comments on this

Addressed separately. - Removed

Yes it has been removed - TBC is required, check Teams

No further comments on this

Removed

For the teams that are using this field, check where the secondary sites are in the back end; check Teams for further feedback on usage

To be discussed and agreed with all regions:

• what should the standard usage process be?
• how should it be recorded?
• How many trainees does this affect?

AP/CL: Needs to be looked into for post MVP.

Workaround for MVP? e.g. comments box. To be discussed/prioritised on Woraround meeting this week.

Yes it has been removed - TBC is required, check Teams

No further comments on this

Data leads to agree on the list. 

CL: List from Intrepid Consolidation to be sent