Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Data Ops Governance topic
No spam. Unsubscribe anytime.
CDR backend migrations complete; beneficiary access code change and CCW catalog migration announced
Summary
Alex Clark said Delta table conversions are complete and seamless to users, warned organizations to update DUAs to include the new EDB_USR epi code by June 30 to maintain beneficiary‑schema access, and announced MBISG/MCBS datasets in the CDR prod catalog will be deprecated by Dec. 31 and replaced by equivalent datasets in a CCW catalog.
Alex Clark, a product owner on the CCSQ data and analytics team, summarized recent operations and access changes affecting CDR users.
Delta migrations: Alex said the team has completed migrations of certain Parquet tables to Delta format to improve performance and reliability. "We are officially complete with all of our Delta table migrations," he said, and added that existing queries, notebooks and views will automatically read from the updated Delta tables with no user action required.
Beneficiary access code change: Alex reminded organizations that the epi code used to provision access to the beneficiary schema (EDB) is being retired and replaced with a new code (EDB_USR). He urged organizations to update their Data Use Agreements (DUAs) and upload the revised DUA to the CCSQ portal; the transition is scheduled to complete by June 30 and organizations that do not update in time may experience access interruption.
MBISG/MCBS transition: Alex also announced that access to MBISG and MCBS cost and survey datasets in the CDR production catalog will be deprecated by Dec. 31; equivalent datasets will be available in a CCW catalog accessible inside the Databricks environment for organizations that already have the required epi codes. Alex said the team will update epi code mappings next week so organizations with the right codes will receive access to the CCW versions without submitting new DUAs.
Next steps: Alex said he will publish a detailed article and encouraged users to begin testing CCW datasets as soon as access is provisioned and to reach out with questions via chat or Slack.
