RxSmart.ai
Platform Engine Agents Economics Deployment FAQ

Medication-adherence Clinical Decision Support

Detect adherence decline before it becomes hospitalization.

Facility-grade, non-device clinical decision support for hospitals exposed to the CMS Hospital Readmissions Reduction Program. RxSmart.ai scores every enrolled patient every cycle and routes each finding to the right clinician, with the right action, inside the right window.

Request a pilot

Non-device CDS under Section 520(o)(1)(E) · Proprietary scoring engine · Every recommendation routes through a licensed clinician

What it is

A cloud-native adherence CDS — not a reminder app, not hardware.

RxSmart.ai turns signals your data already carries into a specific, time-bound clinical action for every patient. Five capabilities, one workflow.

A proprietary scoring engine

Produces a 0–100 adherence score per patient from missed doses, refill latency, polypharmacy, engagement, and cost barriers.

Four ratified risk tiers

STABLE, MONITOR, ALERT, and CRITICAL — each mapped to a distinct clinical action and response window, not a flat nudge.

Five specialized agents

Triage, Billing, Trends, Sentinel, and Copilot operate on your live cohort and report back for clinician review.

Tamper-evident audit chain

Every score, tier change, and action is sealed into an append-only SHA-256 ledger auditors and payers can verify.

EHR-only enrollment

Patients are imported via FHIR R4 from Epic, Cerner, and athenahealth. No hand-typed PHI.

Clinician in the loop

No score or agent acts on a patient alone. Every recommendation routes through a licensed clinician who decides.

The engine

Scores that route to action.

The engine reads signals your data already carries and computes a single 0–100 adherence score. The method is a proprietary scoring engine — the score, its tier, and the recommended action are shown; the formula is confidential.

Missed doses — frequency and recency of gaps
Refill latency — delay between due and fill
Polypharmacy — interaction and regimen complexity
Engagement — response and touchpoint patterns
Cost barriers — affordability signals that predict abandonment
TierScoreAction & window
STABLE70–100Routine monitoring
MONITOR50–69Watch at next touchpoint
ALERT25–49Pharmacist outreach < 72h
CRITICAL0–24Coordinator / physician < 24h
NO DATA—Verify enrollment / source

Thresholds are operationally ratified and under prospective pilot validation — not represented as clinically validated cut-points.

See it work

Move the signals, watch the tier and action change.

An illustrative demonstration of how signals map to a tier and a clinical action. This demo uses simplified illustrative math — not the proprietary scoring engine.

Missed doses (last 30 days)2
Refill latency (days late)3
Active medications4
Connected RPM deviceNo
78
STABLE
Routine monitoring — no outreach required.
Device-free — time-based coding only

Illustrative only — not the proprietary scoring engine and not a guarantee of any score or payment.

The five agents

Purpose-built minds on your live cohort.

Each agent does one job and reports back for clinician review. Agents inform — they never act on a patient without you. They operate only inside the platform, on your enrolled cohort, after sign-in.

Triage

Ranks the cohort by escalation urgency and drafts the day's outreach worklist.

Billing

Reviews device-supply eligibility (99445 / 99454) and time-based capture (99470 / 99457 / 99458), flags missing interactive-communication documentation, and surfaces the RPM / RTM distinction for your certified coder.

Trends

Surfaces adherence trajectories — who is declining before they cross a tier boundary.

Sentinel

Watches for co-firing risk patterns that historically precede readmission, and for data-integrity gaps.

Copilot

Answers staff questions about the live cohort in plain language for nurses and care coordinators.

Economics

A flat fee, designed to be offset by reimbursement.

RxSmart.ai charges a flat $45 per patient per month. It is designed so that CMS remote-monitoring reimbursement can offset that fee. All figures below are illustrative — subject to the current CMS Physician Fee Schedule and geographic adjustment, and not a guarantee of payment.

Enrolled patients250
Share on a connected RPM device60%

Connected-device patients (transmitting ≥16 of 30 days) support CPT 99454 + time-based 99457/99458. Device-free (self-report / pharmacy-fill) patients are billed under time-based codes only; self-reported adherence commonly maps to RTM codes — confirm the mapping with your certified coder.

150
Device-eligible patients — 99454 candidates
100
Device-free patients — time-based review

Illustrative counts only — varies by locality and code family; not a guarantee of payment. Your facility’s certified coder applies its own locality rates — confirm every code with your certified coder.

Where it fits

Different from a reminder app, a pill bottle, or an EHR module.

CapabilityRxSmart.aiReminder appSmart bottleEHR module
Computes clinical risk (0–100 score)YesNoPartialPartial
Time-bound action per tierYesNoNoPartial
Tamper-evident audit chainYesNoNoNo
Reimbursement-aligned billing supportYesNoPartialPartial
Hardware requiredNoNoYesNo

