Phila Phila Sync Core
Offline-first health infrastructure · South Africa

The records, sync & compliance layer your health product shouldn't have to build.

Phila Sync Core is embeddable, offline-first, POPIA-grade infrastructure — encrypted on-device records, conflict-safe multi-tenant sync, FHIR R4, and an audited supervisor dashboard. You keep your clinical workflow and your brand. We give you the plumbing — live in days, not a quarter of engineering.

Book a scoping call See the live app
Works fully offline POPIA operator-ready FHIR R4 export & push On-device AES-256 encryption Self-hostable
Why this exists

Triage logic went free in 2025. The plumbing underneath it didn't.

Open models (MedGemma, HeAR) commoditised guideline triage and on-device inference — that part is free now.
What's still hard: offline reconciliation, conflict safety, audit, multi-tenancy, FHIR and POPIA hygiene — and no team wants to build it twice.
Phila already did, and it's production-tested — 45 + 7 automated tests, CI, and live in the field.
What you embed

One component. The whole frontline-records stack.

Drop it into your product and inherit the parts that take months to get right.

Offline-first capture & sync

Encrypted IndexedDB store with an in-memory cache; capture on a low-end phone with no signal, then reconcile to your server with last-write-wins conflict safety the moment a connection appears.

On-device encryption at rest

Opt-in PIN → PBKDF2 / AES-256-GCM (WebCrypto) seals every record payload on the device. No key or PIN ever leaves the phone.

Multi-tenant sync server

FastAPI (SQLite/Postgres) or a zero-dependency twin — identical API. Bearer-token auth, per-tenant isolation, audit log, rate-limiting and structured logging out of the box.

Supervisor dashboard

Token-gated, XSS-hardened dashboard: caseload by site and tenant, activity, referral follow-ups, and the full sync audit trail.

FHIR R4 interoperability

Export encounters as a FHIR R4 Bundle (Patient, Encounter, LOINC-coded Observations, Consent…) or push a transaction Bundle straight to any FHIR server.

POPIA operator scaffolding

Consent capture, retention & identity scoping, audit trail, and a written operator-agreement template — so you sign vendors as a compliant operator, not a liability.

Optional add-on — Triage Core: the guideline-based (WHO IMCI / W4SS / PEN-adapted), provenance-cited triage & referral-routing engine as a licensed library. Decision-support, human-in-the-loop — surfaced to your nurse/clinician, who makes every call.

Pricing

Priced as a component, not a platform.

Indicative bands below — final scope and figure are quoted per engagement. Anchored under the closest published comparable (CommCare/Dimagi $100–$4,000/mo).

Integration & Pilot

R25k–R40k once
~$1,400–$2,200 · one-off
  • Embed Sync Core into your stack
  • POPIA operator agreement drafted
  • Your brand on the app
  • Onboarding + a live field pilot
Start a pilot

Add-ons

+R3k–R8k / tenant / mo
Triage Core · decision-support
  • Guideline triage & referral routing
  • Per-rule guideline provenance
  • Priority support / SLA — R5k–R10k/mo
  • Postgres + custom FHIR mapping
Talk options

*Per-seat overage ~R35/seat/mo above a generous bundle, mirroring the standard $2/user model. All figures are starting points — your real number depends on tenants, hosting and support tier.

Honest fit

Who it's for — and who it isn't.

We'd rather tell you upfront than waste a call.

A strong fit if you're…

  • A telehealth, femtech or health-app vendor with clinical staff but no records-infra team.
  • A nurse-led or mobile operator capturing patients where the signal drops.
  • You need POPIA-grade records + FHIR yesterday and don't want to build them.
  • You want to embed and white-label, not buy a closed app.

Not the right tool if you…

  • Need a certified occupational-surveillance EMR-of-record (spirometry, audiometry, signed certificates of fitness).
  • Want an autonomous diagnostic / "the app decides" engine — Phila keeps a human in the loop, always.
  • Expect a validated imaging or cough classifier today (that's a separate, study-backed roadmap).
Built for the regulator's questions

Compliance is the product, not an afterthought.

Human-in-the-loop · not a medical device POPIA operator agreement On-device AES-256 encryption Full audit trail FHIR R4 · interoperable Data stays in your control
FAQ

The questions we always get.

Is Phila a medical device?

No. Phila is decision-support and records infrastructure with a registered nurse or clinician in the loop on every decision. Outputs are screening/triage support and referral routing — never a diagnosis. The licence forbids making diagnostic claims with the component.

How fast can we integrate it?

The component is built, tested and live. A typical integration is a fixed-fee project of a few weeks — embed the store + sync, wire your auth/tenants, draft your operator agreement, brand the app, run a pilot. You write no records/sync/FHIR code yourself.

Why not just use a free open-source CHW toolkit?

You can — if you have a team to configure a platform, host it, harden it for POPIA, and maintain it. Sync Core is the done, embeddable, white-labelled component for teams who want the capability in days without standing up a platform practice.

Where does the patient data live?

On the device first (encrypted), then in your sync server — self-hosted or hosted for you, in South Africa. You are the responsible party; we operate under a written agreement. No data is sent anywhere you don't control.

Do you offer the skin / cough screening shown in demos?

Those are illustrative, non-diagnostic demos only and are not part of the product. A genuinely sellable screening capability requires a trained, validated model and a clinical study — a separate roadmap we'll only ship when it's real.

Stop rebuilding the plumbing. Ship the product.

Tell us what you run today. A 30-minute scoping call tells us whether Sync Core fits — and exactly what your number looks like.

or email phila@ebstar.co directly