Five communications make a digital clinic.
LIVIT is really a chain of five connected conversations — device to phone, phone to patient, phone to server, server to pharmacy, and server to the prescription record. Each link has a job, an interface, and a billing code.
The architecture — five links
The whole platform is one signal moving through five communication links and back again. The diagram below is the map; each link is detailed underneath with its app screen and the CPT code it supports.
Reference architecture (from the patent)
The patent's system figure shows the same flow in clinical detail. Read it as a loop, pharmacy → patient → cloud → care team:
- Pharmacy setup — the medication-monitoring device is activated and calibrated at the pharmacy, then shipped to the patient.
- Patient edge — the device + vitals patch + mobile app capture dose and vitals data.
- Cloud — data syncs to the cloud computing infrastructure: a data-processing engine and a database.
- Servers & analytics — the cloud feeds the servers (data transfer) and an analytics layer.
- Caregiver portal — the pharmacist/care team works in the patient–caregiver portal application.
Link 1 — Hardware ↔ Phone app
The medication device (load-cell scale) and the vitals patch send their readings to the phone over Bluetooth / Wi-Fi / 4G. The phone activates and pairs the device — fingerprint + barcode/ship-address verification — and receives the dose and vitals events at the edge.
- Pair & activate the device (biometric + barcode).
- Receive dose / weight-change events and vitals.
- Buffer offline; forward when connected.
Link 2 — Phone ↔ Patient
For the patient, the app is purely about three things — their compliance data, their vitals, and a direct line to the pharmacist by text or video. No clutter.
Compliance data
Doses taken vs prescribed, missed-dose and over-dose alerts, refills — a clear daily and 30-day view.
Vitals
Heart rate, oxygen, temperature and activity from the patch — trends the patient can actually see.
Pharmacist — text or video
A direct, two-way line to the pharmacist/care team: message or video call, no office visit.
Link 3 — Phone ↔ Server
The phone syncs events to the cloud computing infrastructure — a data-processing engine and database — which stores each patient's record securely, applies the adherence algorithms, and returns the schedule and any status changes.
- Secure per-patient cloud accounts; encrypted in transit & at rest.
- Aggregation + algorithms → adherence, compliance, effectiveness, drug-performance.
- Counts the 16+ days of data per 30-day cycle that billing requires.
Link 4 — Server ↔ Pharmacy (pharmacist team)
The provider console is where the work — and the billing — happens. The pharmacist team monitors many patients at once, sees compliance reports and over-utilization alerts, and reaches out: the interactive communication and time that treatment-management billing requires.
- Multi-patient dashboard; compliance & over-utilization reports.
- Interactive communication (call / message / video) — logged with time.
- Medication review: assess compliance & reactions, evaluate new meds.
Link 5 — Server ↔ Specialty-pharmacy prescription data
The platform integrates with the specialty pharmacy's prescription / dispensing system: at the pharmacy the device is activated and the regimen is synced (drug, dose, schedule, refills), and the patient's cloud account is linked to the pharmacy's provider database. That prescribed schedule is the baseline every adherence calculation runs against.
- Regimen sync at dispensing — drug, dose, frequency, special instructions.
- Refill & next-fill data; reconciliation after changes.
- Links the cloud account to the pharmacy provider database.
CPT reference
The codes used across the five links, in one place. Informational only — who may bill, eligibility, and payer rules vary and change; pharmacist billing of these is nuanced. Verify with a billing/compliance specialist.
| CPT | What it covers | Link |
|---|---|---|
| 98975 | RTM initial set-up & patient education ("therapy adherence, therapy response") | 1, 2 |
| 98976 / 98977 / 98978 | RTM device supply (respiratory / MSK / CBT) — 16+ days of data per 30 | 1, 3 |
| 98980 / 98981 | RTM treatment management — 20 min + interactive contact / month | 4 |
| 99605 / 99606 / 99607 | Pharmacist Medication Therapy Management (compliance & reactions) | 4, 5 |
| 99453 / 99454 / 99457 / 99458 | Remote Physiologic Monitoring (RPM) — for patch vitals | 1, 3 |
Security & compliance
- HIPAA-compliant communication & storage across every link, with Business Associate Agreements (2018–2019).
- Authentication — biometric + barcode/ship-address verification at activation; secure per-patient cloud accounts.
- Hardened infrastructure — servers and healthcare security built out as real specialty-pharmacy clients onboarded.
- Build sequence — software design (2017) → Software v1 + servers/HIPAA/security (2018) → refinements, mini-trials, training (2019).
Documented in PCT drawing sets — the LIVIT Mobile App and Patient-Caregiver (PCC) Portal (draft / unfiled). Built with development partner Imaginovation alongside SharkDreams engineering.