Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »


#
Discussion/Action
Responsible
Outcome
Status
1
  • Programme names/numbers aren’t provided for Dental trainees, they’re created by Admins
JH, AP, IO


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. - Was decided that it should be postponed for the moment on advice from James.

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 - Add indicator to drop downs to highlight "ownership" of values to the user TO DO

19/02: AP/JH: Field limit for programme number? Check field validation (Alistair Pringle (Unlicensed))  Max number of characters is 20 including spaces / special characters

09/04: Sent to Andy, Programme number being changed as this was too long. 

ON HOLD till post MVP launch
2Data Quality dashboard to be shared with other regions from LASE

John to schedule time to review it

05/03 Claire to prod on what the progress is on this  

05/03 JT to chase up when he's back in London on 06/03

12/03 Demo to be arranged, check if JH is back. Chris Norman to share SQl script. 

26/03 JT to setup doodle poll to arrange date for demo.

09/04: To chase JT for this to be done.

16/04 - Taking place in the next few days.


OPEN
3Start post funding discussion with local officesJW/JH

Place holder

AP/JH/IO: IO To update with ticket numnber and post on DQ channel.

ON HOLD till post MVP
4

Update on the missing placements (James/Claire) flagged on DQ channel - Data not pulling through rather than missing placements. 

Progress update on the checks between Intrepid and TIS UI (Claire)
JH/CL/IOCL: Spreadsheet uploaded with feedback - Qualifications, Assessments and Placements issues identified.

CL/IO

IO to review the feedback from Claire

09/04: Claire Shared with other Data leads to test the UI and feedback - JH, AB & DS

15/04: Update?

19/04:  Go through BAU tickets

5

Placement import template v.s. Placement manager?

Are these separate and are means to what end?

AP

AP: Follow up with Rob - Extract from NDW and feed into ETL?

AR: 23/04: Rob has setup a slack channel to discuss #intrepid-placement-manager

This channel is being set up to help resolve an efficient way to manage the Intrepid Placement Manager. This module is used by EOE to manage placements.
- The module enables placements to be managed in a "draft", or pre-published state.
- On publishing, the placements are fed into Intrepid.
- The data is available in DR2.
Data flows from TIS to Intrepid and will replace Intrepid placement data. Therefore, on publishing the data also needs to be extracted from DR2 and uploaded into TIS, so that it can be passed back into Intrepid. This needs to happen daily and will require controls.
- The process to manually extract from Intrepid and upload to TIS may be burdensome
- There is a need to make sure data extracted from DR conforms to the placement upload (this is probably the first task) to do...
- Consideration around automation and so on can follow.


6

Bulk Assessment template to be reviewed.

Assessment - Bulk Upload (DRAFT)

Assessment - Bulk Upload (DRAFT)#BulkUpload(DRAFT)-TISBulkAssessmentUploadTemplate(DRAFT)

Data leads

CL/JH/AB/DS

AR: Share on DQ Slack channel

AR 23/04: Alice has added her recommendations and shared on DQ channel, can other data leads review and confirm?


7

Bulk People Import - Feedback

Check if the Expectations are correct on the Jira tickets

CL/AB

Check progress end of week on bug fixes.

Release to users for testing. 

AR 23/04: Demo on people bulk upload was done on last Show & Tell. User guides being updated with to include bulk upload. 

Programme membership rules discussed and agreed to be made consistent on both FE and FE, i.e. where a Programme membership exist against a person where Programme name, number, membership type , start and end dates match exactly to those on the template, it will be flagged as an error.








  • No labels