Call Coverage and Answering Services

Answering Services and EHR Access: What to Allow

How much EHR access an answering service should get: read-only vs booking roles, named logins, audit logs, minimum necessary and messages in the chart.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing8 min read

On this page
  1. Start from what the service has to do
  2. Minimum necessary decides the role
  3. Logins, audit logs and offboarding
  4. How messages land in the chart
  5. Where an automated front layer fits
  6. Frequently asked questions
  7. References
Call Coverage and Answering Services: Answering Services and EHR Access: What to Allow32%: of solo-practice physicians used an EHR from a top-five developer in 2024, vs 90% in groups of 50+CALL COVERAGE AND ANSWERING SERVICESAnswering Services and EHRAccess: What to Allow32%of solo-practice physicians used an EHR from a top-fivedeveloper in 2024, vs 90% in groups of 50+Ava Medical IntakeInsightsCall Coverage and Answering Services: Answering Services and EHR Access: What to Allow32%: of solo-practice physicians used an EHR from a top-five developer in 2024, vs 90% in groups of 50+CALL COVERAGE AND ANSWERING SERVICESAnswering Servicesand EHR Access: Whatto Allow32%of solo-practice physicians used anEHR from a top-five developer in 2024,vs 90% in groups of 50+Ava Medical Intake
Figure source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[1]

Key takeaways

  • Grant access by call type, not by vendor: a message-only service needs no EHR login at all, a booking service needs the scheduling module and nothing more.
  • HIPAA requires a unique login for every user[2]; shared vendor accounts make the audit log useless.
  • Review vendor activity on a schedule: regular review of audit logs and access reports is a required safeguard[3].
  • Decide how messages reach the chart before go-live; re-keying 25 messages a day is about 27 staff hours a month in the example.
  • Small practices are more likely to run less common EHRs[1], so check what role types and interfaces yours actually supports.

Start from what the service has to do

The request usually arrives as one line on a vendor's onboarding form: please provide EHR credentials for our agents. How the practice answers that line decides how much of every patient's chart an outside company can open at 2 am, so answer it with a list of call types rather than a login.

Write down every kind of call the service will handle and what the agent must do to finish it. Taking a message for the morning needs no chart access. Confirming that a caller is a patient of record needs a narrow lookup. Booking a follow-up needs the schedule. Only a clinical service, such as nurse triage working from a medication list, needs anything clinical. Most answering services sit at the first two levels, and many requests for full credentials are a convenience for the vendor rather than a need.

Access levels for an outside answering or scheduling service. Grant the lowest level that finishes each call type.
LevelWhat agents can doTypical call typesControls to require
0. No EHR accessTake a message and deliver it securelyAfter-hours messages, office questionsBusiness associate agreement if messages contain patient information
1. Patient lookupConfirm name, date of birth and provider of recordRouting calls to the right provider or teamRead-only, demographic fields only, named logins
2. Schedule viewSee open slots without changing themOffering times for staff to confirmRead-only scheduling role, no chart tabs
3. BookingBook, move and cancel appointmentsRoutine follow-ups, reschedules, overflow bookingScheduling role only, audit sampling, booking rules in writing
4. Clinical readRead medications, problems or recent notesNurse triage by a clinical serviceLicensed clinicians only, clinical vendor agreement, close audit

The hardest line to draw is between levels 2 and 3. A read-only schedule view lets the agent offer real times, but someone at the practice still has to book them, so every call becomes two pieces of work and some patients never get the confirmation call. Booking access lets the agent finish the call, but every mistake lands in your schedule where your own staff have to find it. Practices that grant booking usually start with one or two visit types with simple rules, audit them for a month, and widen access only when the error count stays low.

Minimum necessary decides the role

HIPAA's minimum necessary rule gives the practice the method. It asks a covered entity to identify the people or classes of people who need access to patient information, the categories of information each needs and any conditions on that access, and then to make reasonable efforts to limit access to match[4]. Treat the answering service's agents as one more class on that list, with its own row, rather than borrowing the front desk's role because it already exists.

  1. List the call types

    Every call the service will handle, from the vendor's onboarding form and your own phone logs.

  2. Name the fields each needs

    For a reschedule: patient name, date of birth, existing appointment, open slots. Nothing about diagnoses or results.

  3. Map them to an EHR role

    Ask your EHR vendor which role types exist and whether chart tabs can be hidden from a scheduling role.

  4. Test with a dummy patient

    Log in as the vendor role and try to open notes, results and billing. Anything that opens and should not gets fixed before go-live.

  5. Put the role in the contract

    Name the access level in the agreement, so a later request for more access is a contract change rather than a support ticket.

