Patient Portal & Care Coordination
A hospital or clinic with clinical records already in place but no way for a patient to see anything about their own care without calling or visiting. Appointment reminders happen by chance. Documents are collected in person. A returning patient re-explains their history at every visit because nothing carries forward for them to see.
The reality
A hospital or clinic already has clinical records and billing in place, but a patient has no way to see any of it without calling or visiting. Appointment reminders happen by chance. Documents are collected in person, one trip at a time. A returning patient re-explains their history because nothing carries forward for them to see.
Where it breaks
- A patient confirming an appointment, checking a bill, or asking whether a result is back has no option but to call.
- A discharge summary or referral letter means a return trip to collect a printout.
- A returning patient's consent and communication preferences get re-asked at every visit because nothing was recorded to carry forward.
- Reminders happen by chance, not by design, so no-shows are discovered as an empty slot rather than prevented.
The Afivox approach
Afivox doesn't build a second patient record. It builds a window onto the one that already exists, linked to the same patient, reading the same documents and the same balance the front desk sees, so nothing the patient sees can ever drift from what the hospital actually has on file.
The system
Users
Patients, care team (document release, messaging)
Application
Patient login, appointments, documents, tasks
Services
Billing visibility, secure messaging, consent and preferences
Data
Patient → PortalAccount, DocumentRelease, ConsentRecord, Message → Thread
Integrations
Reads the same Patient/Account records as the hospital's own platform
Security
Verified identity linking, explicit document release, read-only billing
How it flows
- Patient logs in
- Views appointment or document
- Completes a task
- Sends a message, if needed
- Care team responds
Secure by design
- A portal account is linked to exactly one patient record. Never a shortcut for creating a new one.
- A document is only visible once explicitly released by the clinician who authored it.
- Billing visibility is read-only: a balance shown in the portal can never be adjusted from it.
- Messaging is asynchronous and monitored during stated hours, and every screen states plainly that it is not an emergency channel.
Designed to improve
- Reduced call volume: a patient can check an appointment, a result, or a balance without picking up the phone.
- Faster document access: a discharge summary or referral letter is a download, not a return trip.
- Continuity: a returning patient's consent and preferences are already on file, not re-asked.
Before
- A patient calls to confirm an appointment that's already in the system.
- Collecting a discharge summary means a trip back to the hospital.
- A returning patient answers the same consent and preference questions again.
After
- A patient checks their appointment, result or balance without a phone call.
- A discharge summary is a download the moment it's released.
- A returning patient's preferences are already on file.
This is what we'd build. Yours will look a little different.
Every concept on this page changes once we sit with how your operation actually runs. Tell us what's different about yours.
Start the operations review