Architecture

One chart. Three doors.

Isolated patient, provider, and admin workspaces share a single in-memory clinical store, a rule engine, and a documented HTTP surface — ready for EHR and device adapters later.

Layers

4

Experience · API · Rules · Store

Roles

3

Never mixed in one shell

Entities

9

Patients through documents

Adapters

2

Bluetooth · EHR (reserved)

Clinic

ATX

Austin, TX

System

Workspaces sit on a shared clinical core.

UI

Role shells

Patient, provider, and admin navigation never share modules. Middleware enforces the prefix.

API

HTTP contracts

CRUD routes for logs, labs, meals, visits, messages, and documents. Same shapes a future EHR can speak.

Core

Store + rules

In-memory clinical graph with Prisma schema as the durable model. Flags for A1c, missed logs, unsigned consents.

Business flow

From enrollment to maintenance.

Referral / self-enroll→Consents→Baseline labs→Program→Titration visits→Maintenance

Care loop

Weekly health logs and meal photos feed the chart. Off-trend values raise a provider task. Messages and the next visit close the loop. Admin watches capacity and unsigned documents.

Log / photo→Rules→Inbox→Visit→Plan update

Data flow

  • Patient writes logs, meals, messages.
  • Provider reads panel, reviews labs, replies, schedules.
  • Admin manages roster, staff, clinic, templates.
  • Future: device writes the same HealthLog fields. EHR consumes the same Appointment and Lab shapes.

Rule engine

Quiet flags, not noisy alerts.

Metabolic rules

A1c ≥ 5.7, fasting insulin above range, triglycerides ≥ 150, hs-CRP ≥ 1.0, three missed weekly weights.

Operations rules

Unsigned consents block visit confirmation. No-show reschedule. Paused patients drop from active panel counts.

Clinic map

Where care happens.

DoctorMetabology · 1210 West 6th Street, Suite 400, Austin, TX

Loading clinic map…