Patient experience

Your patients never see our name.

From the first intake question to the refill confirmation, the entire patient experience carries your brand, your domain and your voice. Corevia runs underneath and stays invisible.

The journey

One account, the whole course of care.

Patients don't want a portal. They want to start a program, be seen, get their medication and ask a question when something changes. The portal is organized around those four things.

Conversational intakeProgram-specific questionnaires that branch on answers, save as the patient goes, and resume on another device. Clinical eligibility is screened as they complete it — not after they've paid.

Booking and video visitsSelf-scheduled appointments with a branded waiting room, joined from the browser with nothing to install.

Encrypted messaging with the care teamThreaded, in-portal, and never email — with routing to whoever is responsible for that patient today.

Treatment, refills and shipment trackingCurrent medication, dose schedule, titration guidance, refill requests and where the package is — in one place instead of three emails.

Labs and results the patient can readRequisitions, draw locations and results returned with trends and plain-language context — abnormal values flagged to the clinician, not left for the patient to interpret alone.

Checkout and subscription managementPayment, plan changes, pauses and cancellations — processed on your merchant account, under your descriptor.

Patient portal dashboard showing an active prescription, weight change and the next scheduled check-in — The patient's home: active program, next dose, open messages and refill status. Demo environment; synthetic data.

Secure messaging

Clinical conversation that stays inside the record.

Patient questions are clinical events. Ours are threaded to the patient's chart, attributed to a named clinician, routed to whoever is responsible today, and auditable forever — never sitting in an inbox on someone's phone.

Encrypted in transit and at restMessages never travel by email or SMS. Patients are notified that something is waiting; the content stays in the portal behind authentication.

Part of the medical recordEvery thread is a clinical communication on the chart — visible in context during a review, and included in the audit trail like any other PHI access.

Routed to the responsible clinicianNot broadcast to a shared inbox. The message reaches whoever holds the care relationship for that patient, with coverage rules for absence.

Nothing falls throughUnanswered threads escalate on a timer. A clinical question that goes unread is a safety event, so the platform treats it as one.

AI-drafted replies the clinician ownsThe assistant can draft a response grounded in that patient's chart. A human reads, edits and sends it — the draft is never delivered on its own.

Ongoing care

Check-ins turn a prescription into a program.

The revenue is in month four, not month one. Scheduled check-ins capture progress, side effects and adherence — and route to a clinician automatically when an answer warrants it.

Scheduled to the program, not the calendarCheck-in cadence is part of the program definition — weekly for titration, monthly for maintenance, whatever the protocol says.

Structured, so it trendsWeight, dose, side effects and adherence are recorded as data on the chart, not free text — which means graphs, thresholds and automatic flags.

Escalates on the answers that matterA concerning response opens a consult in the clinician's queue immediately rather than waiting for the next scheduled visit.

Refills that require a real reviewA refill request is a clinical decision with the check-in data attached — not a button that reorders.

A conversational titration check-in asking how treatment is going — A scheduled check-in: dose confirmation, weight, side effects and adherence. Demo environment; synthetic data.

Live visits

A waiting room with your name on it.

When a program or a state requires a live encounter, the patient joins from the same account they already use — not a generic meeting link from a video vendor.

Patient video visit screen, branded to the practice, with mute, camera and end-visit controls — Same login, same brand, same record — no separate download and no meeting ID to find in an email. Demo environment; synthetic data, and the participants are composited stand-ins.

The rest of the surface

Labs, messages and the record, in the same place.

A patient should not need three logins and an email thread to understand their own care.

Patient lab dashboard showing which markers are in reference range — Results in plain language, with the markers that moved. Demo environment; synthetic data.

Encrypted messaging with a separate thread per care program — One thread per program, encrypted, inside the record. Demo environment; synthetic data.

Patient health record with lab orders and a full record export — The whole record, exportable as a standard FHIR bundle. Demo environment; synthetic data.

White-label

Branded to the last transactional email.

Most "white-label" stops at the logo in the header. Ours goes to the places patients actually notice something is off.

Your domain

Patients live on your hostname throughout — no redirect to a platform URL at checkout or sign-in.

Your sender identity

Password resets, appointment reminders and shipping notices come from your domain, authenticated, with your template.

Your card descriptor

The line on the patient's bank statement is yours, because the merchant account is yours.

Your consent documents

Terms, privacy notice and telehealth consent name your practice entity, not ours.

Your colors and type

Palette, typography and imagery are per-brand configuration — several brands can run side by side and look nothing alike.

Your clinicians, named

Patients see the clinician who is caring for them — with the practice's name attached, as the corporate-practice structure requires.