The base subscription price of an EMR is the number that appears on the proposal. The integration fees are the numbers that appear on the invoices for the next five years. A practice that needs a lab interface, an imaging interface, a connection to the regional health information exchange, and an API link to a patient engagement platform can find that integration costs rival the license itself. This guide explains how vendors price connections, what federal rules constrain those prices, and how to compare offers on an equal footing.
Why integration fees are hard to compare
Vendors price integrations in different units. One charges a one-time build fee per interface. Another bundles a fixed number of "standard" interfaces into the subscription and charges for anything else. A third charges a monthly maintenance fee per connection, or a per-transaction fee, or a fee to the third party rather than to the practice. Proposals rarely list all of these on one page, and the terms "interface," "integration," "connector," and "API access" are used inconsistently. The result is that two proposals with similar license prices can differ by tens of thousands of dollars in integration cost over the contract term.
Types of interfaces and how they are priced
| Connection | Typical mechanism | Common pricing patterns | Watch for |
|---|---|---|---|
| Lab orders and results | HL7 v2 messaging, sometimes via a hub | Per-lab build fee; monthly maintenance; sometimes paid by the lab | Whether each additional lab is a new fee; who pays when the lab changes platforms |
| Imaging orders and reports | HL7 v2; DICOM for images | Similar to labs; image viewing may be a separate module | Whether report links or embedded images are included |
| E-prescribing and PDMP | National e-prescribing network; state PDMP gateway | Often included; PDMP integration may be add-on | Per-provider fees for controlled substance prescribing |
| Health information exchange | Document exchange, query-based exchange, TEFCA participation | Included, per-connection fee, or per-document fee | Fees that scale with volume |
| Practice management and billing | Native, HL7 v2, or vendor connector | Included if same vendor; substantial if not | Charge, demographic, and scheduling messages priced separately |
| Third-party apps | FHIR API, proprietary API, SFTP exports | Per-app connection fee; revenue share with the app vendor; per-call fees | Fees charged to the app vendor that are passed back to you in its price |
| Registries and public health | HL7 v2 or FHIR to state systems | Often included for certified capabilities; sometimes per-registry | Ongoing maintenance when the state changes specifications |
For each connection the practice needs, ask three questions: what is the one-time cost, what is the recurring cost, and who pays it. An interface fee charged to the lab or the app vendor is not free; it is usually recovered in that vendor's price to you.
What the information blocking rules say about fees
Federal information blocking rules, adopted under the 21st Century Cures Act, prohibit health IT developers of certified health IT from engaging in practices likely to interfere with access, exchange, or use of electronic health information, unless the practice meets an exception. Fees are addressed directly. The fees exception allows a developer to charge fees for access, exchange, or use, but the fees must meet conditions: they must be based on objective and verifiable criteria applied uniformly to similarly situated parties, reasonably related to the developer's costs, and not based on whether the requestor is a competitor or on the revenue the requestor might earn from the data. Certain fees are excluded entirely, including fees for a patient to access their own information and fees tied to the certified standardized API capability that would fall outside the allowed categories.
What this means for a buyer is that unreasonable, discriminatory, or opaque fees for connecting to a certified EMR are not merely a negotiating point; they may be inconsistent with the developer's obligations. A vendor that cannot explain how an interface fee relates to its costs, or that charges a competitor's product more to connect than it charges a partner, is worth questioning. The rules do not set prices, however, and they do not require a vendor to build an interface for free.
The fees exception under 45 CFR Part 171 constrains how certified health IT developers price access, exchange, and use of electronic health information. It does not set prices, and it does not oblige a vendor to build a custom interface at no charge; it does require that fees be objective, uniform, and cost-related.
API access and certified capabilities
Certified EMRs must provide a standardized FHIR-based API for patient and population services, along with published documentation and terms. The certification conditions include specific limits on fees and on how developers may restrict use of that API. Ask each vendor for its published API terms and fee schedule, which should be publicly available, and compare them directly. Distinguish that certified API from the vendor's proprietary APIs or marketplace programs, which are often where the substantial fees live.
Also ask whether the vendor supports bulk data export through the certified API and whether there is a fee for it. Bulk export is how practices extract their own data for analytics or for migration, and it is the capability that determines how expensive it will be to leave.
A comparison worksheet
Build a table with one row per connection the practice needs today and one row per connection it is likely to need within the contract term. For each vendor, capture the one-time fee, the recurring fee, any per-transaction or per-provider component, who is billed, and whether the connection is a certified capability or a proprietary one. Total the rows over the full contract term, including expected growth in providers and volume. Then add two more rows: the cost to replace the most important connection if the counterparty changes (for example, if the practice switches reference labs) and the cost to export all data at the end of the term.
This exercise usually reveals that the lowest license price is not the lowest total price, and it gives the practice a concrete list of items to negotiate.
Negotiating integration terms
- Ask for a written schedule of all interface and API fees, incorporated into the contract, with a cap on annual increases.
- Negotiate a bundle of included interfaces sized to the practice's actual needs rather than the vendor's default.
- Require that fees for certified API access follow the vendor's published terms and cannot be raised selectively.
- Specify who maintains an interface when the counterparty changes specifications and whether that maintenance is included.
- Obtain a fixed price for full data export at termination.
- Ask for a service level on interface uptime and a defined support path when messages fail.
Integration costs are among the most negotiable items in an EMR contract because the vendor's marginal cost of a standard interface is often low. A practice that arrives with a complete worksheet and a working knowledge of the fees exception is in a strong position to get reasonable terms.
Common questions
Can an EMR vendor charge a fee to connect a third-party app?
Yes, within limits. Under the information blocking fees exception, a certified health IT developer may charge fees that are based on objective, uniformly applied criteria and reasonably related to its costs, but not fees that discriminate against competitors or that are tied to certain patient access and certified API capabilities. The rules do not set specific prices.
Are lab interfaces usually included in the EMR subscription?
It varies. Some vendors include a set number of standard lab interfaces; others charge a build fee per lab plus a monthly maintenance fee. Some national labs pay the vendor for the interface directly. Ask for the fee for each specific lab the practice uses and what happens when a lab is added.
What is the difference between the certified API and the vendor's proprietary API?
The certified API is the standardized FHIR-based interface required for ONC certification, with published terms and fee limits. Proprietary APIs and marketplace programs are additional vendor offerings with their own pricing. Many practical integrations use the proprietary path, so compare both.
Should data export at contract end be priced up front?
Yes. Export cost is the single largest switching cost and is much cheaper to negotiate before signing than at termination. Ask for a fixed price and a defined format, and confirm whether bulk FHIR export through the certified API is available and what it costs.