What it is
The portal is not a separate product with a nightly CSV. It is the patient-facing side of the same tenant-scoped chart. Invite tokens, self-registration, and magic-link sign-in are how a Cleveland, Tennessee pain clinic’s patients get in without a staff-reset password ritual. An old /patientportal address on chartvoyant.com, app, or login serves a short page. A normal browser is sent to portal.chartvoyant.com with the query string kept. An old Home Screen icon stays on that page and explains the move.
On the clinic floor
On a phone, the portal is a navy header and a glass dock: Visits, Messages, Records, Billing, Account. Patients can join a waitlist; Join persists across navigation and shows Leave; repeating join/leave does not stack Open requests. Connected apps (SMART) can be authorized from the portal. Results publish or hold based on a clinician decision and a practice default. SMS reminder consent is an explicit record (portal checkbox default on, plus the desk and Admin defaults) — not an implication from a mobile number sitting on the chart.
What AI does, and what a clinician confirms
The portal does not diagnose. An after-visit summary can be drafted in the patient’s language from the signed note; a person edits and releases it. Inbox AI may message a patient about operational work (a slot, a form). It does not disclose an unpublished result. That split is load-bearing.
Non-Device CDS
Nothing on the portal is a clinical recommendation from a model. Released records are records a clinician already attested. Draft summaries wait on the same confirm step as the note they came from.
Where this sits vs bolted-on tools
A patient-engagement vendor that does not read the chart will show yesterday’s med list. ChartVoyant’s portal is the chart, with a smaller window. Training and demo stacks still serve /patientportal on their own hosts; production patients get the dedicated host so the EMR and the marketing site are not the same door.