Caregiver on the Line: Proxy Access in Geriatric Practices

Proxy access sounds like a portal setting. In a geriatric practice it is the single most consequential thing the front desk gets right or wrong, because most of the calls are not from the patient. They are from a daughter in another state, a son on a lunch break, a spouse holding a stack of paperwork, and every one of those calls opens a chart that may or may not be theirs to open.

Geriatric medicine inverts the assumption every phone workflow is built on. The person calling is frequently not the person the call is about, and the practice has to work out which situation it is in before it can do anything useful.

Get it wrong in one direction and the practice stonewalls a legitimate caregiver who has the legal authority to act, which is both wrong and a terrible experience for a family already stretched thin.

Get it wrong in the other direction and the practice discloses information to somebody who has no standing to receive it, or documents a conversation in a chart that belongs to a different person.

What makes this hard operationally is that the answer is not in the conversation. It is in a record the practice maintains, and most front desks are trying to reconstruct it live, from tone of voice, while the caller waits.

Proxy authority is a legal record, not a phone judgment

The rule is narrower than most staff think, and knowing its shape is what lets the front office stop improvising.

Under the HIPAA privacy rule, a covered entity must treat a personal representative as the individual. The test is whether, under applicable law, that person has authority to act on behalf of the individual in making decisions related to health care. That authority comes from state law and from documents the family has executed. It does not come from the caller saying they are the daughter.

So the practice’s job is not to evaluate the relationship on the call. It is to maintain a record of who is authorized for each patient and for what, and then to read that record every time somebody calls. Written down like that, it is a data problem, and data problems automate well.

The adjacent case is narrower still. A third party who is not a personal representative can sometimes be permitted to do specific administrative things, like booking an appointment, if the practice has explicitly allowed it. One practice’s post-live-call build list included exactly that, permitting named third parties to schedule for a patient. Another wanted the caller’s name and company captured whenever a service company called on a patient’s behalf. Both of those are exceptions the practice defines in advance, not decisions made in the moment.

What the front office should never do is expand the record. If the caller is not on it, the call goes to staff, and staff handle the paperwork that would put them on it.

Shared phone numbers put messages in the wrong chart

The most common real-world failure here has nothing to do with authorization. It is identity, and it is caused by a phone number.

One practice reported a mother calling about her daughter, both patients at the practice. Because the phone number was tied to the mother’s account, both calls were documented in the mother’s chart, and staff had to move the messages by hand afterward. That is now tracked internally as a general defect class covering spouse and spouse as well as parent and child.

The fix is two behaviors, and neither is sophisticated. Ask at the top of every call whether this is for you or for someone else, before touching a chart. And detect the mid-call switch, because in a geriatric practice the phone genuinely does get handed over partway through a conversation.

GET /patients/{patientid} is the lookup, but the lookup is only as good as the question that preceded it. A system that matches on caller ID and opens the first chart it finds will produce exactly the defect above, at scale, every day.

This is one of the clearest cases where automation is more reliable than a person, not less. A busy receptionist skips the question when the caller sounds familiar. A system asks it every single time, and it never assumes the number identifies the human.

The portal was not designed for the person actually reading it

Written communication is where proxy arrangements quietly break, because the channels assume one patient and one reader.

Portal reach in this population is the weakest link. ONC data for 2022 found that about 3 in 5 individuals nationwide were offered and accessed their online medical record or patient portal, and among those who did, 48% used a website only, 19% used an app only and 32% used both. In a geriatric panel the person who will actually read the message is often not the patient, and is often on a different device, in a different household.

So the practical rule is that channel follows the record. POST /patients/{patientid}/securemessage/topatient delivers to the portal when portal delivery is what the arrangement calls for. Where an authorized caregiver is the one who reads and responds, that has to be reflected in how the practice reaches out, not worked around by staff forwarding things informally.

GET /patients/{patientid}/securemessage/inboxmessages matters for the same reason in reverse. A reply arriving through the portal was written by whoever is logged in, and the practice should not assume it was the patient.

Language sits on top of all this. Auto-detection works, but bilingual callers mix languages inside a sentence and a system that flips back and forth is worse than one that picks a lane and confirms it. Practices also want certainty before switching, because guessing wrong about someone’s language in a clinical setting is not a small error. Beyond English and Spanish, quality drops enough that most practices route to a human language line, and that is the correct call.

Access requests are a records workflow with a deadline

The other half of proxy access is the formal one, and it carries a clock.

An individual has a right of access to inspect and obtain a copy of protected health information in a designated record set. A covered entity must act on a request no later than 30 days after receiving it, with one 30-day extension available if the individual is notified in writing. Where a personal representative is making the request, they stand in the individual’s shoes.

For a geriatric practice that means the records request arriving from an adult child is not a favor, it is a request with a due date, and the administrative work around it is entirely mechanical. Confirm the requester is on the record. Log the request with its date. Route it to the right queue. Tell the requester what to expect and when. Follow up if it is approaching the deadline.

None of that requires anyone to read the record or decide what it contains. It requires somebody to be counting days, which is exactly the kind of task that gets dropped when the front desk is three people short.

What stays with a person

The scope boundary here is unusually easy to hold, because everything in scope is a lookup and everything out of scope is a decision.

The automation asks who the call is for before opening anything, then matches the caller against the practice’s record of authorized representatives. It documents in the correct chart, books and reschedules for authorized callers, and sends and receives messages through the channel the arrangement specifies. It logs records requests against their deadline, and hands off cleanly when the caller is not on the record.

It does not judge whether somebody should be authorized, it does not extend authority because a caller is insistent or clearly well intentioned, and it does not answer questions about the patient’s care to anybody. Those calls reach staff, with the identity question already asked and the answer already captured.

For a practice administrator the win is narrow and easy to verify. Fewer messages filed in the wrong chart, fewer caregivers stuck at the front door with real authority, and a records queue where somebody is counting the days.

Key Takeaways

Maintain proxy authority as a record on the chart and read it on every call, rather than reconstructing the relationship from the conversation.
Ask whether the call is for the caller or for someone else before opening any chart, and detect the mid-call handoff.
Never match a caller to a chart on phone number alone, since shared numbers between spouses and between parents and children are the main source of wrong-chart documentation.
Define in advance which named third parties may perform specific administrative tasks, so the front office is applying a rule instead of making an exception.
Route written communication to the channel the arrangement specifies, because in a geriatric panel the reader is frequently not the patient.
Confirm the language before switching rather than flipping mid-sentence, and route past English and Spanish to a human language line.
Track records requests against the 30-day clock, since counting days is the part that gets dropped when the desk is short-staffed.

In geriatrics the front desk is talking to the family most of the day. Getting that right is not about being careful on the phone. It is about having the record of who is authorized, and reading it every time, which is work no receptionist should be doing from memory.

Sources