Dermatology billing software is judged on a claim that carries more procedures per visit than most specialties: a biopsy, a destruction, an excision with a repair, each with its own code, its modifier when two are done at one visit, and the payer's bundling edit waiting for the pair. Add the pathology claim from the lab and the cosmetic services the payer will not touch, and a small dermatology office needs billing that scrubs the claim before it goes rather than a denial queue that explains it afterwards. This page sets out what the software has to carry for a dermatology practice, where its claims fail, and what the practice keeps beside the software.
What the software has to carry for a dermatology claim
Multiple procedure lines per visit with the units and the modifiers that distinguish separate sites and separate procedures; the diagnosis pointers per line, because a destruction of a benign lesion and a biopsy of a suspicious one are paid on different diagnoses; the place of service; and the pathology claim, whether the practice bills it or the lab does. The claim goes out on the 837 or the CMS-1500 with every one of those fields read by the payer's edits, and the CMS guidance on the form is the field list.
Where dermatology claims fail: bundling and the missing modifier
The payer's procedure-to-procedure edits, Medicare's National Correct Coding Initiative among them, say which code pairs are not paid together on the same day without a modifier, and which never are. A biopsy and an excision on separate sites without the modifier come back as CO 234 or CO 97; with the modifier and the note that supports it, they are paid. Software that scrubs the claim against the edits before submission prevents the denial; software without it produces a corrected claim a month later.
The cosmetic line and the patient's share
A dermatology practice bills services the payer will not cover, and the claim has to show them correctly: as non-covered, with the patient having agreed in advance to pay, so the CO 96 or PR 96 that comes back is expected rather than a surprise. The EOB reconciliation worksheet on this site works one covered line's posting; the cosmetic line is posted as the patient's charge from the start, and the software has to keep the two apart on the statement.
What the practice keeps beside the software
The claims register: every visit's claim with its lines, its modifiers, the posted EOB per line, the bundling denial and the corrected claim, the pathology claim linked to the visit, and the patient's balance across covered and cosmetic lines. Eobify Pro keeps that register in a form the practice owns; the billing software carries the claim to the payer and reports what came back.
Questions people ask about dermatology billing software
What is the most common denial in dermatology billing?
Bundling: two procedures on one visit that the payer's edits treat as one, returned as CO 234 or CO 97. The fix is the modifier the edit allows, with the note that shows the procedures were distinct.
Does dermatology billing software need to handle pathology claims?
If the practice bills the pathology itself, yes, as a separate claim linked to the visit. If the lab bills it, the software needs the link so the visit's record is complete.
How should cosmetic services appear on a dermatology claim?
As non-covered lines the patient agreed in advance to pay, kept apart from the covered lines on the claim and the statement, so the non-covered denial that comes back is expected.
Where are the bundling edits published?
For Medicare, in the NCCI procedure-to-procedure edit files CMS publishes, with the modifier indicator per pair. Commercial payers publish their own on the provider portal.