Feature: Data Quality Control
The CTcue DWH is now regularly checked for inconsistencies. For this initial implementation, rules are implemented for patients, admissions, medication, and surgery. This will be expanded in future releases
Improvements
- elasticsearch loading now stops entirely if too many issues are encountered
- fixed an issue where certain source deletes were not propagated properly to the DWH
Generic datamodel/etl changes
- Add a patient's origin information to the admission category via a new dimension
d_admission_source
and fact columnDW_ADMISSION_FACT.SOURCE_ID int not null
, causing a historic reload ofadmission
- altered column:
DW_ADMPART_FACT.BED_NUMBER
wasnvarchar(50) null
, becomesnvarchar(256) null
- altered column:
DW_LAB_DIM_UNIT.MEASUREMENT_UNIT
wasnvarchar(50) null
, becomesnvarchar(100) null
- altered column:
DW_QA_FACT.VALUE_MC
wasnvarchar(2000) null
, becomesnvarchar(max) null
- the new table
metadata.version
keeps track of the deployed datamodel version history
EHR-specific datamodel/etl changes
hix
- add a cancellation indicator to the statuses of
surgery
clarity
- add bednumber to
admission
- add more bmi measurements to
measurement
- improved monitoring by keeping track of clarity source counts
- care provider metadata is added to all texts originating from the
HNO_INFO
source table, causing a partial reload of thereport
category - fixed an issue where lab statuses and dates were sometimes incorrect. This causes a full historic reload of the
measurement
category
CTcue application integrations
- it is now possible to get DWH version info using
metadata.get_datamodel_version()
andmetadata.get_datamodel_date()
.