Try it · Self-scheduling
Patients book themselves — in four taps, at 9pm.
This is the live wizard, end to end. Notice what happens on the last step: rev.health verifies coverage and shows a real cost estimate before the appointment is booked — not as a surprise bill weeks later. Only resource-feasible slots ever appear, because the scheduler solves against rooms, staff, and equipment in real time.
The signature mechanic
One identity, every practice — and a who-viewed-my-chart trail.
Because the Patient and User entities share a primary key, the patient carries one portable record across every rev.health practice they visit. And because there's no separate “patient view” that quietly skips access controls, the same audit that protects the chart is the one the patient can read.
A new patient arriving from another rev.health practice shows up with live structured history — not a faxed PDF dump — and every read of their chart, by anyone, writes an entry the patient can see. Full View-Download-Transmit rights ship as C-CDA, FHIR Bundle, and SMART on FHIR app launch.
The problem
Today's portals are bolted-on afterthoughts.
Stale subsets of the chart. Phone-tag messaging. A separate login from scheduling and billing. Sensitive categories either overexposed or hidden entirely — never consent-gated. And the legally required view-download-transmit rights reduced to a manual export button.
Whitelabeled for your practice
The patient's trust relationship is with their care team, not a technology company — so every surface the patient sees is branded for the practice. Your domain, your logo, your colors. Notifications come from your practice name. Bill-pay receipts come from your merchant account. rev.health appears once: “Powered by rev.health” in the footer.
A record that follows the patient
Because rev.health spans every practice the patient visits, the portal presents one unified longitudinal view — contributions from every consented practice converge into a single record, with each fact's source preserved in the audit trail. Switching practices doesn't reset a patient's history; it travels with them.
Key capabilities
Everything a patient needs, nothing they have to call for.
Secure messaging
Threaded patient-practice messaging with attachments (the rash photo, the wound-healing progress), routed into staff queues with SLA tracking. Median response target: one business day.
Self-scheduling
Slot picker filtered by provider, visit type, and insurance status. Booking creates the appointment and fires the eligibility check automatically.
Plain-language AVS
The after-visit summary arrives with an AI-generated plain-language version at a 6th-grade default reading level and multi-language translation — diagnoses, meds, follow-ups, and care-plan tasks a person can actually act on.
View, Download, Transmit
The longitudinal record viewable in full, downloadable as C-CDA or FHIR Bundle, and transmittable to third-party apps via SMART on FHIR. Every VDT action logged with its authorization chain.
Bill pay & payment plans
Outstanding statements, online payment, and self-service payment-plan enrollment — under the practice's brand, settled to the practice's account.
Sensitive-class consent gating
Mental health, substance use (42 CFR Part 2), HIV, genetic, and reproductive health categories each require explicit patient consent before display — enforced at the API layer, not the UI.
Family & proxy access
Parents, guardians, and authorized caregivers get consent-chain proxy access with state-by-state minor-consent rules enforced — and every proxy read writes an audit entry.
Pre-visit digital intake
Patients complete intake, verify imported data, and update medications before the visit — feeding the clinical intake flow instead of a clipboard.
Document upload
Insurance cards, advance directives, outside records, consent forms — uploaded to the patient-owned document store and routed to the practice's intake queue.
Workflow
A Tuesday evening, from the patient's couch.
Message the practice
“The new med is making me dizzy.” It lands in the clinical queue with an SLA — not in a voicemail box.
Book the follow-up
Three feasible openings for Dr. Lee this week, cost estimate included. Booked in four taps at 9:04 pm.
Re-read the AVS
The plain-language version explains the dose change the way the doctor said it — because it was generated from what the doctor said.
Pay the balance
$30 copay from the last visit, paid in the same session. The practice's statement cycle never has to print an envelope.
Check who's seen the chart
The access log shows every read, by whom, under what authorization. Trust, verifiable.
Who benefits
Messages, results, scheduling, bills, and their full record — one login, their doctor's brand, their phone.
A parent sees their 14-year-old's immunizations and visits through a real consent chain — not a shared password.
Self-scheduled appointments arrive in the queue; document uploads route themselves; call volume drops.
Clinical messages triaged in the inbasket, AVS delivery confirmed, patient-uploaded documents in the reconciliation queue.
Performance targets
The numbers this module is built to hit.
| Metric | Target |
|---|---|
| Portal adoption (login ≥ 1×/quarter) | ≥ 60% within 12 months — vs. ~30% industry baseline |
| Patients completing a VDT action within 6 months | ≥ 80% of registered users |
| Practice-to-patient message response (non-urgent) | ≤ 1 business day median |
| New appointments booked via portal within 12 months | ≥ 40% |
| Patient responsibility collected via portal within 12 months | ≥ 25% |
| WCAG 2.2 AA conformance | 100% of pages, automated + manual audit |
| Sensitive-category consent gating | 100% coverage, API-enforced |
Standards & patient-rights plumbing
The access rights, as product surfaces.
View-Download-Transmit is a first-class product surface, not a compliance checkbox — every VDT action is logged with its authorization chain, and proxy access runs on a real consent chain rather than a shared password.
Connected modules
The patient's window into everything.
Scheduling
Self-scheduling creates real appointments in the resource graph — not requests for a callback.
Module 02 →Revenue Cycle
Statements, online payment, and payment plans flow through the portal's billing surface.
Module 07 →Referrals
Referral status, the specialist, the appointment, and the consult report — patient-visible.
Module 06 →Give your patients their record — under your brand.
A portal patients actually use: 60% quarterly adoption is the design target, not the dream.
Join the waitlist