Skip to content

Rune in Clinical Systems โ€‹

Healthcare has the most demanding requirements for explicit, auditable bindings. The ! invariant โ€” nothing consequential happens without explicit invocation โ€” maps directly to the clinical requirement that every intervention is intentional and logged. The ? primitive carries the regulatory rationale that paper-based systems put in policy manuals that nobody reads at point of care.

Patient Record โ€‹

@patient.name
@patient.dob
@patient.mrn        ?"medical record number โ€” system-assigned, immutable after creation"
@patient.allergies  ?"read from confirmed allergy list โ€” update via !confirm-allergies only"

@vitals.bp          ?"latest reading from monitoring system โ€” not manually entered"
@vitals.hr
@vitals.spo2        ?"peripheral oxygen saturation โ€” alert threshold 94% in !check-vitals"

~diagnosis          ?"ICD-10 required โ€” validated against formulary on !prescribe"
~care-plan          ?"editable by attending only โ€” version-stamped on each save"
~discharge-summary  ?"required before !discharge โ€” auto-populated from ~diagnosis and ~care-plan"

Clinical Actions โ€‹

!prescribe          ?"triggers drug interaction check โ€” logged to medication administration record"
!confirm-allergies  ?"clinician attestation โ€” creates auditable record with timestamp and session"
!order-lab          ?"explicit โ€” no automatic orders on field change, requires ~diagnosis"
!discharge          ?"requires completed ~discharge-summary โ€” notifies care coordinator and GP"
!escalate           ?"triggers rapid response team โ€” logged to incident record"

?"all ! actions require authenticated clinician session โ€” session token validated on dispatch"
?"this record is governed by HIPAA โ€” access logged, export requires patient authorization"
?"medication changes logged to MAR automatically โ€” Rune ! guarantees explicitness"

Medication Administration โ€‹

@medication.name
@medication.dose     ?"weight-based calculation โ€” do not override without attending sign-off"
@medication.route
@medication.schedule ?"derived from !prescribe parameters โ€” read-only at administration"

~administered-by    ?"nurse ID โ€” required for !administer"
~administered-at    ?"defaults to now() โ€” adjustable within ยฑ15 min for documentation lag"
~refused            ?"patient refusal โ€” requires ~refusal-reason before !document-refusal"

!administer         ?"scans barcode, validates ~administered-by, logs to MAR โ€” five rights enforced"
!hold               ?"suspends schedule โ€” requires ~hold-reason, notifies prescribing clinician"
!document-refusal   ?"records patient refusal โ€” requires ~refusal-reason, logged to MAR"

?"five rights enforced on !administer: right patient, drug, dose, route, time"

Why Rune Fits Healthcare โ€‹

  • ! makes every clinical intervention explicit โ€” no implicit side effects from reading or editing fields
  • ~ makes every editable clinical parameter enumerable โ€” auditors can query all mutable fields
  • @ makes feed-driven vitals and system-assigned identifiers structurally non-writable
  • ? keeps the regulatory rationale co-located with the binding โ€” survives system migrations and EHR changes