MDCCD Data Warehouse

Overview

The Medical Device and Clinical Compliance (MDCCD) Data Warehouse is an Oracle 19c based data warehouse maintained by Shared Services Canada (SSC) and Health Canada's (HC) Digital Transformation Branch (DTB).

Problems to Address

• There is no single source of truth for MDCCD’s data.
• Program data is stored a various repositories.
  • Ex: IRS, MDS, eCES, RADAR, ARISg, eSAP

• Repositories are often poorly documented.

• Data is often incomplete, inaccurate or missing.
• IT systems are constantly changing.
  • Requires tools and business intelligence to be rebuilt.

• Data Analysts are not always allowed to access production databases.

Benefits of the MDCCD Warehouse

• Better data quality: A data warehouse centralizes data from a variety of data sources, such as transactional systems, operational databases, and flat files. It then cleanses the operational data, eliminates duplicates, and standardizes it to create a single source of the truth.
• Faster insights: Data warehouses enable data integration, allowing program users to leverage all of the program’s data into each business decision. Data warehouse data makes it possible to report on themes, trends, aggregations, and other relationships among data collected.
• Smarter decision-making:  A data warehouse supports large-scale BI functions such as data mining (finding unseen patterns and relationships in data), artificial intelligence, and machine learning—tools data professionals and program leaders can use to get hard evidence for making smarter decisions in virtually every area of the organization, from compliance verification to financial management and inspection planning.
• Time savings: By using standardized datasets, business intelligence and automation tools can escape the cycle of constant rebuilding whenever IT systems change.
• Documented data: Having all the program data in one location allows for the data to be properly documented with data dictionaries and entity-relationship diagrams resulting in consistent interpretations and reducing misunderstandings. Well documented data also allows for faster product development and training of data analysts.

Scope, Phases & Scalability

Scope

• IT Systems that do not have a preexisting reporting solution.
• Functions where MDCCD is the owner of data.

Phase 1

1. Provisioning of data warehouse. – Completed
2. Creation of standardized datasets for Medical Device inspections. - Completed
3. Creation of ETL from MDID (Medical Device Inspection Database) to MDCCD Data Warehouse. – In Progress

Phase 2

1. AHR Registrations & Inspections
2. CTO Registrations & Inspections

Phase 3

1. Medical Device Compliance Verification, Recalls & Establishment Licencing

Future Phases

• Data utilized by MDCCD, but where MDCCD is not the data owner (Ex: ARISg, eSAP)
• Data from new IT systems (Ex: CIELS)

Potential Scalability

• Incorporate data currently captured by another reporting system (Ex. RADAR Reporting Database).
• Incorporate data utilized by other program partners (Ex. Medical Device Licencing, Drug Product Dictionary).