Polnor.
Hospitals

A modern clinical data warehouse, sovereign, inside your own cloud.

Sovereign by design: hosted on OVHcloud, on infrastructure qualified SecNumCloud 3.2 and HDS-certified, patient data never leaves your perimeter. On top, a full EDS: FHIR (and HL7 v2) ingestion, GDPR de-identification, OMOP, cohorts and clinical AI, with a pipeline where almost every step runs itself.

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

Which patients came back within 30 days?

A care-improvement question, answered on your own clinical data. From your FHIR server to a standardized cohort, without a single row leaving your cloud.

app.your-hospital.fr / eds● health-blind
eds › omop › readmission_30d.sql
▶ Run-- 30-day readmission after an index inpatient stay SELECT count(distinct person_id) cohort, avg(readmit_30d) rate FROM visit_occurrence v JOIN condition_occurrence c USING (person_id) WHERE visit_concept_id = 'inpatient';
results · index cohort0 rows exported ✓
metricvaluewindow
index admissions18,647ref
30-day readmission rate11.4%30d

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

From your FHIR server, or your HL7 v2 feeds

Most French hospitals don't have a FHIR server: they have an integration engine and Ségur-funded HL7 v2 flows (ADT, ORU). Polnor converts those messages to FHIR and lands the same standardized tables. No interface project, no migration.

OMOP · mappingauto
source→ OMOP conceptstd
icd10:I50Heart failureS
icd10:J44COPDS
loinc:718-7HemoglobinS
Almost everything is automated

The platform does the plumbing. Your team does the clinic.

The repetitive, error-prone, compliance-heavy work runs itself, so your clinical and quality teams spend their time on judgment, 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
the clinical question
cohort & index definition
the indicator & its window
the model, and the interpretation
Governance

An EDS you can account for, with a trail behind it.

Every access to patient data is logged, PHI is classified, retention is enforced and export follows EHDS-aligned manifests. Because the warehouse runs on infrastructure you control, qualified SecNumCloud and HDS-certified, and we never train our models on your data, the provenance of every cohort is unambiguous.

Request a demo

From your FHIR server to a defensible cohort, in your cloud.

30 minutes on your clinical case: we run the pipeline on a case like yours and show you exactly where the automation ends and the clinical work begins.