Skip to main content

Engineering Plan

24 epics, ranked P0–P3 by Atlas-parity priority, mapped to a 7-sprint timeline. Yogini stops using Atlas at month 7.

Priority bands

The 24 epics from the launch briefing, re-ranked by Deepak in the polish round so the team grooms in priority order.

P0 — Yogini-can't-switch-without (11 epics)

Foundation work. Without these, Yogini cannot drop Atlas. Everything in this band is table-stakes parity; the wedge moves come in P1.

EpicWhat
FoundationRepo, CI, deploy pipelines
AuthCognito user/practice flows, session, role gates
Chart shellPatient header + 13 left-rail tabs (Summary, Timeline, Notes, Messages, Tasks, Appointments, Documents, Diagnoses, Prescriptions, Labs, Vitals & growth, Bright Futures, Billing)
SOAP editorInline edit, ICD-10 chips, sign-and-add
VitalsPediatric growth charts, weight/height/BMI tracking
eRxDoseSpot integration, refill queue, controlled-substance gating
CalendarWeek/day view, color-coded visit types, prospect calls
Stripe billingSubscriptions, family rollups, MRR/ARR
SMS + emailTwilio for SMS, transactional email, audit trail
Staff-add-patientFront-desk intake flow
DocumentsUpload, tag, attach to chart, e-sign HIPAA + DPC

P1 — Wedge vs Atlas (5 epics)

The reasons to switch. P0 makes parity possible; P1 makes Atlas indefensible.

EpicWhat
Prospect onboardingMagic-link → family registration → e-sign → Stripe Setup Intent → first-visit booking
Parent app + auto-summaryThe leapfrog. Push notification with plain-language visit summary auto-generated by Claude
AI scribeWhisper transcription + Claude SOAP draft + confidence flags
AI triage + riskInbox prioritization, drug-interaction checks, draft replies
Newborn home visit48h post-discharge premium flow with structured measurements + recording

P2 — Modern polish (3 epics)

Quality-of-life that compounds with the wedge.

P3 — Expansion (5 epics)

Future surface area: new specialties, multi-provider practices, billing analytics deepening, etc.

Sprint mapping

7 sprints (sprint-0 through sprint-7+). Targeting Yogini stops using Atlas at month 7.

SprintFocus
sprint-0Foundation, auth, chart shell scaffold
sprint-1SOAP editor, vitals, calendar
sprint-2Documents, Stripe billing
sprint-3eRx (DoseSpot), SMS + email, staff-add-patient
sprint-4Prospect onboarding, parent app shell
sprint-5AI scribe (Whisper + Claude SOAP draft)
sprint-6Auto-summary push, AI triage + risk
sprint-7+Newborn home visit, polish, expansion

The mapping is in the GitHub epic labels; this table is the human-readable summary.

Erik's read on the timeline

"Most likely the epics you have identified will go FSTR than you have projected — because they are well defined and we have clickable screens."

The clickable prototype removes most ambiguity. Each epic ships against a known target UI.

The gap to plan for

"We need to explicitly create engineering time for Security and Regulation Compliance."

P0–P3 doesn't yet line-item HIPAA pilot work, BAA negotiations with subprocessors, audit prep, or pen-test cycles. We need fractional bandwidth from Poy/Allan for security and infrastructure (covered in Decisions, item 2) and at least one fractional QAA — ideally two.

GitHub backlog

Live in dsurana04/starlight-md.

Supporting docs (in the launch page)

The launch briefing prototype includes a bottom-section docs library:

DocPurpose
MVP definitionWhat ships first
Atlas teardownWhere Atlas falls short, evidence-backed
v1 prioritiesThe wedge moves
Record / documents auditDrizzle schema for clinical records
Visit flow specThe end-to-end visit interaction model
18-patient rosterSample data for the prototype
Chart design rationaleWhy the 13-tab left rail looks the way it does
4 QA agent reportsFindings from the parallel QA pass
Epic backlogThe 24 epics, expanded