Patient ID & Consent
Set how Katie confirms a caller's identity and what she may discuss with a spouse, parent or caregiver, so your privacy rules hold on every call.
Identity before details
Before Katie discusses an existing appointment or takes a request on a patient's behalf, she confirms who she is talking to, using the identifiers your practice chooses. The usual choice is full name and date of birth, sometimes with a phone number or address as a second check. Katie then uses athenahealth patient lookup to find the matching record.
If the details do not match, she does not keep trying combinations until something fits. She takes the request and flags the mismatch for staff to resolve, which is also how duplicate or misspelled records tend to get noticed.
When the caller is not the patient
Many calls come from someone other than the patient: a spouse moving an appointment, an adult daughter managing her father's care, a caregiver from a group home. Your practice already has rules about what can be shared with whom, and Katie follows them. Typical rules look like this:
- Scheduling help for family members, if your policy allows it
- A defined path for group homes, assisted living and home health agencies
- No discussion of clinical details with an unverified third party
- The caller's name and relationship recorded in every summary
- Requests that need an authorization check routed to staff
Minors and confidential adolescent care
Parents usually manage appointments for young children, but adolescent care can be different. Some visits, such as reproductive or mental health care, may be confidential from parents depending on state law and your policy. Your rules tell Katie which requests from a teenager should go straight to clinical staff and what she should and should not confirm to a parent who calls asking about them.
It helps to write these rules with your clinicians and your compliance lead together, then review a sample of real calls once the service is live.
Consent already lives in your records
Release-of-information authorizations, proxy access and communication preferences are documented in your intake process and in athenahealth. Katie does not decide whether someone is authorized. When a caller asks for something that would require that check, she captures the request, and your staff verify authorization before anyone responds.
That keeps the judgment where it belongs, with people who can see the signed forms. If a caller says they have permission on file, Katie notes that claim in the summary, and staff confirm it against the record before sharing anything.
The compliance layer underneath
Compliancy Group verifies MedReception AI's HIPAA compliance, and every practice receives a Business Associate Agreement. Katie asks only for what a given call requires, and every summary records who called and what they asked for, so your privacy officer can review how sensitive requests were handled.
Frequently asked questions
- What identifiers does Katie ask for?
- The ones you choose. Name and date of birth are the usual pair; some practices add a second identifier for calls about existing appointments.
- What happens if a caller cannot verify their identity?
- Katie does not share appointment details. She takes the request and flags it, and staff verify the caller through their usual process.
- Can a parent book for a child?
- Yes, when your policy allows it. The summary records the parent's name and relationship, and confidential adolescent requests follow your separate rules.
- Does Katie read chart details aloud so the caller can confirm them?
- No. The caller supplies the identifiers and Katie checks them. Reading details aloud for a caller to confirm would disclose information to whoever happens to be on the line.
Ready to automate this for your athenahealth practice?
Book a demo to see how MedReception AI handles scheduling, referral and after-hours calls for athenahealth practices.
Book a Demo →