Key takeaways
- FHIR is a standard way for software to read and write health data in small, named pieces called resources.
- Supports FHIR does not mean a tool can write to your schedule; read access is common, write access is not.
- Federal rules require many payers to offer FHIR APIs, including for prior authorization, from January 1, 2027.
- Ask vendors which resources they use, whether they read or write each one, and who switches the connection on.
FHIR in plain terms
FHIR, pronounced fire, stands for Fast Healthcare Interoperability Resources. It is a standard published by HL7, the health data standards body, that describes how software should package and exchange health information. Instead of sending a whole chart as one document, FHIR breaks data into small, named pieces called resources: a patient, an appointment, an insurance coverage record, a practitioner. Software asks for those pieces over the web, much as a banking app asks your bank for a balance.
For a practice manager, the useful idea is this: when two systems both speak FHIR, connecting them should take less custom work than older methods such as file transfers or HL7 version 2 interfaces. Should is the important word. FHIR sets the format. Your EHR vendor still decides which resources it exposes, to whom, and whether outside tools can write or only read.
The resources that matter at the front desk
| FHIR resource | What it holds | Front office use |
|---|---|---|
| Patient | Name, date of birth, contact details, language | Matching callers and forms to the right chart |
| Appointment | A booked visit: who, when, where, what type | Online booking, reminders, rescheduling |
| Schedule and Slot | Provider availability and open times | Showing real open times to patients or tools |
| Coverage | Insurance plan, member ID, subscriber | Eligibility checks and intake |
| Practitioner and Location | Providers and sites | Routing calls and bookings to the right office |
| Questionnaire and QuestionnaireResponse | A form and the patient's answers | Digital intake that lands as data |
| DocumentReference | A pointer to a document such as a scanned form | Attachments when structured data is not available |
When a vendor says it uses FHIR, ask which of these resources it reads, which it writes, and which it does not touch. The answers tell you more than any feature list.
Patients already use FHIR every day
Most patients will never hear the word, but many already rely on it. App-based access to online medical records rose from 38% of individuals in 2020 to 57% in 2024[1]. Proxy or caregiver access to portals more than doubled over the same period, from 24% to 51%[1]. Many of those apps pull records from your EHR through a FHIR API.
- 2020
- 2024
Source: Office of the National Coordinator for Health IT (ASTP/ONC), HHS, 2024[1]
Show the data
| Item | 2020 | 2024 |
|---|---|---|
| App-based access | 38% | 57% |
| Proxy or caregiver access | 24% | 51% |
That has a practical consequence for the front desk. A patient who connects a health app to your EHR is exercising the HIPAA right of access, and a covered entity must act on an access request no later than 30 days after receiving it, with one extension of no more than 30 days[2]. When an app connection fails, the patient often calls the office. Staff should know where to send those calls, usually the EHR vendor's patient support or your portal administrator.
Federal rules are pushing payers to FHIR
The CMS Interoperability and Prior Authorization Final Rule requires impacted payers, including Medicare Advantage organizations, Medicaid and CHIP programs and plans, and qualified health plan issuers on the federal exchanges, to implement HL7 FHIR APIs[3]. The Patient Access, Provider Access, Payer-to-Payer and Prior Authorization APIs must be in place beginning January 1, 2027[3].
- Provider Access API: in-network providers with a treatment relationship can receive a patient's claims and encounter data, clinical data and prior authorization information from the payer[3].
- Prior Authorization API: populated with the payer's list of covered items and services, it can identify documentation requirements and supports a prior authorization request and response, for items and services other than drugs[3].
- Patient Access API: adds prior authorization information, excluding drugs, to what patients can see in their apps[3].
Your practice is not the one building these APIs, but your EHR and billing vendors will need to use them. Ask them now what their 2027 roadmap is for the Provider Access and Prior Authorization APIs, and whether the features will cost extra.
SMART on FHIR in two minutes
SMART on FHIR is a companion standard that handles two things FHIR alone does not: how an app proves who it is and what it is allowed to see, and how an app launches inside the EHR with the right patient already open. When a vendor says its tool is a SMART app, it usually means a staff member can open it from inside the chart without a second login, and the app sees only the scopes, or permission sets, that your EHR administrator approved.
Scopes are worth reading. A scope that allows reading patient demographics is very different from one that allows writing appointments. Ask the vendor to list the scopes it requests and explain why it needs each one.
What FHIR does not guarantee
- Write access. Many EHRs expose read-only FHIR endpoints to outside apps. Booking or updating records may require a separate, vendor-specific API or a partner agreement.
- Every field. A resource can exist while key fields you need are missing or empty in your system.
- Real-time data. Some systems update their FHIR endpoints on a schedule rather than instantly.
- Free access. Some EHR vendors charge per connection or require a marketplace listing.
- Correct workflow. FHIR moves data; it does not know your new-patient rules or provider preferences.
Example: a fictional orthopedic group tested an online booking app that used FHIR. Reading open slots worked well. Booking did not, because the group's EHR allowed outside apps to read Schedule and Slot but not to create an Appointment. The vendor offered a request-an-appointment flow instead, where staff confirmed each booking. The group bought it knowing exactly what it was getting.
Questions to ask a FHIR-based vendor
Which resources and which direction?
Ask for a list: resource name, read or write, and what the tool does with it.
Which EHR versions are live?
Ask for customer references on your exact EHR and version, not just the brand.
Who enables the connection?
Find out whether your EHR vendor must approve the app, and how long that takes.
What does it cost on both sides?
Ask both the tool vendor and the EHR vendor about connection or API fees.
How fresh is the data?
Ask how quickly a change in the EHR appears in the tool, in minutes.
What happens on failure?
Ask who is alerted, whether changes queue, and how errors show up to staff.
Where is the BAA?
Any vendor reading patient data on your behalf needs a business associate agreement before go-live.
How FHIR shows up in daily front desk work
Staff rarely see FHIR directly, but they see its effects. When a patient books online and the visit appears on the schedule with the right type and length, an Appointment resource was probably written. When an intake form lands as answers rather than a scanned page, a QuestionnaireResponse probably carried it. When either goes wrong, the symptoms are familiar: duplicate charts, appointments with no visit type, forms stuck in a queue.
- Give staff one place to report integration problems, with the patient, the time and what they expected to see.
- Ask the vendor for a plain-language error list, so staff know the difference between a patient-match problem and a connection outage.
- Review integration problems weekly for the first two months, then monthly.
- Tell patients who call about a health app that will not connect where to get help, instead of troubleshooting at the desk.
A short glossary for vendor calls
- API: the doorway one system offers so other software can request data.
- Endpoint: the web address for a particular API.
- Resource: one named type of FHIR data, such as Patient or Appointment.
- Scope: the permission an app is granted, such as read demographics.
- Sandbox: a test copy of the EHR with fictional patients for trying integrations.
- Bulk FHIR: a way to export data for many patients at once, often used for population reports or migrations.
- USCDI: the US Core Data for Interoperability, a federal list of data classes systems are expected to share.
You do not need to be technical to run a good vendor conversation. You need to ask which resources, which direction, how fast and who maintains it, and write the answers down.
Where this is heading for small practices
Nearly all office-based physicians already use an EHR: 91% used a certified system in 2024[4]. The next few years will be less about adopting software and more about connecting it. As payers bring their FHIR APIs online in 2027, expect your EHR and billing vendors to add features for pulling payer data into the chart and sending prior authorization requests directly. Keep a simple register of every tool connected to your EHR, which resources it reads or writes, and who to call when it fails. That register will matter more each year.
Frequently asked questions
Is FHIR the same as HL7?
HL7 is the standards organization. It publishes several standards, including the older HL7 version 2 messages many interfaces still use, and FHIR, its newer web-based standard. When people say HL7 interface they usually mean version 2.
Does FHIR mean a tool can book appointments in our EHR?
Not necessarily. Many EHRs let outside apps read scheduling data through FHIR but not create appointments. Ask the vendor whether it writes the Appointment resource on your specific system and version.
Do we need to do anything for the 2027 payer API deadline?
The payers build the APIs. Your job is to ask your EHR and billing vendors how and when they will use them for provider access to payer data and electronic prior authorization.
Is a FHIR app automatically HIPAA compliant?
No. FHIR is a data format. A vendor that accesses patient data on your behalf still needs a business associate agreement, sensible access scopes and audit logs.
References
Office of the National Coordinator for Health IT (ASTP/ONC), HHS (2024). Individuals' Access and Use of Patient Portals and Smartphone Health Apps, 2024 (opens in a new tab) ↑
Legal Information Institute, Cornell Law School (current). 45 CFR § 164.524 - Access of individuals to protected health information (opens in a new tab) ↑
Centers for Medicare & Medicaid Services (CMS) (2024). CMS Interoperability and Prior Authorization Final Rule (CMS-0057-F) fact sheet (opens in a new tab) ↑
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) ↑