Choosing a Dermatology EHR for a New Practice
Most EHR decisions are made under time pressure, with incomplete information, right before opening. Here is what actually matters — and what you can safely ignore until later.
Most dermatologists I talk to made their EHR decision in a hurry. They were three weeks from opening, someone recommended a system, and they signed up. Some of those decisions worked out. A lot of them didn't.
Choosing an EHR before you open is harder than it looks because you don't have patients yet, so you can't test the system against real visits. You're evaluating something abstract. And the vendors know that — which is why demos are polished and pricing conversations are vague.
This post is what I tell dermatologists before they sign anything.
Start with billing, not charting
The most common mistake I see is evaluating an EHR entirely on its charting interface. The note templates look clean, the body map is intuitive, and the demo flows smoothly. Then the practice opens, submits its first claims, and discovers that the clearinghouse connection wasn't configured, the fee schedule wasn't loaded, or the payer enrollment is still pending.
Charting is important. But charting doesn't get you paid. The billing infrastructure does.
Before you commit to any system, ask these questions:
- Who sets up the clearinghouse connection — you, a biller, or the vendor?
- How long does payer enrollment take, and who manages it?
- Is the fee schedule loaded before go-live, or do you build it yourself?
- What happens when a claim rejects — who works it?
If the vendor can't give you a clear answer to all four, that's a signal.
Dermatology-specific charting: what you actually need
Dermatology has a few charting requirements that general-purpose EHRs handle poorly. Here's what to look for:
Body mapping. You need to document lesion location, size, and morphology in a way that's reproducible across visits. A text field that says "left forearm" is not enough. A body diagram where you can mark and annotate a site is. This matters for tracking lesions over time and for pathology correlation.
Multi-problem notes. A dermatology visit often covers three or four separate problems — an acne follow-up, a new mole, a rash on the arm, and a cosmetic inquiry — all in one appointment. Your EHR needs to handle multi-problem documentation without forcing you into a single-problem template.
Cosmetic vs. medical separation. This is billing-critical. A cosmetic Botox injection and a medical visit for psoriasis are documented and billed completely differently. The EHR needs to support both workflows cleanly, and ideally flag which visit type applies so your biller doesn't have to sort it out manually.
Pathology tracking. If you're doing biopsies — and most dermatologists are — you need a way to track specimens from collection through result receipt and patient notification. Some EHRs handle this natively. Others require a workaround. Know which one you're getting.
A concrete example: the biopsy visit
Here's what a typical biopsy visit looks like in a well-configured dermatology EHR.
A patient presents with a suspicious lesion on the right shoulder. You document the site on the body map, note the morphology, and perform a shave biopsy. The EHR generates a pathology requisition with the specimen label, links the order to the encounter, and creates a pending result task. When the path report comes back, it attaches to the encounter and triggers a notification workflow — either a letter, a portal message, or a task for your MA to call the patient.
The billing side captures the biopsy CPT code, the diagnosis code from the path report, and the modifier if applicable. The claim goes out with the right documentation attached.
That's the workflow working correctly. If your EHR can't do most of that, you're going to be managing it manually — which means your MA is tracking specimens in a spreadsheet and your biller is chasing documentation.
Pricing: what to watch for
EHR pricing for small practices is genuinely confusing, and some vendors make it that way on purpose.
The most common traps:
Per-provider fees. A system that costs $300/month for one provider costs $900/month when you add two part-time associates. If you plan to grow, model the cost at your target size, not your opening size.
Per-claim or per-transaction fees. Some systems charge a percentage of collections or a flat fee per claim submitted. At 200 claims a month, a $0.50 per-claim fee is $100/month. At 500 claims, it's $250. These fees compound.
Module pricing. The base system is affordable. The e-prescribing module, the patient portal, the lab interface, and the clearinghouse connection are each separate line items. Get a quote that includes everything you'll actually use.
Implementation fees. Some vendors charge $2,000–$5,000 to set up the system. Others include it. Ask upfront.
A flat monthly rate that covers hosting, configuration, support, and clearinghouse access is easier to budget than a base fee plus a menu of add-ons. It's not always available, but it's worth asking for.
What a solo dermatologist needs from an EHR
A solo practice has no IT person and no spare front-desk time, so the EHR has to carry more of the load. Look for: a flat monthly price instead of per-claim or per-module fees; the vendor setting up the clearinghouse and claims for you; dermatology charting (body maps, biopsy tracking, procedure notes) that works without custom building; and a contract you can leave, with your data exported in a usable format. If a system needs a practice manager to run it, it's built for a bigger practice than yours.
The EHR decision checklist
Before you sign with any vendor, work through this list:
- Clearinghouse connection is included and will be configured before go-live
- Payer enrollment process is documented and someone owns it
- Fee schedule can be loaded before you see your first patient
- Body mapping is available for lesion documentation
- Multi-problem notes are supported in a single encounter
- Cosmetic and medical visit types are handled separately
- Pathology tracking is built in or clearly documented as a workaround
- Pricing is all-in — no per-claim fees, no hidden module costs
- Support is a real person, not a ticket queue
- You can export your data if you leave
If you can check every box, you're in good shape. If you can't, decide which gaps you can live with and which ones will cost you money.
What you can safely defer
Not everything needs to be perfect on day one.
Patient portal adoption takes months. You don't need a fully configured portal before you open — you need it working well enough that patients can receive messages and pay bills. The rest can come later.
Telehealth integration, advanced reporting, and custom dashboards are useful but not urgent. Get the core visit-to-payment workflow right first.
Cosmetic service menus and online booking for aesthetic visits can wait until you have a stable patient base and a clear sense of what services you're offering.
The honest version
I've set up EHR systems for a lot of practices, including several dermatology practices. The ones that had the smoothest openings all had one thing in common: they spent more time on billing setup than on charting configuration.
The charting is what you see in the demo. The billing infrastructure is what determines whether you get paid in 30 days or 90.
If you're evaluating systems right now, read what your dermatology practice needs to get paid before you make a decision. It covers the billing side in more detail — the clearinghouse, the payer enrollments, the fee schedule — and gives you a clearer picture of what has to be in place before you open.
You can also see how Tarevo's dermatology EHR handles this — body mapping, multi-problem notes, cosmetic vs. medical separation, and billing setup included before go-live. If you're comparing options, see Tarevo vs ModMed.
If you want to walk through your specific situation — what you're opening, what payers you're credentialing with, what your timeline looks like — book a free 30-minute strategy session. No sales pitch. Just a straight conversation about whether the setup makes sense for your practice.
Written by
Sherwin Gaddis
Sherwin Gaddis has spent more than a decade implementing, customizing, and supporting OpenEMR for independent practices, tribal health programs, and community health organizations. He founded Affordable Custom EHR to give small practices access to a fully configured, clinician-owned EHR without the enterprise price tag.
