WiSeR Model Wound Care: How the CMS Registry Affects Your Practice
The CMS WiSeR registry's operational impact on wound care practices — data submission requirements, MAC participation, workflow changes, and what to prepare for.
Damon Ebanks
Medipyxis
WiSeR Is a Workflow Change, Not Just a Policy Change
If you are looking for a general overview of what the WiSeR model is, see our WiSeR explainer FAQ. This post covers the operational side -- what your practice needs to change in its daily workflow to comply with WiSeR data submission requirements and how to prepare before the registry reaches your MAC jurisdiction.
WiSeR adds structured data submission obligations before and after every skin substitute application. For practices that currently document in free-text clinical narratives, the transition requires changes to EMR templates, clinical workflows, and staff training. The practices that prepare before WiSeR reaches their jurisdiction avoid the compliance scramble.
What Data You Need to Submit
WiSeR requires two categories of structured data for each skin substitute application.
Pre-application submission (before applying the product):
- Wound etiology classified by CMS-defined categories (diabetic foot ulcer, venous leg ulcer, pressure injury, etc.) -- not free-text descriptions
- Wound dimensions in centimeters (length, width, depth) using consistent measurement methodology
- Wound duration -- how long the wound has been present, documented with dates
- Wound bed tissue type percentages (granulation, slough, necrotic, epithelial)
- Conservative treatment history with specific treatments attempted, durations, and documented failure to progress
- Product identification -- the specific CTP/skin substitute product being applied, identified by HCPCS Q-code and manufacturer product name
Post-application outcome reporting (at defined follow-up intervals):
- Wound measurements at each follow-up visit
- Percentage of wound size reduction from baseline
- Wound bed status changes
- Whether additional applications were performed and the clinical rationale
- Adverse events, including graft failure, infection, or wound deterioration
The critical distinction from standard LCD documentation: WiSeR requires these elements as structured data fields with defined value sets, not as free-text embedded in a clinical note. A narrative that says "the wound has failed to respond to four weeks of moist wound therapy" satisfies an LCD auditor but does not satisfy WiSeR's structured submission format.
How It Changes Your Documentation Workflow
WiSeR inserts a mandatory step between clinical assessment and product application. Before the provider applies a skin substitute, the pre-application data must be submitted to the registry. This changes the visit workflow in three ways.
Template restructuring. EMR visit templates need discrete, structured fields for every WiSeR data element. Free-text wound assessment sections must be supplemented with -- or replaced by -- structured dropdowns, numeric fields, and coded value sets. If your EMR captures wound size as part of a narrative note rather than as discrete length/width/depth fields, the data cannot be extracted for WiSeR submission without manual re-entry.
Pre-application checkpoint. Clinicians need a workflow step confirming the registry submission is complete before proceeding with application. This is analogous to a prior authorization checkpoint but is data submission rather than approval. The submission itself is not a gate -- CMS does not approve or deny based on the pre-application data -- but failure to submit is a compliance gap.
Outcome tracking discipline. Post-application outcome data requires wound measurements at defined intervals tied to the original application. Practices need to track which wounds have pending outcome submissions and ensure follow-up visits capture the required data points. Missing outcome submissions create incomplete registry records.
Timeline for Expansion to Additional MACs
WiSeR launched as a regional pilot under Palmetto GBA and Novitas Solutions, covering jurisdictions across the Southeast, Mid-Atlantic, and parts of the Midwest. CMS has signaled intent to expand the program to additional MAC jurisdictions, though specific timelines depend on pilot program data analysis and future rulemaking.
What expansion looks like: CMS announces additional MAC participation through the Federal Register and MAC provider communications. There is typically a lead time between announcement and enforcement, but the lead time may be shorter for later phases since the registry infrastructure is already operational.
How to monitor: Watch your MAC's provider bulletin portal and CMS MLN Matters articles. If your MAC is not currently participating, you have a preparation window -- but it is not indefinite.
How to Prepare Before WiSeR Reaches Your Jurisdiction
Practices outside current WiSeR jurisdictions have an advantage: time to prepare without compliance pressure. Use it.
Audit your EMR templates for structured data gaps. Walk through a skin substitute visit and identify every WiSeR data element. For each one, determine whether your EMR captures it as a discrete, extractable field or buries it in free-text. The gap list is your remediation checklist.
Standardize wound measurement methodology. WiSeR requires consistent, reproducible measurements. If different clinicians measure wounds differently -- or if measurements are estimated rather than taken with a ruler -- outcome tracking data will be unreliable. Standardize on a measurement protocol now.
Build conservative treatment documentation into every wound episode. WiSeR requires documented conservative treatment history before the first application. If your current workflow does not systematically document conservative therapy attempts with dates and outcomes, start capturing this for every chronic wound -- even wounds that may never receive a skin substitute.
Track skin substitute applications by wound episode. WiSeR ties pre-application submissions and outcome reports to specific wound episodes. Practices need to be able to identify which wound received which product on which date and what the outcome was at defined follow-up intervals. If your current tracking is per-visit rather than per-wound-episode, restructure it.
For how WiSeR relates to existing LCD coverage requirements, see our LCD compliance guide. For practices already in WiSeR jurisdictions dealing with the intersection of WiSeR and audit exposure, see the WiSeR explainer for specifics on which MACs currently participate.