Government Reporting Overhaul for a Home Care Platform

The situation

A home care coordination company that helps elderly people remain in their homes — connecting them with grocery delivery, transportation, and in-home nursing — had acquired another company with active government contracts and Medicare reporting requirements. The acquisition brought data obligations the company was not yet equipped to meet.

The data environment reflected the history: GCP and Azure both in use, transformation scripts scattered across Azure Data Factory, queries managed outside any version-controlled transformation layer, and reporting logic that no single person fully understood. Tableau dashboards sat downstream of this infrastructure, serving the analysts who needed to verify outputs before federal submission.

The hard date was February 1. CMS required approximately 100 mission-critical government reports. Missing the deadline was not an option.

What we built

CorrDyn’s first priority was the Azure environment, where the most urgent CMS reporting lived. We implemented dbt as the transformation layer, migrating the existing partner invoice logic and ad hoc scripts into governed, testable models. This gave the team version control and a clear audit trail for every transformation feeding into a government report.

We then built standardized entity models for the three core data objects the reporting touched: member, assessment, and cases. These shared definitions meant that different reports referencing the same concept were pulling from the same underlying model, not from independently maintained query logic that could drift out of sync.

The 837 EDI claim data, which carries Medicare billing transactions, required its own dbt review pass to confirm that the transformation logic matched CMS specification. We worked through that alongside onboarding the client’s internal analysts so they understood the new model structure and could maintain it independently over time.

Planning for the post-deadline work also began during this phase: implementing Estuary for change data capture from SQL Server into the transformation layer, and addressing the GCP/BigQuery side of the environment that the initial engagement had set aside.

What changed

The February 1 CMS filing deadline was met. The approximately 100 government reports that had been running on fragile, undocumented logic were moved onto a governed dbt layer with tests and documented lineage. Analysts could trace any number back to its source.

After the deadline, the engagement transitioned to a managed data team model at a fixed monthly budget. CorrDyn continues to handle dbt model development, new reporting requirements, and infrastructure work as the company builds out its multi-cloud data environment.