Polnor.
Data warehouses (EDS)

One governed health data warehouse. Every team, one standard.

Sovereign by design: hosted on OVHcloud, infrastructure qualified SecNumCloud 3.2 and HDS-certified, data never leaves your cloud. A multi-source warehouse on FHIR and OMOP, with ingestion, de-identification, mapping, quality control and lineage running themselves. Open standards throughout, so there is no lock-in.

Hosted on OVHcloudInfra qualified SecNumCloud 3.2HDS-certifiedData in FranceCLOUD Act immune
A worked case

Many source systems, one governed OMOP layer.

You onboard several hospital and departmental systems into a single warehouse. Each is de-identified, standardized to OMOP and quality-checked, then published as governed tables analysts query directly, without a single row leaving your cloud.

app.your-eds.fr / catalog● health-blind
eds_catalog › omop › sources_onboarded
▶ Run-- governed sources published to the OMOP layer SELECT source, person_count, status FROM catalog.governed_sources WHERE layer = 'omop' ORDER BY person_count DESC;
results · 4 sources0 rows exported ✓
sourcepersonsOMOP rowsgovernance
hospital_a · EHR612,34048,220,110governed ✓
hospital_b · EHR408,91531,904,772governed ✓
lab_network531,20719,551,203governed ✓
claims_feed897,00472,118,640governed ✓

Illustrative interface and figures, shown to explain the workflow. Not results from a Polnor customer.

The features behind it

Everything up to the cohort is automated.

By the time your team writes that query, the hard part is done: the platform has already ingested, de-identified, standardized and quality-checked your data. You start where the question starts.

Automated · ingestion & OMOP

Every source in, at the FHIR standard then OMOP

EHR extracts, lab feeds and claims from each onboarded system are normalized to FHIR R4 then converted to OMOP CDM with OHDSI concept mapping and quality control. Adding the next source does not mean writing bespoke ETL again.

OMOP · mappingauto
source→ OMOP conceptstd
icd10:E11Type 2 diabetesS
loinc:4548-4HbA1cS
atc:A10BA02MetforminS
Almost everything is automated

The platform runs the warehouse. Your teams run the analysis.

The repetitive, compliance-heavy work of running a shared warehouse runs itself, so your teams spend their time on questions, not preparation.

Automated by Polnor
FHIR / HL7 v2 ingestion · refresh
GDPR de-identification
OMOP conversion · concept mapping
clinical quality control
feature materialization · lineage · access log
Your team decides
which sources to onboard
access policy per team
cohort & feature definitions
the analyses, models and interpretation
Governance

Govern the whole warehouse, and stay free to leave.

PHI is classified, every access is logged, and lineage traces each governed table back to its source. Because the warehouse is built on FHIR, OMOP, Apache Iceberg and MLflow-compatible tooling, there is no lock-in: your data and models stay in open standards, on infrastructure qualified SecNumCloud and HDS-certified.

Request a demo

From many source systems to one governed layer, in your cloud.

30 minutes: we stand up the automated pipeline on a case like yours and show you where the automation ends and your teams' work begins.