The role design depends on the EHR, and small practices have a wider spread of systems. In 2024, 32% of physicians in solo practice used an EHR from one of the five market-leading developers, against 90% of physicians in groups of more than 50[1], and solo and physician-led practices had the lowest certified EHR adoption, at 4 in 5[5]. A role type that exists in one product may not exist in yours. The minimum necessary rule at the front desk covers the same principle for your own staff.

Physicians using an EHR from a top-five developer, 2024Office-based physicians by practice size, ONC National Electronic Health Record Survey.
Physicians using an EHR from a top-five developer, 2024Comparison. Solo practice: 32%; More than 50 physicians: 90%.32%Solo practiceSolo practice: 32%90%More than 50 physiciansMore than 50 physicians: 90%Physicians using an EHR from a top-five developer, 2024Comparison. Solo practice: 32%; More than 50 physicians: 90%.32%Solo practiceSolo practice: 32%90%More than 50 physiciansMore than 50 physicians: 90%

Source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[1]

Show the data
Practice sizeShare using a top-five EHR
Solo practice32%
More than 50 physicians90%

Logins, audit logs and offboarding

Shared logins are the most common shortcut and the most damaging. The Security Rule requires a unique name or number for identifying and tracking each user[2], and its audit controls standard requires mechanisms that record and examine activity in systems holding electronic patient information[2]. A single vendor account used by twenty agents satisfies neither in any useful way: the log shows that someone at the vendor opened a chart, never who.

  • One named login per agent, created by the practice, not the vendor, and tied to the vendor role.
  • A monthly roster from the vendor of every agent on your account, matched against active logins.
  • Accounts disabled the day an agent leaves the account; the Security Rule lists termination procedures for exactly this[3].
  • Automatic logoff after inactivity, an addressable safeguard worth switching on for shared vendor workstations[2].
  • Login hours limited to the hours the vendor covers, if your EHR supports time restrictions.
  • A business associate agreement signed before the first login[6], with breach reporting and return or destruction of information at the end of the contract[7].

Ask where the agents physically work. An agent on a supervised call-center floor and an agent working from a kitchen table with family nearby present different risks to the same chart, and the contract should say which you are getting. Ask too whether agents can copy text out of the EHR, print from it or reach it from personal devices, and have the answers written into the agreement rather than taken on trust.

Then actually read the logs. Regular review of information system activity, such as audit logs and access reports, is a required safeguard, not a nice extra[3]. A workable routine for a small practice: once a month, pull the vendor accounts' access report, pick 20 records at random, and match each chart opened to a call the vendor handled. Any chart opened with no matching call goes back to the vendor in writing. The security risk assessment is where this routine and its findings should be recorded.

Plan the end of the relationship on day one. When a vendor contract ends, every vendor login should be disabled the same day, a final access report pulled and kept with your compliance records, and written confirmation obtained that messages and recordings holding patient information have been returned or destroyed.

How messages land in the chart

Even with no EHR access at all, every clinical message from the service has to end up in the record, and somebody's time pays for the trip. Inbox work is already heavy: in a time-motion study, inbox management took 85 minutes of a primary care physician's daily EHR time[8], and 71% of medical groups now designate someone to handle portal and inbox messages for other providers[9]. Overnight messages land on top of that.

There are four common routes. Staff can re-key each message into a telephone encounter, which is safe and slow. The vendor can write telephone encounters directly, which needs write access to clinical documentation and a careful role. An interface can import messages as documents, if your EHR and the vendor support one; questions to ask every EHR integration vendor helps there. Or messages arrive by secure email or fax and are attached to the chart, which is quick to set up and easy to lose track of.

ExampleExample: staff time spent re-keying service messages into the chart
Example: worked figures
InputExample
Service messages per day25
Minutes to chart each message3
Share that must be charted (%)100%
Loaded hourly cost of staff$36.73
Calls a month543
Staff hours on these calls27
Hours handed off27
Monthly value of that staff time$996

How it is worked out: Calls a day ร— 21.7 working days ร— minutes per call รท 60 ร— share handled = hours; hours ร— hourly cost.

Assumptions

  • $36.73 an hour is average total compensation for private-industry office and administrative support workers in June 2026.[10]
  • 25 messages a day at three minutes each is an example; time ten real messages from your own service to replace it.

Example only. The result is the monthly cost of the manual route, to weigh against direct entry or an interface.

