Solum
Solum
Clinical EHDS compliance layer — enforce, translate, evidence.
In development · Stage 1BUSL-1.1 · Stage 1 · EHDS-oriented · FHIR
Solum is Stage 1: actively developed and installable from source. Technical readiness only — not a named pilot portfolio.
Why Solum exists
Built so clinics, labs, pharmacies, and Health-Tech / HMIS vendors can run technical controls relevant to EHDS- and data-protection-oriented duties without a large compliance organisation. Solum is a compliance layer beside your systems of record: enforce jurisdiction policy, translate interchange (FHIR first), and produce evidence—on infrastructure you control. It does not claim legal compliance on your behalf.
Two clear paths
Same product, two operating stories. Ferrum is never required to run Solum.
Standalone compliance layer
For organisations that need clinical compliance controls without adopting Ferrum. You keep your EHR/HMIS; Solum sits beside it for policy enforcement, field encryption, consent/access evidence, and FHIR-oriented interchange.
Optional Ferrum companion
For teams that already use or plan Ferrum for genomic / research infrastructure and need a clinical compliance plane next to it—not a second genome platform. Shared Crypt4GH envelope format; companion surfaces are additive and optional.
Ferrum + Solum together
Clinical compliance beside a genomic GA4GH plane: optional companion, shared Crypt4GH patterns, one joint pilot conversation when both planes matter.
Ask about Ferrum + SolumWhat Stage 1 already does
Benefit language maps to implemented Stage-1 capabilities. It does not claim legal compliance on your behalf.
- Jurisdiction rules as data — TOML profiles checked at startup; refuse to start on contradictory residency, key-custody, audit, or consent posture.
- Field encryption under customer-controlled keys (Crypt4GH); optional AWS KMS path is feature-gated and off by default.
- Capability-checked authorisation that fails closed, plus a durable hash-chained audit trail you can export and verify.
- FHIR-oriented interchange with an IPS-oriented Patient Summary binding in Stage 1; broader EEHRxF categories remain on the roadmap.
EU and African health markets
Equal core markets. EU orientation tracks EHDS-style readiness for primary-use interoperability. African jurisdictions are modelled as profile data—not a single “GDPR clone.” Kenya is the first African profile in-tree (provisional after engineering review—not production / not ODPC-certified until qualified legal review). Nigeria- and South Africa–oriented profiles remain planned.
Orientation, not legal advice
Stage 1 technical controls for EHDS- and data-protection-oriented duties. Evidence you interpret with your counsel and governance — not a legal compliance certificate by itself.
Institutional pricing (indicative)
Evaluation and permitted research use under BUSL can be licence-fee-free. Production clinical / commercial operation needs a written agreement. Track A is the sidecar beside your EHR; Track B adds an optional openEHR CDR plane (partner UIs — we do not sell a hospital EHR).
| Item | Guide (net EUR) |
|---|---|
| Track A — single-site sidecar | €12,000–28,000 / year |
| Track B — CDR add-on | +€8,000–20,000 / year (+ implementation at €800–1,200/day consulting rate) |
| Track A pilot (60–90 days) | €8,000–18,000 fixed |
| Support | Standard included · Priority +15% · Enterprise +30% |
Indicative only — Stage 1 maturity. Binding terms in writing. Optional Ferrum companion quoted separately.
Year-1 worked example (indicative)
A single-site DIC piloting Ferrum + Solum Track A together often lands around €18k–38k in Year 1 before support uplifts: Ferrum pilot €10k–20k (creditable toward year-1 licence) plus Solum Track A pilot €8k–18k. Multi-site and Track B CDR add-ons sit above that band. Binding totals only in writing.
Support tiers
Same support model as Ferrum for paid institutional licences and support agreements.
Delivered by a small team (founder-scale), business hours CET/CEST, Monday–Friday (Baden-Württemberg holidays excluded). Not a 24/7 NOC.
| Tier | First response | Hours / channels |
|---|---|---|
| Standard | 2 business days | Business hours CET · email / ticket · included |
| Priority | 8 business hours | Business hours CET · email + scheduled call · typically +15% |
| Enterprise | 4 business hours | Extended 07:00–20:00 CET · dedicated contact · typically +30% |
First response means acknowledgment and triage, not resolution. BUSL research use may get good-faith community replies without a contractual SLA.
Numeric production uptime percentages are not a standing vendor promise for customer-hosted deployments. Enterprise uptime SLA only if a signed SOW defines measurable scope; otherwise N/A.
What Solum is not
- Not a full hospital EHR UI from Synaptic Four. An optional openEHR CDR (Track B) offers APIs for partners to persist clinical data—your systems of record remain yours.
- Not a medical device and not diagnosis or therapy support.
- Not a legal compliance certificate by itself—technical controls and evidence you still interpret with counsel and governance.
Technical reports
Stack architecture notes (DOI’d) that technical evaluators can cite — Ferrum-focused, relevant when Solum runs beside it.