purpose built mrrAvailability to confirm

RxPertise by SoftWriters: software review and current status

An established SoftWriters MRR product with live support; new-license terms need confirmation

RxPertise is identified on MHA's current page as a SoftWriters MRR solution for consultant pharmacists. SoftWriters maintains live support and separately markets Framework RxP as its cloud MRR application, but the reviewed sources do not announce an RxPertise retirement or publish current new-license terms. Evaluate support, availability, technical fit, and migration as separate questions.

Long-term care pharmacy team reviewing a migration and reporting plan
Original editorial image; it does not depict a product customer or vendor interface.

RxPertise status snapshot

What current public sources establish—and what still needs a direct answer

Separate support, commercial availability, data connectivity, and migration evidence. They answer different questions, and none should be used as a shortcut for the others.

Support

Live support resources

SoftWriters maintains an RxPertise Help Center with knowledge-base material, current-software downloads, ticketing, maintenance-status checks, and support contacts.

Source: RxPertise Help Center

New-sale status

Confirm directly

The public support and clinical-consulting pages do not publish current edition-specific licensing, pricing, added-user terms, or a support horizon for a new account.

Sources: RxPertise Help Center · Clinical Consulting Software

FrameworkLTC data route

Real-time retrieval described

SoftWriters describes FrameworkExchange as a route for RxPertise to retrieve FrameworkLTC data in real time; that does not establish a broader connector catalog.

Source: FrameworkLTC Utilities

Web sources say:

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' Help Center offers a knowledge base, tutorials, Product ID status, current software downloads, ticketing, and support contacts-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 markets Framework RxP as a cloud-based MRR product and publishes an AmPharm case study describing one transition from RxPertise. That demonstrates one path in use, not parity or a required move: some organizations may value continuity with a mature installed workflow, while others need browser access or a different implementation model. Get the current licensing, support horizon, migration scope, and acceptance terms in writing.

Evidence we found

Current support channel

SoftWriters provides RxPertise support resources including tutorials, current software downloads, ticketing, maintenance-status checks, and support contacts.

Source: RxPertise Help Center

LTC consulting and reporting positioning

MHA's current solution page describes clinical consulting software with State Operations Manual alignment, interfaces, and robust reports.

Source: Clinical Consulting Software

FrameworkLTC data route

SoftWriters describes FrameworkExchange as a way for RxPertise to retrieve FrameworkLTC data in real time.

Source: FrameworkLTC Utilities

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.

Source: RxPertise Help Center

Installed-software characteristics need current validation

The Help Center's current-software downloads indicate installed-software characteristics. Historical Enterprise material should not be used as proof of current architecture, collaboration, or operating-system support.

Sources: RxPertise Help Center · FrameworkLTC Utilities

Fit by operating model

Specialized fit

Independent & small practice

Most relevant to existing workflows.

  • A current RxPertise user may value continuity, support, and a familiar process.
  • New independent-practice 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

Specialized fit

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

  1. 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.
  2. What infrastructure, operating system, and data-backup responsibility applies to our edition? The answer affects security ownership, maintenance, and remote access.
  3. 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.

Source: Clinical Consulting Software

Buyer prompt: Is the workflow designed around recurring consultant-pharmacist review?

Understand this feature

Deployment

Installed characteristics; current edition to confirm

The Help Center includes current-software downloads. Confirm the exact current architecture and technical requirements.

Source: RxPertise Help Center

Buyer prompt: Is it browser-based, installed, or dependent on another pharmacy platform?

Understand this feature

Reviews

LTC consulting workflow

The current MHA page describes consulting alignment but does not enumerate review types.

Source: Clinical Consulting Software

Buyer prompt: Which monthly, admission, interim, and other review types are publicized?

Understand this feature

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?

Understand this feature

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?

Understand this feature

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?

Understand this feature

Analytics

Robust reporting claimed

MHA calls out robust reports; current dashboard and QAPI detail is not published.

Source: Clinical Consulting Software

Buyer prompt: Can leaders see trends beyond one resident or one report packet?

Understand this feature

Integrations

FrameworkLTC data retrieval described

FrameworkExchange is described for RxPertise and FrameworkLTC; broader connector coverage is not public.

Source: FrameworkLTC Utilities

Buyer prompt: Which dispensing, EHR, eMAR, HIE, and lab connections are actually identified?

Understand this feature

Reporting

Robust reports claimed

Current report type, format, and distribution detail should be requested.

Source: Clinical Consulting Software

Buyer prompt: Which report audiences, formats, routing, and delivery methods are described?

Understand this feature

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?

Understand this feature

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?

Understand this feature

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?

Understand this feature

Clinical support

Not publicly specified

The reviewed current pages do not define medication screening, clinical-content sources, or decision-support logic.

Buyer prompt: Which medication, laboratory, diagnosis, screening, and guidance tools support-but do not replace-the pharmacist's judgment?

Understand this feature

Automation

Not publicly specified

The reviewed current pages do not describe configurable alerts, automatic reminders, or rules-based workflow.

Buyer prompt: Which recurring tasks, status changes, reminders, and exceptions can the product surface without hiding responsibility?

Understand this feature

Data portability

Migration and export scope to confirm

FrameworkLTC retrieval is described, and one vendor case study documents a move to Framework RxP, but complete export scope and migration fidelity are not publicly defined.

Sources: FrameworkLTC Utilities · AmPharm: Leveraging Technologies to Unlock Customer Service and Growth

Buyer prompt: Can the practice retrieve usable resident, review, recommendation, report, and audit data during operation and at exit?

Understand this feature

Implementation

Current support resources

The Help Center provides tutorials, downloads, ticketing, maintenance-status checks, and support contacts. Current implementation, training, and migration services depend on edition and should be confirmed.

Source: RxPertise Help Center

Buyer prompt: What help is available to configure, migrate, validate, train, launch, and support the product?

Understand this feature