+ {item.title} +
++ {item.body} +
+diff --git a/README.md b/README.md
index ddff1c1..fb1b788 100644
--- a/README.md
+++ b/README.md
@@ -1,10 +1,10 @@
# Medscribe Web
-Public product website for [Medscribe](../README.md) — a privacy-first,
-on-device medical companion in internal beta on iOS and Android.
+Public product website for [Medscribe](../README.md) — a private,
+patient-controlled care companion for iOS and Android.
Built with [create-t3-app](https://create.t3.gg/) (Next.js + TypeScript +
-Tailwind). There is no product database or beta-form backend.
+Tailwind).
Uses **bun** exclusively (`bun.lock`).
@@ -19,12 +19,12 @@ Open [http://localhost:3000](http://localhost:3000).
## Routes
-The first public product slice includes:
+Public routes include:
- `/` — consumer-first portable-context story
- `/how-it-works` — inputs, review loop, medication maintenance, and handoff
-- `/privacy` — data map, sharing limitations, and evidence boundaries
-- `/beta` — expectations and a health-data-free email request
+- `/privacy` — plain-language privacy and patient-control commitments
+- `/access` — health-data-free access request
Named partner print material remains isolated and excluded from search:
@@ -32,10 +32,8 @@ Named partner print material remains isolated and excluded from search:
- `/cvs`
- `/walgreens`
-`/executive-summary` and `/landscape` remain retired/internal and are also
-excluded from search. `SITE_PASSWORD` still gates the entire site when set; a
-future pass should make protection route-specific before the public site is
-deployed alongside private briefs.
+Legacy routes redirect to the current public experience and are excluded from
+search.
### Analytics (optional)
@@ -58,7 +56,8 @@ precomposited iPhone product-bezel assets in
`public/screenshots/product-bezel-2026-08-20/`; there are no raw or CSS-framed
product captures in the rendered site. The versioned path keeps newly captured
UI from being hidden by stale browser or image-optimizer caches.
-Public pages label product imagery as synthetic demo data and beta UI.
+Public pages label product imagery as an illustrative profile and Medscribe
+interface.
### Capturing raw screenshots for the site
diff --git a/src/app/(marketing)/access/page.tsx b/src/app/(marketing)/access/page.tsx
new file mode 100644
index 0000000..7916313
--- /dev/null
+++ b/src/app/(marketing)/access/page.tsx
@@ -0,0 +1,177 @@
+import type { Metadata } from "next";
+import {
+ ArrowRight,
+ CalendarDays,
+ Check,
+ ContactRound,
+ Mail,
+ Pill,
+ Smartphone,
+ Users,
+} from "lucide-react";
+
+import { SectionLabel } from "~/components/section-label";
+import { Badge } from "~/components/ui/badge";
+import { Button } from "~/components/ui/button";
+import { productRelease } from "~/content/product";
+import { ACCESS_INVITE_MAILTO } from "~/lib/access";
+
+export const metadata: Metadata = {
+ title: "Request access",
+ description:
+ "Request access to Medscribe without including personal health information.",
+};
+
+const fitCards = [
+ {
+ icon: Smartphone,
+ title: "Several moving pieces",
+ body: "You coordinate visits, medications, reminders, or follow-ups across everyday life.",
+ },
+ {
+ icon: Users,
+ title: "A trusted care circle",
+ body: "You want an easier way to keep a family caregiver informed when you choose.",
+ },
+ {
+ icon: Check,
+ title: "Clear, reviewable context",
+ body: "You value a record you can read, check, and bring into the next conversation.",
+ },
+] as const;
+
+const productCards = [
+ {
+ icon: CalendarDays,
+ title: "Visits that stay useful",
+ body: "Keep notes, transcripts, summaries, and follow-ups together so the details remain easy to revisit.",
+ },
+ {
+ icon: Pill,
+ title: "Medication routines at a glance",
+ body: "See medications, schedules, reminders, and refill details in one calm, readable place.",
+ },
+ {
+ icon: ContactRound,
+ title: "A ready-to-share picture",
+ body: "Bring selected medications, allergies, conditions, contacts, and preferences together in Know Me.",
+ },
+] as const;
+
+export default function AccessPage() {
+ return (
+ <>
+
+ Medscribe is made for people managing repeated visits, several
+ medications, and the trusted family members who help them stay
+ organized.
+
+ Tell us your platform and whether you are interested as a patient,
+ caregiver, or both.
+
+ Please do not send diagnoses, medication names, visit notes, or
+ other health details. Email is not a medical-support or emergency
+ channel.
+
+ {item.body}
+
+ {item.body}
+
+ Keep your care team in the loop
+
- We are looking for people managing repeated visits or several
- medications, especially family caregiver pairs willing to review
- the record over time and tell us where it fails.
-
- The draft asks only for your platform, whether you are testing as
- a patient, caregiver, or both, and whether you can test with
- another person.
-
- Do not send diagnoses, medication names, visit notes, transcripts,
- or other health details. Email is not a medical-support or
- emergency channel.
-
- {item.body}
-
- Availability is controlled and continuity is not guaranteed.
- Medscribe is not emergency care, diagnosis, dosing guidance, or
- a replacement for your care team.
-
- {item.body}
-
- Current test focus
-
- See what stays local, how sharing works, and the current
- evidence.
-
+ Bring your care context together.
+
+
+ Request Medscribe access
+
+
+ Keep the details close without carrying the whole burden in your
+ head.
+
+
+ {item.title}
+
+
+ Visits, medications, and the people who matter—together.
+
+
+ {item.title}
+
+
+ Medscribe helps you prepare for better conversations. Medical
+ decisions remain with you and your qualified care team.
+
+
- Test the care context, not just the demo.
-
-
- Request access by email
-
-
- The beta needs real maintenance and handoff situations.
-
-
- {item.title}
-
-
- This is collaborative product testing.
-
-
- {item.title}
-
-
- The questions we are trying to answer
-
-
- {testFocus.map((item) => (
-
-
- Want the technical boundaries first?
-
-
- This private, search-excluded route preserves the existing three-page - print document. Use Print PDF (or Cmd+P, then Save as PDF) to export - it. + This page is formatted as a three-page print document. Use Print PDF + (or Cmd+P, then Save as PDF) to export it.
- {TAGLINE} -
-- {SNAPSHOT} -
-{PROBLEM}
-{PROBLEM_BROADER}
-- {DIFFERENTIATION} -
-- Medscribe connects the daily loop to the emergency handoff: one - private record that stays current through normal use and is - ready when the system does not know the patient. -
-- {MOAT} -
-- {FOR_HEALTH_SYSTEMS} -
-- {BETA_SUMMARY} If you'd like to try it, reach out. -
-- Sean O'Connor -
-- Executive Summary · June 2026 -
-- {TAGLINE} -
-- {SNAPSHOT} -
-- {PROBLEM} -
-- {WHO_ITS_FOR} -
-- - {item.title}. - {" "} - {item.body} -
- ))} -- - {item.title}. - {" "} - {item.body} -
- ))} -- - {item.title}. - {" "} - {item.body} -
- ))} -Medscribe is useful at a handoff only if ordinary moments keep the - picture current. Every generated result has a person in the review - loop. + picture clear. You stay in the review loop from the first note to + the next conversation.
- The person reviews summaries and extracted medication fields. - Medscribe does not silently turn model output into an - authoritative medical record. + You review summaries and medication details before they become + part of the record you carry.
- Supported transcription and summarization run locally. The visit - remains available beside the summary so a person can check - follow-ups and wording. + The visit remains available beside the summary so you can check + wording, follow-ups, and the details you want to remember.
- What comes next: a - structured review inbox for accepting, correcting, or dismissing - changes inferred from a visit. + Stay oriented: move + between the transcript and summary whenever you want the fuller + context.
- Synthetic demo data · beta interface + Illustrative profile · Medscribe interface
- Synthetic demo data · beta interface + Illustrative profile · Medscribe interface
- {productClaims.medicationFacts.publicCopy} Schedules can record - whether they are fixed-time or as-needed, the times supplied by - the person's source, confirmation, and timezone. + See medication details, schedules, reminders, and refill + information together without hunting through separate notes.
Medscribe records timing supplied by a label, pharmacist, or @@ -185,27 +181,24 @@ export default function HowItWorksPage() { Know Me is the view. Sharing is a separate choice.
- Open the local Know Me screen when someone needs a concise - picture. For a caregiver, pair devices, compare a safety number, - review the record, and manually export an encrypted snapshot. + Open Know Me when someone needs a concise picture. Review the + details first, then show or share the selected context with a + trusted caregiver.
- The current import path does not yet require the sender to be in - the recipient's active trust list, so recipients must - verify the sender out of band. Revocation prevents a future - local export; it cannot invalidate already-exported ciphertext - or erase a copy the recipient imported. + You stay in control of the handoff: what is included, who sees + it, and when the conversation happens.
- Synthetic demo data · beta interface + Illustrative profile · Medscribe interface
- Read what stays local, what can use a network, and what remains - unfinished. + See how Medscribe keeps you in control of the context you keep, + review, and share.
- {INTRO} -
-- {item.examples} -
-- AlignCare matches the consumer bundle on paper: visit recording, - summaries, an AI assistant, medication reminders and logging, - documents, and caregiver sharing. It is real competition, not a - strawman. -
-- The openings it leaves: its app-store disclosures indicate cloud - collection and tracking rather than on-device processing; it has no - first-class emergency handoff for a patient who cannot explain - themselves; and its medication answers are not described as - deterministic, on-device, facts-first rendering. Those are - Medscribe's wedges. -
-- Each box above has partial substitutes. No single incumbent unites - all of this into one private, patient-owned record: -
-- That intersection, the daily maintenance loop that keeps an - emergency-ready record current and private by architecture, is the lane - Medscribe is built to own. -
-Visits, medications, and the critical details between them—kept - together on the device you carry. + together wherever care takes you.
- Synthetic demo data · beta interface + Illustrative profile · Medscribe interface
- The missing picture + The connected picture
Bring in typed notes, a portal screenshot, a document, or an - optional consent-gated recording. The work happens locally. You - decide what is useful. + optional consent-gated recording. You decide what is useful and + what belongs in your record.
@@ -239,7 +239,7 @@ export default function HomePage() { Between visits
The list, the label, the schedule, and the latest confirmation @@ -272,16 +272,16 @@ export default function HomePage() {
- Ask about a visit or medication without uploading the record to a - remote model. Answers are grounded in local history and bundled - facts, with the boundary kept in view. + Ask about a visit or medication using the context you have already + collected. Answers help you prepare for a clearer conversation.
Informational only. Medication changes still belong with a
@@ -325,7 +324,7 @@ export default function HomePage() {
Know Me gathers selected medications, allergies, conditions, - baseline, and contacts into one readable snapshot. Freshness - signals show what may need another look. + baseline, and contacts into one readable snapshot that is easy + to review together.
- Manually export an encrypted copy for a paired recipient. + Share selected context with someone you trust.
- Pair by QR code, compare a safety number, and choose when to - export. The caregiver imports a local copy on their device. + Choose the context that helps, review it first, and share it + with a trusted caregiver when the moment calls for it.
- Manual today—not live sync or a household cloud account. - Import-side sender trust enforcement is still being hardened; - revocation cannot recall a copy already exported. -
- A precise privacy boundary + Privacy that feels personal
- The working record and supported AI tasks stay on the device. - Medication facts come from bundled references, not a model trying - to remember medicine. + Medscribe keeps the experience focused on your choices: what you + keep, what you review, and what you share with people you trust.
- The right beta participant + Made for people who carry a lot
- This is an internal beta. Expect close feedback, manual review, - rough edges, and possible resets—not guaranteed continuity. + Bring visits, medication routines, and trusted caregivers into one + clearer picture—without losing your place at the center.
- Start with your platform and whether you are testing as a patient, - caregiver, or both. Please do not email health details. + Start with your platform and whether you are interested as a + patient, caregiver, or both. Please do not email health details.
- “Local” is not a magic word. Here is where each task happens, when a - network can be involved, what the design protects, and what it does - not. +
+ Medscribe is designed around a simple idea: you should be able to + carry useful care context without giving up control of it.
| - {heading} - | - ))} -|||
|---|---|---|---|
| - {row.task} - | -- {row.location} - | -- {row.network} - | -- {row.control} - | -
- {item.body} -
-- New snapshots use authenticated encryption targeted to the - recipient key. Ciphertext integrity and wrong-recipient - rejection are tested. The current import path does not yet - require the sender to be in the recipient's active trust - list, and recipient-key metadata is not authenticated and - checked on import. Verify the sender out of band. The beta does - not claim the Signal protocol or live synchronization. -
-- The practical rule -
-- Medication language is based on named public reference datasets, - but condensed wording is not FDA-reviewed. Coverage counts - describe the bundle; they do not prove clinical completeness. -
-+ {item.body} +
+ + ); + })} +
- Source families include openFDA label data, RxNorm terminology,
- MED-RT and DailyMed class inputs, plus a bounded high-priority
- interaction list. Release dates and full methodology should be
- published with each wider release.
+
+ The important part is not technical vocabulary. It is knowing what
+ Medscribe is for, what you can control, and when another person
+ sees your information.
+ {item.body}
+
+ Your choices
+
- The internal beta is focused on correctness, comprehension, and
- caregiver handoffs.
+
+ Follow the journey from a visit to a medication routine and a
+ trusted handoff.
+ Privacy should feel understandable.
+
+
+ {item.title}
+
+
- Designed to protect against
-
-
- {protects.map((item) => (
-
-
- It does not eliminate
-
-
- {doesNotProtect.map((item) => (
-
-
- Help test the boundary.
+
+ Keep the context that helps. Share it when it matters.
-
+ {choices.map((item) => (
+
+
+ See how Medscribe fits into the day.
+
+