These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Patient Portal
- Implementation
How a Patient Portal rollout works
Start with one care cycle and expand after the handoffs are tested.
Define the pilot
Choose one clinical team, its visit types and the person who owns intake, note signing, review and follow-up.
Prepare identities
Load staff and patient records, check patient numbers and connect clinicians to their user accounts.
Set governance
Review consent purposes, privilege evidence and care-team assignment dates before scheduling care.
Rehearse the visit
Schedule an encounter, record arrival, add observations and a signed note, then complete reviewer handoff.
Add exceptions
Practice an escalated task, rejected specimen, amended note, voided charge and refunded payment.
Review the operating cycle
Compare visit status, due tasks, charges and receipts with the source records before broadening use.
What the customer provides
Bring the clinic’s patient numbering rule, visit types, consent documents, staff roster, privilege evidence and a sample set of visits. Name the people who review clinical evidence and check charges against encounters. If lab processing, invoicing or payment collection happens elsewhere, provide its reference format and a person who can resolve failed handoffs.
Changing it afterwards
Add new visit types and consent purposes through a controlled review with the team that uses them. Rehearse a representative patient visit after changing roles or the care handoff. Keep prior signed notes, charges and receipt references traceable when correcting a record. Review the data model and roles before changing import or access rules.
Set up Patient Portal your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.