Entity

Infection Surveillance Record

The tracked record of hospital-acquired infections including CLABSI, CAUTI, SSI, and CDI with patient details, device days, and NHSN reporting data.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI HAI prediction requires infection history linked to patient factors; without surveillance data, AI cannot identify high-risk patients for prevention.

Quality & Patient Safety Capacity Profile

Typical CMC levels for quality & patient safety in Healthcare organizations.

Formality
L3
Capture
L3
Structure
L2
Accessibility
L2
Maintenance
L2
Integration
L2

CMC Dimension Scenarios

What each CMC level looks like specifically for Infection Surveillance Record. Baseline level is highlighted.

L0

Hospital-acquired infections are not formally tracked. Infection prevention staff may notice individual cases but there is no systematic surveillance program. CLABSI, CAUTI, and SSI rates are unknown. When CMS or state agencies request infection reporting, the data does not exist.

None — AI cannot detect infection clusters, calculate standardized infection ratios, or support surveillance because no formal infection records exist.

Implement infection surveillance tracking — create records for each HAI event with the infection type (CLABSI, CAUTI, SSI, CDI), patient identifier, onset date, device days, organism, and NHSN reporting criteria.

L1

Infection surveillance records exist in a basic tracking log, but case identification depends on the infection preventionist's manual chart review. Some infections are caught; others are missed because review is time-consuming and inconsistent. The infection type and date are recorded, but device days, lab culture results, and NHSN-specific criteria are not consistently documented.

AI could count recorded infection events by type, but cannot calculate standardized infection ratios because device day denominators and NHSN-specific criteria are not formally documented. Surveillance completeness is unreliable.

Standardize infection surveillance records — require NHSN-compliant documentation for every HAI event including infection site, organism with susceptibility, device days, operative procedure details for SSI, and all NHSN-specific inclusion and exclusion criteria.

L2

Infection surveillance records follow NHSN-compliant formats with documented infection criteria, device day denominators, organism identification with susceptibility, and procedure details for SSI surveillance. The infection prevention team can calculate standardized infection ratios and submit NHSN reports with complete, accurate records. But surveillance records are isolated from the patient's clinical timeline — the infection record does not link to the specific lab cultures, device insertion dates, or clinical events that define the infection.

AI can calculate SIRs, generate NHSN reports, and trend infection rates by type and unit. Can benchmark against national rates. Cannot automate case identification because infection records are not linked to the clinical events (lab cultures, device days) that determine NHSN criteria.

Link infection surveillance to clinical event timelines — connect each infection record to the specific lab culture results, device insertion and removal dates, operative procedure records, and clinical signs that establish NHSN criteria.

L3Current Baseline

Infection surveillance records are linked to clinical event timelines. Each infection connects to the lab culture that identified the organism, the device insertion and removal dates, the operative procedure details, and the clinical signs that triggered investigation. An infection preventionist can query 'show me all CLABSI events where the central line was in place more than 14 days and the organism was MRSA' and trace from the infection through the complete clinical timeline.

AI can perform semi-automated case identification — analyzing lab cultures, device day calculations, and clinical timelines against NHSN criteria to flag potential HAI events for infection preventionist review. Can detect emerging infection clusters from clinical event patterns.

Implement formal infection surveillance schemas with entity relationships — model each surveillance record as a structured entity with typed relationships to lab results, device records, operative procedures, patient risk factors, and NHSN reporting algorithms.

L4

Infection surveillance records are schema-driven with full entity relationships. Each record links to lab culture results with susceptibility, device records with precise insertion-removal timelines, operative procedures with wound classification, patient risk factors, and NHSN reporting algorithm criteria. An AI agent can evaluate any potential HAI against the complete NHSN criteria by traversing the clinical-surveillance relationship graph.

AI can perform autonomous HAI surveillance — evaluating every potential infection against NHSN criteria by traversing the complete clinical context, generating surveillance reports, and detecting clusters. Manual chart review is required only for edge cases.

Implement real-time infection surveillance streaming — publish every infection-relevant clinical event (positive culture, device insertion, fever onset) as a real-time event, enabling continuous automated surveillance.

L5

Infection surveillance records are real-time intelligence streams. Every lab culture, device event, and clinical sign publishes in real-time. HAI case identification runs continuously against NHSN criteria. The infection surveillance system is a living intelligence that detects, classifies, and reports infections as clinical events unfold rather than through retrospective chart review.

Can autonomously manage infection surveillance in real-time — detecting, classifying, reporting, and alerting on HAI events as a continuous infection intelligence engine that operates faster than manual chart review.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on Infection Surveillance Record

Other Objects in Quality & Patient Safety

Related business objects in the same function area.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.