Three layers of infrastructure
on one FHIR spine.
Individuals, teams and institutions each act as infrastructure. Every layer writes to an HL7 FHIR-compatible database on a dedicated server, which is what makes a record created anywhere usable everywhere.
Individual, team, institution.
Personal Health Account
The individual holds the account. Connected devices and remote monitoring write into the person's own profile.
Explore → DATA-2Care Team
Screening teams, schools and polyclinics operate as independent integrated systems sharing one record.
Explore → DATA-1Institution
Hospitals, radio-diagnosis applications and public health bodies at district and population level.
Explore →The pieces you actually get.
Dedicated FHIR server
An HL7 FHIR-compatible database on a server of your own, not a shared tenancy.
Open source
The personal health assistant system is open — inspectable, extensible, auditable.
Data porting
Community records move into clinical systems without re-entry or loss of context.
Application porting
Existing public and private platforms adopt the environment rather than replace what they run.
Who may see what, and where it lives.
Consent-based access
A record is released against the consent attached to it, not against who holds the login.
Data residency
Your own server means the record stays in the jurisdiction you choose.
Inspectable by design
Open components can be reviewed by the institutions depending on them.
How a deployment begins.
Put the infrastructure to work.
Most deployments start with a single result type flowing into one system.