A practice takes on a new nurse on a Monday. She needs to see results. The person who set up the account left in March, nobody knows who the administrator is, and the reset email goes to a mailbox that no longer exists.
Three clinical days are now spent telephoning for results that have been sitting in a portal since Friday.
Why this generates so much contact
Because access is set up once, by one person, and everything afterwards is somebody else's problem. Staff turnover, lost passwords and permission changes all land on the laboratory's support line.
Step 1: publish a setup guide
How a practice gets access, who can request it, what is needed and how long it takes. One page, findable, with the steps in order.
Step 2: name the administrator role
Who at the practice controls access, what they can do and how to transfer the role when somebody leaves. Most access problems are really administrator problems.
Step 3: publish how to add a user
The route, who can request it, what identification is needed and how quickly it happens. Practices add staff constantly and should not need to ask each time.
Step 4: publish how to remove a user
Just as important, and almost never documented. Practices need to remove access when somebody leaves and frequently do not know how.
Step 5: publish the password reset route
Self service where possible, with the fallback and who to contact. It is the single highest volume support request in any portal.
Step 6: explain the permission levels
Who can see what, whether clinicians and administrative staff differ and how to change a permission. Practices assume it is all or nothing.
Step 7: explain what happens to the account if nobody logs in
Dormancy, expiry and reactivation. Practices that refer occasionally find themselves locked out at the moment they need it.
Step 8: publish the browser and device requirements
What works, what does not and whether mobile access is supported. Clinicians increasingly work from a tablet between rooms.
Step 9: publish the integration option
Where results can flow into the practice's own system, what is required and who to talk to. It removes the portal problem entirely for practices able to use it.
Step 10: explain how results are notified
Whether an alert is sent, to whom, and how a practice makes sure the right person sees an abnormal result. This is the part that matters clinically.
Step 11: explain what to do when a result is missing
Where to look first, how long to wait and who to contact, which prevents the premature chasing described in results timing questions labs should answer up front.
Step 12: give access problems a fast route
A named contact and a stated response time. Access failures block patient care and should not sit in a general queue.
Step 13: never handle patient results automatically
Anything about a specific patient or a specific result goes to a person. Published information covers access and process only, which is the discipline in how to handle sensitive questions in your chatbot.
Step 14: answer setup questions outside clinic hours
Practices sort administration in the evening, the same friction as procurement portal questions that stall B2B suppliers, and it belongs alongside test ordering questions from new referring practices.
Getting started
Publish a portal setup guide covering users, permissions, resets and integration, then answer access questions at any hour while patient matters reach a person. SpideyChat for healthcare organisations answers from your published pages. Try SpideyChat on your own site, or read about routing on the features page.