+ {item.title} +
++ {item.body} +
+
+
+
+
+
+
+ {productRelease.stage}
+ {productRelease.platforms}
+
+ + Test the care context, not just the demo. +
++ 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. +
+
+
+
+
+
+ + Request access by email +
++ 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. +
+
+ A good fit
+
+ + The beta needs real maintenance and handoff situations. +
+
+ {[
+ {
+ icon: Smartphone,
+ title: "Several moving pieces",
+ body: "You regularly coordinate visits, medication reminders, or follow-ups.",
+ },
+ {
+ icon: Users,
+ title: "A caregiver relationship",
+ body: "You can test a deliberate handoff with a trusted family caregiver.",
+ },
+ {
+ icon: Check,
+ title: "Comfort reviewing",
+ body: "You understand generated information can be wrong and will check it.",
+ },
+ ].map((item) => {
+ const Icon = item.icon;
+
+ return (
+
+
+
+ );
+ })}
+
+
+
+
+
+
+
+ What to expect
+
+ + This is collaborative product testing. +
++ Availability is controlled and continuity is not guaranteed. + Medscribe is not emergency care, diagnosis, dosing guidance, or + a replacement for your care team. +
+
+ {expectations.map((item) => {
+ const Icon = item.icon;
+
+ return (
+
+
+
+ );
+ })}
+
+ + {item.title} +
++ {item.body} +
+
+
+
+
+
+
+
+ + Current test focus +
++ The questions we are trying to answer +
+-
+ {testFocus.map((item) => (
+
- + + {item} + + ))} +
+
+
+
+
+ + Want the technical boundaries first? +
++ See what stays local, how sharing works, and the current + evidence. +
+
+ Executive summary · Northwell Health
+
+
+ );
+}
diff --git a/src/app/(marketing)/cvs/page.tsx b/src/app/(marketing)/cvs/page.tsx
new file mode 100644
index 0000000..b7d6b39
--- /dev/null
+++ b/src/app/(marketing)/cvs/page.tsx
@@ -0,0 +1,32 @@
+import type { Metadata } from "next";
+
+import { CvsPrintSummary } from "~/components/cvs-print-summary";
+import { PrintButton } from "~/components/print-button";
+import { SectionLabel } from "~/components/section-label";
+
+export const metadata: Metadata = {
+ title: "CVS executive summary",
+ robots: { index: false, follow: false, nocache: true },
+};
+
+export default function CvsSummaryPage() {
+ return (
+ <>
+ + The health-system executive summary +
++ 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. +
+
+
+
+ Executive summary · CVS Health
+
+
+ );
+}
diff --git a/src/app/(marketing)/executive-summary/page.tsx b/src/app/(marketing)/executive-summary/page.tsx
index 20d129c..952395f 100644
--- a/src/app/(marketing)/executive-summary/page.tsx
+++ b/src/app/(marketing)/executive-summary/page.tsx
@@ -21,6 +21,7 @@ export const metadata: Metadata = {
title: "Executive Summary",
description:
"One-page executive summary for Medscribe, a private medical context app for families managing complex care.",
+ robots: { index: false, follow: false, nocache: true },
};
const TAGLINE =
diff --git a/src/app/(marketing)/how-it-works/page.tsx b/src/app/(marketing)/how-it-works/page.tsx
new file mode 100644
index 0000000..3ada5d5
--- /dev/null
+++ b/src/app/(marketing)/how-it-works/page.tsx
@@ -0,0 +1,268 @@
+import type { Metadata } from "next";
+import {
+ ArrowRight,
+ Camera,
+ Check,
+ FileText,
+ Keyboard,
+ Mic,
+ ShieldAlert,
+} from "lucide-react";
+import Link from "next/link";
+
+import { PhoneMockup } from "~/components/phone-mockup";
+import { SectionLabel } from "~/components/section-label";
+import { Badge } from "~/components/ui/badge";
+import { Button } from "~/components/ui/button";
+import { productClaims } from "~/content/product";
+
+export const metadata: Metadata = {
+ title: "How it works",
+ description:
+ "See how Medscribe turns visits and medication routines into one local record a person can review and carry.",
+};
+
+const inputs = [
+ {
+ icon: Keyboard,
+ title: "Type or paste",
+ body: "Start from notes you already have and keep the source close to the result.",
+ },
+ {
+ icon: Camera,
+ title: "Import a screenshot",
+ body: "Bring in a portal summary or prescription label, then correct extracted fields.",
+ },
+ {
+ icon: FileText,
+ title: "Attach a document",
+ body: "Use a photo or document as the input to a local review workflow.",
+ },
+ {
+ icon: Mic,
+ title: "Record with consent",
+ body: "Optional visit audio requires consent and is transcribed on the device.",
+ },
+] as const;
+
+const boundaries = [
+ "It does not diagnose or recommend treatment.",
+ "It does not calculate, shift, or supply medication timing.",
+ "It does not replace a pharmacist, prescribing team, or emergency service.",
+ "It does not automatically synchronize a household in the background.",
+] as const;
+
+export default function HowItWorksPage() {
+ return (
+ <>
+ + The pharmacy executive summary +
++ This page is formatted as a two-page print document: the medication + record that moves adherence, keeps refills, and lowers cost of care. + Use Print PDF (or Cmd+P, then Save as PDF) to export it. +
+
+
+
+ Current beta workflow
+
+ + One record, built through everyday use. +
++ Medscribe is useful at a handoff only if ordinary moments keep the + picture current. Every generated result has a person in the review + loop. +
+
+ Start where the information is
+
+ + Four ways in. One review checkpoint. +
+
+ {inputs.map((item, index) => {
+ const Icon = item.icon;
+
+ return (
+
+
+ );
+ })}
+
+
+
+
+
+
+ 0{index + 1}
+
+
+ + {item.title} +
++ {item.body} +
+
+
+
+ + The person reviews summaries and extracted medication fields. + Medscribe does not silently turn model output into an + authoritative medical record. +
+
+
+
+
+
+
+ Review what changed
+
+ + A summary is a draft, not a verdict. +
++ Supported transcription and summarization run locally. The visit + remains available beside the summary so a person can check + follow-ups and wording. +
++ What comes next: a + structured review inbox for accepting, correcting, or dismissing + changes inferred from a visit. +
+
+
+ + Synthetic demo data · beta interface +
+
+
+
+
+
+ + Synthetic demo data · beta interface +
+
+ Maintain the medication picture
+
+ + Facts and schedules carry their boundary with them. +
++ {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. +
++ Medscribe records timing supplied by a label, pharmacist, or + prescribing team. It does not calculate or shift medication + times. +
+
+
+
+ Prepare the handoff
+
+ + 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. +
++ 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. +
+
+
+ + Synthetic demo data · beta interface +
+
+
+
+
+
+
+
+ + What Medscribe does not do +
++ A useful boundary is part of the product, not fine print after it. +
+-
+ {boundaries.map((item) => (
+
- + + {item} + + ))} +
+
+
+
+
+ + See the trust boundary task by task. +
++ Read what stays local, what can use a network, and what remains + unfinished. +
+
- {/* Phone floats right on sm+; prose sections wrap around it like a newspaper column */}
-
-
-
-
- {/* Origin */}
-
- Executive summary · Northwell Health
-
- Be known when care gets complicated
+ <>
+
- Be known when care gets complicated
+ <>
+
+
+
+
+
+ {productRelease.stage}
+
+
+ {productRelease.platforms}
+
+
+
+ Carry the context.
-
-
- A grandfather with three adult children, each living twenty to
- fifty minutes away. None able to be at every appointment. No
- shared, current view of his medications, his visits, or what had
- changed.
-
-
- Then came the emergency. A fall. A hospital that did not
- understand his condition. Some of his medications were
- time-critical. They were administered incorrectly, his decline was
- misread, the wrong path was taken, and he passed six weeks later.
- The clinicians were not negligent. The system was blind to who he
- was, and no trustworthy picture of him existed to hand over.
-
-
- Medscribe is the private, patient-owned record built for that gap:
- the whole picture, held by the patient, ready to hand over the
- moment the chart in front of you doesn't have it.
-
-
-
- On-device · no cloud AI
- Emergency-ready
- Complements Epic
- iOS · Android beta
-
-
-
- {/* What it is */}
-
- What it is
-
- A medical record the patient owns and carries
-
-
- Current medications, allergies, baseline, visit summaries, and an
- emergency “know-me” record, kept current through
- everyday use, and ready to hand to a caregiver, a new doctor, or an
- ER in seconds. Everything runs on the device. Nothing is uploaded.
+
+ Visits, medications, and the critical details between them—kept
+ together on the device you carry.
-
-
- How the record stays current (live in beta today)
-
-
- -
- Visit summaries: type
- or paste notes, import MyChart and portal after-visit summaries
- from a screenshot, or attach photos and documents; optional
- consent-gated audio recording for patients who want it. Any path
- feeds the same on-device summary.
-
- -
- Medication management:
- pill-bottle label recognition, reminders, and on-device Q&A
- grounded in FDA drug facts
-
- -
- Emergency handoff: a
- know-me card and encrypted caregiver sharing, patient-controlled
-
-
-
- Structured MyChart / FHIR export import is on the roadmap:
- import-and-own, not write-back.
-
+
+
+
-
+
- {/* The gap Epic's own tools can't close */}
-
- Where the picture breaks
-
- Epic knows what Epic sees
-
-
- MyChart is excellent inside the Epic walls. It puts the chart on the
- patient's phone, links their Epic portals through MyChart
- Central, and lets them share with a caregiver or a provider. What no
- institutional record can be is the whole picture: the urgent care,
- the community specialist, the facility that isn't on Epic; the
- changes between visits; the context a patient keeps themselves. Epic
- aggregates Epic. And when it matters most, at an out-of-network ER,
- or when the patient can't generate a share code, the record
- that's actually there is the one they already carry.
+
+
+
+ Synthetic demo data · beta interface
-
+
+
- {/* What makes it different */}
-
- What makes it different
-
- No one else owns the whole job
-
-
- Existing Electronic Health Record (EHR) systems owns the
- institutional view, and every institutional tool stops at its own
- walls. Around them, the market is full of single-purpose apps: visit
- notetakers, medication trackers, record vaults, emergency-ID cards.
- Each owns one slice. None holds a private, patient-owned record that
- spans every system, Epic and non-Epic alike, stays current through
- daily use, and is ready to hand over in a crisis, all on the
- patient's own device. Medscribe is that combination, beside
- Epic, not instead of it.
+
+
+
+ The missing picture
-
+
+ Care happens in fragments. Your context shouldn't.
+
+
+ One instruction lives in a portal. A medication label sits in a
+ cabinet. The latest change lives in someone's memory. Medscribe
+ is the patient-held thread between those moments.
+
+
+
- {/* Why it fits Northwell: clear float so the card grid spans full width */}
-
-
- Why it fits Northwell
-
- Built to strengthen the Epic investment, not compete with it
+
+
+
+
+ After the visit
+
+
+ Turn what happened into something you can check.
+
+ Bring in typed notes, a portal screenshot, a document, or an
+ optional consent-gated recording. The work happens locally. You
+ decide what is useful.
+
+
+
+ The safety loop:{" "}
+ review generated information before acting. Medscribe does not
+ diagnose, prescribe, or replace clinical verification.
+
+
-
- {fit.map((item) => {
- const Icon = item.icon;
+
+
+ {visitMoments.map((moment) => (
+ -
+
+
+
+ {moment.number}
+
+
+ {moment.eyebrow}
+
+
+
+ {moment.title}
+
+
+ {moment.body}
+
+
+
+
+
+ ))}
+
+
+
+
+
+
+
+
+
+ Between visits
+
+
+ Keep the medication picture from going stale.
+
+
+ The list, the label, the schedule, and the latest confirmation
+ belong in the same view—not scattered across paper and memory.
+
+
+
+
+
+
+
+
+
+ {item.title}
+
+
+ {item.body}
+
+
+ ))}
+
+
+
+
+
+
+
+
+
+ Ask from the record
+
+
+ Better questions begin with your context.
+
+
+ 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.
+
+
+ Informational only. Medication changes still belong with a
+ clinician or pharmacist.
+
+
+
+
+
+
+
+
+
+
+
+ At the handoff
+
+
+ Bring the picture when the chart is incomplete.
+
+
+ Know Me gathers selected medications, allergies, conditions,
+ baseline, and contacts into one readable snapshot. Freshness
+ signals show what may need another look.
+
+
+
+
+
+ Quick handoff
+
+
+ Show or share a selected, readable snapshot.
+
+
+
+
+
+ Caregiver copy
+
+
+ Manually export an encrypted copy for a paired recipient.
+
+
+
+
+
+
+
+
+
+
+
+ Share a snapshot. Not an invisible feed.
+
+
+ Pair by QR code, compare a safety number, and choose when to
+ export. The caregiver imports a local copy on their device.
+
+
+
+ {[
+ ["1", "You review", "Choose the record to send"],
+ ["2", "Encrypted copy", "Protected for the recipient key"],
+ ["3", "They import", "A local, readable snapshot"],
+ ].map(([number, title, body]) => (
+ -
+
+ {number}
+
+
+ {title}
+
+
+ {body}
+
+
+ ))}
+
+
+
+ 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
+
+
+ Local changes what you have to trust.
+
+
+ The working record and supported AI tasks stay on the device.
+ Medication facts come from bundled references, not a model trying
+ to remember medicine.
+
+
+
+
+ {proofStats.map((stat) => (
+
+ - {stat.label}
+ -
+ {stat.value}
+
+
+ ))}
+
+
+
+ {privacyPrinciples.map((principle) => {
+ const Icon = principle.icon;
return (
-
-
-
- {item.title}
- {item.body}
-
-
+
+
+
+ {principle.title}
+
+
+ {principle.body}
+
+
);
})}
-
- {/* Who's behind it + the ask */}
-
-
-
-
-
- Who's behind it
-
-
- Sean O'Connor, a Bucknell computer science and engineering
- graduate, built Medscribe after watching his own family try to
- hold this together for his grandfather, when the record
- scattered exactly at the moment it mattered most. It is live in
- beta on iOS and Android today.
-
-
- The ask is a short conversation about whether a patient-owned
- record that spans the systems Epic can't reach, and feeds
- that context back into Northwell's Epic, is worth
- exploring together.
-
-
-
+
+
+
+
+
+
+ The right beta participant
+
+
+ Help build the record people can actually carry.
+
+
+ This is an internal beta. Expect close feedback, manual review,
+ rough edges, and possible resets—not guaranteed continuity.
+
+
+ {betaFit.map((item) => (
+ -
- Start the conversation
-
-
-
-
-
-
+
+
+
+ {item}
+
+ ))}
+
+
+
+
+
+
+ Start with your platform and whether you are testing as a patient,
+ caregiver, or both. Please do not email health details.
+
+
+
+
);
}
diff --git a/src/app/(marketing)/privacy/page.tsx b/src/app/(marketing)/privacy/page.tsx
new file mode 100644
index 0000000..b947ebe
--- /dev/null
+++ b/src/app/(marketing)/privacy/page.tsx
@@ -0,0 +1,388 @@
+import type { Metadata } from "next";
+import {
+ AlertTriangle,
+ ArrowRight,
+ Check,
+ Database,
+ FileCheck2,
+ KeyRound,
+ LockKeyhole,
+ Wifi,
+} from "lucide-react";
+import Link from "next/link";
+
+import { SectionLabel } from "~/components/section-label";
+import { Badge } from "~/components/ui/badge";
+import { Button } from "~/components/ui/button";
+import { productClaims, productRelease } from "~/content/product";
+
+export const metadata: Metadata = {
+ title: "Privacy & evidence",
+ description:
+ "A task-by-task view of Medscribe's local architecture, network behavior, caregiver sharing, evidence, and beta limitations.",
+};
+
+const dataMap = [
+ {
+ task: "Visit transcription",
+ location: "Device",
+ network: "No cloud inference",
+ control: "Recording requires consent",
+ },
+ {
+ task: "Summary generation",
+ location: "Device",
+ network: "No cloud inference",
+ control: "The person reviews output",
+ },
+ {
+ task: "Medication-label OCR",
+ location: "Device",
+ network: "No cloud inference",
+ control: "Extracted fields remain editable",
+ },
+ {
+ task: "Drug facts and known pairs",
+ location: "Bundled on device",
+ network: "No runtime fact lookup",
+ control: "Sources and coverage are disclosed",
+ },
+ {
+ task: "Model installation or update",
+ location: "Downloaded to device",
+ network: "Network may be required",
+ control: "Approved URLs and file integrity checks",
+ },
+ {
+ task: "Caregiver sharing",
+ location: "Encrypted device-to-device snapshot",
+ network: "The person chooses ciphertext transport",
+ control: "Verify out of band; import trust enforcement is incomplete",
+ },
+ {
+ task: "Primary record storage",
+ location: "Local app database",
+ network: "No Medscribe cloud account",
+ control: "The unlocked device remains a trust boundary",
+ },
+ {
+ task: "Website analytics",
+ location: "Marketing site only",
+ network: "Optional Umami script when configured",
+ control: "Disabled when no website ID is configured",
+ },
+] as const;
+
+const protects = [
+ "Runtime disclosure of visits or medications to a cloud AI provider",
+ "A Medscribe account database becoming the default copy of the record",
+ "A readable caregiver export being sent to someone who was not paired",
+] as const;
+
+const doesNotProtect = [
+ "Information viewed on an unlocked or compromised phone",
+ "A snapshot that a verified recipient already imported",
+ "Someone intentionally copying or sharing visible information",
+ "Every possible drug interaction or model failure",
+] as const;
+
+export default function PrivacyPage() {
+ return (
+ <>
+
+
+
+
+ Last verified {productRelease.verifiedOn}
+
+ Internal beta
+
+
+ Privacy should be specific enough to challenge.
+
+
+ “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.
+
+
+
+
+
+
+ Data map
+
+ Task by task, not “everything” absolutes.
+
+
+
+
+
+ Medscribe tasks, processing location, network behavior, and user
+ control
+
+
+
+ {[
+ "Task",
+ "Where it happens",
+ "Network behavior",
+ "User control",
+ ].map((heading) => (
+
+ {heading}
+
+ ))}
+
+
+
+ {dataMap.map((row) => (
+
+
+ {row.task}
+
+
+ {row.location}
+
+
+ {row.network}
+
+
+ {row.control}
+
+
+ ))}
+
+
+
+
+
+
+
+
+
+ {[
+ {
+ icon: LockKeyhole,
+ title: "Supported AI work stays local",
+ body: productClaims.localAi.publicCopy,
+ },
+ {
+ icon: Database,
+ title: "The primary record stays local",
+ body: `${productClaims.localRecord.publicCopy} The beta relies on the device and operating system's protections; it does not claim a separately encrypted app database.`,
+ },
+ {
+ icon: Wifi,
+ title: "Downloads are the network exception",
+ body: "Installing or updating a model can require a network. Approved model files are checked against an expected SHA-256 digest before use.",
+ },
+ ].map((item) => {
+ const Icon = item.icon;
+
+ return (
+
+
+
+
+
+ {item.title}
+
+
+ {item.body}
+
+
+ );
+ })}
+
+
+
+
+
+
+
+
+
+
+
+ Caregiver sharing
+
+ Verify a person, then export deliberately.
+
+
+ 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
+
+
+ {[
+ "Compare the safety number with the intended caregiver.",
+ "Review the snapshot before every material export.",
+ "Re-export after important changes; it is not automatic.",
+ "Treat revocation as a block on future local exports; it cannot invalidate already-exported ciphertext.",
+ ].map((item, index) => (
+ -
+
+ {index + 1}
+
+ {item}
+
+ ))}
+
+
+
+
+
+
+
+
+ Evidence, not superlatives
+
+
+
+ What the current release can actually point to.
+
+
+
+ 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.
+
+
+
+
+ {[
+ [
+ productRelease.drugFacts.toLocaleString(),
+ "Condensed drug records",
+ ],
+ [
+ productRelease.rxNormTerms.toLocaleString(),
+ "RxNorm search terms",
+ ],
+ [
+ productRelease.interactionPairs.toLocaleString(),
+ "Known high-priority pairs",
+ ],
+ [
+ productRelease.flaggedForReview.toLocaleString(),
+ "Records flagged for review",
+ ],
+ ].map(([value, label]) => (
+
+ -
+ {label}
+
+ -
+ {value}
+
+
+ ))}
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+
+
+
+ Designed to protect against
+
+
+
+ {protects.map((item) => (
+ -
+ {item}
+
+ ))}
+
+
+
+
+
+
+ It does not eliminate
+
+
+
+ {doesNotProtect.map((item) => (
+ -
+ {item}
+
+ ))}
+
+
+
+
+
+
+
+ Help test the boundary.
+
+
+ The internal beta is focused on correctness, comprehension, and
+ caregiver handoffs.
+
+
+
+
+
+
+ );
+}
diff --git a/src/app/(marketing)/walgreens/page.tsx b/src/app/(marketing)/walgreens/page.tsx
new file mode 100644
index 0000000..1dcc2b6
--- /dev/null
+++ b/src/app/(marketing)/walgreens/page.tsx
@@ -0,0 +1,33 @@
+import type { Metadata } from "next";
+
+import { PrintButton } from "~/components/print-button";
+import { SectionLabel } from "~/components/section-label";
+import { WalgreensPrintSummary } from "~/components/walgreens-print-summary";
+
+export const metadata: Metadata = {
+ title: "Walgreens executive summary",
+ robots: { index: false, follow: false, nocache: true },
+};
+
+export default function WalgreensSummaryPage() {
+ return (
+ <>
+ Executive summary · Walgreens
+
+ The pharmacy executive summary
+
+
+ This page is formatted as a two-page print document: what Medscribe
+ can do, and how every capability pays off twice, for the patient and
+ for Walgreens. Use Print PDF (or Cmd+P, then Save as PDF) to export
+ it.
+
+
+
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+ 
+ {page === 1 ? (
+
+
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+ 
+
+ Medscribe
+
+
+
+ Executive summary · CVS Health
+
+
+ ) : null}
+
+ {children}
+
+
+
+ );
+}
+
+const capabilities = [
+ {
+ icon: Mic,
+ title: "Understand a visit",
+ body: "Type, paste, snap the after-visit summary, or record the conversation with consent. Medscribe transcribes and summarizes it on the phone.",
+ },
+ {
+ icon: ScanLine,
+ title: "Read a pill bottle",
+ body: "Point the camera at a prescription label and the drug, dose, and schedule land in the record automatically.",
+ },
+ {
+ icon: MessageSquare,
+ title: "Answer the hard questions",
+ body: "Ask whether two medications are safe together and get an answer grounded in bundled FDA drug facts and known interaction pairs, not a chatbot's guess.",
+ },
+ {
+ icon: Layers,
+ title: "Hold the whole picture",
+ body: "Medications, allergies, conditions, baseline, and visit history across every provider, in one place the patient owns.",
+ },
+ {
+ icon: HeartPulse,
+ title: "Be ready for an emergency",
+ body: "A patient-controlled Know Me card puts the time-critical facts one tap away for a caregiver or an ER.",
+ },
+ {
+ icon: ShieldCheck,
+ title: "Share without exposure",
+ body: "End-to-end encrypted sharing lets a caregiver help, without a server ever reading the record.",
+ },
+] as const;
+
+const payoffs = [
+ {
+ patientTitle: "One picture, everywhere they are treated",
+ patient:
+ "Nothing falls through the cracks between a specialist, an urgent care, and the pharmacy.",
+ cvsTitle: "One central pharmacy",
+ cvs: "Refills route back to CVS and scattered scripts consolidate, instead of leaking to Amazon, Cost Plus, or mail order. Share of scripts, won.",
+ },
+ {
+ patientTitle: "Medications that fit their day",
+ patient:
+ "Reminders and refill nudges that actually help, so they stay on their medications.",
+ cvsTitle: "Star Ratings",
+ cvs: "Diabetes, hypertension, and statin adherence are triple-weighted in Part D Star Ratings: Quality Bonus Payments and retention for Aetna and SilverScript.",
+ },
+ {
+ patientTitle: "Fewer dangerous surprises",
+ patient:
+ "Interactions and duplicate prescriptions caught across every prescriber, not one pharmacy's slice.",
+ cvsTitle: "Lower cost of care",
+ cvs: "Fewer adverse events and ER visits: direct medical spend saved for the members shared with Caremark and Aetna.",
+ },
+ {
+ patientTitle: "Ready at the counter",
+ patient:
+ "They arrive with a clean list and their routine questions already answered.",
+ cvsTitle: "Pharmacist leverage",
+ cvs: "Less low-value counter volume, more time for the billable MTM and CMR work pharmacists already do.",
+ },
+ {
+ patientTitle: "A tool that is theirs",
+ patient:
+ "An advocate they control, on their own device. Not a sales pitch, and never on a server.",
+ cvsTitle: "Engagement without the liability",
+ cvs: "A CVS-branded habit patients actually open, with no PHI on a server: no new breach surface and no BAA to negotiate.",
+ },
+] as const;
+
+export function CvsPrintSummary() {
+ return (
+
+ );
+}
diff --git a/src/components/feature-showcase.tsx b/src/components/feature-showcase.tsx
index 7092c9c..8d3cb0a 100644
--- a/src/components/feature-showcase.tsx
+++ b/src/components/feature-showcase.tsx
@@ -1,120 +1,122 @@
"use client";
+import type { KeyboardEvent } from "react";
import { useState } from "react";
import {
CalendarDays,
- Camera,
Check,
ContactRound,
- Home,
MessageCircle,
- Shield,
+ Pill,
} from "lucide-react";
import { PhoneMockup } from "~/components/phone-mockup";
import { cn } from "~/lib/utils";
const features = [
- {
- id: "home",
- label: "Profile",
- icon: Home,
- title: "One profile for the person you care for",
- description:
- "Visits, medications, reminders, and questions live together under the person they belong to.",
- points: [
- "Switch between everyone you care for",
- "One home for the whole picture",
- "Nothing scattered across apps",
- ],
- image: "/screenshots/home.png",
- alt: "Medscribe home dashboard with record visit, search, medications, and ask shortcuts",
- },
- {
- id: "context",
- label: "Context",
- icon: ContactRound,
- title: "The context behind the handoff",
- description:
- "Conditions, medication changes, visit summaries, and caregiver notes stay close enough to become useful when time is short.",
- points: [
- "Baseline, allergies, and conditions up front",
- "Time-critical medications flagged",
- "A source trail behind each fact",
- ],
- image: "/screenshots/emergency-record.png",
- alt: "Medscribe emergency record with critical care context",
- },
{
id: "visits",
label: "Visits",
icon: CalendarDays,
- title: "Visit recordings that refresh the record",
+ title: "Turn a visit into context you can review",
description:
- "A visit can become searchable context, so a medication change or follow-up instruction does not depend on memory alone.",
+ "Type or paste notes, import a portal screenshot or document, or use consent-gated recording. The beta creates a local summary for the person to check.",
points: [
- "Consent-gated, on-device recording",
- "Searchable transcript and summary",
- "Follow-ups captured, not forgotten",
+ "Supported transcription and summarization run on device",
+ "The person reviews generated information",
+ "Structured visit-to-record change review is still roadmap",
],
- image: "/screenshots/visit-timeline.png",
- alt: "Medscribe visit timeline with appointment cards",
+ image: "/screenshots/visit-detail.png",
+ alt: "Synthetic Medscribe beta visit detail showing a visit summary and follow-up information",
},
{
- id: "meds",
- label: "Meds",
- icon: Camera,
- title: "Medication OCR, reminders, and history",
+ id: "medications",
+ label: "Medications",
+ icon: Pill,
+ title: "Keep the daily medication picture close",
description:
- "Prescription labels, reminders, refill alerts, and dose history help the family see what is supposed to happen and what actually happened.",
+ "Scan a label, correct the extracted fields, set reminders, follow refills, and see a local intake history without asking a language model to invent drug facts.",
points: [
- "Scan labels with the camera",
- "Reminders and refill alerts",
- "Dose history at a glance",
+ "Label text remains editable before it becomes the record",
+ "Bundled facts and known pairs use named reference datasets",
+ "Coverage is intentionally bounded, not a complete interaction check",
],
- image: "/screenshots/medications.png",
- alt: "Medscribe medications screen with active medications",
+ image: "/screenshots/medication-detail.png",
+ alt: "Synthetic Medscribe beta medication detail with schedule and medication information",
},
{
- id: "ask",
- label: "Ask",
+ id: "questions",
+ label: "Questions",
icon: MessageCircle,
- title: "Medication questions grounded in the record",
+ title: "Facts first, fluent answers second",
description:
- "Plain-language questions can draw from the person's record and bundled FDA facts, while keeping diagnosis and dosing with clinicians.",
+ "Medication questions can use the person’s local record and bundled fields. Dosing changes, diagnosis, and treatment decisions stay with a clinician or pharmacist.",
points: [
- "Plain-language answers",
- "Grounded in the record and FDA facts",
- "Defers dosing and diagnosis to clinicians",
+ "Known facts render from bundled data",
+ "The local model helps with conversational phrasing",
+ "High-risk or unsupported questions defer to a professional",
],
- image: "/screenshots/chat.png",
- alt: "Medscribe Ask chat answering a question about blood pressure medications",
+ image: "/screenshots/chat-response.png",
+ alt: "Synthetic Medscribe beta answer with medication context and a safety boundary",
},
{
- id: "privacy",
- label: "Privacy",
- icon: Shield,
- title: "Private by architecture, not policy",
+ id: "handoff",
+ label: "Know Me",
+ icon: ContactRound,
+ title: "Prepare one readable handoff",
description:
- "The sensitive work happens on device, so the family record is not another cloud inbox waiting to be mined.",
+ "The Know Me view brings selected medications, allergies, conditions, baseline, and contacts together. Current, unconfirmed, and review-needed states make uncertainty visible.",
points: [
- "On-device AI, no cloud processing",
- "No inbox to breach or mine",
- "You control what is ever shared",
+ "Medication schedules can include source and confirmation",
+ "The person can show or share the snapshot they reviewed",
+ "It complements—not replaces—clinical verification",
],
- image: "/screenshots/settings.png",
- alt: "Medscribe settings showing on-device AI models and privacy notice",
+ image: "/screenshots/emergency-record.png",
+ alt: "Synthetic Medscribe beta Know Me handoff with active medications and review state",
},
] as const;
+type FeatureId = (typeof features)[number]["id"];
+
export function FeatureShowcase() {
- const [activeId, setActiveId] = useState<(typeof features)[number]["id"]>("home");
- const active = features.find((f) => f.id === activeId) ?? features[0];
+ const [activeId, setActiveId] = useState("visits");
+ const active =
+ features.find((feature) => feature.id === activeId) ?? features[0];
+
+ const onTabKeyDown = (event: KeyboardEvent) => {
+ const activeIndex = features.findIndex(
+ (feature) => feature.id === activeId,
+ );
+ let nextIndex: number | undefined;
+
+ if (event.key === "ArrowRight" || event.key === "ArrowDown") {
+ nextIndex = (activeIndex + 1) % features.length;
+ } else if (event.key === "ArrowLeft" || event.key === "ArrowUp") {
+ nextIndex = (activeIndex - 1 + features.length) % features.length;
+ } else if (event.key === "Home") {
+ nextIndex = 0;
+ } else if (event.key === "End") {
+ nextIndex = features.length - 1;
+ }
+
+ if (nextIndex === undefined) return;
+
+ event.preventDefault();
+ const nextFeature = features[nextIndex];
+ if (!nextFeature) return;
+
+ setActiveId(nextFeature.id);
+ document.getElementById(`feature-tab-${nextFeature.id}`)?.focus();
+ };
return (
-
-
-
+
+
+
{features.map((feature) => {
const Icon = feature.icon;
const isActive = feature.id === activeId;
@@ -122,49 +124,67 @@ export function FeatureShowcase() {
return (
);
})}
-
-
+
+
+ Current beta
+
+
{active.title}
-
+
{active.description}
-
-
- {active.points.map((point) => (
- -
-
-
- ))}
-
+
+ {active.points.map((point) => (
+ -
+
+
+
+ {point}
+
+ ))}
+
+
-
-
+ Synthetic demo data · beta interface
+
diff --git a/src/components/northwell-print-summary.tsx b/src/components/northwell-print-summary.tsx
new file mode 100644
index 0000000..f70e431
--- /dev/null
+++ b/src/components/northwell-print-summary.tsx
@@ -0,0 +1,381 @@
+import Image from "next/image";
+
+function PrintPage({
+ page,
+ children,
+}: Readonly<{ page: number; children: React.ReactNode }>) {
+ return (
+
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+
+ {page === 1 ? (
+
+
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+
+
+ Medscribe
+
+
+
+ Executive summary · Northwell Health
+
+
+ ) : null}
+
+ {children}
+
+
+
+ );
+}
+
+const people = [
+ [
+ "The student on their own",
+ "Managing prescriptions and appointments for the first time, away from the parent who used to track it all.",
+ ],
+ [
+ "The newly diagnosed",
+ "A new routine, new instructions, and follow-ups that are a blur by the next visit.",
+ ],
+ [
+ "The long-distance caregiver",
+ "An adult child coordinating a parent's medications with siblings who cover different days.",
+ ],
+ [
+ "The emergency",
+ "An older patient at an out-of-network ER, where no one has met them or knows which medications cannot be delayed.",
+ ],
+] as const;
+
+const productPillars = [
+ [
+ "Capture visits",
+ "Type or paste notes, import a portal screenshot, attach a document, or use consent-gated recording. Summarization stays on device.",
+ ],
+ [
+ "Keep medications current",
+ "Pill-bottle label recognition, reminders, refill tracking, dose history, and questions grounded in bundled FDA facts.",
+ ],
+ [
+ "Be ready to hand off",
+ "A patient-controlled Know Me record and encrypted caregiver sharing keep critical context ready when the chart is incomplete.",
+ ],
+] as const;
+
+const northwellFit = [
+ [
+ "AI patients can trust",
+ "Visit summarization and medication Q&A run on the phone, while medication facts come from bundled reference data rather than model recall. It is a clear AI posture for patients, privacy teams, and clinicians.",
+ ],
+ [
+ "A Northwell story worth telling",
+ "Northwell can lead with a concrete patient benefit: one private, emergency-ready picture that travels across systems. The experience could carry Northwell's brand without pretending to replace MyChart.",
+ ],
+ [
+ "An everyday touchstone",
+ "Reminders, refills, dose tracking, questions, and record updates create useful reasons to return between appointments. Each moment can point the patient back to the Northwell care team.",
+ ],
+] as const;
+
+const recordContents = [
+ "Active medications, doses, schedules, and refill status",
+ "Allergies, conditions, baseline, and the context that changes a handoff",
+ "Visit summaries, follow-up instructions, and questions for the next visit",
+ "Emergency contacts and a concise, patient-controlled Know Me record",
+] as const;
+
+export function NorthwellPrintSummary() {
+ return (
+
+ );
+}
diff --git a/src/components/phone-mockup.tsx b/src/components/phone-mockup.tsx
index 42a6767..c6bdce3 100644
--- a/src/components/phone-mockup.tsx
+++ b/src/components/phone-mockup.tsx
@@ -1,7 +1,4 @@
-"use client";
-
import Image from "next/image";
-import { IPhoneMockup } from "react-device-mockup";
import { cn } from "~/lib/utils";
@@ -27,33 +24,26 @@ export function PhoneMockup({
const isSimulatorCapture = captureMode === "simulator";
return (
-
-
-
-
+
+
+
+
{children}
);
diff --git a/src/components/site-footer.tsx b/src/components/site-footer.tsx
index 4cf9a9f..c948d70 100644
--- a/src/components/site-footer.tsx
+++ b/src/components/site-footer.tsx
@@ -1,24 +1,69 @@
+import Link from "next/link";
+
+import { MedscribeLogo } from "~/components/medscribe-logo";
+
+const footerLinks = [
+ { href: "/how-it-works", label: "How it works" },
+ { href: "/privacy", label: "Privacy & evidence" },
+ { href: "/beta", label: "Beta access" },
+] as const;
+
export function SiteFooter() {
return (
-
+
- What it is
-
- Where the picture breaks
-
- {/* What makes it different */}
-
- What makes it different
-
+
+
+ {productRelease.stage}
+
+
+ {productRelease.platforms}
+
+
+ + Carry the context.
-
-
- - A grandfather with three adult children, each living twenty to - fifty minutes away. None able to be at every appointment. No - shared, current view of his medications, his visits, or what had - changed. -
-- Then came the emergency. A fall. A hospital that did not - understand his condition. Some of his medications were - time-critical. They were administered incorrectly, his decline was - misread, the wrong path was taken, and he passed six weeks later. - The clinicians were not negligent. The system was blind to who he - was, and no trustworthy picture of him existed to hand over. -
-- Medscribe is the private, patient-owned record built for that gap: - the whole picture, held by the patient, ready to hand over the - moment the chart in front of you doesn't have it. -
-
- On-device · no cloud AI
- Emergency-ready
- Complements Epic
- iOS · Android beta
-
-
-
- {/* What it is */}
- - A medical record the patient owns and carries -
-- Current medications, allergies, baseline, visit summaries, and an - emergency “know-me” record, kept current through - everyday use, and ready to hand to a caregiver, a new doctor, or an - ER in seconds. Everything runs on the device. Nothing is uploaded. +
+ Visits, medications, and the critical details between them—kept + together on the device you carry.
-
-
- {/* The gap Epic's own tools can't close */}
- - How the record stays current (live in beta today) -
--
-
- - Visit summaries: type - or paste notes, import MyChart and portal after-visit summaries - from a screenshot, or attach photos and documents; optional - consent-gated audio recording for patients who want it. Any path - feeds the same on-device summary. - -
- - Medication management: - pill-bottle label recognition, reminders, and on-device Q&A - grounded in FDA drug facts - -
- - Emergency handoff: a - know-me card and encrypted caregiver sharing, patient-controlled - -
- Structured MyChart / FHIR export import is on the roadmap: - import-and-own, not write-back. -
+
+
+
-
+ - Epic knows what Epic sees -
-- MyChart is excellent inside the Epic walls. It puts the chart on the - patient's phone, links their Epic portals through MyChart - Central, and lets them share with a caregiver or a provider. What no - institutional record can be is the whole picture: the urgent care, - the community specialist, the facility that isn't on Epic; the - changes between visits; the context a patient keeps themselves. Epic - aggregates Epic. And when it matters most, at an out-of-network ER, - or when the patient can't generate a share code, the record - that's actually there is the one they already carry. +
+
+
+
+
+
+ + Synthetic demo data · beta interface
- +- No one else owns the whole job -
-
- Existing Electronic Health Record (EHR) systems owns the
- institutional view, and every institutional tool stops at its own
- walls. Around them, the market is full of single-purpose apps: visit
- notetakers, medication trackers, record vaults, emergency-ID cards.
- Each owns one slice. None holds a private, patient-owned record that
- spans every system, Epic and non-Epic alike, stays current through
- daily use, and is ready to hand over in a crisis, all on the
- patient's own device. Medscribe is that combination, beside
- Epic, not instead of it.
+
+ The missing picture
+ One instruction lives in a portal. A medication label sits in a
+ cabinet. The latest change lives in someone's memory. Medscribe
+ is the patient-held thread between those moments.
+
+ After the visit
+
+ Bring in typed notes, a portal screenshot, a document, or an
+ optional consent-gated recording. The work happens locally. You
+ decide what is useful.
+
+ The safety loop:{" "}
+ review generated information before acting. Medscribe does not
+ diagnose, prescribe, or replace clinical verification.
+
+ {moment.eyebrow}
+
+ {moment.body}
+
+ Between visits
+
+ The list, the label, the schedule, and the latest confirmation
+ belong in the same view—not scattered across paper and memory.
+
+ {item.body}
+
+ Ask from the record
+
+ 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.
+
+ Informational only. Medication changes still belong with a
+ clinician or pharmacist.
+
+ At the handoff
+
+ Know Me gathers selected medications, allergies, conditions,
+ baseline, and contacts into one readable snapshot. Freshness
+ signals show what may need another look.
+
+ Quick handoff
+
+ Show or share a selected, readable snapshot.
+
+ Caregiver copy
+
+ Manually export an encrypted copy for a paired recipient.
+
+ Pair by QR code, compare a safety number, and choose when to
+ export. The caregiver imports a local copy on their device.
+
+ {title}
+
+ {body}
+
+ 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
+
+ The working record and supported AI tasks stay on the device.
+ Medication facts come from bundled references, not a model trying
+ to remember medicine.
+
+ {principle.body}
+
+ The right beta participant
+
+ This is an internal beta. Expect close feedback, manual review,
+ rough edges, and possible resets—not guaranteed continuity.
+
+ Start with your platform and whether you are testing as a patient,
+ caregiver, or both. Please do not email health details.
+
+
+
+ Care happens in fragments. Your context shouldn't.
+
+
-
+
+
+
+ {item}
+
+ ))}
+
+
- Built to strengthen the Epic investment, not compete with it
+
+
+
+
-
+ Turn what happened into something you can check.
+
+
- {fit.map((item) => {
- const Icon = item.icon;
+
+
+
+
+
+ {visitMoments.map((moment) => (
+
+
+
+
+
+
+ {moment.number}
+
+
+
+ {moment.title}
+
+
+
+
+
+
+
+
+
+ Keep the medication picture from going stale.
+
+
+
+
+
+
+
+
+
+
+
+ {[
+ {
+ title: "Show where a schedule came from",
+ body: "Schedules can carry their source, confirmation, timezone, and freshness state.",
+ },
+ {
+ title: "Keep facts deterministic",
+ body: productClaims.medicationFacts.publicCopy,
+ },
+ {
+ title: "Make uncertainty visible",
+ body: "Missing or stale details stay visible so the person or clinician can verify them.",
+ },
+ ].map((item) => (
+
+
+ {item.title}
+
+
+
+
+
+
+ Better questions begin with your context.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Bring the picture when the chart is incomplete.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Share a snapshot. Not an invisible feed.
+
+
+ {[
+ ["1", "You review", "Choose the record to send"],
+ ["2", "Encrypted copy", "Protected for the recipient key"],
+ ["3", "They import", "A local, readable snapshot"],
+ ].map(([number, title, body]) => (
+
+
+
+
+
+
+
+ Local changes what you have to trust.
+
+
+ {proofStats.map((stat) => (
+
+
+
+
+ ))}
+
+ {privacyPrinciples.map((principle) => {
+ const Icon = principle.icon;
return (
-
-
- {/* Who's behind it + the ask */}
-
-
-
+ {principle.title}
+
+
-
-
+
-
+ Help build the record people can actually carry.
+
+
+ {betaFit.map((item) => (
+
+
+
+
+
+
+
+
+ Last verified {productRelease.verifiedOn}
+
+ Internal beta
+
+ + Privacy should be specific enough to challenge. +
++ “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. +
+
+ Data map
+
+ + Task by task, not “everything” absolutes. +
+ +
+
+
+
+ | + {heading} + | + ))} +|||
|---|---|---|---|
| + {row.task} + | ++ {row.location} + | ++ {row.network} + | ++ {row.control} + | +
+
+
+ {[
+ {
+ icon: LockKeyhole,
+ title: "Supported AI work stays local",
+ body: productClaims.localAi.publicCopy,
+ },
+ {
+ icon: Database,
+ title: "The primary record stays local",
+ body: `${productClaims.localRecord.publicCopy} The beta relies on the device and operating system's protections; it does not claim a separately encrypted app database.`,
+ },
+ {
+ icon: Wifi,
+ title: "Downloads are the network exception",
+ body: "Installing or updating a model can require a network. Approved model files are checked against an expected SHA-256 digest before use.",
+ },
+ ].map((item) => {
+ const Icon = item.icon;
+
+ return (
+
+
+
+
+
+ );
+ })}
+
+ + {item.title} +
++ {item.body} +
+
+
+
+
+
+ Caregiver sharing
+
+
+
+
+ + Verify a person, then export deliberately. +
++ 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 +
+-
+ {[
+ "Compare the safety number with the intended caregiver.",
+ "Review the snapshot before every material export.",
+ "Re-export after important changes; it is not automatic.",
+ "Treat revocation as a block on future local exports; it cannot invalidate already-exported ciphertext.",
+ ].map((item, index) => (
+
- + + {index + 1} + + {item} + + ))} +
+ Evidence, not superlatives
+
+
+
+
+
+
+ + What the current release can actually point to. +
++ 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. +
+-
+ {[
+ [
+ productRelease.drugFacts.toLocaleString(),
+ "Condensed drug records",
+ ],
+ [
+ productRelease.rxNormTerms.toLocaleString(),
+ "RxNorm search terms",
+ ],
+ [
+ productRelease.interactionPairs.toLocaleString(),
+ "Known high-priority pairs",
+ ],
+ [
+ productRelease.flaggedForReview.toLocaleString(),
+ "Records flagged for review",
+ ],
+ ].map(([value, label]) => (
+
- + {label} + +
- + {value} + +
+
+ ))}
+
+
+
+ + 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. +
+
+
+
+
+
+
+
+
+ + Designed to protect against +
+-
+ {protects.map((item) => (
+
- + {item} + + ))} +
+
+
+
+
+ + It does not eliminate +
+-
+ {doesNotProtect.map((item) => (
+
- + {item} + + ))} +
+
+
+
+
+ + Help test the boundary. +
++ The internal beta is focused on correctness, comprehension, and + caregiver handoffs. +
++ The pharmacy executive summary +
++ This page is formatted as a two-page print document: what Medscribe + can do, and how every capability pays off twice, for the patient and + for Walgreens. Use Print PDF (or Cmd+P, then Save as PDF) to export + it. +
+
+
+
+ {page === 1 ? (
+
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+
+
+ Medscribe
+
+
+
+ Executive summary · CVS Health
+
+
+
+ Medscribe
+
+ {children}
+
+
+
-
-
+
+
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+
+ {page === 1 ? (
+
+
+ ) : null}
+
+
+ );
+}
+
+const people = [
+ [
+ "The student on their own",
+ "Managing prescriptions and appointments for the first time, away from the parent who used to track it all.",
+ ],
+ [
+ "The newly diagnosed",
+ "A new routine, new instructions, and follow-ups that are a blur by the next visit.",
+ ],
+ [
+ "The long-distance caregiver",
+ "An adult child coordinating a parent's medications with siblings who cover different days.",
+ ],
+ [
+ "The emergency",
+ "An older patient at an out-of-network ER, where no one has met them or knows which medications cannot be delayed.",
+ ],
+] as const;
+
+const productPillars = [
+ [
+ "Capture visits",
+ "Type or paste notes, import a portal screenshot, attach a document, or use consent-gated recording. Summarization stays on device.",
+ ],
+ [
+ "Keep medications current",
+ "Pill-bottle label recognition, reminders, refill tracking, dose history, and questions grounded in bundled FDA facts.",
+ ],
+ [
+ "Be ready to hand off",
+ "A patient-controlled Know Me record and encrypted caregiver sharing keep critical context ready when the chart is incomplete.",
+ ],
+] as const;
+
+const northwellFit = [
+ [
+ "AI patients can trust",
+ "Visit summarization and medication Q&A run on the phone, while medication facts come from bundled reference data rather than model recall. It is a clear AI posture for patients, privacy teams, and clinicians.",
+ ],
+ [
+ "A Northwell story worth telling",
+ "Northwell can lead with a concrete patient benefit: one private, emergency-ready picture that travels across systems. The experience could carry Northwell's brand without pretending to replace MyChart.",
+ ],
+ [
+ "An everyday touchstone",
+ "Reminders, refills, dose tracking, questions, and record updates create useful reasons to return between appointments. Each moment can point the patient back to the Northwell care team.",
+ ],
+] as const;
+
+const recordContents = [
+ "Active medications, doses, schedules, and refill status",
+ "Allergies, conditions, baseline, and the context that changes a handoff",
+ "Visit summaries, follow-up instructions, and questions for the next visit",
+ "Emergency contacts and a concise, patient-controlled Know Me record",
+] as const;
+
+export function NorthwellPrintSummary() {
+ return (
+
+ );
+}
diff --git a/src/components/phone-mockup.tsx b/src/components/phone-mockup.tsx
index 42a6767..c6bdce3 100644
--- a/src/components/phone-mockup.tsx
+++ b/src/components/phone-mockup.tsx
@@ -1,7 +1,4 @@
-"use client";
-
import Image from "next/image";
-import { IPhoneMockup } from "react-device-mockup";
import { cn } from "~/lib/utils";
@@ -27,33 +24,26 @@ export function PhoneMockup({
const isSimulatorCapture = captureMode === "simulator";
return (
-
+
{features.map((feature) => {
const Icon = feature.icon;
const isActive = feature.id === activeId;
@@ -122,49 +124,67 @@ export function FeatureShowcase() {
return (
);
})}
-
-
+
+
+
+ Current beta
+
+
{active.title}
-
+
{active.description}
-
-
- {active.points.map((point) => (
- -
-
-
- ))}
-
+
+ {active.points.map((point) => (
+ -
+
+
+
+ {point}
+
+ ))}
+
+
+ Current beta +
+{active.title}
-+
{active.description}
-
-
diff --git a/src/components/northwell-print-summary.tsx b/src/components/northwell-print-summary.tsx
new file mode 100644
index 0000000..f70e431
--- /dev/null
+++ b/src/components/northwell-print-summary.tsx
@@ -0,0 +1,381 @@
+import Image from "next/image";
+
+function PrintPage({
+ page,
+ children,
+}: Readonly<{ page: number; children: React.ReactNode }>) {
+ return (
+
-
+
+ Synthetic demo data · beta interface +
+ {page === 1 ? (
+
+ {/* eslint-disable-next-line @next/next/no-img-element */}
+
+
+ Medscribe
+
+
+
+ Executive summary · Northwell Health
+
+
+
+ Medscribe
+
+ {children}
+
+
+
-
-
+
-
-
+
);
}
diff --git a/src/components/product-device.tsx b/src/components/product-device.tsx
new file mode 100644
index 0000000..1709bbe
--- /dev/null
+++ b/src/components/product-device.tsx
@@ -0,0 +1,39 @@
+import Image from "next/image";
+
+import { cn } from "~/lib/utils";
+
+type ProductDeviceProps = {
+ src: string;
+ alt: string;
+ className?: string;
+ sizes?: string;
+ priority?: boolean;
+};
+
+/**
+ * A precomposited product capture using the licensed device bezels in
+ * `public/screenshots/pitch`. Keeping the frame in the source image preserves
+ * the bezel details without adding layout or client-side work.
+ */
+export function ProductDevice({
+ src,
+ alt,
+ className,
+ sizes = "(min-width: 1024px) 360px, (min-width: 640px) 320px, 72vw",
+ priority = false,
+}: ProductDeviceProps) {
+ return (
+
+
+
{children}
); diff --git a/src/components/site-footer.tsx b/src/components/site-footer.tsx index 4cf9a9f..c948d70 100644 --- a/src/components/site-footer.tsx +++ b/src/components/site-footer.tsx @@ -1,24 +1,69 @@ +import Link from "next/link"; + +import { MedscribeLogo } from "~/components/medscribe-logo"; + +const footerLinks = [ + { href: "/how-it-works", label: "How it works" }, + { href: "/privacy", label: "Privacy & evidence" }, + { href: "/beta", label: "Beta access" }, +] as const; + export function SiteFooter() { return ( -