Homeo AI vs RadarOpus 4.2: Update or Note-First AI?

Quick answer

Choose RadarOpus 4.2 when the clinic already depends on RadarOpus and wants its newly released desktop update, expanded documents, native Windows ARM support, and fixes inside a deep repertory and materia medica environment. Choose Homeo AI when the larger problem begins before repertory analysis: converting ordinary consultation notes into an editable structure, reviewing candidate rubrics and source passages, documenting a differential, and carrying that reasoning into follow-ups.

This is a release-specific decision, not a general claim that one product replaces the other. RadarOpus 4.2 improves an installed professional suite. Homeo AI is a browser-based, note-first clinical workflow copilot. An established RadarOpus user may sensibly upgrade and still test Homeo AI for the narrative-to-review stage. A clinic buying its first system should compare the full source, device, training, privacy, backup, and workflow requirements rather than treating one new version number as the whole purchase case.

What RadarOpus released on 23 July 2026

The official RadarOpus version history lists version 4.2 with a release date of 23 July 2026. It says the update is free for owners of RadarOpus 2.2.16 and higher and payable for users on legacy versions 2.1 and lower. That entitlement statement is more useful than assuming every existing license receives the same upgrade. A clinic should confirm its exact installed version, license status, dealer, language, and optional content before changing a working machine. The reviewed version-history page is linked in the sources below.

The vendor's official 4.2 summary, linked below, says the release covers versions 4.2.1 through 4.2.4. It highlights new remedies from Petrucci and Kissling, the EKAP GPS module, Qt 6.10, new WIBU protection, Japanese Synthesis content, and additional documents. These are vendor release statements, not independent validation of the clinical accuracy or completeness of any included source.

The more detailed official 4.2 release notes, also linked below, add several concrete facts. RadarOpus now runs natively on Windows ARM devices, including Snapdragon-based PCs. The document list includes Robin Murphy's MetaRepertory, Nature's Materia Medica Fourth Edition, a Japanese Synthesis Treasure edition, QRep V5, Suggesta 2.0, new provings, and other content. Analysis changes include improved clipboard performance, a select-all-rubrics shortcut, sharper repertory and materia medica rendering, and fixes for crashes, searches, family limitations, rubric movement, and Personal Materia Medica work.

The technical section says RadarOpus moved to Qt 6.10, updated CodeMeter, introduced new communication libraries, and disabled importing some obsolete Radar 10 and legacy WinCHIP formats. Those changes can improve compatibility and maintenance, but they also make a controlled upgrade test important for a clinic with old files or a customized setup.

The current official US add-on catalogue displayed the MetaRepertory at $204 and the EKAP GPS module at $360 when reviewed on 24 July 2026. The catalogue is linked below. Those prices are snapshots for named add-ons, not a quote for a complete RadarOpus configuration or a promise that the content is included in every 4.2 license. Taxes, region, dealer offers, existing entitlements, package level, and future changes can alter the total.

Where RadarOpus 4.2 is genuinely stronger

RadarOpus has a mature desktop environment built around named repertories, materia medica collections, patient files, analysis tools, expert modules, and a large optional library. Version 4.2 extends that environment instead of asking an existing user to rebuild the clinic's working method in a different product. That continuity is a concrete advantage when a practitioner has years of saved analyses, custom views, trained habits, licensed books, and staff procedures.

The new native Windows ARM support is also specific and testable. A clinic considering a current Surface or another Snapdragon computer can install the approved version on that exact device and measure startup, search, analysis, printing, backup, and restore behavior. Native support is more meaningful than a generic Windows logo when the processor architecture has changed.

The release is unusually transparent about fixes. Search, clipboard, crash, rendering, and Personal Materia Medica corrections describe practical defects that an existing user can retest. A long list of fixes does not prove that every workflow is defect-free, but it gives a clinic a reproducible upgrade checklist.

RadarOpus remains the stronger fit when the primary requirement is a licensed, installed source library with detailed manual analysis, offline continuity, specialized modules, and a known desktop workflow. The official US packages page, linked below, describes lifetime licenses, offline use, customizable packages, training, and support. Verify those terms for the actual region and package because dealer arrangements can differ.

What the 4.2 update does not answer

The release does not turn RadarOpus into a note-first workflow by itself. The new documents and fixes improve the repertory environment, but a practitioner still needs a reliable process for preserving the patient's original language, deciding which details matter, translating them into candidate rubrics, recording rejected interpretations, and explaining later why a differential changed.

The release also does not settle migration automatically. The notes say some obsolete import paths are disabled. A clinic with old Radar 10, legacy WinCHIP, unusual character sets, external media, or dealer-installed content should not infer that every historical file will open perfectly. Test copies first, retain the original application and backup, and obtain written vendor guidance for unsupported formats.

Nor does the version number prove that every add-on shown in release notes is included. Separate catalogue entries, package entitlements, content updater items, and free program updates can have different licensing rules. Ask for an itemized manifest that names the program version, repertories, materia medica, modules, languages, devices, and support terms.

Where Homeo AI is the better fit

