MediFlow.

Release notes

What’s new.

What changes from one version to the next, written for people working in an outpatient practice. Technical detail and the checks behind each delivery stay on GitHub.

After 0.9.0, already on main

These changes landed after the tag and will ship with the next version. Anyone running the main branch from source already has them.

One launcher

macOS, Windows and Linux open the same launcher: MediFlow.command, MediFlow.cmd or MediFlow.sh. It asks how you want to use MediFlow and starts the production build for ordinary use; its configuration stays outside the clinical archive.

Source · #529

Ollama 0.40.5

Ollama 0.40.5 is now also supported for local models. Configure a supported model for each function. With an incompatible version, MediFlow reports the error and stops the request without switching providers.

Source · #548

Update AIFA

With network consent, MediFlow checks at most once a day whether AIFA has published a new catalogue version. The update starts only with Update now, asks for confirmation if the catalogue shrinks, and keeps source and date.

Source · #525

Embedded ICD-11 MMS

The embedded ICD-11 MMS catalogue supports local lookup without Docker. Source and version remain identifiable: finding a code does not establish clinical appropriateness or amount to a live WHO service query.

Source · #527

Sources for assistive devices

Assistive-device prescribing uses its own sources and keeps the original documents in the archive, included in the full backup. The prescription records which source an item comes from; choosing and confirming it stays with the professional.

Source · #528

A quieter interface

One typographic voice: Newsreader for titles and people, the system typeface for everything else, monospace only for codes. Buttons share one height, and actions repeated on every row no longer carry a frame.

Source · #530

Less code

Unused code and outdated historical material are gone, about 8,000 lines. Historical references point to the v0.9.0 tag.

Source · #531

15 October 2026 · source release

0.9.0

0.9.0 adds no clinical features: it makes the existing ones sturdier. AI functions remain optional, off until you choose them, and only produce proposals to review.

What changes in the outpatient practice

  • Safe writes. Diary, treatments, measurements, prescriptions and records are saved in a single transaction with their audit: either everything is recorded, or nothing is.
  • Explicit conflicts. If two sessions edit the same entry, the second does not silently overwrite it: you can cancel, reread or start again from the current version.
  • Passphrase access. The passphrase opens the archive; the PIN remains only to confirm sensitive operations.
  • Full recovery. The encrypted backup contains the whole archive, can be verified from the interface and restores atomically.
  • Runtime identity. At startup MediFlow checks that it is the version you downloaded: a different or outdated server is not opened by mistake.
  • First start. On a new computer the archive prepares itself, with no manual steps.

Where it runs

Source release with Node 24, tested on macOS (Apple Silicon), Windows 11 ARM and Arch Linux ARM. Start from a Git checkout of the v0.9.0 tag. Native apps and signed installers are not part of this release.

git clone --branch v0.9.0 --depth 1 https://github.com/Wulfgardr/mediflow

Limits to know

  • Publishing the source does not authorise use with real clinical data: admitting a given installation remains the decision of whoever runs it.
  • The full backup keeps embedded content, not external originals that were already missing.
  • Some automated tests affected by two sources of instability are quarantined until 23 October 2026 at 00:00 UTC: they keep running, but the causes are not yet resolved.

Release page on GitHub Full CHANGELOG