In the example that is about 27 staff hours a month[10]. Direct entry by the vendor removes most of it but gives outside agents write access to clinical documentation, which raises the bar on roles, training and audit. Many practices settle in the middle: messages arrive in a structured, consistent format that staff can paste into a telephone encounter in under a minute, and only messages needing clinical action are routed to a nurse or provider. The morning handoff covers the routine for working through them.

Example: an overnight message, from call to closed encounter
  • Caller
  • Your team
  • System
  1. 01Caller

    Patient calls at 9:15 pm

    Asks for a callback about a medication question; no emergency described.

  2. 02Your team

    Service takes the message

    Name, date of birth, callback number and the question, in the agreed format.

  3. 03System

    Secure delivery overnight

    Message arrives in the practice's secure inbox, flagged routine.

  4. 04Your team

    Charted at 8 am

    Front desk opens a telephone encounter and routes it to the nurse.

  5. 05Your team

    Callback documented

    The nurse calls back and closes the encounter with what was said.

Example sequence for a message-only service with no EHR access.

Where an automated front layer fits

The cleanest way to avoid an access question is a layer that never needs the chart. An SI Employee works that way: calls forward to it for the hours you choose, it answers office questions from information the practice approves, and it hands anything patient-specific to the staff line the practice picks without taking health details. It has no EHR login, and since AssistCall does not sign business associate agreements today, the setup is built to keep patient information out of its part of the call. Scheduling inside a PM or EHR system is planned, not live. The integrations page lists what connects today.

The modelled orthopedic after-hours example follows the same boundary: office questions answered in full, post-op patients offered the on-call physician, and patient messages left on the practice's own voicemail line and portal. If you need a service that does book into your system, what to ask an answering service that books appointments is the next read, and the same access rules apply to outsourced scheduling call centers.

Frequently asked questions

Should our answering service have access to our EHR?

Only as much as its call types need. A message-only service needs no login. A service that routes calls may need a read-only patient lookup, and one that books needs the scheduling module only. Under the minimum necessary rule, the practice defines what each class of user needs and limits access to it[4].

Can answering service agents share one EHR login?

No. The Security Rule requires a unique name or number to identify and track each user[2]. A shared vendor account also makes the audit log useless, because it can never show which agent opened which chart.

Does an answering service need a business associate agreement if it never logs into the EHR?

If it takes or delivers messages containing patient information for the practice, yes. HIPAA allows a vendor to handle that information only with satisfactory assurances in a business associate agreement[6].

How should answering service messages get into the patient chart?

Staff re-entry, direct entry by the vendor, an interface or secure delivery attached to the chart. Re-entry is safest and slowest; in the example, 25 messages a day is about 27 staff hours a month[10]. Direct entry saves time but needs write access and closer audit.

How often should we review an answering service's EHR activity?

Regular review of audit logs and access reports is required[3]; monthly works for most small practices. Match a random sample of charts opened by vendor accounts to calls the vendor actually handled, and query any that do not match.

References

  1. Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief) (opens in a new tab) โ†‘

  2. Legal Information Institute, Cornell Law School (current). 45 CFR 164.312 - Technical safeguards (opens in a new tab) โ†‘

  3. Legal Information Institute, Cornell Law School (current). 45 CFR 164.308 - Administrative safeguards (opens in a new tab) โ†‘

  4. Legal Information Institute, Cornell Law School (current). 45 CFR 164.514 - Other requirements relating to uses and disclosures of protected health information (minimum necessary) (opens in a new tab) โ†‘

  5. Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Office-based Physician Electronic Health Record Adoption, 2008-2024 (ONC Data Brief): summary (opens in a new tab) โ†‘

  6. Legal Information Institute, Cornell Law School (current). 45 CFR 164.502 - Uses and disclosures of protected health information: general rules (opens in a new tab) โ†‘

  7. Legal Information Institute, Cornell Law School (current). 45 CFR 164.504 - Uses and disclosures: organizational requirements (opens in a new tab) โ†‘

  8. Annals of Family Medicine (2017). Tethered to the EHR: Primary Care Physician Workload Assessment Using EHR Event Log Data and Time-Motion Observations (opens in a new tab) โ†‘

  9. Medical Group Management Association (MGMA) (2026). Who owns the inbox? How medical groups can redesign portal message work (MGMA Stat) (opens in a new tab) โ†‘

  10. U.S. Bureau of Labor Statistics (2026). Employer Costs for Employee Compensation, Table 4: private industry workers by occupational and industry group, June 2026 (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo