Epic ships wound documentation tools inside its ambulatory and inpatient builds, but they’re built as flowsheets and wound care navigators, not a coding-aware system for CTPs, debridement, and LCD-driven medical necessity. If your program is charting skin substitute applications or complex debridement inside a general Epic build and wondering why denials keep landing on the same codes, the Epic wound care module is very likely the reason. This article breaks down what Epic’s native wound functionality covers, where it creates audit and revenue exposure for wound care programs, and how specialty wound care documentation software integrates with Epic through FHIR without forcing double entry.
What Does Epic’s Native Wound Care Documentation Include?
For many hospital systems and ambulatory practices, Epic’s wound care functionality lives inside Flowsheets or the LDA (Lines, Drains, Airways) navigator, sometimes supplemented by a wound care-specific SmartSet built by the local Epic team. These tools capture the basics: length, width, depth measurements, wound staging fields, drainage characteristics, and photo attachment tied to the encounter. For trending a wound’s progress visit over visit, that structure works reasonably well, and it gives clinicians a familiar place to document that mirrors how vitals and I/Os get charted elsewhere in the record.
Where it breaks down is specificity. Wound photos and measurements in a flowsheet are discrete data points, but they aren’t structured for the calculations that drive wound care billing and clinical decision-making. Epic’s flowsheet architecture wasn’t designed to calculate CTP application area against a documented wound size, track cumulative application counts across a treatment course, or apply Wagner or University of Texas staging logic to diabetic foot ulcers in a way that feeds directly into coding. A field for “wound depth in cm” is not the same as a field that maps depth and tissue plane to the correct debridement CPT code.
This is by design. Epic’s core flowsheet and navigator tools serve every specialty in the enterprise, from ICU wound rounding to post-op incision checks to ostomy care. They’re built for breadth, not for the LCD-specific documentation burden that governs skin substitute grafts, the CPT distinctions between excisional debridement by depth (11042 through 11047) and active wound care management (97597 and 97598), or the E/M complexity criteria unique to a wound care visit. A local build team can customize SmartSets to add wound-specific fields, and many hospital-based wound centers do exactly that, but the result is still a workaround layered onto a general-purpose EHR rather than a system built around wound care’s coding and compliance logic from the ground up. That gap is where the operational and revenue risk starts.
Where Does Epic Fall Short for CTP and E/M Documentation?
Skin substitute (CTP) documentation has requirements that a generic flowsheet doesn’t prompt for, and as of 2026, those requirements are a moving target. On December 24, 2025, CMS announced that the A/B MACs were withdrawing the Skin Substitute Grafts/CTP LCDs for diabetic foot ulcers and venous leg ulcers that had been scheduled to take effect January 1, 2026. Withdrawn, not delayed. Coverage reverted to legacy MAC policies, which means Novitas, First Coast, and CGS still have active skin substitute policies carrying application limits and conservative care requirements, while the remaining jurisdictions currently have no skin substitute LCD in force. Separately, the payment side did change on schedule: the CY 2026 Physician Fee Schedule and the companion OPPS rule reclassified most skin substitutes as incident-to supplies paid at a single rate of roughly $127 per square centimeter, effective January 1, 2026, in both the non-facility and hospital outpatient settings.
Neither change reduces the documentation burden. They relocate it. Per-square-centimeter wastage still has to be recorded and tied to the product lot applied, and under a flat per-square-centimeter payment the arithmetic linking wound size, product size, and units billed is now the single most scrutinized number on the claim. Application counts still need to be tracked across the treatment course wherever a legacy MAC policy caps them, and medical necessity for continued applications still has to be established in the note. Initiation of CTP therapy still requires proof of a failed conservative care period, along with wound measurements taken at that specific point in time. None of this is calculated or flagged automatically inside a standard Epic wound navigator. A clinician can type the wastage amount into a free-text note, but nothing in the build cross-checks it against the product size billed or the application area measured.
E/M level selection carries a similar gap. The level billed for a wound care visit depends on documented complexity: comorbidities factored into medical decision-making, wound characteristics that raise risk, and the data reviewed to support that level. Epic’s SmartPhrases can absolutely capture this information if a clinician types it in or pulls it from a macro, but the system itself doesn’t calculate the supported E/M level from what’s documented, and it won’t flag a note where the billed level exceeds what the narrative actually supports. That validation step is left entirely to the clinician or, more often, to a coder reconstructing the visit after the fact.
Debridement coding is arguably the most exposed area. Selecting between 11042 and 11047 depends on precise depth and tissue type language: subcutaneous tissue for 11042, muscle and fascia for 11043, bone for 11044, with 11045 through 11047 as the add-on codes for each additional 20 sq cm. And the threshold question comes before any of that, which is whether the service was excisional debridement at all or active wound care management, coded 97597 and 97598, a separate code family with its own documentation expectations. In a general note template built for any specialty, it’s easy for a clinician to write “debrided wound, removed necrotic tissue” without the depth, tissue-plane, and technique specificity a reviewer needs to support the code billed. That ambiguity is exactly what downcoding on review looks for, and it’s a direct consequence of documenting wound care work inside a template that wasn’t built to prompt for wound care specificity.
How Does This Gap Show Up in TPE Audits and Denials?
Targeted Probe and Educate reviews focused on skin substitute grafts and debridement consistently cite a narrow set of deficiencies: missing wound measurements at the time of service, absent language establishing that conservative care was tried and failed for the required duration, and staging that shifts inconsistently from visit to visit without clinical explanation. Trace any of those findings back far enough and they land on the same root cause: a documentation template that wasn’t built to require those specific fields before a note can be signed.
The downstream cost isn’t only the denial itself. When an ADR arrives, defending it means pulling the chart and finding every element tied to the CPT or HCPCS code billed. In a structured, wound-specific system, those elements live in discrete fields that can be pulled and organized quickly. In a general Epic build, the same information is often scattered across free-text progress notes, flowsheet rows from a different part of the encounter, and SmartPhrase blocks that vary by clinician. Reconstructing a defensible response takes longer, ties up clinical and billing staff, and increases the odds that something required simply wasn’t documented at all rather than just documented inconveniently.
The fix that costs nothing to start is a self-audit, and 2026 is the year to run one. Pull a sample of recent CTP charts and check them against the coverage policy that actually governs your jurisdiction today, which after the December 2025 withdrawal may be a legacy MAC policy or may be no skin substitute LCD at all. Verify that in the Medicare Coverage Database rather than working from a checklist built around the LCDs that never took effect, and note that the absence of an LCD is not the absence of a medical necessity standard. Then confirm that wound measurements at initiation, conservative care documentation, application counts, product lot, and wastage are all present and internally consistent across the treatment course, since the new flat per-square-centimeter payment makes unit and wastage math a direct audit target. Programs that run this exercise quarterly tend to catch template gaps before an ADR forces the issue, rather than after.
Can Wound Care Software Integrate with Epic Without Double Charting?
The interoperability path here isn’t hypothetical. ONC’s (now ASTP/ONC) 21st Century Cures Act rules pushed SMART on FHIR and standard HL7-based interfaces as the required mechanism for certified EHR data exchange, and Epic supports these standards for exactly this kind of use case. A specialty wound care system can pull demographics, allergies, active medications, and problem lists from Epic at the start of an encounter, and push the signed wound note back into the Epic chart as a document or as discrete structured data, depending on how the interface is configured. The hospital or practice record of truth stays current without a clinician re-typing information that already exists.
This is the model Intellicure’s wound care app for Epic and its mobile wound care EHR are built around: working alongside the EHR systems already in place, including Epic, rather than asking a program to replace its system of record. Wound-specific documentation, staging, CTP application logs with wastage and application counts tracked automatically, debridement detail tied to CPT selection, happens inside a workflow purpose-built for that documentation. The general medical record stays in Epic, where the rest of the care team expects to find it.
For mobile practitioners rounding across facilities, this matters most at the point of care. Bidirectional sync means a clinician isn’t pulling up Epic on one device to confirm a med list, then switching to a separate wound app to chart the visit, then circling back to Epic to enter a note summary. That re-keying of vitals, allergies, and medication lists that already live in the hospital record is where charting time disappears during bedside rounds, and it’s the first thing to eliminate when integrating a specialty system rather than running two disconnected ones side by side.
What Should a Wound Center Evaluate Before Building on Epic Alone?
Before deciding that a custom Epic build is sufficient, a wound center should test it against a short list of practical questions rather than assuming general EHR functionality will cover wound-specific needs.
- Automatic code suggestion: Does the current build suggest CPT/HCPCS codes based on documented wound characteristics, depth, and tissue type, or are coders reconstructing the code from narrative text after the visit is already signed?
- Supply and DME ordering: Is medical supply ordering, tied to application area, product lot, and wastage, triggered automatically from the chart, or is it a separate manual step that delays fulfillment and creates a gap between what’s documented and what’s actually billed?
- MIPS quality measure capture: Are wound healing quality measures captured as discrete, reportable data at the point of charting, or does someone have to manually abstract unstructured notes each MIPS reporting period to pull the numbers?
- Registry and benchmarking readiness: Can the data your program generates support qualified clinical data registry reporting or comparison against national wound healing benchmark rates, or does it stay locked in free text that can’t be aggregated?
- Audit defensibility: If a TPE ADR arrives tomorrow, can staff pull every required element for a billed CTP or debridement code from structured fields in minutes, or does it require a manual chart reconstruction?
If the honest answer to more than one of these is “manual workaround,” that’s the signal a general EHR build has reached its limit for wound-specific compliance and revenue needs, regardless of how well it serves the rest of the hospital or practice.
Closing the Gap Without Adding a Second Chart
Epic handles the general medical record well: allergies, medication reconciliation, cross-specialty visibility, the hospital-wide record every department needs to see. It was never built to carry the coding-specific logic that skin substitute grafts, debridement selection, and wound care E/M documentation require, and asking a general flowsheet to do that job is where compliance exposure and denied claims tend to originate. In a year when coverage policy has been withdrawn and payment methodology rebuilt, that exposure is larger, not smaller. The practical fix isn’t replacing Epic. It’s pairing it with a specialty wound care EHR or SMART app that syncs through FHIR, so wound-specific documentation happens in a system built for it while the hospital record stays current automatically. Schedule a live demonstration of Intellicure to see how it works in your build.
