Healthcare interoperability · Cloud platform
A regulated FHIR API for clinical systems
Context
The i.s.h.med ecosystem required a cloud-based FHIR API that third parties could use in regulated healthcare environments. Standards conformance, terminology support, product scope and cloud delivery all had to advance as one product rather than separate technical workstreams.
What I owned
Own backlog prioritisation, roadmap execution, release planning, API conception and coordination of standards compliance.
Approach
Translate conformance requirements into product scope and acceptance criteria, then keep engineering, terminology and attestation work aligned through releases. Treat standards and compliance as product requirements with explicit ownership, not as validation work left until the end.
Outcome
The API was implemented and attested against ISiK levels 2 and 3. Martin also shared responsibility for its successful BSI C5 level 1 attestation.