RxPertise
An established MRR system still supported while Framework RxP is positioned as its web successor
RxPertise remains relevant because it has a live support presence and a meaningful installed base. MHA continues to describe its clinical consulting software around State Operations Manual alignment, interfaces, and reporting, while SoftWriters maintains product support and calls Framework RxP the web-based successor. It should be evaluated as a current workflow and migration decision—not casually labelled discontinued.
What the public record says
The current MHA page still presents RxPertise-related clinical consulting software for long-term care, with State Operations Manual alignment, interfaces, and robust reporting. SoftWriters' support page offers a knowledge base, tutorials, product ID status, version downloads, tickets, call-center support, and technical requirements—evidence that the product is actively supported in some form.
RxPertise also has a documented bridge into the Framework ecosystem. SoftWriters describes FrameworkExchange as a web service that allows RxPertise to retrieve FrameworkLTC data in real time. That matters to an installed user connected to FrameworkLTC, but it does not establish a general integration catalog outside that environment.
The right comparison is often migration-oriented. SoftWriters calls Framework RxP a web-based successor to RxPertise. That wording is useful context, not a forced verdict: some organizations value a mature installed workflow, while others need browser access, modernization, or a future implementation path. Get the vendor's current licensing and support horizon in writing.
Evidence we found
Current support channel
SoftWriters provides RxPertise support resources including tutorials, downloads, ticketing, call-center support, and technical requirements.
LTC consulting and reporting positioning
MHA's current solution page describes clinical consulting software with State Operations Manual alignment, interfaces, and robust reports.
FrameworkLTC data route
SoftWriters describes FrameworkExchange as a way for RxPertise to retrieve FrameworkLTC data in real time.
Where a buyer should slow down
Support does not answer new-sale status
A current support page is strong evidence that existing customers remain supported, but it does not identify which new licenses, editions, or commercial paths are available today. Ask directly.
Installed-software characteristics need current validation
Version downloads and technical requirements indicate installed-software characteristics. Historical Enterprise material should not be used as proof of current architecture, collaboration, or operating-system support.
Fit by operating model
One- and two-person practice
Most relevant to existing workflows.
- A current RxPertise user may value continuity, support, and a familiar process.
- New solo buyers should confirm licenses, setup, system requirements, and migration alternatives before assuming it is a lightweight path.
Validate: New-license availability · Current technical requirements · Support scope · Data export
Larger organization
A migration and ecosystem question.
- Installed base, support, reporting, and FrameworkLTC data retrieval can be material for larger pharmacy organizations.
- Current multi-site, security, and roadmap details need direct evidence.
Validate: Edition and architecture · FrameworkLTC dependency · Migration to RxP · Support horizon
Questions to take to the demo
- Which RxPertise editions can be newly licensed today, and what is the support horizon for ours? Current support for an installed base is different from current new-customer availability.
- What infrastructure, operating system, and data-backup responsibility applies to our edition? The answer affects security ownership, maintenance, and remote access.
- What data, reports, and audit history can move to Framework RxP, and what changes in the workflow? A migration decision is safer when data and operating implications are concrete.
Public comparison detail
LTC MRR
Yes
Current MHA materials position it as LTC clinical consulting software.
Buyer prompt: Is the workflow designed around recurring consultant-pharmacist review?
Deployment
Installed characteristics; current edition to confirm
Support includes version downloads and technical requirements. Confirm exact current architecture.
Buyer prompt: Is it browser-based, installed, or dependent on another pharmacy platform?
Reviews
LTC consulting workflow
The current MHA page describes consulting alignment but does not enumerate review types.
Buyer prompt: Which monthly, admission, interim, and other review types are publicized?
Recommendations
Not publicly specified
Current public detail about templates and recommendation routing is limited.
Buyer prompt: How does the product create, reuse, route, and standardize recommendations?
Follow-up
Not publicly specified
The reviewed current pages do not describe outcome tracking.
Buyer prompt: Can pharmacists record responses and find recommendations still awaiting action?
Psych / GDR
Not publicly specified
The reviewed current pages do not describe dedicated psychotropic or GDR workflow.
Buyer prompt: What medication-use and gradual dose reduction support is publicly described?
Analytics
Robust reporting claimed
MHA calls out robust reports; current dashboard and QAPI detail is not published.
Buyer prompt: Can leaders see trends beyond one resident or one report packet?
Integrations
FrameworkLTC data retrieval described
FrameworkExchange is described for RxPertise and FrameworkLTC; broader connector coverage is not public.
Buyer prompt: Which dispensing, EHR, eMAR, HIE, and lab connections are actually identified?
Reporting
Robust reports claimed
Current report type, format, and distribution detail should be requested.
Buyer prompt: Which report audiences, formats, routing, and delivery methods are described?
Collaboration
Not publicly specified
Historical enterprise collaboration should not be treated as a current capability without confirmation.
Buyer prompt: How does work move between pharmacists, facilities, and prescribers?
Controls
Not publicly specified
Current public role and audit-control detail is not stated.
Buyer prompt: What role, activity-log, and administrative controls does the vendor state publicly?
Business tools
Not publicly specified
No public consultant timekeeping, invoicing, or billing function was identified.
Buyer prompt: Does the public product include timekeeping, invoicing, claims, or client billing?