Transparent pricing for clinical programs at every scale.
Three tiers designed around enrolled patient volume. All plans include the Lyra Alert Engine, CPT monitoring-minutes documentation workflow, HL7 FHIR R4 data integration, and a Business Associate Agreement.
- 3 device class integrations (glucose, BP, weight)
- Lyra Alert Engine — 30-day readmission risk scoring
- CCM billing workflow — CPT 99453/99454/99457/99458
- HL7 FHIR R4 data feed
- Email alert notifications
- BAA included
- Self-guided onboarding + 2 training sessions
- Everything in Community, plus:
- Unlimited device integrations
- Custom alert threshold configuration by condition
- SMART on FHIR EHR integration
- Population-level analytics dashboard
- Monthly CPT billing summary reports
- Dedicated clinical success manager
- Priority support (4-hour response)
- Everything in Clinical, plus:
- Multi-site deployment
- Custom EHR integration scope
- Dedicated implementation team
- SLA-backed uptime commitment
- Executive reporting & QI dashboard
- On-site training options
- Quarterly clinical outcomes review
All plans include a Business Associate Agreement. Published ranges are indicative — final pricing depends on patient volume, integration scope, and support level. RPM reimbursement from CPT 99454 + 99457 + 99458 typically offsets platform cost at sustained enrollment rates.
Pricing questions from health system procurement
RPMLyra pricing is structured per actively enrolled patient per month. This aligns with your CPT reimbursement — you pay for the patients generating billable readings. There are no per-reading fees or alert charges.
The economics are designed so that RPM reimbursement (99454 + 99457 + 99458) exceeds platform cost at average engagement rates. However, each health system's billing capacity and payer mix are different — we'll walk you through the math for your specific patient panel in a demo.
Yes. A BAA is required before you enroll any patients, and we execute BAAs as part of standard contract setup for all tiers. Our BAA template addresses PHI handling, breach notification obligations, and permitted uses.
Pilot tier includes structured onboarding: IT environment scoping, FHIR integration configuration, staff training, and a dedicated support contact for the first 90 days. Clinical and Enterprise tiers include a named clinical success manager throughout the contract.
Pilot tier without EHR integration: 2–3 weeks from contract to first patient enrollment. With FHIR R4 EHR integration: 4–8 weeks depending on EHR configuration. We've designed the integration layer to minimize your IT team's involvement — typically 10–15 hours of configuration work.