Frequently Asked Questions
1. Which devices are compatible with your RPM platform?
We support a broad catalog of FDA-cleared and Health Canada-licensed devices, including blood pressure monitors, glucometers, SpO2 sensors, ECG patches, digital weight scales, and multiparameter wearables. Cabot maintains a rigorous validation framework: every device undergoes interoperability testing, encryption verification, and firmware review before being whitelisted. Because the platform is built on an extensible driver architecture, onboarding a new device family typically takes less than two weeks—no core code changes required. Over-the-air (OTA) firmware updates, remote troubleshooting tools, and lifetime device health analytics are also baked in, ensuring accuracy and longevity without burdening your clinical engineering team.
2. How do you ensure HIPAA compliance?
Compliance is engineered into every layer of the stack. All PHI is encrypted in transit with TLS 1.2+ and at rest with AES-256-GCM keys managed by an HSM. We enforce least-privilege, role-based access controls, MFA for all clinical users, and immutable audit logs retained for a minimum of six years. Annual SOC 2 Type II and HITRUST audits, quarterly penetration tests, and continuous vulnerability scanning verify that security controls remain effective. We execute Business Associate Agreements (BAAs) with all covered entities and hosting providers, and our DevSecOps pipeline automatically checks every code commit against the NIST 800-53 and OWASP Top 10 frameworks before release.
3. Can the solution integrate with our existing EHR?
Yes—interoperability is one of our core differentiators. We provide pre-built FHIR R4 and HL7 v2/v3 interfaces for Epic, Cerner, MEDITECH, Allscripts, and athenahealth. During discovery, our integration architects map your specific encounter types, observation codes (LOINC, SNOMED), and document templates to our canonical data model. We support a full spectrum of workflows, from discrete data pushes and CCD document exchange to SMART-on-FHIR launch contexts for in-workflow access. All interfaces are transaction-logged, version-controlled, and monitored 24/7 with automatic alerting to ensure data fidelity and uptime.
4. What reimbursement support do you offer?
The platform automatically tracks patient enrollment dates, device-usage days, and clinician interaction minutes, translating them into ready-to-submit claims for CPT 99453, 99454, 99457, and 99458. Built-in rules engines flag eligibility gaps and duplicate claims, reducing denials. Finance teams can export billing files in ANSI 837P or HL7 DFT formats, while administrators access dashboards that correlate reimbursement with patient outcomes for value-based care contracts. We also keep your coders updated on evolving CMS and commercial payer guidance through quarterly webinars and in-app policy alerts.
5. How long does implementation take?
Most customers achieve go-live in 12–16 weeks. The timeline is influenced by EHR integration complexity, device procurement lead times, and the number of clinical pathways you wish to enable at launch. A typical schedule allocates 2–3 weeks for discovery, 3–4 sprints for core development, 2 weeks for integration and user acceptance testing, and 1–2 weeks for training and phased rollout. Our dedicated project manager provides a Gantt chart, risk log, and weekly status reports, ensuring all stakeholders—clinical, IT, finance—stay aligned and on time.
6. Do you provide clinical monitoring staff?
Absolutely. Cabot partners with a network of RNs and CCM-certified nurses licensed across all U.S. states and Canadian provinces. Our 24/7 monitoring center follows physician-approved escalation protocols: tier-1 nurses triage alerts, document interventions within the platform, and escalate to the attending physician or emergency services as needed. Average response time to critical alerts is under 60 seconds, and all interactions are captured for audit and reimbursement. You may choose full-service monitoring, overflow coverage, or a hybrid model where your internal team handles daytime shifts while we manage nights, weekends, and holidays.
