In practice
What the platform
actually does.
Aurem is built around three audiences—clinicians, patients, and the clinic itself.
Each gets a surface that earns the standard implied by the name. None ask for more
attention than the work requires.
For your clinicians
A composed clinical record.
The unit of work is a Visit—a flexible container that
adapts to its purpose. Full onboarding, follow-up review, annual review,
consultation-only, prescription-only, letter-only, fitness review, nutrition
review, custom. Each visit type pre-populates the right child entities so
paperwork mirrors the clinical reality of the appointment.
AI assists where the work is repetitive—drafting lab interpretations,
treatment plans, nutritional plans, fitness plans. The clinician reviews,
edits, and signs. Nothing reaches the patient unsigned,
and the sign-off matrix is enforced by the platform: doctors for prescriptions
and treatment plans, nutritionists or doctors for nutritional plans, any
clinician for fitness review.
- Visit lifecycle DRAFT → IN_PROGRESS → UNDER_REVIEW → PUBLISHED → AMENDED
- Doctor's letters and prescriptions on letterhead
- Step-up authentication for destructive actions
- Patient activity log visible to doctor and nurse
For your patients
One record. Theirs.
A single, continuous record across every visit—labs, plans, notes,
prescriptions, history. Patients sign in at your
domain, see your brand, and read content written by
your clinicians.
Self-service registration with a structured intake questionnaire captures
the right information once, then re-administers it on review. Rights under
the Personal Data Protection Act—access, rectification, portability,
erasure with grace—are implemented as real flows, not policy gestures.
Original lab PDFs are preserved unmodified alongside the structured data.
- Public self-signup with PDPA + Informed Consent capture
- Email + magic-link login; trusted devices for thirty days
- In-app notifications alongside email for important events
- One-click data export and deletion request
For the clinic itself
A platform that disappears.
Each clinic runs on its own database, isolated from every other tenant.
Sensitive fields—names, identifiers, biomarker values, plan content,
notes—are encrypted at the field level with keys derived for that clinic
alone. An exfiltrated database is unreadable without the platform's master
key. Privacy is structural, not promised.
A clinic offerings catalog (services and products you provide) is used by
AI when proposing treatment plans, so recommendations stay within what you
actually offer. Audit history records every change with field-level
before-and-after for one-click rollback. The platform is visible only in
the absence of friction.
- Custom domain, palette, typography—rendered at request time
- Per-clinic D1 database, field-level AES-256-GCM encryption
- Append-only audit log with separate clinical activity feed
- Tenant timezone and operating hours drive notification timing