Content Comparison

💡 Details

Actions / Decisions

https://hee-tis.atlassian.net/wiki/spaces/NTCS/pages/4595941521/Oriel-TIS+Solution+Options+-+Phased+Approach#1.-Filter-and-Enrich-Oriel-Data-with-Timestamps

1. Added Fields:

   1. DayToDayActivitiesLimited (yes/no) – PIDSpecial Schema

   2. MaritalStatus – PIDSpecial Schema

   3. OfferRoundName – PID Schema

   4. StaffGroups – PID Schema

   5. AllocationPreference – PIDSpecial Schema

2. Still outstanding

   1. OfferPreference – Is this still required?

   2. AllocationCode – Is this different to AllocationPreference

   3. Public Health Application Type – Not sure what this is but assume it is Medic vs Non-Medic Public Health. Can this be derived from other fields?

1. Andrew Horton tweaks to SQL script

   1. Marital Status values removed – couldn’t get uploads to work with them in.

   2. We’ve put a case statement in to make Nationality a Nationality – may have missed some but had everything we needed last year.

   3. Case statement for to match to the TIS Gender reference values as at April 2024 reference values.

   4. We put the provided OrielID’s into an IN statement to capture the records we want. – How are these known?

2. Other pain points from Andy and team

   1. Move address 3 into address 2 where it is blank

   2. Check the telephone number looks correct as there is sometimes an issue with formatting (Convert the column to number, then remove the decimal places)

3. Questions:

   1. Will the ‘tweaks’ above be useful for all and should they be applied?

   2. Do the Address[RT1]  and Phone Number pain points hold true for all? Should a fix be investigated for them?