What SOFUS does not do

This page outlines explicit boundaries to ensure correct use, appropriate expectations, and responsible deployment across different clinical settings.

SOFUS is designed to support clinical interpretation and situational awareness. Equally important is a clear understanding of what SOFUS does not do.

SOFUS does not make clinical decisions

SOFUS does not diagnose conditions, prescribe treatment, or make autonomous clinical decisions.

All outputs produced by SOFUS are supportive in nature and are intended to inform, not replace, clinical judgment. Responsibility for clinical decisions always remains with qualified healthcare professionals.

SOFUS does not replace clinical workflows

SOFUS does not define, enforce, or replace local clinical workflows.

Hospitals and care settings differ in organization, escalation pathways, and documentation practices. SOFUS is designed to integrate into existing workflows and support them, not to standardize or override them.

SOFUS does not expose raw patient data

SOFUS does not act as a data access layer.

Raw patient data, original observations, and source-system records remain the responsibility of Journl Streamed and upstream systems. SOFUS consumes structured inputs and produces derived outputs, not raw datasets.

SOFUS does not require fixed or universal input sets

SOFUS does not assume that the same data is available in all clinical environments.

The input set used by SOFUS is configurable and context-dependent. Absence of certain inputs does not imply system failure, and deployments are always evaluated and adapted to local data availability and clinical relevance.

SOFUS does not rely on single measurements

SOFUS does not base assessments on isolated observations alone.

Clinical signals are derived from patterns across time and context, not from single values interpreted in isolation.

SOFUS does not operate as a black box

SOFUS does not produce unexplained scores or opaque outputs.

Where relevant, SOFUS provides explanations that describe contributing factors and observed patterns, supporting transparency and clinical understanding without exposing proprietary logic.

SOFUS does not define regulatory classification on its own

SOFUS does not independently determine regulatory classification or clinical responsibility.

Regulatory assessment, clinical validation, and governance are handled in collaboration with customers and stakeholders, taking local regulations and intended use into account.

SOFUS does not function independently of Journl Streamed

SOFUS does not ingest data directly from source systems.

It operates exclusively on structured, normalized data provided by Journl Streamed, preserving a clear separation between data management and clinical interpretation.