How SOFUS Outputs are intended to be used

The outputs produced by SOFUS are consumable artifacts that can be integrated into downstream systems, user interfaces, and operational processes.

SOFUS outputs are designed to support clinical awareness, prioritization, and interpretation within existing healthcare workflows. They are not intended to function as standalone decisions or automated actions.

Supporting clinical situational awareness

SOFUS outputs are intended to provide a concise, interpretable view of patient status and risk.

Typical uses include:

• Highlighting patients who require increased attention

• Supporting overview dashboards for clinical teams

• Enabling rapid understanding of why a patient’s status or risk has changed

Status outputs support understanding of the current clinical state, while prediction outputs support awareness of potential future development.

Prioritization and workflow support

SOFUS outputs are designed to support prioritization, not escalation logic.

They may be used to:

• Inform triage or task prioritization

• Support handovers and shift changes

• Provide context for clinical discussions and decision-making

Any escalation rules, alert thresholds, or workflow actions are defined outside of SOFUS, in accordance with local clinical governance.

Interpretability and transparency

A core design principle of SOFUS outputs is interpretability.

Outputs are intended to be used in a way that allows clinicians and downstream systems to:

• Inspect contributing factors

• Understand which inputs influenced the output

• Distinguish between observed values, derived status, and predicted risk

Explanation components (e.g. SHAP values) are included to support understanding, not to imply causality or prescribe action.

Integration with downstream systems

SOFUS outputs are designed to be integrated into:

• Clinical decision-support interfaces

• Monitoring and alerting systems

• Analytics and quality-improvement solutions

Outputs are represented using structured FHIR resources to enable consistent consumption across systems.

SOFUS does not define how outputs are visualized, stored long-term, or acted upon. These decisions are made by downstream systems and organizations.

Clinical responsibility

SOFUS outputs are decision-support inputs, not decisions.

They are intended to:

• Inform clinical judgment

• Support discussion and assessment

• Provide structured, explainable insight

Clinical responsibility always remains with healthcare professionals and the organizations deploying SOFUS.