Guideline Propagation
Keep Your Medical Notes Up To Date
When a guideline you rely on changes, Suture compares the changed sections against your notes and raises a banner on every note affected — whether it cites the guideline or not, in any language.
Changed section · Pharmacotherapy in HFpEF
No therapy has convincingly reduced mortality in HFpEF.
HFpEF — diagnosis & management
Your note · cites ESC Heart Failure 2021
Diagnosis rests on symptoms, EF ≥ 50% and evidence of raised filling pressures…
The problem
Guidelines Move. Notes Don’t.
Societies revise their recommendations continually. The note you wrote in third year doesn’t know that — it reads exactly as confidently as the day you wrote it.
- 1
A note has no expiry date
A recommendation you wrote down years ago may have been rewritten since — but on the page, nothing changes. Stale knowledge looks identical to current knowledge.
- 2
Updates don’t announce themselves
A new guideline version publishes, and no signal reaches the hundreds of notes quietly built on the old one.
- 3
Rechecking everything is impossible
Nobody rereads years of notes against every new version of every guideline. Manual vigilance does not scale — so it simply doesn’t happen.
Watching the source
Only The Changes Are Checked
When a guideline publishes a new version, Suture diffs it against the prior one and extracts only the sections that actually changed. Those changed sections — not the whole document — are then compared against your notes via semantic similarity and fanned out as impact flags on the notes they touch.
- New versions diffed against the prior version
- Only changed sections are compared to your notes
- Semantic similarity finds the affected notes
- Impact flags land on the exact notes that need review
2 changed sections → 3 notes flagged
Only what changed is compared — never the whole document
Two kinds of warning
A Hard Warning And A Soft One
Notes that formally cite a changed guideline get a stale-citation warning — the hard banner: your source has moved. Notes that are semantically about a changed section, even without citing it, get a softer “this note may be affected” banner. Both appear right in the editor, and both are dismissible.
- Stale-citation warning when a note cites a changed guideline
- Softer impact banner for uncited but affected notes
- Both shown in the editor, on the note itself
- Every banner is dismissible — you stay in charge
Stale citation
Formally citedThis note cites ESC Heart Failure 2021 — superseded by the 2023 focused update.
This note may be affected
No citation neededA section about SGLT2 inhibitors in HFpEF changed — this note covers the same topic.
Hard when the note cites the guideline · soft when it only writes about it
Across languages
An English Update Flags Your Dutch Note
Propagation is semantic, not textual — so it crosses languages. When an English-language guideline changes, notes you wrote in Dutch about the same recommendation are still found and flagged. Your notes stay current in whichever language you think in.
- Matching works across languages
- English guideline updates flag Dutch notes
- Semantic comparison, not string matching
- Write in the language you think in
ESC 2023 · changed section
“SGLT2 inhibitors are recommended in HFpEF to reduce HF hospitalisation (Class I).”
Your note · Dutch
Hartfalen met behouden ejectiefractie
Behandeling: diuretica bij congestie; SGLT2-remmers verlagen HF-opnames…
This note may be affected — matched across languages
Built for professionals
A CPD Signal, Not Spam
Practicing specialists are notified when guidelines in their field change — a genuine continuing-development signal from their own notes. The system is deliberately tuned for recall: better to raise a dismissible banner too often than to miss a change that matters. One dismiss, and a flag is gone.
- Specialists notified when their guidelines change
- A continuing-development signal from your own notes
- Tuned for recall — over-flag rather than miss
- Dismissed banners stay dismissed
ESC Heart Failure — 2023 focused update published
1 note in your corpus flagged for review
Detection tuning
Recall-firstA dismissible over-flag beats a missed change — and dismissed stays dismissed.
Notes That Age. Notes That Update.
A note is a snapshot of the evidence on the day you wrote it. Guideline propagation turns that snapshot into a document that reacts when its sources move.
Notes left alone
- Notes frozen the day you wrote them
- Manually rechecking every source
- Stale citations found by luck
- Uncited topics slip through
- Updates lost across languages
- A missed change you never hear about
With Guideline Propagation
- Notes that react when guidelines change
- Changed sections compared automatically
- Stale-citation warnings in the editor
- Semantic matching flags them anyway
- English updates flag your Dutch notes
- Tuned to over-flag, never to miss
From Med School To Continuing Development
Students keep study notes aligned with the current recommendation; specialists get a CPD signal from their own writing — all fed by the same guideline library that powers the rest of Prognia.
From New Version To Reviewed Note
Suture watches the source, diffs the versions and flags the affected notes — the only step left for you is the review itself.
- 1
Detect
A guideline you rely on publishes a new version.
- 2
Diff
Only the changed sections are extracted and compared to your notes.
- 3
Flag
Affected notes get a banner — hard for citations, soft for topic matches.
- 4
Resolve
Update the note, or dismiss the banner if it doesn’t apply.
Grounded in living evidence
Guidelines are living documents — these are the sources and the science of keeping up.
Questions about Guideline Propagation
Notes That Notice When Medicine Moves
Write it once, and let Suture watch the source — every affected note flagged the moment a guideline changes.
Free forever for students · No credit card required