Frequently Asked Questions
1. How long does it take to build a custom care coordination platform?
While every project is unique, most of our Canadian healthcare clients move from discovery to production launch in 6–9 months. The timeline depends on factors such as the number of third-party integrations, the complexity of clinical workflows, bilingual requirements, and regulatory approvals. We provide a detailed, phase-by-phase project plan with milestones and deliverables during the road-mapping stage.
2. Can you integrate with our existing EHR, HIE, and lab systems?
Yes. Integration is a core part of our value proposition. We work with leading Canadian EHRs and leverage HL7 v2/v3, FHIR, SMART on FHIR, and custom APIs to connect to provincial HIEs (e.g., Alberta Netcare, eHealth Ontario), laboratory information systems, pharmacy platforms, and imaging repositories. Our interoperability specialists handle interface configuration, data mapping, and conformance testing to ensure seamless, bidirectional data exchange.
3. How do you ensure data privacy, PHIPA, and PIPEDA compliance?
Security and compliance guide every stage of our SDLC. We host data in Canadian data centres that meet Tier III+ standards, implement AES-256 encryption in transit and at rest, enforce granular role-based access control, and maintain immutable audit logs. Our compliance team conducts privacy impact assessments (PIAs), threat-risk assessments (TRAs), and routine penetration testing. We also help clients establish data-sharing agreements and consent management workflows inline with PHIPA and PIPEDA guidance.
4. Do you offer bilingual (English/French) interfaces and patient materials?
Absolutely. Our UX/UI team designs all user-facing components with built-in localization support. We translate static and dynamic content into French (or other languages as required) and validate terminology with clinical subject-matter experts to ensure linguistic accuracy. We also conduct accessibility testing to confirm conformance with WCAG 2.1 AA standards in both languages.
5. What type of post-launch support and SLAs do you provide?
Cabot offers 24/7 monitoring, incident management, and a tiered support structure with clear response times (e.g., P1 within 1 hour, P2 within 4 hours). Clients receive a dedicated Customer Success Manager, quarterly roadmap reviews, and access to our DevSecOps pipeline for continuous improvements. We also provide optional managed hosting and on-site support packages.
6. Can the platform scale across multiple facilities or regions?
Yes. Our cloud-native microservices architecture supports horizontal scaling, multi-tenant configurations, and regional data residency controls. Whether you are a single clinic or a health authority with dozens of facilities, the platform can be partitioned—or unified—according to your operational and governance needs.
7. How is the project priced, and what cost models do you offer?
We provide three flexible pricing options: (1) Fixed-scope, fixed-price for well-defined projects; (2) Time-and-materials for agile, evolving requirements; and (3) Dedicated team/retainer for long-term product roadmaps. All models include transparent reporting on hours, deliverables, and expenses. Licensing fees for third-party components, cloud hosting, and ongoing maintenance are itemized separately for full clarity.
8. Who owns the intellectual property (IP) after project completion?
Upon full payment, all custom source code, documentation, and design artifacts are transferred to you under a work-for-hire agreement. We retain rights only to our pre-existing reusable components and accelerators, which are licensed to you royalty-free.
9. What training and change-management services do you provide?
We conduct role-specific training sessions (clinicians, administrative staff, IT) via live workshops, recorded modules, and bilingual user manuals. Super-users are empowered to become in-house champions, and adoption analytics help us refine training materials over time. We also facilitate stakeholder communication plans to mitigate resistance and accelerate user adoption.
10. How do you future-proof the platform for evolving interoperability standards?
Our modular architecture isolates interoperability services, allowing for updates as new HL7/FHIR versions, provincial mandates, or national standards (e.g., pan-Canadian Patient Summary) emerge. Continuous integration pipelines run regression tests against new standard releases, ensuring your platform stays compliant without disruptive overhauls.
