Does Aivault use language models?
Yes. A language model helps read the visit record and match it against the protocol requirements. The requirements themselves come from the clinical protocol, not from the model.
How it works
How a visit is checked against the clinical protocol
In short: Aivault takes the visit record from the clinic’s medical information system (MIS), extracts confirmed diagnoses and prescriptions, selects the clinical protocol and checks each of its requirements. The result is a list of met and missed requirements together with the protocol text.
Updated:
Five steps of the check
-
Receiving the visit record
Aivault receives the visit record from the MIS via API: complaints, medical history, diagnoses with ICD-10 codes, tests, lab results and prescriptions.
-
Extracting facts
A language model reads the record and extracts structured facts: confirmed diagnoses, prescribed medications and doses, tests.
-
Selecting the protocol
For each confirmed diagnosis the system finds the matching clinical protocol in the library.
-
Checking requirements
Each protocol has been broken down in advance into a requirement register: what to do, for whom and under which conditions. Each requirement is matched against the visit record.
-
Report
Each requirement is marked as done, missed or not applicable. Missed critical requirements are highlighted separately, next to the requirement text from the protocol.
Checked against the clinical protocol
- R1 Blood pressure measurement done
- R2 12-lead ECG done
- R3 Lipid profile missed
- R4 Creatinine, potassium and eGFR Critical requirement Before prescribing an ACE inhibitor missed
Requirement text: before prescribing an ACE inhibitor, measure blood creatinine and potassium and calculate eGFR
- R5 Hospitalisation for a hypertensive crisis Only if there is a crisis not applicable
2 done 2 missed, 1 of them critical 1 not applicable
How to read the marks
- done requirement found in the record
- missed the record lacks what the protocol requires
- not applicable requirement for a different situation
What a protocol requirement register is
A clinical protocol is a long document. To check it automatically, Aivault turns each protocol into a requirement register: separate lines such as “for this diagnosis, order this test”, with the conditions under which they apply. The check goes line by line, so every remark can be traced back to a specific point of the protocol.
Which protocols are in the libraryWhy the result can be trusted
- Every remark is linked to a specific protocol requirement and can be verified.
- You can see which requirements were found not applicable to this visit.
- The final decision is always the doctor’s; the medical director reviews the deviations.
Limitations
- Aivault Health does not diagnose and does not replace the doctor: it is a quality control tool, and the final decision is the doctor’s.
- Diagnoses confirmed in the visit record are checked against the protocol.
- The system sees only what is recorded in the MIS. If a test or prescription is not in the visit record, the check cannot take it into account.
- Protocol requirements that apply to inpatient care or to later visits are marked as not applicable to an outpatient visit.
Frequently asked questions
What happens if the diagnosis is not confirmed?
Confirmed diagnoses are checked against the protocol. A provisional diagnosis alone does not trigger a protocol check.
What if data is missing from the record?
Aivault sees only what is recorded in the MIS. If a test or prescription is not in the visit record, the check cannot take it into account, so the completeness of the record directly affects the result.
Still have a question? Write to us or call, and we will answer you personally.
Free demo
See Aivault at work in a free demo
Tell us briefly about your clinic and the medical information system (MIS) you use. We will get in touch, arrange a meeting and give you a free demo.
- Free demo using sample cases
- We will discuss integration with your MIS
- We will prepare a cost estimate for your clinic