Ask Qyro or search⌘K New

AI Triage Platform

DCB 0129, as manufacturer · GP Triage · 31 hazards, 26 suggested by Qyro

Describe or upload your documentation

We’ll read it and propose the system it describes: components, people and steps.

Drop files or browse
PDF, Word or text · or paste a description below
IFU draft v2.pdfRead in full · 14 elements foundRead
Architecture overview.docxRead the first 12,000 characters of 31,400 · split it to read the restPartly read
Patient journey.pdfReading now

Or import an existing hazard log

.xlsx or .csv. We’ll map the columns and keep the original wording.

Import a hazard log
Last import: Hazard log v7.xlsx · 83 hazards · 12 Oct · Edit mapping
Qyro proposes elements only from what you give it. Nothing joins the model until you confirm it.

System model 14 proposed, 9 confirmed.

All 14To confirm 5Confirmed 9
ComponentTriage engine (Infermedica MGP)Scores urgency from symptoms · from IFU section 4Confirmed
ComponentPatient entry and demographic matchingMatches the patient to their practice record · from Architecture overviewConfirmed
PersonPractice reception staffRead the routing outcome and book · from Patient journeyTo confirm
InterfaceEMIS Web appointment bookingWrites appointments into the practice system · from DescribeConfirmed

Patient pathway 6 steps, in order.

Confirmed order · stamped 14 Oct by Zak
Step 1 of 6Patient opens the online form
Step 2 of 6Patient describes symptoms
Step 3 of 6Triage engine scores urgency
Step 4 of 6Outcome routed to the practice
Step 5 of 6Practice staff review the outcome
Step 6 of 6Appointment booked or advice sent