Glossary
Public definitions for the mechanisms and roles of HealthOS ICU. The site uses the same terminology as the submission-ready IHA article series.
Roles
knowledge-author
Knowledge author. The role that drafts and edits formal medical rules and supporting terminology before review.
knowledge-approver
Knowledge approver. The role that reviews, clinically validates, and formally approves governed knowledge changes before compilation or release.
release-operator
Release operator. The role that promotes accepted release artifacts through governed release and deployment handoff.
break-glass-operator
Break-glass operator. A rare emergency role authorised to request urgent governed action outside the standard cadence. Every action is flagged for post-hoc review.
Knowledge and governance
semantic-authority
Semantic authority. The upstream governed source of clinical meaning. Runtime services carry compiled term references and evidence, but do not create or approve clinical semantics.
knowledge-compiler
Knowledge compiler. The toolchain that transforms authorized semantic inputs into compiled bundles, runtime catalogs, and traceable execution artifacts.
trusted-knowledge-snapshot
Trusted knowledge snapshot. The approved, immutable knowledge state used as the input for governed release. It is identified by digest and review evidence.
compiled-bundle
Compiled bundle. A deterministic compiled artifact produced from an approved knowledge snapshot. It is release-bound before runtime use.
runtime-term-reference
Runtime term reference. A compiled term identity carried through request preparation, response evidence, audit refs, debug refs, and evidence projection.
term-registry
Term registry. The lookup surface used to trace runtime term references back to governed terminology and definitions.
term-trace
Term trace. A review path showing how a runtime term reference connects to compiled knowledge and governed source semantics.
diagnostic-contour
Diagnostic contour. The evidence-driven loop that classifies issues, prepares remediation material, records operator decisions, and closes review without making the runtime service a semantic authority.
medical-knowledge-graph-store
Medical knowledge graph store. The governed graph surface that stores reviewed clinical rules and supporting semantic material. It is part of semantic authority, not runtime execution.
refinement-candidate
Refinement candidate. A proposed knowledge update derived from runtime evidence and submitted for governed review.
Runtime and analyzer contours
runtime-library
Runtime library. The unified library linked into analyzer services at compilation. It contains the Compute core path and, where applicable, the Safety kernel path.
compute-core
Compute core. The deterministic execution path that evaluates release-bound executable knowledge over normalized inputs and returns reviewable runtime evidence.
safety-kernel
Safety kernel. The guarded decision path used for downstream stateful human-in-the-loop command application. It is not the ordinary stateless or stream feature-analysis path.
stateless-rule-based-analyzer
Stateless rule-based analyzer. The service-host contour for request-local analysis. It prepares input, invokes the Compute core, publishes results, and cleans up without retaining clinical state.
stateful-rule-based-analyzer
Stateful rule-based analyzer. The stream/session/window contour for continuous inputs. It keeps operational state for windows and sessions, but it is not semantic authority.
device-protocol-gateway
Device protocol gateway. The medical-device-facing protocol boundary. It performs protocol framing, admission, ACK/NACK, and handoff into bounded analyzer queues or internal buses.
runtime-evidence
Runtime evidence. The bounded evidence emitted during execution: response facts, runtime term refs, audit refs, debug refs, hashes, digests, and publication references.
runtime-evidence-report
Runtime evidence report. A compact report assembled from runtime evidence for review, replay, or governed refinement.
audit-ref
Audit ref. A link to durable audit material. Debug traces may link to audit refs, but cannot reconstruct or replace them.
debug-ref
Debug ref. A link to diagnostic debug material. It supports investigation and replay, but is not an audit record.
audit-event-log
Audit event log. A durable audit publication surface for runtime and command evidence. It is distinct from diagnostic debug traces.
clinical-data-facade
Clinical-data facade. A public integration surface that projects selected results, audit material, and provenance records to clinical information systems.
configuration-manifest
Configuration manifest. A deployment-specific configuration artifact that pins accepted parameters and runtime selections for a release-bound service.
module-manifest
Module manifest. The per-module configuration artifact for a single pluggable analyzer module: its identity, version, declared inputs and outputs, and the release-bound knowledge it is permitted to use. It scopes one module, unlike the configuration manifest, which pins parameters for a deployment as a whole.
per-monitor-context
Per-monitor context. The bounded runtime state scoped to a single bedside monitor or device stream: its session, window state, and the runtime term references carried with that stream. It is held by the stateful analyzer behind the device protocol gateway: the gateway is the admission boundary itself, not the state kept for each device.
Release and trust
governed-release
Governed release. The controlled path from trusted knowledge snapshot and compiled bundle to release candidate, gates, evidence-of-fact receipt, signed release evidence, and deployment handoff.
release-receipt
Evidence-of-fact receipt (proof of provenance). The compact release record that binds accepted artifacts, image and bundle digests, configuration fingerprint, SBOM material, test refs, and publication evidence.
release-manifest-capture
Release manifest capture. The release-wave record that preserves compatibility and handoff facts for analyzers deployed together.
continuous-chain-of-trust
Continuous chain of trust. The verification continuity from release evidence through attestations, signatures, transparency evidence, deployment admission, startup verification, and diagnostic trust signals.
deployment-admission
Deployment admission. The trust-chain check that deployment may use only accepted release artifacts and evidence.
governed-write-surface
Governed write surface. The controlled write path used only after policy, authority, and audit checks have accepted a proposed change or command.
Clinical and regulatory concepts
instant-health-assessment
Instant health assessment. A bounded, evidence-driven assessment of current patient state from controlled term values, signals, and executable knowledge.
cardio-flag
Cardio flag. A bounded ECG-domain output that marks a rule-based interpretive condition without claiming autonomous diagnosis.
ecg-mimic-exclusion
ECG mimic exclusion. The controlled rule boundary used to separate ECG-like patterns from accepted ECG interpretation inputs.
samd
SaMD (Software as a Medical Device). Autonomous software that performs a medical purpose without requiring a hardware medical device as a host. HealthOS ICU is positioned as supervised software in a medical-device environment, not as an autonomous SaMD claim.
software-in-device
Software in a medical device. A regulatory classification for software that is integral to, or an accessory of, a hardware medical device and does not independently perform the medical purpose without that device.