Source: https://quadevs.com/healthcare/clinical-data-platforms/

Title: Clinical data warehouse and aggregation platform | quadevs

[Home](https://quadevs.com/)/ [Healthcare software development](https://quadevs.com/healthcare/)/ Clinical data warehouses and data aggregation platforms

# Clinical data warehouses and data aggregation platforms

A healthcare data platform for analysts and product teams. It keeps the history of every record, and partner loads survive outages.

[Tell us about your project](https://quadevs.com/contact/)  [or email us](mailto:hello@quadevs.com)

A **clinical data warehouse** stores patient, encounter and claim records with every past version. An analyst can ask what a record looked like on any date. An aggregation platform answers another need: engineering teams want one API in front of many clinical sources. We build either, or both over the same data.

## Data platform components

Patient, encounter, claim and partner data load idempotently into history tables and are served through one aggregation API.

- ### History tables

  Normalized patient, encounter and claim data with each change kept.
- ### Idempotent partner loads

  ETL batches with idempotency keys. A load resumed after a missed window adds no duplicates.
- ### Analytics replicas

  Read-only replicas for reporting, away from operational traffic.
- ### Aggregation API

  Schema-versioned endpoints, a typed C# SDK and per-request budgets.
- ### Safe schema changes

  Forward-only migrations and stored procedures that live in the repository.

## Data platforms we run

- [Clinical data warehouse](https://quadevs.com/case/clinical-data-warehouse/)

  One MSSQL warehouse grew from a few hundred thousand records to many millions over years of feature releases. Its referential integrity held the whole time.
- [Clinical data aggregation hub](https://quadevs.com/case/clinical-data-hub/)

  When a source behind our clinical aggregation hub changes its schema, the hub absorbs the change. None of the services that read from it need a release.
- And many more projects

  [All case studies](https://quadevs.com/cases/) [Ask about your project](https://quadevs.com/contact/)

## How a data platform project starts

1. ### Sources and readers

   List the source systems, the teams that read the data and the questions they cannot answer today.
2. ### Model one entity

   We model one entity, usually the encounter, with its history and load it from two sources.
3. ### First consumers

   Replicas and access logging open to the first team. More entities follow in the order teams ask for them.

**And much more.** [Ask about your project](https://quadevs.com/contact/)

## Further reading in Insights

[### Clinical data aggregation: a hub architecture

 Data · 7 min read Read](https://quadevs.com/insights/clinical-data-aggregation/)   [### Clinical data warehouse design: notes from production

 Data · 7 min read Read](https://quadevs.com/insights/clinical-data-warehouse/)

## What can your analysts not answer today?

Describe the sources, who reads the data and what breaks when a source changes.

### Your project brief