General category comparison for orientation only; individual products vary. RxSmart.ai is non-device CDS under Section 520(o)(1)(E) and is not FDA approved, cleared, or authorized.

Deployment

From signature to first scored cohort in about a week.

1

Sign the BAA (days 1–2)

A standard, attorney-reviewed Business Associate Agreement. No data is connected before it is executed.

2

Connect your data via FHIR (days 3–5)

Authorize RxSmart.ai against your FHIR R4 endpoint with read-only scopes; your tenant is provisioned on encrypted infrastructure.

3

First scoring pass (day 6)

Every enrolled patient is scored and tiered; the worklist is triaged on first login.

4

Operate & bill (week one)

Clinicians work the tiers; billing-eligible encounters are staged with documentation and audit provenance.

Request a 30-day pilot

Training

Your team is onboarded inside the platform.

An interactive clinical training library — modules, knowledge-check questions, and saved progress — maps each concept to a workflow: the tiers and escalation windows, the routing rules, the billing distinction, FHIR enrollment, MemoryAnchor framing, and audit-chain review.

Tiers & windows

How the ratified bands map to a 72-hour or 24-hour clinical action, and the override workflow.

Billing workflow

The CY2026 code set, mutual exclusivity, the interactive-communication rule, and the RPM / RTM distinction.

FHIR & audit

Enroll via the EHR with no hand-typed PHI, and verify the SHA-256 chain before compliance review.

Inside the platform

A worklist ordered by clinical urgency.

After sign-in, the cohort surfaces highest-need patients first — NO DATA, then CRITICAL, ALERT, MONITOR, STABLE.

RxSmart.ai · Cohort worklist (illustrative)
Patient — CHF
missed 11 / 30 · 12 days late
CRITICAL 18
Patient — T2DM
missed 6 / 30 · 5 days late
ALERT 41
Patient — COPD
missed 3 / 30 · on device
MONITOR 61
Patient — HTN
missed 1 / 30 · on device
STABLE 88

MemoryAnchor

A cognitive memory buffer — cognitive support, not treatment.

For patients who struggle to remember, MemoryAnchor holds the patient's profile, people, medications, and routine, and returns them on demand — with a patient link and a caregiver link, and weekly adherence monitoring that routes to the care team. It is cognitive support, not treatment: it does not treat, restore, or cure dementia or Alzheimer's disease, and it is not a substitute for clinical care.

FAQ

Questions hospitals ask.

How is the score different from MPR or PDC?
MPR and PDC are retrospective, aggregate ratios. The engine combines multiple live signals into a prospective, per-patient 0–100 score that routes to a specific clinical action each cycle. We are building pilot data to demonstrate comparative performance; we do not claim the score outperforms PDC without that study.
Is it HIPAA-aligned?
A Business Associate Agreement is signed with each facility before any data is connected; no patient data is connected until a Business Associate Agreement is executed with every subprocessor, and every action seals to a tamper-evident SHA-256 audit chain.
Does it replace our EHR?
No. RxSmart.ai reads from your EHR via FHIR R4 and supports clinicians; it is not a system of record.
What does the Section 520(o)(1)(E) exemption apply to?
It applies to the software's status as non-device Clinical Decision Support: the clinician remains the decision-maker, and RxSmart.ai is never described as FDA approved, cleared, or authorized.
What happens to our data if we cancel?
Your tenant data is handled per the Business Associate Agreement and the data-handling terms agreed at signing.
Who built RxSmart.ai?
Bionectech, Inc. (Texas) and Bionectech AI, LLC (Maryland).

Honest status

What is live today — and what is on the roadmap.

Live in production

  • Cohort dashboard, patient roster, and admin console
  • Scoring engine with the ratified four-band tiering and NO-DATA handling
  • Five-agent console and MemoryAnchor cognitive memory buffer
  • JWT authentication and role-based access control
  • SHA-256 append-only audit chain
  • CPT staging for the CY2026 code set (99445 / 99454 device tiers; 99470 / 99457 time tiers (mutually exclusive); 99458 add-on only after 99457 is met) with interactive-communication capture — RPM vs RTM set by your certified coder
  • Discharge medication-reconciliation view (FHIR-computed)
  • FHIR R4 patient import (Epic, Cerner, athenahealth)
  • Interactive clinical training library

On the roadmap

  • SMS / IVR outreach
  • Connected smart-dispenser (BLE) device pairing
  • EDI 837P batch billing export (CSV export available today)
  • Caregiver mobile companion app

Get started

Run a zero-cost 30-day pilot.

Sign a standard BAA, connect a data feed, and the engine scores your first cohort within a week. If you decide not to continue, no invoice is sent.

Request a pilot
RxSmart.ai

