SIJILL Co.
Contact Request a briefing
Product releases

Versioned development, with the validation boundary stated.

SIJILL release notes record the product version, build number, material changes, validation performed and remaining limitations. These are development releases, not a substitute for deployment-specific clinical, security or institutional validation.

Current · 28 September 2026

Sijill 0.33.0 · Build 58

ICU Automation Core

This release makes the high-acuity layer more explicit as a state, event, protocol, safety and reassessment core. It builds on the ICU Operations Console from build 57.

Implemented

  • Canonical ICU patient state
  • Typed provenance events and trend engine
  • Versioned protocol registry
  • Independent Safety Gate and consultant re-check
  • Prepared workflow artifacts with consultant-authorized staging
  • Persisted state and closed-loop reassessment
  • ICU operations console retained around the core
  • ICU Automation Lab with guided/showcase simulation
  • Deterministic regression fixtures for ICU workflow behavior

Validation

  • 28 Swift source files passed syntax validation
  • Shared clinical and ICU layer type-check passed in the available validation environment
  • 12 / 12 deterministic ICU regression fixtures passed
  • Project references, assets, versioning and distribution archive validated
BoundaryConsequential actions stop at consultant-authorized staging. Build 58 does not directly execute medication, ventilator, vasoactive, transfusion or procedural actions against a production clinical system. Final native production-environment compilation and deployment validation remain separate.
28 September 2026

Sijill 0.32.1 · Build 57

ICU Operations Console

This release replaced the earlier prototype-card treatment of ICU automation with a denser clinical operations console.

Implemented

  • Patient and attending header with physiologic status strip
  • Organ-system synthesis
  • Table-based automation queue
  • Consultant-review inspector
  • Safety Gate findings and evidence provenance
  • Reassessment schedule and authorization audit log
  • ICU Automation Training Center using synthetic cases and monitor data
  • Explicit simulation state with no real patient data
  • Clinical-responsibility attestation before consultant sign-off

Validation

  • 27 Swift source files passed syntax validation
  • Shared clinical and ICU layer type-check passed in the available environment
  • Project, assets, versioning and distribution archive validated
28 September 2026

Sijill 0.32.0 · Build 56

Supervised ICU automation foundation

This release established the supervised high-acuity workflow that later builds made more explicit and operational.

  • Prepared action bundles rather than direct execution
  • Separate Safety Gate
  • Consultant or attending sign-off
  • Staged execution state
  • Reassessment checkpoints
  • Simulator and tutorial workflow
Release principles

What a SIJILL version number means.

A version and build number identify a specific development state of the product. Release validation records what was checked in that state. It does not silently convert development validation into a claim of production readiness, certification or institutional approval.

  • Version identifies the product release.
  • Build identifies the packaged software revision.
  • Validation records the checks actually performed.
  • Deployment acceptance remains institution- and environment-specific.