Homeo AI is the more direct fit when the recurring cost occurs between the consultation and the repertory. Its workflow begins with narrative notes, proposes a structure that the practitioner can edit, exposes candidate mappings and source passages for review, supports a documented differential, and keeps the reasoning visible during follow-up work.

That emphasis is useful when the clinic wants to measure interpretation rather than library size. A practitioner can inspect whether location, sensation, modality, chronology, intensity, and qualifiers survived the conversion from ordinary language. A proposed rubric can be accepted, corrected, or rejected. The useful outcome is not more generated text. It is a reviewable path that another practitioner can understand.

Homeo AI does not claim to provide every licensed RadarOpus source or specialist module. A combined workflow may be appropriate: Homeo AI for note structuring and documented review, then RadarOpus 4.2 for the clinic's licensed analysis environment. The handoff must preserve original wording, accepted mappings, source identity, and corrections without creating two conflicting case records.

Side-by-side decision

| Decision area | RadarOpus 4.2 | Homeo AI | | --- | --- | --- | | Primary change | Desktop suite update with new content, Windows ARM support, improvements, and fixes | Note-first case structuring, source review, differential documentation, and follow-ups | | Best fit | Existing RadarOpus users and clinics needing deep installed libraries and analysis modules | Clinics trying to reduce narrative-to-rubric translation and review friction | | Deployment | Installed Windows or macOS software with package and content entitlements | Browser-based copilot workflow | | Source model | Licensed repertories, materia medica, documents, and optional modules | Reviewable mappings and source passages inside a guided workflow | | Main proof needed | Upgrade compatibility, exact entitlement, source manifest, backup, restore, and file continuity | Mapping accuracy, correction time, source traceability, and follow-up continuity |

A reproducible upgrade and workflow test

Prepare ten completed, de-identified cases from the clinic's normal mix. Remove names, contact details, dates of birth, faces, document numbers, exact visit dates, and rare combinations that could identify a person. Keep an answer sheet outside both tools with the original narrative, the practitioner's accepted totality, sources checked, corrections made, and documented reason for the final differential.

First clone the RadarOpus working environment or use a supported test machine. Record the installed version, license, content manifest, operating system, processor, storage, and backup checksum. Upgrade the copy to 4.2. For each case, verify patient-file opening, attachments, searches, saved analyses, custom views, source citations, printing, and export. Test a backup restoration on a second approved environment. If the clinic is evaluating Windows ARM, run the same checklist on the actual ARM device.

Then submit the same de-identified narratives to Homeo AI. Record the proposed symptom structure, accepted and rejected mappings, source passages inspected, correction time, and whether a second practitioner can reconstruct the final reasoning. Reopen half the cases as follow-ups and check that baseline facts remain separate from new observations.

Score both workflows on:

1. Minutes to a reviewable analysis. 2. Material interpretation errors. 3. Missing or mismatched sources. 4. Time to correct an error. 5. Historical file and attachment continuity. 6. Backup and restore success. 7. Clarity for a second practitioner. 8. Follow-up continuity. 9. Total three-year software, content, support, and administration cost.

This test can show that the products belong at different stages. Do not force a single winner if one is the stronger installed library and the other is the stronger note-review layer.

Privacy, safety, and known limits

RadarOpus publishes detailed data-protection settings on its version-history page, including encrypted patient data and backups, password controls, printing, and deletion functions. A clinic still needs to test how those settings behave in its version and jurisdiction. Local installation reduces some cloud dependencies but does not secure an unencrypted device, weak account, exposed backup, remote-support session, or copied export.

Homeo AI also requires a clinic-specific privacy review. Confirm who can access records, what is retained, where processing occurs, how deletion and export work, and what happens during a service interruption. Use de-identified material until the clinic has approved the data path.

Both products can produce incomplete, outdated, or incorrectly interpreted information. The presence of a repertory entry, source passage, ranked result, or AI suggestion does not establish a diagnosis or validate a clinical decision. Neither tool should make an emergency-care decision or replace diagnosis, referral, emergency care, practitioner judgment, prescription, potency, dosage, or follow-up responsibility.

Conditional verdict

Choose RadarOpus 4.2 if the clinic already relies on RadarOpus, needs the new Windows ARM or content support, and can prove that the upgrade preserves its licensed sources, files, analyses, backups, and working speed. Its advantage is continuity inside a deep professional desktop environment.

Choose Homeo AI if the larger gap is turning narrative notes into a transparent, correctable analysis path and preserving why choices changed over time. Its advantage must be demonstrated through fewer material translation errors, faster review, and clearer follow-up reasoning.

Use both only when the handoff is documented and avoids duplicate records. A new release is a reason to test the workflow again, not a reason to assume clinical or operational fitness.

Official sources checked

• RadarOpus official version history
• RadarOpus 4.2 official summary
• RadarOpus 4.2 official release notes
• RadarOpus US official packages
• RadarOpus US official add-on catalogue

Product facts reviewed 2026-07-24. Confirm current features, prices, source libraries, and terms with the vendor.