Skip to content
DOCS — OVERVIEW · LONG-TERM USE

Long-Term Use

OpenMed Agent 1.0 is the final release line, and its last maintenance update has shipped. No further versions, fixes, or support are planned. On the latest 1.0.x release, openmed update reports that you are up to date. This page explains what that means in practice and how to keep working as the world around the software changes.

The terms are in the license, which you can read at any time with openmed --license.

What stays the same

  • The software on your machine. The installed binary has no expiry date, and your sessions, plans, skills, and settings stay in ~/.openmed/.
  • Your own providers. Your API keys talk directly to your model provider. As long as the provider serves a compatible API, OpenMed keeps working with it.
  • Your own services. Anything you point at your own servers, such as a custom model endpoint or your own medical service endpoints, depends only on those servers.

What can change

OpenMed depends on things outside the binary. The table shows what to do when one of them changes.

What changes What you will see What to do
A provider retires a model An error saying the model is unavailable, with a hint to pick another one Choose a newer model. See Default model and newer models
A provider releases a newer model It is not in the /model list Pass its ID with --model, or add it to your list with openmed config provider-set
ChatGPT sign-in stops working Sign-in or request errors Switch to an OpenAI API key. ChatGPT sign-in is experimental and can stop working at any time
A provider changes its API Provider errors on every request Use another provider, or a custom endpoint that speaks the OpenAI-compatible API
A hosted medical service is unavailable "Temporarily unavailable" errors, stopped reviews, or DEGRADED reports Try again later. See When a service is unavailable
Hosted medical services are discontinued The same errors, and they do not clear See If hosted services go away
Trusted certificates change, or your network inspects TLS Certificate errors on every connection Set SSL_CERT_FILE to a current CA bundle, for example export SSL_CERT_FILE=/path/to/ca-bundle.pem

Hosted services are provided as available and may change, be interrupted, or be discontinued.

If hosted services go away

The agent, your model provider, local file tools, sessions, and your own skills do not need OpenMed-hosted services. These parts do:

Part Without hosted services
Built-in skills Unavailable. They are delivered by the hosted service and are not stored in the binary
Reference data for prior authorization and appeal reviews Unavailable. Those workflows stop with an error
Coding and terminology tools, HCC, and RAF Unavailable, unless you point them at a compatible server you operate
Extraction, PII detection, and de-identification Unavailable, unless you point them at a compatible server you operate. DEID mode depends on this service

Your own skills keep working, and MCP connectors can supply your own medical tools.

Clinical reference data ages

Code sets, coverage policies, and risk models change every year. The workflows, skills, and medical tools use reference data that does not update with the software, and OpenMed does not promise that hosted data will follow each new release of ICD-10-CM, CPT, HCC models, or coverage determinations.

  • Check the model, payment year, and segment shown in each coding report.
  • The hosted service loads one ICD-10 fiscal year at a time. A code retired in that year shows as not in the reference set, even for an earlier encounter, and a code added after the HCC tables were published shows no HCC category. For retrospective work, check the code against the release that applied on the encounter date.
  • Treat risk scores as estimates. They are not CMS payment determinations.
  • Verify codes, coverage, and scores against the current official source before billing, submission, or any clinical use.

A reviewer remains responsible for every output, as with any version of OpenMed.

Keep your installation safe

  • Keep a copy of the installed binary. Your install link depends on OpenMed-hosted services. A saved copy does not. On macOS, copy the versioned folder under ~/.local/share/openmed/; on Linux, copy ~/.local/bin/openmed. Keep the copy somewhere else, because openmed update removes older versions from the install folder.
  • Back up what matters. Your settings, sessions, and custom skills are in ~/.openmed/. That folder also contains your credentials, so protect any backup accordingly.

  • Watch the session folder. Sessions keep large tool results on disk. To see how much space they use:

    du -sh ~/.openmed/sessions

    Folders in ~/.openmed/sessions/ belong to individual sessions. Deleting one removes that session and its saved results, and it cannot be resumed afterwards.

Operating systems

OpenMed 1.0 was built for macOS on Apple Silicon and for Linux on x86-64 (GNU libc). Future operating system releases may stop running it, and no rebuilt binary will follow the final 1.0.x update. If you depend on OpenMed, test operating system upgrades before you roll them out.

Getting help

The documentation on this site is the reference for 1.0. There is no obligation to provide support, but you can still reach OpenMed through the support page.