15/01/2018
# | Discussion/Action | Responsible | Outcome |
---|---|---|---|
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. |
4 | Data stories to be tasked up to support Oriel integration Create an Oriel Integration Channel on Teams. Tasks with AR to review and close. Confirm the mandatory fields on Recruitment Import and close. | AR | Tasks created in next up and summarised in the table here. Create an Oriel Integration Channel on Teams - Done Tasks with AR to review and close - Done Confirm the mandatory fields on Recruitment Import and close. - Done |
6 |
| JH, AP, IO | Proposed Solution (JH)
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 |
7 | ESR Integration Data Quality tasks. Some of the fields are mandatory for ESR to create records.
| IO: |
|
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 | Separate spreadsheet reviewed - to be attached |
Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213