Sign up, sign, pay, book
The patient enters, signs the agreement, pays the $39 membership, and chooses a visit.
RonanRx · Internal product atlas
Explore the full patient journey, open every clickable prototype, trace the systems behind care, and reach the operating tools without hunting through disconnected pages.
The path we protect
The real production path now runs from signup through visit, transcript, AI-assisted drafting, physician sign-off, and prescription payment. The visual map shows the full handoff.
The patient enters, signs the agreement, pays the $39 membership, and chooses a visit.
The dashboard’s first “Right now” action informs care without becoming a join gate.
Patient and doctor converge in one room with transcription configured on.
RonanRx prepares the note, Rx suggestion, and ICD suggestions for review.
The prescriber reviews, edits, chooses, reauthenticates, and signs before Rx payment.
Prototype library
The old click path, onboarding flows, patient dashboards, message previews, and engineering diagrams are indexed here as direct links.
Production-style landing and deterministic iMessage intake.
→Seven-document patient packet with typed or drawn signature.
→Simulated Apple Pay, first month free, then $39 per month.
→Business-day and time-slot selection for physician review.
→The original tap-through closing presentation.
→The current shipped flow, click through end to end.
→Post-booking health history with 16 sections and two design modes.
→Review, sign, seal, download, and replay seven agreements.
→Provider details, credentials, pricing, disclosures, and signature.
→The six plain-text agreements behind the provider packet.
→OTP, resend, expiration, lockout, and success states.
→The personal-link arrival screen before document review.
→The original eight high-fidelity patient cases in one index.
→Consolidated switcher across onboarding, review, fulfillment, labs, and check-ins.
→Why the dashboard is the chart and next-action spine.
→New patient onboarding with unsigned text authorization.
→The plan is with the prescriber; nothing is required.
→Preparation underway with pharmacist quality release pending.
→Out-for-delivery state with the standing-order record.
→Month-three continuity and the next refill action.
→Weight and hormone programs reconciled into one priority.
→Reviewed results, ranges, and longitudinal trends.
→A focused 20-second patient check-in action.
→The full-size OpenGraph card for a personal document link.
→The document card in the patient’s actual message context.
→The full-size $39 membership payment card.
→The payment card inside a synthetic patient thread.
→Current scripted flow beside warmer goal-aware conversations.
→Text intake, portal completion, phone OTP, and dashboard.
→How a signed screen changes the clinical conversation.
→Sign, seal, store, record, and retrieve architecture.
→Care loop, agent fan-out, PHI planes, tools, and send guard.
→Plain-English binding rules, approved targets, gaps, and card-level open items.
→Strict spec: tables, fields, integrations, flags, schedules, and dormant code.
→Current implementation evidence, separated from binding product rules and targets.
→Frozen 2026-07-17 census: 177 tables and 2,238 columns, with current main and staging both labeled at 168 tables.
→Naming registry: one canonical name per concept, every alias mapped.
→Generated operating graph with typed nodes and edges, focused views, nested workflows, and complete card specs.
→Interactive status-coded map of patient, doctor, pharmacy, agent, and ops layers.
→No matching surfaces. Try a broader term or another filter.
Operations + architecture
Planning, growth, open work, architecture, and the older directory pages remain available as direct tools.
KPIs, patient momentum, current projects, accounts, and AI usage.
O2Finished work, implementation notes, future work, and open decisions.
O3Priority relationships, growth segments, owners, and follow-ups.
O4Codex and Claude token usage with estimated teammate spend.
O5Care loop, system of record, permissions, architecture, and workstreams.
O6Implementation-ready product and engineering to-dos.
O7The previous clickable-demo directory and its source descriptions.
O8The previous directory for product and engineering flow documents.
O9Palette, typography, wordmark rules, and downloadable logo and font files for design partners.