Mobile wound care practices and hospital-based wound centers rarely lose CTP and E/M reimbursement because of bad clinical care. They lose it because the same encounter gets documented three different ways across a hospital outpatient EHR, a SNF’s PointClickCare instance, and a provider’s own notes on a phone between stops. EHR documentation alignment for wound practices closes that gap by forcing one standard of wound-specific data into every facility record, regardless of which native EHR sits underneath it. Following this process gives your practice a documentation workflow that survives payer audits, particularly Targeted Probe and Educate review, and eliminates the double entry that quietly costs providers charting time every day. Before starting, pull six months of denied claims and a sample of recent CTP/skin substitute notes. You’ll need both to see where your current documentation actually breaks down, rather than where you assume it does.
One note: mobile wound care practices and hospital-based wound centers using Intellicure already enjoy all of the important strategies mentioned below, and to our knowledge, only Intellicure does this in wound care.
Step 1: Audit Current Documentation Gaps Across Facility EHRs
Start with a structured sample, not a general impression. Pull 20 to 30 charts from each facility type you round in: hospital outpatient, SNF, home health. For each chart, compare the wound measurement fields, staging or classification language, and photo documentation against the coverage and documentation requirements that actually apply in your MAC jurisdiction. Not every MAC publishes an LCD for every wound care service, so part of this audit is establishing what your jurisdiction actually requires versus what it leaves to a general “reasonable and necessary” standard. You’re looking for where the native EHR’s generic wound module diverges from what a reviewer actually needs to see. Of course, if you use a regulatory-minded, wound care specific EMR like Intellicure, your documentation likely already meets your MAC requirements if you followed Intellicure’s charting process.
Pay particular attention to terminology drift. Generic EHRs frequently allow providers to document “debridement” as a single free-text entry without capturing the depth of tissue removed, the tissue type, the instrument used, and the surface area treated, the specific elements that determine which code is correct. A note that says “wound debrided” supports nothing on its own. This is something Intellicure presses. The distinction matters because the code families are built on depth: CPT 97597/97598 describe selective debridement of devitalized epidermis and dermis, billed by total wound surface area, while 11042 and the codes above it describe debridement to subcutaneous tissue, muscle and fascia, or bone. A note documenting selective sharp debridement of devitalized epidermis and dermis with scissors, 12 sq cm, supports one code. A note documenting sharp debridement of nonviable tissue down to and including subcutaneous tissue supports a different one. Flag every instance where the chart language and the billed code don’t clearly connect, a pattern covered in detail in our guide to debridement audit documentation requirements, and one that Medicare contractors have scrutinized for years, as the Novitas debridement policy discussion in this real-world data series illustrates.
Then identify which facilities are forcing double entry. This happens whenever the native EHR has no wound-specific template (or a slow workflow for one), so providers chart once in the facility system to satisfy that record, and again in a separate wound app or paper note to capture the clinical detail payers require. Double entry is one of the top drivers of missed CTP documentation: providers under time pressure will complete the facility’s required fields and skip the supplemental wound-specific ones, especially application counts and conservative-care duration, because nothing in the facility EHR forces them to. This is where Intellicure’s integrations with generic EHRs are so important.
Close the audit by writing down your baseline numbers, because you will need the same figures again in Step 6 and Step 7. Capture four things: denial rate by facility and by provider, your top three denial reasons from the six months of denied claims you pulled, CTP documentation completeness (the percentage of applications with conservative-care duration, application count tracking, and photo/measurement trend all present), and a score for each facility on measurement field completeness, staging or classification specificity, and photo documentation consistency. That set of numbers is your before picture.
Step 2: Standardize Wound-Specific Data Elements Into One Template Set
Once you know where the gaps are, lock down a single set of required fields that travels with the provider regardless of facility: wound dimensions (length, width, depth), tissue type percentages, exudate amount and character, periwound condition, and etiology-specific measures, ABI or toe pressures for VLU, monofilament testing and vascular status for DFU. These aren’t optional fields to fill in when convenient. They’re the minimum data set outlined across our wound care documentation requirements series that supports both clinical decision-making and coding defense.
Build the classification fields correctly while you’re at it, because this is a common source of chart language that can’t be defended. Staging in the formal sense applies to pressure injuries, using the NPIAP staging system. Diabetic foot ulcers are classified with a system such as Wagner or the University of Texas classification, and venous leg ulcers are described by CEAP class, not staged. A template that offers “stage” as a universal dropdown for every wound type teaches providers to document something that doesn’t exist, and a reviewer will notice.
Build this template once, in a wound-specific EHR or mobile charting app, and reuse it identically across every facility you serve. Resist the temptation to customize the template per site to match each facility’s native workflow. The entire point of standardization is that the provider charts the same way at bedside in a SNF as they do in a hospital outpatient wound center, so the data structure never depends on which building they’re in.
The most common failure at this step is letting individual providers free-text tissue description or wound classification “in their own words.” It feels efficient in the moment, but produces charting that’s impossible to audit consistently across a multi-provider group. One provider’s “mostly granulation” is another’s “70% granulation, 30% slough,” and a TPE reviewer has no way to reconcile the two. Structured fields with defined options, dropdowns, or required numeric entry remove that variance. Again, Intellicure’s method is the way to go here. If a provider needs narrative space for clinical nuance, give them a comment field in addition to the structured fields, not instead of them.
Step 3: Map Each Documentation Field to E/M and HCPCS Coding Support
With standardized fields in place, cross-reference each one against the coding it’s meant to support. For E/M levels, that means building the template around how E/M is actually leveled now. Since January 1, 2021, for office and outpatient visits, and since January 1, 2023, for the other E/M families including nursing facility and home or residence services, the level is selected on medical decision-making or total time on the date of the encounter. History and exam are still performed and documented as medically appropriate, but they no longer determine the level. If your template captures wound measurements and treatment plan changes, but nothing reflecting the number and complexity of problems addressed, the data reviewed and analyzed, and the risk of the management selected, you’re leaving E/M level support on the table even when the clinical work justified a higher level. A template that still leans on history and exam bullets is documenting to a standard that was retired years ago, and payers are already using automated review to downcode notes that don’t support the level, as this look at automated E/M downcoding shows.
CTP and skin substitute documentation needs the same treatment, field by field, but the coverage landscape changed at the end of 2025 and your template should reflect the current reality rather than the one most practices prepared for. Intellicure’s CTP Audit Defender does this for you. The unified skin substitute LCDs that all seven A/B MACs had finalized for a January 1, 2026 effective date were withdrawn on December 24, 2025, which means there is currently no national covered or non-covered product list. Coverage reverted to legacy policy: Novitas, First Coast, and CGS still have active skin substitute policies, while Palmetto, NGS, WPS, and Noridian have none, and in those jurisdictions medical necessity is judged case by case against the general reasonable-and-necessary standard. What did not change is payment: as of January 1, 2026, skin substitutes are paid as incident-to supplies at a flat national rate of roughly ~$127 per square centimeter rather than under ASP. Before locking any number into your template, confirm the current conservative-care duration and application limits against your own MAC’s published policy, and if your MAC has no policy, build the template to document medical necessity on its own terms.
Your template’s application note should force entry of the conservative-care start date, the therapies tried, the wound’s failure to progress, and the current application count, every time, whether or not an LCD is imposing a specific cap on you. The absence of an LCD is not the absence of audit risk. Payment at a fixed rate with no coverage list means documentation is now the main thing standing between the practice and a recoupment.
Build a coding cross-check into the note before it’s signed, not after the claim is submitted. This can be as simple as a required checklist the provider reviews before finalizing: does the note support the E/M level selected, does the CTP application note include conservative-care duration and application count, is the medical necessity language present and specific. Catching a gap at the point of signature costs a provider thirty seconds. Catching it after a denial costs the practice an appeal, and possibly a pattern flag in a future TPE cycle, one reason many practices review our breakdown of the most common wound care claim denial triggers before finalizing a template.
Step 4: Build an LCD-Compliant CTP and Skin Substitute Workflow
CTP denials cluster around a small number of predictable failures: no documented conservative therapy duration, no clear application count tracking, and missing photo or measurement trend evidence. Build the workflow so none of those failures are possible by the time a claim goes out, a challenge our series on skin substitute LCD documentation details covers extensively.
Require documentation of the conservative therapy timeline before a CTP order can be placed at all. That means the chart must show the wound duration, the specific conservative treatments attempted (compression, offloading, standard dressings) and their dates, and confirmation that the wound has failed to progress as expected under that care. Where an active LCD applies, match that timeline against the policy’s threshold. Application counts need the same rigor: if your MAC’s policy caps coverage at a defined number of applications for a given product and indication, your workflow should flag the count at each subsequent application rather than rely on a provider remembering how many times they’ve already billed for that wound. In jurisdictions with no active policy, track the count anyway. It is the single fastest thing for a reviewer to question and the hardest to reconstruct after the fact.
Remember that Intellicure’s CTP Audit Defender makes documenting skin subs fast and easy, ensuring you won’t have a MAC/LCD problem later.
Attach photo documentation and a measurement trend line to every application. A single photo at the time of the initial evaluation isn’t sufficient for retrospective medical necessity review; reviewers want to see progression (or lack of it) across the treatment course, tied to the same standardized measurement fields from Step 2. This is also where structured wound care data pays off beyond the individual claim: consistent measurement and photo capture across a caseload gives your practice a defensible record of real-world healing rates instead of a set of disconnected images. That matters more under flat-rate payment than it did under ASP, because product selection now has to be defended on outcomes rather than on price.
Finally, automate the connection between the chart and the supply order, like Intellicure does with its OrderTrak module inside IntellicureEHR. If the CTP order can be placed through your medical supply ordering workflow before the required documentation fields (conservative care duration, wound measurements, application count) are complete, providers and staff will find that path under time pressure. Configure the order trigger to require those fields first, a gap addressed directly in our guide to medical supply ordering delays in wound care. This single control eliminates a large share of the CTP documentation gaps most practices carry, because it removes the option to order before the chart supports the order.
Step 5: Connect Mobile and Bedside Charting to the Facility EHR via FHIR/SMART
Standardized templates only solve half the problem if the data still lives in a silo separate from the facility’s system of record. Use FHIR and SMART-on-FHIR interfaces to push wound-specific charting directly into the facility’s native EHR, whether that’s a hospital’s inpatient/outpatient system or a SNF’s PointClickCare instance, so the provider charts once and the data lands everywhere it needs to, an approach detailed in our wound care EHR integration best practices guide.
The integration only counts if it moves structured data, not a flattened PDF. A PDF attachment satisfies a record-keeping requirement but does nothing for quality reporting, because quality measures pull from discrete, structured fields, not from an embedded document a downstream system can’t parse. That matters for your own clinicians first: MIPS is a clinician-level program, and the wound care quality measures developed by the US Wound Registry are QCDR measures that practitioners report through the registry, as described in this announcement that CMS approved another year of USWR measures. Facilities report under their own programs, such as the SNF Quality Reporting Program, and they draw on the same discrete fields. Before you consider the integration live, confirm specifically that wound dimensions, classification, and treatment codes sync as structured values the facility EHR can query and report on, not as an image or a note field dump.
Test this with a real encounter before go-live, not a demo record. Chart an actual visit through your wound-specific app or mobile EHR, push it through the FHIR interface, and then open the record in the facility’s native system to confirm every field landed where it should. The most common failure point at this stage is measurement data arriving as unstructured text buried in a notes field, technically present, functionally invisible to any reporting query. If that happens, it defeats the entire purpose of the integration: the facility’s quality team and your billing team are both still working from disconnected data, just with an extra sync step in between. Fix the field mapping before you roll the connection out to a full caseload, and re-test any time the facility upgrades its own EHR version, since those upgrades routinely break existing FHIR mappings without warning.
Step 6: Build an Audit-Defense Checklist for TPE Readiness
Targeted Probe and Educate reviews are aimed at providers and items with high claim error rates or billing patterns that differ significantly from peers, and each round looks at a small sample of claims, with education after each round and up to three rounds before a provider may be referred to CMS for further action. Reviewers evaluate that documentation against the same coverage criteria you’ve already built into your workflow. Turn that into a pre-submission checklist covering medical necessity language, physician signature and date, and the coverage-specific elements tied to your top three denial reasons from the Step 1 audit, a process our team walks through in this podcast on getting a wound clinic through an audit, and one Dr. Helen Gelly has written about directly in her guest post on TPE strategy. If your denial history shows conservative-care duration as a recurring failure point, that item goes at the top of the checklist, not buried in a generic compliance form.
Run internal spot audits quarterly using the exact criteria a TPE reviewer would apply: pull a sample of recent claims, check them against the checklist blind to who the treating provider was, and score them the way CMS’s review contractors would. This is more useful than an annual full-scale audit because it catches drift while it’s still a training issue rather than a billing pattern serious enough to trigger an actual TPE referral, since as we’ve discussed before, Medicare auditors are not wound care specialists and rely heavily on documentation clarity. Confirm your review criteria against CMS’s current published TPE guidance periodically, since the process and its documentation expectations get refined over time.
When a provider gets flagged twice on the same issue, whether that’s incomplete CTP application counts or missing conservative-care documentation, keep a documented corrective-action trail: what was flagged, what training or template change was made, and what the follow-up audit showed. TPE reviewers and, more broadly, any payer audit look for evidence of pattern remediation. A single correction with no record of follow-through reads as an unresolved pattern, even if the provider genuinely improved. The paper trail matters as much as the fix itself.
Step 7: Train Staff and Monitor Compliance Metrics Ongoing
Roll the standardized template out with training built from your own denial audit, not a generic vendor slide deck. Show providers the actual chart excerpts that triggered denials in your practice, alongside the corrected version using the new template fields. Providers retain “this is the note that got denied and here’s why” far better than an abstract policy statement about documentation standards, which is why watching real case discussion, like this session on trends in wound care audits and denials, resonates more than a slide deck.
After go-live, track three leading indicators monthly rather than waiting for the next denial report to surface a problem: denial rate by facility and by provider, average time-to-chart per encounter, and CTP documentation completeness (what percentage of applications have full conservative-care duration, count tracking, and photo/measurement trend attached). A rising time-to-chart number alongside a falling completeness rate usually means the template is fighting the workflow at a specific facility, and that’s worth investigating before it shows up as a denial three months later, a dynamic also explored in our piece on how small documentation details impact wound care revenue.
Re-audit the full chart sample every quarter, not just the monthly metrics. New hires won’t know the standardized workflow unless they’re trained into it directly, facility EHR upgrades can silently break your FHIR field mappings from Step 5, and coverage policy can shift underneath you, as the withdrawal of the skin substitute LCDs demonstrated on a week’s notice. A template that was defensible in Q1 may not be by Q3. Quarterly re-audits catch all three sources of drift before they accumulate into a denial pattern significant enough to draw payer attention.
Ninety days after rollout, pull the same baseline numbers you recorded in Step 1: denial rate by facility and provider, CTP documentation completeness, and your facility scores for measurement completeness, classification specificity, and photo consistency, measured the same way, across the same facility types. If they’ve moved in the right direction, the alignment is holding and you have a template set worth defending as your standard. If a metric hasn’t moved, go back to the facility where the gap persists before assuming the whole program failed; misalignment is usually isolated to one EHR integration or one provider’s workflow, not the entire rollout. Once the 90-day check confirms the template set is working, extend it to any new facility before a single provider charts there, rather than letting a new site revert to whatever documentation habits its native EHR encourages by default.
It’s important to note that by using Intellicure and its suite of tools and integrations, you’ll accomplish everything mentioned above for aligning EHR documentation across multiple wound centers, or across multiple mobile wound care practices.
