Sentia Why “OS” not “app”
Experiences plug into the same kernel. Marketplace (R9) only makes sense after the wedge is loved.
About Sentia →Most clinics run on paper + chat, or on EMRs where lab, pharmacy, and doctor charts barely talk. Sentia starts from one event stream.
| Capability | Paper + WhatsApp | Siloed EMR modules | Sentia OS |
|---|---|---|---|
| Single patient truth | — | Often partial | ✓ One stream |
| Ambient documentation | — | Rare / bolt-on | ✓ Draft → human sign |
| Consent revoke that works | — | Policy only | ✓ Kernel enforced |
| Nurse vitals → doctor view | Chase / retype | If integrated | ✓ Instant |
| Lab / Rx on same graph | Separate slips | Interfaces vary | ✓ Shared queues |
| Patient-owned access list | — | Rare | ✓ Companion |
| Offline-tolerant day | Paper only | Vendor-specific | ✓ Queue + sync path |
| AI that can’t silently write | N/A | Varies | ✓ Sign required |
Experiences plug into the same kernel. Marketplace (R9) only makes sense after the wedge is loved.
About Sentia →Gateway and projections over an append-only log — replayable, auditable, consent-gated.
Security →If it was entered once (vitals, order, Rx), every role that is allowed can see it.
Use cases →