Article guide
Portal support is easiest when staff separate access help from patient care. The caller should leave knowing the next support step without having exposed a password or sensitive detail.
Identify the support issue
Ask whether the problem is invitation, sign-in, password reset, message navigation, or document access. Do not ask for credentials. If the caller describes a clinical concern, move it to the approved clinical message route.
Use the standard reset path
Give the current practice-approved instructions or transfer to the portal owner. If identity verification is required, follow the office process. Do not create an account or change contact details outside the role’s permission.
Protect the conversation
Keep voicemail language general. Avoid reading portal content to an unverified person. If the caller is using a shared device or email, explain that the practice can only follow its approved privacy process.
Document the outcome
Record the issue category, support action, and whether a clinical or technical owner remains responsible. Close the item only when the next step is clear.
Maintain the script
Test the instructions periodically and remove obsolete screenshots or menu names. A short, current script is safer than a detailed guide that no longer matches the portal.
Sources and verification notes
- U.S. Department of Health and Human Services: HIPAA Security Guidance: Provides security context for handling electronic protected health information.
Sources support the specific guidance identified above. Policies, prices, and service scope can change; verify current details before relying on them.
Common questions
Should staff ask for a portal password?
No. Use the practice's approved support process and never ask a caller to disclose credentials.
What if the portal message is clinical?
Route it through the practice's clinical message workflow rather than answering from the front desk.