A patient portal rollout succeeds when the right person can open the right record and understands what is shared. Sending an invitation is only one step: reception also needs a way to check the address, explain sign-in and handle access problems.
This checklist describes Talven's current email invitation and Google sign-in flow. It does not assume that every patient has a suitable account or wants portal access. Registration and care coordination should still have a practical clinic-assisted route when the portal is unsuitable.
Check the patient and address together
Open the intended chart and confirm the patient's identity before adding an email address. A family mobile number, a similar name or a caregiver relationship is not enough to establish which person should receive access. Read the address back with the patient and check that it is the Google account they intend to use.
In Talven, an invitation is bound to both the patient record and the invited email. The recipient must sign in with that exact address. Do not use a convenient staff email as a substitute, and do not ask patients to share their Google password with reception.
An existing staff membership cannot silently become a patient membership. If an account is already linked in a way that does not match the intended access, resolve that explicitly with the clinic instead of repeatedly sending new links.
Explain what the portal will contain
Give a short explanation before sending: the patient can see their own appointments, released documents, intake forms and invoices. Internal working notes and unreleased reports do not appear. A report being uploaded is different from it being reviewed or released.
A useful demonstration uses fictional records and shows both the staff view and the patient-visible result. In the real chart, check which documents are ready to share through the clinic's established review process. Do not release an unreviewed file merely to populate a new portal account.
The reports guide explains review and sharing, while the patient portal instructions provide the exact invitation steps.
Send once, then check the state
Add the patient's email to their record, open Portal access and choose Send patient invitation. Reception can also choose to send an invitation during registration when the optional details are entered. Confirm the visible invitation and email status after submission.
Do not describe an invitation as accepted just because an email was sent. The patient must open the link, sign in and accept it. Talven then shows Portal connected. An email delivery status also does not prove that the recipient has read the message.
Invitations expire after 14 days and can be accepted once. The panel provides Revoke invitation for an unused link and Send replacement invitation after a one-minute wait. A replacement invalidates the previous invitation; explain which message the patient should use.
Rehearse the common support cases
| What the patient sees | What the clinic should check |
|---|---|
| The email is missing | Confirm the recorded address and visible email status; ask the patient to check their inbox and spam folder |
| Sign-in uses the wrong account | Compare the signed-in Google address with the invitation address and switch accounts |
| The invitation has expired | Verify the intended patient and address, then send a replacement |
| The wrong person was invited | Revoke the unused invitation; if access was accepted, revoke portal access and follow the clinic's incident process |
| A report is not visible | Check whether that document has been released to the intended patient's portal |
When an address is wrong, resolve the old invitation before sending another one. Pending invitation revocation and revoking already-connected access are separate actions. Avoid asking the patient to forward an invitation to a relative: forwarding does not change the account or record it authorizes.
Keep caregiver contact and access separate
Talven can store a caregiver's contact details, but that does not create a caregiver portal account or permission to open the patient's chart. Do not promise household account switching or proxy access as part of the current portal flow.
If a child, dependent adult or someone sharing an email needs assistance, confirm the clinic's appropriate access process before issuing an invitation. Where the current account model does not fit, use the clinic's established assisted process and discuss the requirement with the product team. Do not create an account arrangement that misidentifies the person accessing the record.
Separate invitations from reminder choices
Portal invitations are transactional access messages. Email appointment reminders are a separate choice recorded in the patient record; invitation acceptance is not a substitute for reminder agreement. Talven skips reminder jobs without recorded agreement, and WhatsApp messaging is not currently connected.
Start a rollout with a small, supported group of willing patients, then review where help was needed: missing emails, wrong accounts, unclear document availability or unsuitable access needs. Track these operational issues without copying private patient information into a public feedback document.
Use reminders and caregiver contacts help and access controls when training the team. A portal should reduce confusion about the next step, not make access to the clinic depend on a patient solving a sign-in problem alone.