Features
Clinical surveillance software built around one job: your local resistance picture
This is not a hospital-wide surveillance platform and it does not try to be. It does the resistance reporting thoroughly, publishes what it costs, and states plainly what it leaves to other systems.
Antibiogram engine
The cumulative report, built the way the guidance describes
Everything here exists to make one number defensible: the percentage in a cell, and the count under it.
Organism by antibiotic matrix
Every cell carries its percentage susceptible and the isolate count behind it, because a percentage without its denominator is a claim rather than a measurement.
First isolate de-duplication
One isolate per patient per organism per period, on by default, with the before and after counts shown so the effect is visible.
Reporting threshold
Cells under 30 isolates are marked rather than deleted, so a thin cell reads as a decision and not as missing data.
Stated intermediate handling
Excluded from the denominator by default, counted as resistant on request, and printed under the matrix either way.
Cuts and filters
The cut is the unit of work, not the annual report
A cut is a filter combination, not a new project, so the follow-up question costs a click rather than a week.
Specimen source
Urine, blood, respiratory, wound and whatever else your export carries, because the source decides the organism mix.
Unit and location
Intensive care, inpatient, emergency and outpatient, mapped from your free-text locations during onboarding.
Period
Full year, quarter or a trailing twelve months, with suppression recalculated for each cut rather than inherited from the whole.
Syndrome grouping
Bacteraemia, urinary tract infection and pneumonia built from your own source and organism definitions. Stewardship plan and above.
Trends and MDRO
Movement, with the counts that make it readable
Movement only means something when the method is held constant between the two periods being compared.
Quarterly trend for any pair
Pick an organism and drug and see the four quarters, with the isolate count behind each point.
MDRO watch list
Carbapenem resistance, ESBL phenotype, MRSA fraction and VRE, reported as counts because a percentage on a rare phenotype is noise.
Threshold flags
Mark a movement you want to be told about in the next report. This is reporting, not real-time alerting, and we do not describe it as alerting.
Period comparison
The same cut across two periods with the method held constant, which is the only way a difference means anything.
Breakpoints
CLSI and EUCAST, applied on purpose
The breakpoint version is part of the result. A report that cannot name its own table cannot explain its trend.
Your reported interpretation
Used as your laboratory issued it, by default. Nothing is silently overridden.
Reinterpretation from MIC
Re-run a year against a chosen CLSI or EUCAST version where MIC values are present. Stewardship plan and above.
Version on the output
The breakpoint source and version are stamped onto every export, because a trend that spans a revision needs the label.
SDD and NS mapping
Susceptible-dose-dependent and non-susceptible are mapped explicitly during import rather than guessed at.
Data handling
The file stays yours
The demo on this site never uploads your file. For an account, a pseudonymous key is all de-duplication needs.
Browser parsing in the demo
The builder on this site parses your CSV locally. No upload, no network request carrying rows, and you can watch the network tab to confirm it.
Pseudonymous patient keys
De-duplication needs to know that two rows share a patient, never who the patient is. A hash you generate is enough.
Column mapping you control
Detected automatically, corrected by you, and saved so the next export loads without the conversation.
Exports
CSV of any view and a clean print page, both carrying the rule receipt and the generation date.
Team and enterprise
What larger organisations ask for
What appears in a procurement questionnaire, described as what the plan includes rather than as a badge.
Multiple facilities
Up to three on Stewardship, up to twelve with cross-facility comparison on Network, unlimited on Enterprise.
Roles and audit log
Who ran which report, and when. Audit log on Network, full role management on Enterprise.
SSO and SAML, SCIM
Part of the Enterprise plan, described as what that plan includes rather than as a certification we hold.
Scheduled ingest and API
Pick up an export your systems already produce on a schedule. Network plan and above.
Out of scope, on purpose
What this does not do
A short list of things a buyer might reasonably assume are included. They are not, and finding out after signing would be worse than reading it here.
- Antibiotic consumption metrics. Days of therapy and defined daily doses come from administration data, which this product does not receive.
- Prospective audit and feedback workflow. There is no worklist and no intervention tracking.
- Real-time alerting. Reports are built from the export you provide, on your schedule.
- Electronic health record integration. It knows about isolates, not admissions, devices or procedures.
- Clinical decision support. It does not diagnose, prescribe or recommend therapy for a patient.
- Healthcare-associated infection surveillance. It does not compute NHSN infection definitions.
For the workflows these features serve, see antimicrobial stewardship program use cases, the hospital antibiogram itself, and the infection prevention side of the same data.
Start with your own export
See your own resistance picture, cut the way you actually work
Build the antibiogram on the synthetic sample dataset, or drop in your own CSV and watch it parse without leaving your browser. When you want an account, one email address is the whole sign-up.
Your file is parsed in your browser and never uploaded. No card required.