2017-07-13 DR v1.17 issues

Owned by Russell Steel (Unlicensed)
Last updated: 13 Sept 2017 by Graham O'Regan (Unlicensed)
Date2017-07-13
Authors
Russell Steel (Unlicensed)
StatusIn progress
SummaryThe latest DR release, v1.17 has different columns names defined that in v1.16
ImpactCausing nightly ETL to fail

Root Cause

Their are table column name differences between v1.16 and v1.17;

e.g vwPerson.NaltionalityDual is name vwHEE_Person.DualNationallity

Trigger

Resolution

Hicomm to rationalise the DR view columns names

Detection

Sent: 29 June 2017 13:10
To: Yvonne Cunningham; Graham O'Regan
Cc: Benjamin Witton; Adrian Ashley
Subject: Re: Data Repository Access
 

Hi Yvonne, 


I have been looking at the latest Data Repository for TV and SW,  v1.1.7, and compared the view structures back to the previous versions, and have noted the following vwPerson column names didn't exist in v1.1.6 of the data repository;



namenamenamecolumn_id
HESWvwHEE_PersonLegalForename10
HESWvwHEE_PersonDualNationality39
HESWvwHEE_PersonSexualOrientation40
HESWvwHEE_PersonReligiousBelief41
HESWvwHEE_PersonEthnicOrigin42
HESWvwHEE_PersonInactiveFromDate53
HESWvwHEE_PersonInactiveNotes54
HEWTVvwHEE_PersonLegalForename10
HEWTVvwHEE_PersonDualNationality39
HEWTVvwHEE_PersonSexualOrientation40
HEWTVvwHEE_PersonReligiousBelief41
HEWTVvwHEE_PersonEthnicOrigin42
HEWTVvwHEE_PersonInactiveFromDate53
HEWTVvwHEE_PersonInactiveNotes54

For example, the new column DualNationality was previously namedNationalityDual, LegalForname was previously named LegalFornames, the other columns look to be newly introduced in v.1.1.7.
Please could you confirm that these column names changed are expected, and what steps can be taken to minimise these types of difference going forward ?
From: Yvonne Cunningham <Yvonne.Cunningham@hicom.co.uk>
Sent: 29 June 2017 13:53
To: Russell Steel; Graham O'Regan
Cc: Benjamin Witton; Adrian Ashley
Subject: RE: Data Repository Access
 

Hi Russell

 

The change of names between versions was not intentional and our upcoming release should contain the fixes to restore these back to the naming convention they previously used.

 

The “vwHEE_” prefix is also temporary while we transition the HEE users over to 10.90, once this is complete we would look to removing the “vwHEE_” prefix.

 

Once we have a confirmed upgrade timeline for the HEE users we can proceed to plan a release where we remove the prefix, but there is no intention to rename the columns within the views.

 

Please note the changes for consolidation also includes the removal of some fields, where they no longer exist in the datasource.

 

Hope that makes sense.

Action Items

Action ItemTypeOwnerIssue

mitigate/prevent









Timeline

Supporting Information

e.g. monitoring dashboards

Slack: https://hee-nhs-tis.slack.com/
Jira issues: https://hee-tis.atlassian.net/issues/?filter=14213