RxSmart.ai is non-device Clinical Decision Support under Section 520(o)(1)(E) of the FD&C Act. It is not FDA approved, cleared, or authorized. Every recommendation routes through a licensed clinician. Adherence scores are produced by a proprietary scoring engine. Reimbursement figures are illustrative and subject to the current CMS Physician Fee Schedule and geographic adjustment.

Bionectech, Inc. (Texas) · Bionectech AI, LLC (Maryland) · info@bionectech.com

Product

PlatformEngineEconomics

Company

Contact
RxSmart.ai

Clinician platform

Detect adherence decline before it becomes hospitalization.

Sign in with your facility credentials.

RxSmart.ai is non-device Clinical Decision Support under Section 520(o)(1)(E) of the FD&C Act. Every recommendation routes through a licensed clinician. Adherence scores are produced by a proprietary scoring engine.

RxSmart.ai
Non-device CDS under Section 520(o)(1)(E).
Proprietary scoring engine.

Cohort Dashboard

Engine
-

HRRP cohort

Cohort Dashboard

Risk worklist ordered by clinical urgency. Scores from the proprietary scoring engine; every action routes through a clinician.

Cohort median score
-
Proprietary scoring engine, 0 - 100
Critical alerts
-
24-hour coordinator / physician escalation
Time-based queue
-
Device-free, Alert/Critical - IC verification pending
Active patients
-
Enrolled via FHIR R4 import

Risk worklist

Ordered: No data - Critical - Alert - Monitor - Stable
PatientScoreTierAction & windowBilling
Loading cohort -

Score distribution

Ratified bands

Live alert stream

Alert and Critical tiers
No active alerts

Cohort

Patients

All patients are enrolled via FHIR R4 import from the EHR. Manual entry is disabled facility-wide.

PatientMRNScoreTierSignal sourceBilling
Loading -

Posted to patient - awaiting clinician review

Result Triage Queue

Finalized results the laboratory has already posted to the patient that no clinician has acknowledged yet - surfaced here as one passive worklist. RxSmart.ai surfaces and routes; it never interprets a result. The laboratory's interpretation flag is rendered verbatim.

Sorted by time since posting - oldest first. Order reflects elapsed time only, never clinical severity.
PatientResultLab interpretation flagTime since posting
Loading result queue -

Critical values are handled by the laboratory's existing critical-value notification policy - a direct call from the lab, not this queue. This worklist is passive and does not replace that policy.

FHIR R4

EHR Enrollment

Enrollment is EHR-only. Connect your EHR, search for the patient, and import the record - patient, active medications, and active conditions.

Manual patient entry is disabled facility-wide and rejected by the backend. All PHI enters through the FHIR import path only - no hand-typed demographics.
1 Connect EHR
2 Search patient
3 Import

Select your EHR

Read-only FHIR R4 scopes

Search patient

Connected

Agent console

Five agents on your live cohort

Each agent does one job and reports back for clinician review. Agents inform - they never act on a patient without you.

Triage

Ranks the cohort by escalation urgency and drafts the outreach worklist.

Not yet run.

Billing

Reviews device-supply and time-based capture; flags missing interactive-communication documentation for your certified coder.

Not yet run.

Trends

Surfaces adherence trajectories - who is declining before crossing a tier boundary.

Not yet run.

Sentinel

Watches for co-firing risk patterns that historically precede readmission, and for data-integrity gaps.

Not yet run.

Copilot

Answers staff questions about the live cohort in plain language.

Not yet asked.

Agent outputs are decision support for licensed clinicians - not orders, not diagnoses.

Cognitive Memory Buffer

MemoryAnchor

Provision a per-patient buffer - profile, people, medications, routine. It generates a patient link and a caregiver link, persists server-side, and monitors weekly adherence for the care team.

Provision buffer

Access links

Generated on provisioning; weekly adherence monitoring routes to the care team.
Patient link
-
Caregiver link
-
No buffer provisioned in this session yet.

Caregiver access

Server-issued companion links for the selected patient - copy and send. The patient link is for the patient; the caregiver link is for a family member or carer.
Patient link - for the patient
-
Caregiver link - for a family member or carer
-
MemoryAnchor is cognitive support, not treatment. It holds the patient’s memory externally - profile, people, medications, routine - and returns it on demand. It does not treat, restore, or cure dementia or Alzheimer’s disease, and it is not a substitute for clinical care.

Tamper-evident ledger

Audit Chain

Every score, tier change, acknowledgment, and override is sealed into an append-only SHA-256 chain. Verify integrity before compliance review.

Not yet verified this session.
SeqTimestampEventHash
Run verification to load the chain.

Clinical training library

Training

Interactive modules with knowledge checks. Progress is saved on this device.

0 lessons complete