Frequently Asked Questions
1. How long does it take to launch a minimum viable care-coordination platform?
Most clients go live with an MVP in 16–20 weeks. Timeline depends on the number of EHR integrations, custom modules, and regulatory documentation required.
2. Can you integrate with our existing Epic instance without additional licensing?
Yes. We leverage your current Epic Interconnect and FHIR® APIs, ensuring no new license fees while adhering to Epic’s Connection Hub policies. Our team has completed multiple Epic-validated integrations.
3. What security certifications do you hold?
Cabot is ISO 27001 certified and undergoes annual SOC 2 Type II audits. All projects conform to NIST Cybersecurity Framework controls and HIPAA Security Rule safeguards, including encryption at rest and in transit, RBAC, and continuous vulnerability scanning.
4. Do you support value-based care reporting?
Absolutely. Our analytics module tracks HEDIS®, MIPS, and custom quality measures. Dashboards are configurable for CFOs, CMOs, and care managers, and data can be exported in QRDA or Excel formats for payers and CMS submissions.
5. How does your pricing model work?
We offer fixed-scope or dedicated-team models. Both include transparent time tracking, fortnightly invoicing, and no hidden change-request fees. For value-based organizations, we can align a portion of fees to outcome milestones.
6. What happens after the platform is deployed?
Post-launch, our DevOps and support teams provide 24×7 monitoring, SLA-backed incident response, patch management, and quarterly roadmap workshops. We also train super-users and supply updated compliance documentation for auditors.
7. Do you provide patient-engagement modules like appointment reminders and remote check-ins?
Yes. We build HIPAA-compliant patient portals and mobile apps supporting appointment scheduling, medication adherence, symptom surveys, RPM device feeds, and secure messaging—all integrated into the same data fabric as provider dashboards.
8. How do you ensure clinicians adopt the platform rather than reverting to existing tools?
Our human-centered design process involves clinicians from day one—interviews, co-design workshops, and usability tests. We also embed clinical champions into sprint reviews, provide single-sign-on, and offer in-app guided tours to minimize resistance and training overhead.
9. Can the platform support remote patient monitoring (RPM) devices and IoT data?
Definitely. We integrate FDA-cleared devices via Bluetooth, Wi-Fi, or cellular gateways. Data is ingested through secure APIs, normalized, and surfaced in alerts, dashboards, or automated care-plan triggers.
10. What is your approach to migrating data from legacy care-management systems?
We start with a data-quality assessment and mapping workshop, extract data via CSV, APIs, or direct database access, cleanse and transform it using ETL pipelines, and load it into the new platform under rigorous reconciliation checks. Migration is scripted and tested in staging before cut-over.