In short
- Proxy access lets a caregiver sign in with their own account and act for a patient within limits the patient or the law sets.
- HIPAA treats a personal representative, such as a guardian or a health care agent, as the patient, while family and friends who help with care get only information directly relevant to their role.
- Design separate proxy types with granular permissions, verify each proxy's authority, handle minors under state law, and make it easy to revoke access and to record a patient's request not to share.
Proxy access lets a caregiver use a patient portal on someone else's behalf, with their own login and only the permissions they have been given. A parent manages a young child's appointments, an adult daughter reads her father's results, a guardian handles everything for a person who cannot. The design rests on two parts of the HIPAA Privacy Rule. A personal representative, someone with legal authority to make health care decisions for the patient, is treated as the patient. Family members and friends involved in care may receive only the information directly relevant to their involvement. A good proxy feature turns those two rules into clear account types, permissions and controls.
How many people use a portal for someone else?
ASTP/ONC Data Brief No. 77 reports that the share of individuals who accessed someone else's medical record or portal, while providing care or making decisions for them, rose from 24% in 2020 to 46% in 2022 and 51% in 2024. The brief describes this as more than doubling over four years. Caregivers are now a core user group. Without a proxy feature, the only way in for them is the patient's own password.
When a daughter signs in with her father's password, the system cannot tell who did what, the father cannot limit what she sees, and the practice has no record that she was ever authorized. A proxy account fixes all three.
What does HIPAA say about who can act for a patient?
Under 45 CFR 164.502(g), a covered entity must generally treat a personal representative as the individual. The rule describes several situations:
- Adults and emancipated minors: a person with authority under applicable law to make health care decisions for the patient, such as a court-appointed guardian or a health care agent, is the personal representative for the related information.
- Unemancipated minors: a parent, guardian or person acting in loco parentis is generally the personal representative, with exceptions described below.
- Deceased individuals: an executor, administrator or other person with authority to act for the deceased or the estate is the personal representative.
A separate rule, 45 CFR 164.510(b), covers family members, relatives, close personal friends and anyone else the patient identifies. A covered entity may share information directly relevant to that person's involvement in the patient's care or payment. If the patient is present and able to decide, the entity needs the patient's agreement, gives them a chance to object, or reasonably infers from the circumstances that they do not object. If the patient is absent or incapacitated, staff may use professional judgment about what is in the patient's best interests.
For a portal, this means two different kinds of proxy. A personal representative can be given what the patient would see. A helper who is not a legal representative should get a defined, narrower set of permissions that the patient chose.
Which proxy types should a portal support?
- Full proxy for a legal representative: a parent of a young child, a guardian, or a health care agent acting under a power of attorney. Access mirrors the patient's own, within the scope of the legal authority.
- Limited proxy chosen by the patient: a spouse, adult child or friend who helps with appointments, billing or reminders, with the patient deciding which sections they see.
- Shared access for adolescents: a parent account with a narrower view once the patient reaches the age where some care can be confidential under state law.
- Temporary proxy: access with an end date, for a recovery period or a hospital stay.
- Estate access: for an executor after a patient's death, usually set up by staff from documents rather than by invitation.
How should proxy permissions work?
Treat permissions as a list of separate capabilities that can each be granted or withheld. Typical capabilities are viewing results, viewing notes, viewing medications, sending messages, booking and changing appointments, requesting refills, viewing and paying bills, and completing forms. Then apply these rules:
- Each proxy has their own login. One person can be a proxy for several patients and switch between them.
- The screen always shows whose record is open, so a caregiver for two parents never sends a message from the wrong chart.
- Every action records who did it and on whose behalf, so staff can tell a patient's own message from a proxy's.
- The patient, when able, can see every proxy on their account, change their permissions and remove them.
- Permissions can have an end date and are reviewed when circumstances change, such as a minor turning 18.
- Messages from a proxy are labeled as such in the care team's inbox.
How should a portal handle teenagers?
Minors are the hardest part of proxy design. Under 164.502(g)(3), a parent is generally the personal representative of an unemancipated minor, but not for a specific service when the minor consents to the care and no other consent is legally required, when the minor may lawfully obtain the care without parental consent, or when the parent agreed to a confidentiality arrangement between the provider and the minor. State law also matters: where state or other law permits or requires disclosure to a parent, the provider may disclose, and where it prohibits disclosure, the provider may not. Where neither applies, a licensed health care professional decides, using professional judgment.
These are legal decisions, and the software's job is to apply them. Configure age thresholds and rules per state with your legal team. Let clinicians mark specific encounters, results or notes as confidential so they do not appear in the parent's view. Give the adolescent their own account when the rules allow it. Test the parent view after every EHR mapping change, because one missed flag can expose a confidential visit.
How do you verify that a proxy has the right to access?
Verification depends on how the proxy is created.
- Patient invitation: an adult patient with capacity invites the proxy from their own account and picks the permissions. The patient's own sign-in is the authorization, and the proxy still verifies their own identity.
- Staff-created proxy: for a guardian, a health care agent or a parent, staff review the supporting document, such as a guardianship order, a power of attorney or proof of parentage, and record what they reviewed and when.
- Self-requested proxy: a caregiver asks for access through a form. The request goes to a staff queue and, where the patient can respond, to the patient for approval.
Store the basis for each proxy relationship: who approved it, which document supported it, and its scope and end date. That record is what staff need when someone later asks why a person had access.
When can you deny or end proxy access?
HIPAA allows a covered entity to decline to treat someone as a personal representative, notwithstanding state law, when it reasonably believes the patient has been or may be subjected to domestic violence, abuse or neglect by that person, or that treating the person as the representative could endanger the patient, and a professional judges that doing so is not in the patient's best interest. The rule adds that such a belief cannot rest only on the fact that the person provided or facilitated reproductive health care at the patient's request.
The portal needs a fast path for this: a staff action that suspends a proxy immediately, without notifying the proxy, and routes the case for review. Patients also need a simple way to remove a proxy themselves.
Information blocking rules shape how restrictions are recorded. Under the privacy exception at 45 CFR 171.202(e), an actor may decline to share a patient's electronic health information when the patient asked for that restriction, as long as the actor did not improperly encourage or induce the request, documents it within a reasonable time, and applies the practice consistently. The restriction may end only when the patient agrees in writing, agrees orally with documentation, or is notified of the termination. A portal that lets patients hide sections from a proxy should store each such request in that form.
What does role-based caregiver access look like in practice?
We built role-based access of this kind for a white-label home-based care platform in Australia. It has five user roles, Captain, Admin, Helper, Inner-Circle Helper and the broader Helper Network of family and friends, each with different access and workflows, on top of chat, a calendar with tasks and risk-assessment flows. Tasks can be marked for the inner circle only. Six apps are live on that foundation, and the partnership has run since 2017.
In any proxy design, name the roles in the patient's language. Captain and Helper mean more to a family than "principal" and "delegate", and clear names lead to fewer wrong permissions.
What should you check before launching proxy access?
- Every permission is enforced on the server for every API call, whatever the interface shows.
- Proxy actions are attributed to the proxy in the record and in staff views.
- Adolescent confidentiality rules are configured per state and tested with real encounter types.
- Suspension and removal take effect on all devices at once.
- Patients' requests not to share are recorded with date, scope and how they can be ended.
- Staff on the clinical side see only their own patients, so a proxy request reaches the right team.
We sign a BAA before anyone on the team sees PHI, and we run a penetration test before launch, which for proxy features includes trying to reach another patient's record from a proxy session.
Designing proxy access for your portal?
Talk to an engineer at Onix Health about your proxy types, your EHR and your state rules. Our free five-day technical audit ends with a written report on your current proxy model and what to change first.
Sources
- 45 CFR 164.502: uses and disclosures of PHI, including (g) personal representatives (Cornell LII)
- 45 CFR 164.510: uses and disclosures requiring an opportunity to agree or object (Cornell LII)
- 45 CFR 171.202: privacy exception to information blocking (Cornell LII)
- ASTP/ONC Data Brief No. 77: individuals' access and use of patient portals and smartphone health apps, 2024