Need Standards Adoption Forced by Regulation
Iris has watched well-designed healthcare data standards stall for years until regulation made them mandatory — FHIR via 21st Century Cures, openEHR via the European Health Data Space. She needs the regulation-to-implementation path to be cheap, demonstrable, and reusable.
Take Control Of Your Signals — Become a Naftiko Design Partner Today!
Persona Story:
Iris has watched well-designed standards (FHIR, openEHR, OMOP) sit on shelves for years until a regulator forced the issue. The 21st Century Cures Act dragged FHIR into US production. PSD2 did the same for open banking. Now the European Health Data Space is the forcing function for openEHR and cross-border patient records — every EU healthcare provider has to implement, even though most still don’t have a model to copy. Iris doesn’t need more standards work. She needs the regulation-to-implementation path to be cheap and demonstrable: a runnable reference for “what does an EHDS-conformant data flow actually look like in code”, forkable by any provider in any country.
Problem Context
- Standards bodies produce schemas; regulators turn them into mandates; providers then need an implementation path that wasn’t part of either
- Each regulated jurisdiction (US Cures, EU EHDS, PSD2, GDPR) ships its own variation; reference implementations are fragmented
- The window between “regulation announced” and “regulation enforced” is the period where reusable reference implementations have outsized impact
- Implementation guidance from regulators is usually narrative and slide-shaped, not runnable — leaving each provider to translate from text to code
Problem Impact
- Smaller providers can’t fund a from-scratch implementation; they wait for vendors who ship late and charge a premium
- Cross-border interoperability stalls because each country produces a slightly-different implementation
- The window between announcement and enforcement closes faster than industry can react, leading to a flurry of last-minute non-conformant implementations
- Standards bodies miss feedback from real implementations because the implementation track is too expensive to run early
Naftiko Today
- Executable YAML capability spec turns a regulator’s data flow into a runnable, forkable artifact — anyone can clone, run, and inspect
- Open-source-by-default capabilities mean the regulation-to-implementation gap is closed in the public domain rather than behind vendor paywalls
- Naftiko Engine runs in any deployment posture (cloud, on-prem, containerized) so the same reference works in different jurisdictional environments
- Spectral ruleset (15 rules) catches non-conformant capabilities before they ship, mapping regulatory expectations to lint rules
Naftiko Tomorrow
- Reference capabilities for major regulated standards (FHIR, openEHR, EHDS, PSD2) maintained in public repos, kept current as standards evolve
- OpenAPI-to-Naftiko import (Second Alpha) — pull regulator-published OpenAPI definitions into capability scaffolds in one step
- JSON Schema Store publication (GA) — regulator-aligned schemas discoverable as a reusable index for any provider
- Fabric capability discovery (v1.1) — providers find peer implementations of a regulation rather than greenfielding their own