HINT for Clinical Operations

Your assistant drafts SOPs fast. HINT keeps it out of clinical judgment.

HINT keeps operational protocols, roles, routes and checklists in plain-text notes beside unit documents. Your assistant reads the applicable approved source before drafting an operational step.

Where it helps

Three situations your team will recognize

Before: A routing instruction is improvised from general medical knowledge.

Every route needs an approved source

The assistant points to the declared guideline and escalation role instead of deciding care.

Before: A handoff checklist drops one required step.

Ordered steps remain complete

The role, timing and required record travel with the checklist through every revision.

Before: One unit's protocol is applied in another unit.

Operational scope stays local

Hospital-wide policy can inherit downward while pharmacy and emergency-intake procedures remain isolated.

See it

A real arrival-routing protocol from the demo

The Sacred Heart demo grounds its emergency-intake operations protocol in SRC-1.

demo-sacred-heart-clinical/units/emergency-intake/sop-arrival-routing.md.hint ↗

# read Approved source

../../sources/approved.md

# protocol emergency-intake-1 {#clinical_operations_demo}

Approved protocol grounded in SRC-1.

# never Invented details

What your assistant does next

It drafts only the declared operational route, preserves the required escalation, and refuses requests for diagnosis, treatment or triage judgment.

What your AI assistant receives
<protocol name="emergency-intake-1">
  Approved protocol grounded in SRC-1.
</protocol>
<never name="Invented details">…</never>

Your boundaries stay visible

What it will never do

  • Provide medical advice, diagnosis, treatment, dosing or triage decisions.
  • Invent a routing rule, clinical criterion or guideline.
  • Skip a declared step, red flag or escalation role.

FAQ

Questions clinical operations ask

Does it give medical advice?

No. The vocabulary explicitly limits the assistant to operations documents and excludes diagnosis, treatment, dosing and triage decisions.

Does it know current regulations?

No. Your organization supplies and approves the sources that govern each protocol.

Can it approve an SOP?

No. It can carry owner and review fields; your clinical governance process controls approval.

For your technical colleague

The vocabulary

A hintbook is a vocabulary for your profession—installed, not written by you.

protocol
Names an operational protocol, version and owner.
sop
Defines a standard operating procedure from approved sources.
record
States what operational information must be documented.
role
Defines who is authorized to perform an action.
route
Maps a declared condition to an operational destination.
redflag
Triggers immediate escalation without making a diagnosis.
deviation
Records how a departure from procedure is handled.
training
States who must be trained on an approved procedure.

Manual setup

Bootstrap is read-only: it prints instructions for the assistant. The assistant performs the installation.

npm install -g @openhint/cli
hint config
hint add @openhint/hintbook-clinical-operations
hint apply
hint verify units/emergency-intake/sop-arrival-routing.md
hint emit units/emergency-intake/sop-arrival-routing.md

Hintbook repository ↗ · Demo repository ↗

Works with