Antimicrobial stewardship software requirements and an RFP checklist for hospital pharmacy teams
A requirements list for a stewardship software RFP, split into must-have, nice-to-have and items you can buy separately, with the contract questions most teams forget.
9 min read
Antimicrobial stewardship software requirements fall into four groups: data feeds from the laboratory, pharmacy and ADT systems, the work the pharmacist does on top of them (alerts, review lists, interventions), reporting for NHSN and accreditors, and the contract terms around interfaces and price. Write the RFP around those four groups and score every vendor on the same grid, because the demos will otherwise be scored on how good the screens look.
This checklist is for the pharmacy director, stewardship lead or IT analyst who has been told to "get a quote" and needs a document to send. It is vendor neutral where the requirement is generic, and it marks the one report, the cumulative antibiogram, that does not need a platform at all.
What should an antimicrobial stewardship software RFP include?
An RFP should state the hospital profile (beds, EHR, laboratory system, current stewardship staffing), a numbered requirement list with a must-have or nice-to-have flag on each line, the reporting obligations, the interfaces you expect the vendor to build, and the pricing format you want back. Asking for itemized pricing by module, implementation and support is the single change that makes quotes comparable.
- Hospital profile: licensed beds, EHR and version, LIS and microbiology instrument, pharmacy system, ADT source
- Program profile: FTE of pharmacist and physician time, existing committee, current review method
- Requirement list with must-have and nice-to-have flags, answered yes, no or roadmap
- Reporting duties: NHSN AUR, accreditation, state reporting
- Pricing in a fixed format: implementation, annual subscription, each module, each interface, support tier
- Contract terms: term, auto-renewal date, cap on annual increases, data return on exit
Data feed requirements
Everything a stewardship tool shows is only as good as its feeds, so list them first. At minimum the platform needs microbiology results with susceptibility interpretations, active antimicrobial orders and administrations, and patient location and demographics. Ask which of these arrive in real time and which arrive in a nightly batch, because an alert built on a nightly batch is a report, not an alert.
| Feed | Why it is required | What to ask the vendor |
|---|---|---|
| Microbiology results with MIC or zone and interpretation | Bug-drug mismatch, antibiogram, resistance trends | Is the interpretation taken from the lab or recalculated, and against which CLSI edition |
| Antimicrobial orders and administrations (MAR) | Days of therapy, time-out review, IV to oral lists | Order feed or administration feed, and how fast |
| ADT and location | Unit-level rates, ICU versus ward split | Does location history follow the patient between units |
| Diagnosis or indication | Indication-based review, syndromic antibiogram | Coded field, free text, or not captured |
| Labs: creatinine, vancomycin levels | Renal dosing and vancomycin review lists | Which values and how often |
Stewardship workflow requirements
The CDC lists action as one of the seven core elements of a hospital antibiotic stewardship program, and the software question is whether it makes the daily review faster. Test that with your own data. Give each vendor the same week of cultures and ask them to show the pharmacist review list for one morning.
- A prioritized review list with the reason each patient is on it
- Bug-drug mismatch alerts that can be filtered by organism, drug and unit
- Prospective audit and feedback documentation with a record of who changed what
- Intervention tracking that can be exported, so the committee sees acceptance rates
- Time-out prompts at 48 to 72 hours with the culture result attached
- Alert suppression rules you can edit without a vendor ticket
Reporting requirements: NHSN AUR and accreditation
The CDC NHSN Antimicrobial Use and Resistance (AUR) Module takes monthly antimicrobial use and resistance data from facilities, and the vendor has to say whether it generates the files or only supplies the data for your EHR to generate. Those are different products. Our guide to NHSN AUR reporting software covers who does what.
For accreditation, ask the vendor to show the report you would hand a surveyor. The Joint Commission stewardship standard and the CDC core elements both expect that you can show tracking, reporting and action. A dashboard that cannot be printed or exported for a committee does not meet that need, however good it looks. The Joint Commission stewardship requirements page maps the elements to documents.
Integration requirements
Interfaces are where projects slip, so put them in the RFP as named deliverables. Ask who builds each one, who tests it, who pays for the interface engine time on your side, and what happens to the price if your EHR is upgraded. A vendor that lists implementation as one line with no interface detail is leaving the hardest part to your IT team.
- Standards supported: HL7 v2 ORU and ADT feeds, FHIR where your EHR exposes it
- Who maintains the interface after go-live and the response time for a broken feed
- Test environment for the lab and pharmacy feeds before production
- Single sign-on and role-based access for pharmacists, physicians and infection preventionists
Which requirements you can buy separately
The cumulative antibiogram is the one report on this list that needs no live feed. It is built once a year or once a quarter from a laboratory export, and CLSI M39 sets the rules: first isolate per patient per species per period, and a minimum of 30 isolates before a percentage is reported. Hospitals that split it out of the platform contract often find the platform quote drops and the antibiogram gets better rules. Antimicrobe builds it from a lab CSV and is priced from $249 a month on the pricing page. Platform vendors compared on this point are in best antimicrobial stewardship software for community hospitals.
A scoring grid for the vendor demos
Weight the grid before the first demo and do not change it afterward. A simple 0 to 3 score on each line, multiplied by a weight of 1 to 3, is enough. The weights below are a starting point for a community hospital with one stewardship pharmacist.
| Criterion | Weight | Score 0 means | Score 3 means |
|---|---|---|---|
| Live microbiology and MAR feeds | 3 | Nightly batch only | Real time, tested on your data |
| Daily review list quality | 3 | Raw alert list, no priority | Ranked with reasons, filterable |
| NHSN AUR support | 2 | Not supported | Files generated and submitted |
| Antibiogram rules (CLSI M39) | 2 | No first-isolate rule | Rules printed on the report |
| Interface ownership | 3 | Customer builds all | Vendor builds and maintains |
| Itemized, capped pricing | 2 | One lump sum, no cap | Itemized, capped renewal |
Contract questions teams forget
- What is the cap on the annual increase, and does it apply after the first term
- Is a data export included at exit, in a format you can reuse
- Does the price change if you add a facility or merge with another hospital
- Which modules are included in the quote and which are sold later
- Is the implementation fee refundable if go-live slips past a stated date
Is a platform required to meet the CDC core elements?
No. The CDC Core Elements of Hospital Antibiotic Stewardship Programs describe leadership, accountability, expertise, action, tracking, reporting and education, and do not name software. Small hospitals meet them with a pharmacist, a committee and the right reports. Software is justified when the volume of review or reporting is more than the team can do by hand.
Related on this site: antibiogram software vs spreadsheet, stewardship software cost for a small hospital, NHSN AUR reporting software, Joint Commission stewardship requirements, pharmacy surveillance software compared.