Interfaces
Name the system, version, fields, direction, cadence, failure handling, source of truth, cost, and test plan. “HL7 ready” and a one-time conversion are not a live operational feed.
Multi-site, integration-heavy, or formally governed
The review screen matters. The interface, implementation, role design, reporting, and recovery path matter just as much once several pharmacists and facilities rely on the same system.
Do not classify the organization by seat count alone. A two-person practice that must ingest live pharmacy data and satisfy a facility security review belongs in this conversation; a larger group with a stable manual workflow may not need every enterprise feature.

The procurement brief
Public vendor pages are a starting point. A serious evaluation makes the promised workflow specific to the pharmacy systems, care settings, users, records, and legal terms that will exist after go-live.
Name the system, version, fields, direction, cadence, failure handling, source of truth, cost, and test plan. “HL7 ready” and a one-time conversion are not a live operational feed.
Specify what history moves, who cleans it, how report continuity works, how records are accepted, and what remains available in the retiring system.
Map pharmacist, technician, facility, leadership, and administrator access. Ask for offboarding, activity history, exports, authentication, and the evidence your own security reviewers need.
Get a named owner, a realistic timeline, training plan, acceptance tests, escalation model, and post-launch support terms. The strongest product can fail under an undefined rollout.
Products to investigate
These products make team, reporting, interface, migration, or implementation claims worth examining. The right result still depends on the exact scope demonstrated and contracted.
TrioMRR keeps review context, structured recommendations, outcomes, and facility-facing reports in one shared system. Its public story is strongest around straightforward MRR work, reusable reporting, team continuity, and migration from RxPertise.
Framework RxP is SoftWriters' cloud MRR product, with a public story centered on real-time FrameworkLTC data, consistent recommendations, consultant handoffs, and multi-facility reporting.
ConsultRx is a purpose-built MRR product with unusually specific public evidence around real-time dispensing data, electronic routing, automated follow-up, and managed implementation. Its public fit is strongest where a team has interface, conversion, and rollout work to solve—not merely a need for another review form.
RCShealth.io is the most explicit small-practice contender in the group. Its public page targets independent consultants and groups, combines MRR documentation with psychoactive medication work and reporting, and adds time tracking, invoicing, client billing, and activity export—business functions many clinical systems omit.
methodRx promotes a modern MRR workflow with dashboards, 600+ customizable templates, reassignment controls, role-based access, discipline-specific PDF reports, and QAPI visibility. Its public material is promising but internally inconsistent about availability: the same site says the product has launched and invites people to secure a place for a 2026 launch.
OpalCare sits slightly wider than a classic long-term-care MRR application. Its public positioning combines medication review, quality assurance, MTM, and comprehensive care management, with team coverage, tasks, historic reports, and claimed HIE, eMAR, EHR, pharmacy-system, and laboratory integration support.
GeriMed Profiles360 is a substantial MRR product that belongs in a serious comparison. Its current official material describes monthly consulting workflows, medication, disease, and lab management, CMS tools, dispensing imports, multi-consultant collaboration, 200+ customizable reports, inspections, benchmark tools, stewardship guidance, and clinical screening. Its current delivery model should be confirmed.
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.
| Product | LTC MRR | Deployment | Integrations | Reporting | Collaboration | Business tools | Pricing |
|---|---|---|---|---|---|---|---|
| TrioMRR | Yes — purpose-built The public product is organized around consultant-pharmacist medication regimen review in long-term care. | Cloud / browser The vendor states that the product runs in a browser on computers, tablets, and mobile devices with no local installation. | RxPertise conversion publicized Direct RxPertise conversion is publicized; no named live dispensing, EHR, eMAR, HIE, or lab connector was found on the reviewed pages. | Seven report types and multiple layouts Reports target leadership, prescribers, nursing, and operations, with reusable profiles and multiple resident-level layouts. | Shared database and coverage reassignment The vendor describes one source of truth for the team and reassignment when consultants cover another facility. | Not publicly specified The reviewed pages do not describe time tracking, invoicing, medical claims, or client billing. | $200/month for 1–2 users |
| Framework RxP | Yes — purpose-built SoftWriters markets Framework RxP specifically for the medication regimen review process. | Secure cloud platform The current product page describes Framework RxP as cloud based; SoftWriters calls it the web-based successor to RxPertise. | FrameworkLTC real-time data The product is positioned around real-time information within the FrameworkLTC ecosystem. Supported third-party connectors are not listed publicly. | Multi-facility reports Cross-facility reporting is public, but report types, formats, recipient routing, and archival behavior are not enumerated. | Contextual consultant handoffs The public page specifically identifies contextual notes for consultant handoffs and a collaborative approach. | Not publicly specified No RxP-specific consultant timekeeping, invoicing, or claims feature is public. Do not conflate broader Framework pharmacy operations with RxP. | Custom quote |
| ConsultRx | Yes ConsultRx is marketed as MRR software for consultant pharmacists and long-term care workflows. | SaaS The vendor calls ConsultRx a SaaS solution. | Real-time dispensing data claimed The vendor says it interfaces with dispensing systems for ADT and order data but does not name systems publicly. | Custom reports and electronic routing Custom reporting and discipline-specific report delivery are public features. | Clinician, pharmacist, and physician communication The product is positioned around electronic sharing and workflow communication. | Not publicly specified No public consultant timekeeping, invoicing, or client-billing feature was identified. | Pricing is not publicly listed |
| RCShealth.io | Yes The product is marketed for MRR and consultant pharmacist work. | Browser based The vendor describes browser access and automatic backups. | Dispensing-platform independent The vendor says it is not tied to a dispensing platform but does not name external data connections. | Multiple report scopes and export Patient, facility, organization reports and detailed activity-log export are described. | Real-time team sharing The public page names team data sharing across pharmacists. | Time, invoicing, and client billing This is explicitly described on the product page. | Pricing is not publicly listed |
| methodRx | Yes methodRx is explicitly marketed for consultant pharmacist MRR work. | Cloud accessible The vendor describes a cloud platform. | HL7 integration ready Readiness and partner language is public; active named connections are not. | PDF reports and direct email The product page names discipline-specific PDFs and direct email. | Real-time state sync and reassignment The vendor describes coverage reassignment and shared state. | Not publicly specified No public timekeeping, invoicing, client billing, or claims capability was identified. | Early-adopter pricing mentioned; amount not public |
| OpalCare | MRR within a broader clinical platform MRR is public, but the platform also covers QA, MTM, and care management. | Cloud based The vendor positions OpalCare as a cloud clinical platform. | HIE, eMAR, EHR, pharmacy, and lab support System categories and HIE-sourced notifications are public claims; named live partners are not. | MTM documentation and historical storage The vendor says CMS MTM documentation is generated during reviews and reports are stored automatically. | Shared coverage and care-team work The product page describes cross-pharmacist coverage and collaboration. | Not publicly specified The vendor discusses revenue and growth but no explicit timekeeping, invoicing, or claims feature was identified. | Pricing is not publicly listed |
| Profiles360 | Yes GeriMed positions Profiles360 around monthly consulting requirements for LTC settings and private consulting. | Current deployment to confirm Older official materials describe Windows desktop characteristics; current material does not specify the delivery architecture. | Dispensing-system imports Current materials name dispensing imports but do not list systems. | 200+ templates and transmission formats The vendor says reports are available in multiple transmission formats. | Multi-consultant data combination The current page describes combining consultant data. | Not publicly specified No current public timekeeping, invoicing, or billing feature was identified. | Current pricing is not public |
| RxPertise | Yes Current MHA materials position it as LTC clinical consulting software. | Installed characteristics; current edition to confirm Support includes version downloads and technical requirements. Confirm exact current architecture. | FrameworkLTC data retrieval described FrameworkExchange is described for RxPertise and FrameworkLTC; broader connector coverage is not public. | Robust reports claimed Current report type, format, and distribution detail should be requested. | Not publicly specified Historical enterprise collaboration should not be treated as a current capability without confirmation. | Not publicly specified No public consultant timekeeping, invoicing, or billing function was identified. | Pricing is not publicly listed |
Before a shortlist becomes a contract
Use the same representative facility scenario, source systems, user roles, report packet, exception, and migration question for every demo. Score whether the vendor demonstrated the workflow, scoped it for implementation, or left it open. That creates a decision record your clinical, operational, and security stakeholders can actually use.
Use the seven integration questions →