Prenosis

| Aspect | Prenosis (Sepsis ImmunoScore®) | CLEW Medical (sepsis-focused surveillance) | Inflammatix (HostDx™ Sepsis) | |--------|--------------------------------|--------------------------------------------|-------------------------------| | Starting Price | Not publicly disclosed | Not publicly disclosed | Not publicly disclosed | | Typical Fit | Hospitals seeking an FDA-authorized sepsis risk assessment tool that uses multiple data types | Hospitals seeking a broader clinical surveillance platform including sepsis workflows | ED/acute settings considering a host-response diagnostic assay approach | | Key Strength | FDA De Novo authorization; multi-parameter risk scoring; interpretability features described in product materials | Broad surveillance capability and operational program support (e.g., virtual monitoring constructs) | Host-response assay approach provides a different diagnostic signal and has associated economic studies in the literature | | Key Weakness | Limited public peer-review and end-user review footprint; public information on pricing and enterprise security is limited | May be perceived as an alerting/surveillance platform (implications for alarm fatigue depend on implementation) | Different operational requirements (assay logistics) and potential fit challenges for some clinical workflows | - Narrative analysis - Epic / EHR-native sepsis models - Many hospitals use EHR-native or internally developed screening tools. Independent evaluations have scrutinized Epic's sepsis model performance and generalizability; this broader scrutiny affects category expectations for transparency and validation. - CLEW Medical - Positions around clinical surveillance and sepsis operationalization; competes when a buyer prioritizes a single platform for multiple deterioration use cases and centralized operations. - Inflammatix - Competes primarily on a diagnostic testing/assay approach (host response) rather than EHR-derived risk modeling. - Roche/navify ecosystem - Functions as a distribution and workflow integration layer that can facilitate deployment of partner algorithms in Roche-aligned environments. - When customers choose competitors instead (and why) - Choose EHR-native solutions when: - Integration simplicity and governance within the EHR are prioritized - Budget constraints favor in-house or vendor-provided EHR-native screening - Choose surveillance platforms when: - The hospital wants a single platform for multiple deterioration use cases and centralized monitoring operations - Choose diagnostic assay-first approaches when: - Lab turnaround time and assay logistics are operationally feasible and align with clinical utility goals