Start with the live evidence, not the label
SoftWriters' live RxPertise Help Center offers a knowledge base, current-software downloads, tutorials, tickets, update emails, and support contacts. A Product ID lookup returns the license's maintenance status and end date. SoftWriters describes that date as a renewal marker—not a public product-retirement date.
MHA's undated public page says RxPertise serves existing and prospective users and receives enhancements. Treat that as vendor positioning, not independent performance evidence. ‘Maintained,’ ‘supported,’ ‘sold to new customers,’ and ‘strategically preferred’ are separate statuses; obtain each answer for the actual account.
A named successor is direction—not a deadline or parity claim
SoftWriters calls Framework RxP a built-from-the-ground-up, web-based successor. Its AmPharm case study also shows that one RxPertise-to-Framework RxP conversion occurred. That proves a path has been used—not parity for another account. The vendor-selected story supplies no public field map, exclusions, reconciliation results, fees, downtime, or rollback detail, and the customer also changed staffing and used the wider Framework suite.
Request a one-page statement covering maintenance term, support and escalation, updated versions, added-user or new-license availability, and any retirement milestone. A successor label is product direction; a renewable maintenance date is not a roadmap commitment.
The operating-system question now deserves a written answer
SoftWriters' public requirements, last modified in December 2023, describe RxPertise 9.2 on Windows 10. Standard is installed locally on one computer rather than as a server-client or remote multi-user system; periodic internet supports updates and license checks. The page also says a 9.1 database upgraded to 9.2 cannot be taken back to 9.1. Useful discovery facts are not a current compatibility statement for every edition.
Ordinary Windows 10 support ended on October 14, 2025, although LTSC and Extended Security Update arrangements differ. That does not prove RxPertise is insecure or unsupported. It means the practice should document its Windows edition and servicing channel, approved RxPertise version, and ownership of patching, backup, recovery, endpoint protection, remote access, and hardware replacement with the vendor and qualified IT advisers.
Map the data route before comparing screens
FrameworkExchange lets RxPertise retrieve FrameworkLTC data in real time. A separate Consulting Software Interface exports demographics and orders from FrameworkLTC to a DAT file for third-party consulting software. Neither description proves that RxPertise can export its review history or that a broad catalog of EHR, eMAR, laboratory, or dispensing interfaces exists.
For the actual account, map source and version, facilities, fields, direction, refresh, matching, corrections, failure visibility, history, and owner. A modern replacement can lose a dependable route; preserving an interface is insufficient if review, handoff, or reporting no longer fits.
Define migration in layers
A resident count is the weakest possible conversion result. Build an inventory across six layers: facility and resident master data; medication and clinical context; recommendation, response, and status history; attachments and report artifacts; templates and facility configuration; and provenance such as author, recipient, source identifier, and timestamps. Mark each item as converted, archived for reference, rebuilt, or unavailable.
Protect work in flight: open recommendations, urgent items, reports due during cutover, coverage handoffs, and unreconciled corrections. Name the authoritative system, freeze point, late-change process, production approver, and rollback threshold.
Get seven answers before choosing continuity or migration
- Identity: Which edition, version, Product ID, database, operating system, and deployment pattern are actually in use?
- Commitment: What maintenance, updates, response times, escalation, and support dates apply to this account?
- Commercial path: Can the practice add users, devices, facilities, or licenses, and on what current terms?
- Data route: What supplies current resident and medication information, and what exact mechanism would replace it?
- Exit: Which structured data, readable reports, attachments, identifiers, configuration, and audit information can be exported?
- Conversion: What transfers, what changes meaning, what does not transfer, who resolves exceptions, and what fees apply?
- Acceptance: Do active, inactive, pending-response, GDR, corrected-report, attachment, and multi-author records all reconcile before cutover?
Make the decision from demonstrated operating fit
Run the same resident through both workflows: refresh source data, review, route a recommendation, record response and rationale, retain follow-up, correct a released report, hand off coverage, and export. Score observed behavior separately from vendor claims and planned configuration.
Staying may be proportionate for one practice; Framework RxP or another product may fit another. The defensible decision rests on maintained support, a viable endpoint, a dependable data route, and demonstrated conversion fidelity—not a brand-status label.