Antimicrobial stewardship EHR reporting that holds up
Nobody argues about antimicrobial stewardship any more. The argument is about where the numbers come from, and it is usually settled by whoever is willing to export a spreadsheet every month.
Antimicrobial stewardship EHR reporting means getting antimicrobial use and resistance data out of the record and into NHSN in a standard format, automatically. The clinical programme is well defined. What stops most organisations is that the data sits across pharmacy, lab and ADT systems that were never asked to agree.
Stewardship has a clear playbook and a messy data supply.
CDC sets out seven core elements for a hospital programme — leadership commitment, accountability, pharmacy expertise, action, tracking, reporting and education — and the tracking element asks organisations to “monitor antibiotic prescribing, impact of interventions, and other important outcomes, like C. difficile infections and resistance patterns.” None of that is contentious. All of it assumes you can get the numbers.
In practice the numbers live in three places that do not naturally speak to each other: the pharmacy system knows what was dispensed, the electronic medication administration record knows what was given, and the laboratory system knows what grew and what it was sensitive to. Stewardship reporting is the work of making those three agree about the same patient on the same day.
The AUR module and what NHSN actually wants
Antimicrobial use and resistance reporting goes to CDC’s National Healthcare Safety Network through its AUR module, and it is not a spreadsheet upload. It expects a structured electronic submission generated from your systems.
The standard is specific, and specifically dated. ONC lists the named implementation guide for reporting antimicrobial use and resistance to public health agencies as the HL7 CDA Release 2 Healthcare Associated Infection Reports guide, and adds a warning worth reading twice: “While there are more current releases of the Healthcare Associated Infection Reports IG, they are not valid for AU or AR submissions to NHSN.” Newer is not better here. Newer is rejected.
That single sentence explains a category of stalled projects. A vendor upgrades to the current release of a guide, the submission stops validating, and the failure surfaces months later as a gap in the data rather than as an error anybody saw.
The condition of participation, read properly
Hospitals have a regulatory obligation here, and it is more specific than most summaries suggest. The Medicare condition of participation requires an antibiotic stewardship programme that demonstrates “coordination among all components of the hospital responsible for antibiotic use and resistance,” and that the hospital document the evidence-based use of antibiotics in all departments and services and document improvements, including sustained improvements, in proper antibiotic use.
Two words in that do real work. “All” means the programme cannot be a medicine-floor exercise. “Sustained” means a single good quarter is not the evidence being asked for. Both are documentation requirements before they are clinical ones, and both are answered by a reporting pipeline rather than by a policy.
- The regulation asks you to document improvement over time across every service. That is a longitudinal, organisation-wide dataset. You cannot produce it retrospectively from a programme that was tracking in a spreadsheet.
Days of therapy, not prescriptions counted
The measure that matters is exposure, not orders. Days of therapy counts each antimicrobial a patient receives on each day, so a patient on two agents for three days contributes six. It is normalised against patient days to make wards and months comparable.
This is where the eMAR earns its place. An order that was written and never given is not therapy, and a system counting orders will overstate use in exactly the units the committee is trying to reduce. If your data comes from pharmacy dispensing rather than administration, say so on the report, because the two are not interchangeable and the difference is not constant.
Practices moving from manual counting to an automated feed should expect the numbers to move, sometimes substantially. That is not the new system being wrong. It is usually the first time anyone measured the denominator consistently.
Your antibiogram is a data-quality report
A cumulative antibiogram summarises which organisms were isolated and what they were susceptible to. Clinicians read it to choose empiric therapy, which makes it the most consequential report the laboratory produces.
It is also the most revealing test of your data. Duplicate isolates from the same patient inflate resistance. Missing organism identifiers break the grouping. Surveillance cultures mixed in with clinical ones change the picture. If the antibiogram looks implausible to the infectious disease physicians, the fault is almost always upstream of the report, and finding it is the same work as preparing to submit AR data.
Treat building the antibiogram as the pilot for the submission rather than as a separate task. Where several source systems have to be reconciled, a dedicated interface layer gives you one place to fix a mapping instead of three.
Not sure whether your AUR submission is actually landing?
We check what your systems send, what NHSN returns, and where the feed is failing quietly, then hand you written findings.
Getting prescribing data out without a project
Not every organisation is a hospital submitting to NHSN, and an outpatient infectious disease practice still needs to see its own prescribing data. The useful starting point is smaller than people expect: antimicrobial orders by clinician, by agent, by indication where it is recorded, over a rolling quarter.
That report exists in every certified system. What stops it being useful is usually that indication is captured as free text, so the most interesting cut is unavailable. Fixing that is a template change rather than an integration, and it is worth doing before anything more ambitious — usually alongside rebuilding the ordering workflow around it.
- Start with the acknowledgement. If you already submit, check that NHSN is accepting it. Silence is not success.
- Pin the implementation guide version. Write down which release you validate against and who is told before it changes.
- Count administrations, not orders. Or state clearly that you are not.
- Build the antibiogram first. It surfaces the same data faults at a fraction of the effort.
Qventive provides antimicrobial stewardship EHR reporting services in Hackensack NJ and across the surrounding counties, usually as part of our infectious disease EHR and IT support and a broader infectious disease practice management engagement. Because these feeds move identifiable clinical data between systems and out to a public health agency, the design belongs in your HIPAA risk analysis alongside the clinical plan.
Stewardship reporting: common questions
Do we have to submit AUR data, or is it optional?
How long does an AUR submission take to stand up?
What are the HIPAA implications of public health surveillance reporting?
Can an outpatient practice do meaningful stewardship without NHSN?
What happens when the implementation guide version changes?
Let’s meet
Qventive works with infectious disease programmes across New Jersey on surveillance feeds, antibiogram data quality and reporting. Thirty years healthcare-exclusive, from our office in Hackensack.
- Seven core elements of hospital antibiotic stewardship, including the tracking element. cdc.gov
- Condition of participation requiring coordination, documentation of evidence-based antibiotic use in all departments, and sustained improvement. ecfr.gov
- Named HL7 CDA implementation guide for AU and AR reporting, and the warning that newer releases are not valid. isp.healthit.gov