Clinical data
Kivú FHIR
FHIR repositories and services for exposing, exchanging and operating clinical data through standards-based APIs.
What it solves
Every project rebuilds the same foundation
When an architecture needs to persist and serve clinical information through FHIR, the same capabilities come up every time: storage, validation against profiles, and interactions that behave the way the standard says. Rebuilding them from scratch in every initiative spends the budget before reaching the problem that justified it.
Capabilities
FHIR repository
Interoperability APIs
Validation and profiles
Application integration
Where it fits
Services where this component can show up
As one option among several. The service neither depends on Kivú nor assumes it.
This component is an option, not a requirement: Meddyg's services can be delivered on your own infrastructure, on a third party's, or with Kivú components.