The record, the work around it, and clinical reference in one place.

The patient story stays together.

Patient identity, active problems, notes, results, medications, orders and encounter history are kept together as one continuing record.

Core record domains

• Patient identity and encounter context
• Problem-oriented clinical documentation
• Laboratory and diagnostic results
• Medication and order context
• Longitudinal history and active clinical state

Pending work stays visible.

Notes are only one part of care. SIJILL also keeps pending work, responsibility, handoffs, results and follow-up close to the record.

Operational surfaces

• Tasks and responsibility states
• Inbox and result acknowledgement
• Schedule and encounter context
• Care-team visibility and handoff support
• Priority and today-focused service views

Supervised critical-care automation.

The ICU layer is built around a supervised loop rather than autonomous clinical action. Canonical patient state keeps the current high-acuity picture coherent. Typed events preserve provenance, trend logic detects meaningful change and versioned protocols prepare workflow artifacts for review.

What the ICU layer keeps together

• Acuity, physiologic state, respiratory or other support, new results, pending work and critical findings
• Trend-aware patient state rather than isolated measurements
• Versioned protocol logic and typed provenance events
• An independent Safety Gate and consultant re-check before staging
• Prepared workflow artifacts with explicit authorization state
• Persisted state, monitoring and closed-loop reassessment

Sijill 0.33.0 · Build 58

ICU Automation Core is the current shipped development release, validated on 28 September 2026. It follows build 57's ICU Operations Console and turns the high-acuity work into a more explicit state, event, protocol, safety and reassessment core.

Validation summary

• 28 Swift source files passed syntax validation
• Shared clinical and ICU layer type-checked in the available validation environment
• 12 of 12 deterministic ICU regression fixtures passed
• Project references, assets, versioning and distribution archive validated

A final native production-environment build, signing and deployment validation remains separate from source-level and model-level validation.

Full release notes →

Clinical reference with clear review status.

The Clinical Reference area brings Pathways, Calculators, Evidence, Microbiology, Formulary and Order Sets into the same clinical environment. Governed material is kept visibly separate from live literature discovery.

How the reference workspace is organized

• Pathways — evidence-structured clinical topics intended to keep practical guidance close to the chart.
• Calculators — 78 formula-verified and executable tools, with implementation-pending entries kept explicitly distinct.
• Evidence — governed guidance and curated material separated from live PubMed/PMC discovery.
• Microbiology — structured organism profiles for identification, clinical context and susceptibility reasoning.
• Formulary and Order Sets — workspaces intended for locally governed medication and ordering context rather than hidden global defaults.

Reference counts reflect the latest validation that explicitly restated the full corpus. Later ICU-focused release validation did not restate those corpus totals.

Sources, review state and responsibility remain visible.

Clinical reference and prepared workflows should show where they came from, whether they have been reviewed and who is responsible for the next action.

• Source and provenance metadata
• Verification and review states
• Institution-specific content boundaries
• Separation of demonstration or simulation data from production institutional data
• Governance-aware evidence organization

Integration should be explicit, not assumed.

Hospital environments differ. SIJILL treats identity, data exchange and system integration as an implementation scope that must be validated with the institution before production use.

Typical integration domains

• Identity, authentication and role mapping
• Standards-based exchange such as FHIR or HL7 where appropriate
• Laboratory and diagnostic-result interfaces
• Medication and order context
• Imaging, scheduling and messaging interfaces
• Audit, export and institutional reporting requirements

Quiet enough for clinical work.

SIJILL uses neutral surfaces, standard typography, thin separators and restrained clinical color. Patient information should carry more visual weight than decoration.