Support healthcare teams with
local operational knowledge.
Healthcare connects procedural knowledge, migration evidence and operational memory. Three related concepts bring organisational information closer to the people who need it, through local processing and source-linked records.
Vendor-neutral by design: organisational procedures remain useful as clinical systems change.
The problem
Keep procedures and escalation paths within reach
Digital change creates a need for current procedural evidence and clear escalation. A bounded local assistant could help staff find approved information while preserving human responsibility.
Procedures are hard to retrieve under pressure
Staff may need a current SOP, a system-specific instruction and an escalation contact during the same incident. Those sources belong together in the local procedural record.
Routine queries compete with judgement calls
Documented steps and escalation contacts support routine queries while clinical judgement stays with qualified staff.
Operational lessons become fragmented
Questions, incident records and procedure changes can sit in separate systems. Reviewed links make recurring documentation gaps easier to trace.
| Downtime risk | Cutover window and fallback |
| Retraining | Training across the clinical system |
| Lock-in | Contract and exit arrangements |
| Reversibility | Recovery plan and source records |
| Downtime risk | Per-cohort cutover |
| Retraining | Training on the Compass surface |
| Lock-in | Reverse manifest retained |
| Reversibility | Source-to-destination reconciliation |
Related concepts
Three applications of a shared evidence approach
Compass, Migrate and Manage connect procedural knowledge, records through change and the lessons retained afterwards.
WYRM Compass
Local procedural knowledge
Procedural guidance grounded in approved SOPs, runbooks and escalation paths, with the relevant source and document version alongside each answer.
- Approved document corpus
- Version-aware source references
- Defined refusal and escalation paths
- Local retrieval and inference
WYRM Migrate
Migration evidence and reconciliation
A migration concept centred on source-to-destination mappings, record reconciliation and the review of incomplete or conflicting information.
- Authorised source and destination access
- Explicit mapping and completeness checks
- Human review of identity conflicts
- Recovery and exit requirements
WYRM Manage
Reviewed operational memory
Operational memory linking approved procedures, reviewed incident lessons and change history, with ownership and revision records kept together.
- Approved procedure revisions
- Reviewed incident themes
- Role-specific access
- Reviewed workflow changes
- Datix payload (anonymised) into the WORM audit log
- Narrative tokenised + theme-tagged (verbal-prescription · handover · medication)
- Cross-references existing SOPs touching those themes
- Flags the cluster to Patient Safety committee queue
Illustrative concept demos
Interactive examples using a fictional trust
Explore procedural lookup, migration reconciliation and operational-memory examples using fictional records.
Tap a preset or type a procedural question — try one about an allergy or downtime SOP.
Interactive demonstration. All trust documents, EPR data, and operational metrics shown are fictional. Production deployments are gated by a per-trust DCB0129 Safety Case.
Vendor-neutral
Document-led support across different systems
Compass centres on approved SOPs, runbooks and escalation records across different clinical-system contexts.
Organisational procedures and records provide continuity across changes in clinical systems.
Clinical safety + compliance
Clinical responsibility and information governance
Clinical responsibility, controlled information access and traceable review decisions shape the healthcare concept.
Clinical safety case
Hazards, controls and clinical safety responsibilities form part of the workflow design.
Information governance
Lawful access, data handling and record ownership follow the organisation’s information-governance requirements.
Deployment assessment
Assess clinical safety, data protection, technical security, interoperability and usability for the selected scope.
Named clinical responsibility
Named clinical leads and escalation owners keep responsibility clear when a question needs professional judgement.
Customer-controlled boundary
Local processing, role-based access and documented data flows keep information within the organisation’s chosen boundary.
Auditable review decisions
Source records, revisions and review decisions provide a traceable account of how operational knowledge changes.
- ·PAT-001 v2.3 (rank 1, score 0.92)
- ·PAT-001 v2.2 (superseded, rank 2, 0.78)
- ·DOWN-001 v1.7 (rank 3, 0.41)
Returned PAT-001 §3.1 v2.3 procedure with PDS-trace cross-reference. 178 tokens · 412 ms.
Local workflow design
Keep uncertainty and escalation visible
Local retrieval brings the relevant source into context. Defined workflow checks organise the response, while named escalation paths connect staff with human expertise.
Knowledge with context
A procedural answer needs its source, version and context. When a document does not resolve the question, the next step is a clear route to the right person.
Questions
Frequently asked
What is the Healthcare concept?
Local procedural knowledge, migration evidence and operational memory, connected through the records healthcare teams already work with.
How does Compass relate to an EPR?
Compass centres on SOPs, runbooks and escalation guidance alongside the organisation’s existing clinical systems.
What belongs with clinical teams?
Clinical judgement and patient-care decisions belong with qualified staff. The focus here is procedural information and the records supporting it.
What does migration assurance cover?
Source-to-destination mappings, reconciliation, identity conflicts and a clear record of what has moved and what needs attention.
What about notes and attachments?
Narrative notes and linked documents sit alongside structured records in the migration picture, with their own mapping and completeness checks.
Why local processing?
Customer-controlled retrieval and inference keep organisational knowledge close to the teams and access policies that govern it.
What do the examples show?
The interactive examples use fictional records to illustrate procedural lookup, migration reconciliation and incident review.
How do the three areas connect?
Compass organises procedural knowledge, Migrate follows records through change, and Manage connects procedures with reviewed operational lessons.
Examples: The interactive scenarios use a fictional trust and EPR. Clinical judgement remains with qualified healthcare staff.
Vendor neutrality — WYRM is independent of the clinical-system vendors named on this page.