Bringing intake, scheduling, refills, reports, and the practitioner's whole clinical surface into the app your team already built, with Menrva as the system of record instead of Bright.
Your app already works. Phenotype, symptoms, wearables, community, all of it shipped and running on iOS, Android, and web. Patients are in it daily. Bright still owns intake, scheduling, refills, and every screen your practitioners touch.
The original Phase 2 plan was to build seven sync points into Bright and leave your practitioners where they are. Kelly and Betty asked the better question: why build a bridge to a system you want to leave? So Phase 2 changes shape, and Menrva becomes the system of record.
That is 125 development hours of Bright integration coming out and a practitioner workspace going in. Patients get intake, scheduling, refills, and reports in the app they already have. Practitioners get charts, notes, and approvals in the same place. One system, one record, and no API you do not control sitting on the critical path.
Every optional feature is switched on. This is the top of the range.
Priced at your contracted rates. Approving the task list locks this number, and it bills across four milestones: half of design before we start, half at design handoff, half of development at kickoff, half at launch.
Design and development, itemized on the scope pages. Project management, CTO oversight, design review, and QA break out separately so nothing is buried in a lump sum.
Your patients are already registered and logged in. We extend that profile with a clinical baseline, then add full intake, an adaptive follow-up before each visit, and consent signed in the app.
Medplum becomes the system of record, running on the same Postgres and TypeScript stack your app already uses, sharing one database instance, open source, forkable, and yours to white-label later.
Practitioners get charts, encounters, clinical notes, and a working queue for refill approvals and orders, built inside Menrva so the whole practice runs on one system instead of two.
Patients book, reschedule, and request refills against live availability and their current prescription. Every month a single report carries Minerva score, symptom trend, sleep, and wearable data to their practitioner.
A full clinical export, charts and appointment history mapped into Medplum, reconciled record by record, then a dual-run window and a rehearsed cutover with a rollback path tested before the switch.
Clinical roles and permissions, wearables and lab pipelines, a HIPAA security baseline, environments, deploys, monitoring, and a WCAG AA pass across every new surface for a 40-plus audience.
Design does not finish before development starts. Weeks 4 through 9 run both, which is how 14 weeks holds instead of 20. The tradeoff is that design decisions late in a track cost more to change.
Ross, Luiz, and Brianne already know this product inside out, and this is the version Kelly and Betty asked for: Menrva as the system of record, not a bridge to Bright. Six moves, 843 hours before anything optional, live to your patients by January 2027, at your contracted rates across four milestones. Open any line in the scope for the detail. Whenever you are happy with it, just say the word.
Brian Hammond
VP of Sales, FYC Labs
bhammond@fyclabs.com
fyclabs.com