In this article
- EHR vs EMR: the plain definitions
- Side-by-side comparison
- What an EHR system usually contains
- EHR, practice management, and clearinghouse: three different things
- How data flows from visit to payment
- Interoperability: what it means and where it breaks
- Where interoperability fails in billing
- What a billing team needs from the EHR
- Billing data checklist
- How to choose: questions to ask an EHR vendor
- Specialty and practice-size considerations
- How billing teams use EHR data day to day
- Charge capture and coding
- Claim scrubbing and edits
- Denial follow-up and appeals
- Worked hypothetical: a data break that looks like a coding problem
- Switching or upgrading an EHR: what to protect
- Security and access for billing work
- What Mednex handles and what the practice handles
- Next steps
- The textbook difference is portability: an EMR lives in one practice, an EHR is designed to move with the patient across settings.
- Most current products are marketed as EHRs. Judge the product by how it exchanges data, not by its label.
- Billing depends on data that starts in the clinical system: demographics, insurance, orders, diagnoses, procedures, and signed notes.
- The EHR is not the same thing as the practice management (PM) system or the clearinghouse. Many revenue cycle problems come from the gaps between the three.
- Ask vendors for specifics: certification status, interfaces, claim edit capabilities, reports, and data export terms.
EHR vs EMR: the plain definitions
The two terms were once cleanly separated. An EMR was the electronic replacement for a paper chart in a single office: the visit notes, medication list, allergies, lab results, and immunization history a practice kept about its own patients. An EHR was the broader idea: a longitudinal record that follows the patient and can be shared between hospitals, specialists, labs, pharmacies, and the patient themselves.
The federal Office of the National Coordinator for Health Information Technology (ONC) has published explanations along these lines on its HealthIT.gov site, and the distinction is widely taught. In practice, software vendors blurred the terms. A product that began as an EMR often gained interfaces and patient portals and was renamed an EHR. Today the two words are often used as synonyms, and a clinic that says “our EMR” may be describing a fully connected system.
Because of that, the label is a weak buyer’s signal. Two products can both say “EHR” and differ widely in how they exchange data, how they generate claims, and how easily you can get your own data out.
Side-by-side comparison
| Feature | EMR (classic meaning) | EHR (classic meaning) |
|---|---|---|
| Main purpose | Digital chart for diagnosis and treatment inside one practice | Whole-patient record designed to be shared across organizations |
| Who sees the data | Staff and providers of that practice | Authorized providers across settings, plus the patient through a portal |
| Portability | Often limited. Records may need to be printed or exported when a patient moves | Built for exchange through standards and interfaces |
| Patient access | May be minimal | Typically portal and app access |
| Interoperability | Depends on the product | Expected as a design goal |
| Billing link | Often separate or manual | Often integrated or interfaced to practice management and a clearinghouse |
| Common in the market today | The term persists in speech | The term most vendors use for their products |
Treat this table as a vocabulary guide. When you evaluate a real product, test each row against the actual software and its contract.
What an EHR system usually contains
A modern ambulatory EHR is a collection of modules. The names vary, but most include:
- Clinical documentation. Visit notes, templates, problem list, medication list, allergies, vitals, and results.
- Orders and results. Lab, imaging, referrals, and e-prescribing, often with electronic results returned from outside labs.
- Scheduling and registration. Appointments, demographics, and insurance capture. Sometimes this is part of a separate PM system.
- Patient portal. Secure messaging, forms, record access, and bill pay.
- Coding and charge capture. Fields where the provider or coder selects diagnosis and procedure codes.
- Reporting. Quality measures and operational reports.
- Interfaces. Connections to labs, hospitals, pharmacies, health information exchanges, and a clearinghouse.
The more of these live in one product, the fewer places a data error can creep in. The more of them are separate products, the more important the interfaces become.
If you suspect your system setup is costing you claims, a Free Medical Billing Audit can show where the data breaks.
EHR, practice management, and clearinghouse: three different things
Billing staff often use all three systems in a day, and confusion about which does what causes wasted time. Here is the usual division.
| System | Main job | Typical billing data it holds |
|---|---|---|
| EHR | Clinical documentation and orders | Signed notes, diagnoses, procedures performed, time, orders, authorization notes if recorded there |
| Practice management (PM) | Scheduling, registration, charges, claims, patient accounts | Demographics, insurance, charges, claim status, payments, adjustments, patient balances |
| Clearinghouse | Moves electronic transactions between the practice and payers | Submitted claims, acknowledgments, eligibility responses, remittances |
Some vendors offer one product that combines EHR and PM. Others sell them separately, and the practice connects them with an interface. Neither design is automatically better. What matters is that the data crosses each boundary reliably, and that someone owns the check.
How data flows from visit to payment
- The front desk registers the patient and captures insurance in the PM or EHR registration module.
- Eligibility is checked through the clearinghouse or a payer portal.
- The provider documents the visit and selects or confirms diagnoses and procedures in the EHR.
- The charge flows to the PM system, where it is combined with patient and insurance data.
- The PM system or a scrubber runs edits, then builds the claim for the clearinghouse in the standard electronic format (the 837P for professional claims).
- The clearinghouse and payer return acknowledgments. Rejections come back here. For a closer look, see the claim rejection vs denial guide.
- The payer adjudicates and sends a remittance (the 835). Payments post to the patient account. The payment posting article covers this step.
- Unpaid or denied items move into follow-up, which is where accounts receivable recovery work starts.
Interoperability: what it means and where it breaks
Interoperability is the ability of different systems to exchange data and use it. It has layers.
- Technical. Systems can send and receive messages, using standards such as HL7 messaging and FHIR application programming interfaces.
- Structural. Data arrives in a predictable format, such as defined fields for allergies or lab results.
- Semantic. Both sides interpret the content the same way, often through common code sets such as ICD-10-CM, CPT, LOINC, and SNOMED CT.
Federal policy has pushed on this. ONC runs a health IT certification program, and the 21st Century Cures Act added information blocking rules that restrict practices that unreasonably interfere with access to electronic health information. The practical effect for a practice owner is to ask a vendor how patient data can be accessed, exchanged, and exported, and to read what the contract says about fees for those functions.
Where interoperability fails in billing
| Break point | Symptom | Billing effect |
|---|---|---|
| Demographics not syncing between EHR and PM | Name or date of birth differs between systems | Rejection for subscriber or patient mismatch |
| Insurance updated in one system only | Old payer ID or member ID on the claim | Rejection or denial for coverage |
| Charge does not cross from EHR to PM | Visit documented but never billed | Missed revenue that shows up only in an audit |
| Diagnosis pointers lost in transfer | Claim shows diagnoses in a different order or limit | Denial for medical necessity or diagnosis mismatch |
| Authorization stored as free text | Billing cannot see number or date range | Denial for missing authorization |
| Rendering and billing provider mapping wrong | Wrong NPI or location on the claim | Rejection or denial, delayed payment |
Most of these show up in your own rejection and denial reports. If you see the same cause repeatedly, the issue is often in the interface or the setup, not in individual claims.
What a billing team needs from the EHR
A billing or coding team can only work with what the clinical system captures. Before you pick or reconfigure a system, check that it can capture and expose each item below in a way billing can read.
Billing data checklist
- Patient legal name, date of birth, sex, address, and contact details, with a rule for who edits them.
- Primary, secondary, and tertiary insurance with payer ID, member ID, group number, subscriber details, and effective dates.
- Eligibility check results stored with date and reference, not only as a screenshot.
- Authorization or referral number, approved codes, units, and date range in a structured field.
- Rendering, referring, ordering, and supervising providers, with NPIs.
- Place of service and location data per visit, including telehealth indicators.
- Diagnosis codes selected by the provider with the ability to rank them and point each to a service line.
- Procedure codes and modifiers, units, and time where relevant.
- Signed and dated notes locked to the date of service, with a visible addendum trail.
- Supply, injectable, and drug details where billed, including NDC data where payers require it.
- Charge status: pending, sent, held, and why.
Where a product hides these fields or buries them in free text, billing staff end up calling the front desk, re-reading notes, or guessing. The extra work shows up as slower claims and more denials. For a summary of the issues that follow, see the common medical billing errors article.
How to choose: questions to ask an EHR vendor
A sales demonstration shows the best path through the software. Your questions should look at the edges: data movement, error handling, and exit terms.
| Topic | Question to ask | Why it matters |
|---|---|---|
| Certification | Is the product certified under the ONC health IT certification program, and for which criteria and edition? | Some federal programs require certified technology. Ask for the listing and verify it |
| Integration | Is billing built in, or do you integrate with a PM system? Who builds and maintains the interface, and who pays? | Interface cost and ownership affect long-term total cost |
| Clearinghouse | Which clearinghouses do you support? Can we choose our own? What are the claim edits? | Clearinghouse choice affects rejection handling and reporting |
| Reports | Can we export A/R aging, denial and remittance data, and charge lag reports without a services fee? | Without reports you cannot measure the revenue cycle |
| Access for billing partners | Can an outside billing company get role-based, auditable access? Is there a user cost? | Access method and cost matter if you outsource billing |
| Data ownership and export | What do we receive if we leave? In what format? At what cost? How long? | Switching later is easier with a clear exit |
| Security | Where is data hosted? Will the vendor sign a business associate agreement? How are access logs kept? | HIPAA requires business associate agreements with vendors that handle protected information |
| Support | How are billing-related defects handled and what is the escalation path? | A claim defect can block revenue for weeks |
| Templates | Can templates enforce required documentation fields such as laterality, severity, and time? | Specific documentation reduces coding queries and denials |
| Telehealth | Does the system record modality, place of service, and modifiers? | Telehealth rules differ by payer and change often |
If you are comparing broader operating models, including whether to hand billing to a partner, the questions to ask a medical billing company article gives a parallel checklist, and outsource medical billing vs in-house covers the decision itself.
Specialty and practice-size considerations
No single system fits every practice. These differences are common.
- Solo and small practices often benefit from a single combined EHR and PM product to limit interface work, as long as reporting and exports are adequate.
- Behavioral health needs time-based documentation, treatment plan support, telehealth fields, and careful privacy controls. Our mental health billing services page covers billing details for that setting.
- Dental practices use a different code set and claim form, so a medical EHR is rarely the right fit. See the dental billing services page.
- Procedure-heavy specialties need strong charge capture, supply tracking, and authorization workflows.
- Multi-location groups need consistent provider and location mapping, which is a frequent source of claim errors.
How billing teams use EHR data day to day
Understanding the daily use helps you set up the system in a way billing can work with.
Charge capture and coding
Billing staff compare the visit note, the encounter form, and the charge entered. A note may describe a service that no one charged, or a charge may appear that the note does not support. A weekly charge reconciliation, comparing scheduled visits to completed notes to submitted charges, finds the gaps. The revenue leakage in healthcare article explains why those gaps matter.
Claim scrubbing and edits
Many systems run built-in edits. Edits are rules that catch missing data and incompatible code combinations before the claim leaves. A good edit set reflects payer-specific rules and is updated regularly. A weak one passes errors to the payer, which become rejections and denials.
Denial follow-up and appeals
When a claim is denied, staff go back to the clinical record to find the note, the order, the authorization, or the lab result that supports payment. If the EHR makes that difficult, appeals take longer and some never get filed. The denial management page describes how that follow-up is organized.
Worked hypothetical: a data break that looks like a coding problem
Hypothetical example. The figures here are illustrations, not data from any practice. A five-provider practice notices that a recurring group of commercial claims is denied for a missing authorization. Billing staff first assume the front desk forgot to get approvals.
- Evidence. The denial report shows 40 denials in a month for the same reason, spread over several payers and several providers.
- Check. Staff pull ten of the denied claims and look in the EHR. In eight, the authorization was obtained. The number is in a scheduling note, not in the structured authorization field.
- Cause. The PM system reads the structured field only. Anything typed into the note never reaches the claim.
- Corrective action. The practice adds a required authorization field at scheduling, trains the front desk, and asks the vendor to confirm the field maps to the claim.
- Rework. Billing resubmits the eight claims with the number added and appeals the denials the payer will reconsider.
- Measure. The next month’s report shows how many authorization denials remain, and what share of scheduled visits have the field filled in.
The fix was a setup change and a habit, not a coding correction. Without a look at how the systems share data, the practice would have spent months retraining the wrong people.
Switching or upgrading an EHR: what to protect
A system change is one of the riskiest periods for cash flow. Plan for it.
- Run claims and A/R aging reports from the old system before cutover and keep them.
- Decide who works old A/R. Legacy balances do not move automatically into the new system.
- Confirm clearinghouse enrollment, payer IDs, and remittance enrollment for the new setup. Electronic remittance often needs a new enrollment.
- Test claims from each provider, payer type, and location before go-live.
- Keep a daily rejection report for the first weeks.
- Watch charge lag and days to submission as early indicators.
- Keep read access to the old system for appeals and audits as long as your retention policy and state rules require.
The old unpaid claims question also appears when you change billing companies. See the old unpaid claims when switching billing company guide for how to plan for that.
Security and access for billing work
Billing needs access to protected health information, and access should follow the minimum necessary principle. Practical controls include role-based user accounts, unique logins, multi-factor authentication where available, audit logs, and a signed business associate agreement with every outside party that handles protected information. Shared logins make it impossible to know who changed what. If a billing partner works inside your system, how access is granted, logged, and removed should be confirmed in writing before work starts.
Do not email screenshots or exports with patient details. Use the secure channel set up for the engagement. On this website, never enter patient information in a contact form.
What Mednex handles and what the practice handles
| Mednex can support | The practice keeps |
|---|---|
| Reviewing how EHR and PM data reach the claim, and listing the breaks | Choosing and contracting with the EHR vendor |
| Working claims, rejections, and denials in the practice’s systems or exports, as arranged | Clinical documentation and note signing |
| Reporting on rejection and denial causes by payer and provider | Registration accuracy and insurance capture at the front desk, unless that is added to scope |
| Recommending template and field changes that reduce avoidable errors | Approving and making system configuration changes with the vendor |
The method of system access, security terms, and reporting schedule are confirmed with the practice before work starts. Mednex does not choose your EHR for you, and cannot guarantee any claim payment. The broader service description is on the medical billing page.
Next steps
If you are using an EHR or EMR today, a good first move is to measure how well it supports billing. Pull your last quarter of rejections and denials, group them by cause, and ask which causes trace back to missing or misplaced data. That report tells you whether the problem is people, templates, or the system.
The Free Medical Billing Audit reviews a de-identified or secure-portal sample of recent claims, denial and rejection reasons, and A/R aging by payer. You provide report exports from your systems, and you do not send patient records through the website form. For questions first, use the contact page, or browse the Mednex blog.
This guide is educational. It is not legal, coding, compliance or clinical advice. Rules differ by payer, plan, state and contract, so confirm against the payer's current policy before acting.
Frequently asked questions
What is the main difference between EHR and EMR?
An EMR is the digital version of a patient's chart inside one practice. An EHR is designed to hold a broader record that can be shared with other organizations, such as hospitals, labs, and specialists, and with the patient. In practice most vendors now sell products called EHRs, so judge any system by how it exchanges data and exports reports, not by the label on the box. Ask the vendor how a patient record leaves the system, since that tells you more than a feature list does. For billing purposes the practical question is whether diagnoses, procedures, provider details, and authorizations leave the clinical system accurately and arrive on the claim without retyping, which depends on setup and interfaces more than on the acronym.
Is an EHR the same as practice management software?
No. An EHR holds clinical documentation, orders, and results. Practice management software handles scheduling, registration, charges, claims, and patient accounts. Some vendors bundle both in one product and others sell them separately with an interface. Billing depends on both, so ask which system holds insurance, authorizations, and charge status, and who verifies that the data crosses between them. Whichever design you have, assign one person to check that data crosses the boundary correctly each week. For example, a patient's insurance card may be scanned in one system while the claim reads from the other. If the two disagree, the claim rejects, so a weekly reconciliation of registration data is a low-cost control worth assigning.
Does the EHR send claims to insurance companies?
Usually not directly. The EHR or practice management system builds the claim, then a clearinghouse routes it to the payer and returns acknowledgments. Some vendors have a clearinghouse built in and others let you choose. Ask which clearinghouses are supported, how rejections are reported, and whether you can export claim status and remittance data without extra fees. Check each claim's status in the clearinghouse before assuming the payer received it, because rejections stop a claim before processing. The clearinghouse also gives you reports that the EHR may not show, including payer acknowledgments and rejection reasons. A practice that never looks at those reports often learns about problems only when cash drops.
What should I ask an EHR vendor about billing?
Ask whether billing is built in or interfaced, who maintains the interface and what it costs, which clearinghouses work with it, what claim edits run, which reports you can export, and what access an outside billing company can get. Also ask about authorization fields, telehealth fields, template controls, and what data you receive and in what format if you leave. Put the answers in writing and compare vendors on the same list, so the demonstration does not decide for you. Request a demonstration using one of your own typical visits, from scheduling to remittance posting, and watch where staff must retype, export, or work around the system. Gaps visible in a demo are cheaper than gaps found after contract signing.
Does ONC certification matter for a small practice?
It can. Some federal programs, including parts of Medicare quality reporting, expect certified health IT, and certification lists criteria the product has met. Certification does not tell you whether billing works well for your specialty. Ask the vendor for the certification listing, check the criteria and edition, and then test the billing workflow with your own scenarios. Also ask whether the certification covers the version you will actually run, since upgrades can change it. Certification is one input among many. Reference checks with similar specialty practices and a trial of your own scenarios usually reveal more about daily billing performance than a listing does.
What is interoperability and why does it affect revenue?
Interoperability is the ability of systems to exchange data and use it correctly. In a practice, breaks show up as mismatched demographics, outdated insurance, charges that never reach billing, lost diagnosis ranking, and authorizations stored as free text. Each break can cause a rejection, a denial, or an unbilled visit, so repeated errors often point to setup problems and not coder mistakes. Ask your vendor which interfaces are included in the subscription and which carry a separate fee. Typical examples include a patient's secondary insurance entered as a note instead of a field, or a referring provider's identifier missing from the encounter. Both are easy to find once someone looks at the interface mapping.
Can a billing company work inside my EHR?
Often yes, but the method varies. Options include role-based accounts inside your system, a read-only data feed, scheduled report exports, or a secure portal. Each has different security and workflow tradeoffs. Confirm the access method, who grants and removes it, how activity is logged, and that a business associate agreement is signed before any protected information is shared. Removing access when staff or partners leave matters as much as granting it, so ask how that is logged. A read-only feed is often easier to approve, but it limits correction work, so decide what your billing partner must change directly and what stays with your staff before choosing the method.
What happens to old claims when we switch EHRs?
Open balances and unpaid claims do not move on their own. Run A/R aging and claims reports before cutover, decide who works the old balances, confirm clearinghouse and remittance enrollment for the new setup, and keep read access to the old system for appeals and audits. Watch daily rejections and charge lag closely for the first weeks. Do not assume the new vendor will import every legacy balance, and ask for the migration scope in writing. Also plan for payments that arrive after cutover for services billed in the old system, since those remittances must be posted somewhere. Name the owner and the system for each category before go-live.
How do I tell if my EHR is causing denials?
Group a quarter of rejections and denials by cause and check whether the same cause repeats across providers and payers. Then pull a few affected claims and compare the claim to the chart. If the information exists in the record but not on the claim, the issue is likely a field, template, or interface problem, which is a setup fix and not a retraining issue. Sample ten claims from each major cause before deciding, because one weak template can look like a coding problem. A useful comparison is whether denials cluster on one template or one provider. A cluster on a template points to setup, while a cluster on a provider points to workflow or training.
Does Mednex choose or replace my EHR?
No. Mednex does not select your EHR or promise it will fix your system. It can review how EHR and practice management data reach the claim, work claims and denials in the arrangement agreed with the practice, and recommend field or template changes. The access method, security terms, and reporting schedule are confirmed in writing before work begins. Mednex also cannot guarantee payment of any claim, since payers make coverage decisions. If you are considering a change of system, Mednex can describe what billing data and reports it would need from the new system, which gives you a concrete checklist for vendor conversations.
