Interoperability & security
Built to integrate, and built to be trusted
Biometric speaks standard healthcare data from the data model up. No proprietary lock-in, no export layer bolted on afterwards, and access governed the way clinical systems have to be.
Standards & coding
Standard resources, standard vocabularies
Because clinical data is stored as conformant FHIR with recognised coding systems, it stays portable and future-proof, ready to flow into the systems you already run.
-
HL7 FHIR R4Every clinical resource, on a HAPI FHIR R4 server -
HL7 Physical Activity IGThe prescription model follows the implementation guide -
SNOMED CTClinical concepts, e.g. 229065009 Exercise therapy -
LOINCObservations, e.g. 8867-4 heart rate, 3141-9 body weight -
UCUMUnits of measure, consistently applied
Integration modes
Three ways to meet your EMR
Hospitals keep control of the clinical record. Biometric handles the execution detail and hands the results back.
Read from the EMR
Pull patient context and clinical intent from the record, then execute rehabilitation in Biometric.
Write summaries back
Return adherence and outcome summaries to the EMR so the record stays the source of truth.
SMART on FHIR launch
Launch Biometric directly from the patient chart with single sign-on and scoped, contextual access.
SMART on FHIR is used for authentication, authorisation and clinical context, single sign-on, launched from the chart, with scoped access. It is a way in, not a replacement for the execution platform.
Security & governance
Patient data, handled the way it has to be
Authorisation, provenance, audit and consent are part of the data model, not features layered on top of it.
Care-team-scoped access
Patient data is visible only to the care team responsible for that patient, enforced at the FHIR layer, not just the UI.
Provenance on every change
Each prescription action, sign, modify, hold, resume, revoke, complete, is recorded as a FHIR Provenance with a reason.
Full audit trail
Patient-data access is logged as FHIR AuditEvent, queryable per patient and per practitioner.
FHIR-native consent
Wellness-data sharing with a fitness specialist is granted and revoked by the patient, recorded as a FHIR Consent.
Role-based authorisation
PATIENT, HCP, FITNESS_SPECIALIST and ADMIN, each scoped. Admin manages accounts and has no access to patient health data.
Secured FHIR facade
A read-only, secured /fhir facade means the frontend never touches the FHIR server directly.
Where we are, honestly
Pilot-stage, with the compliance path in view
Biometric is an early-access platform. It is not yet a regulated, generally available product. Here is what's in progress for NHS deployment.
UK GDPR pack
DPIA, records of processing, retention policy and breach process for NHS deployment.
DCB0129 clinical safety
A hazard log and clinical safety officer sign-off, the standard for NHS clinical software.
SaMD pathway
Assessing where the platform sits against medical-device regulation as capability grows.
Multi-tenancy & billing
Organisation-level isolation and commercial billing for trust and clinic deployment.
See it against your integration requirements
Bring your EMR, your information-governance checklist and your hardest questions. We'd rather show you exactly where the platform is.