Frequently Asked Questions
Q1. How long does a typical implementation take?
Implementation timelines usually span 12–24 weeks. The first two weeks focus on discovery—clarifying objectives, mapping regulatory obligations, and agreeing on success metrics. Weeks 3–6 involve UX prototyping with direct clinician and patient feedback to ensure rapid validation and user-centred design. Development proceeds in two-week sprints with parallel security reviews, giving you continuous visibility of progress. Complex EMR integrations or bespoke workflow automations may extend the timeline to the upper range, whereas portal-only deployments can launch in as little as three months. Throughout the engagement, we provide detailed Gantt charts, sprint burndown reports, and executive dashboards so you always know where the project stands and what risks have been mitigated.
Q2. Can you integrate with our existing EMR?
Yes. We maintain certified connectors and middleware adapters for Epic, Cerner, MEDITECH, Telus PS Suite, OSCAR, and several provincial EMRs. Our interoperability team starts by conducting a technical assessment of your current environment—HL7 feeds, FHIR endpoints, VPN requirements, and data-mapping rules. We then build or configure the required interfaces, handle version mismatches, and perform end-to-end validation in a sandbox that mirrors your production instance. Data governance policies, transformation logic, and audit tables are documented to satisfy both IT and compliance teams. The net result is bi-directional data flow that preserves clinical context and eliminates tedious double-entry for staff.
Q3. Is the solution bilingual?
Absolutely. All UI components, email/SMS templates, and educational assets are delivered in English and French out of the box. A centralised content-management layer stores translation keys and resource files, making it easy for your team to edit or add additional languages—such as Inuktitut or Cree—without developer intervention. Language can be selected explicitly by the user or auto-detected from device settings or postal-code demographics. Our localisation process follows ISO 17100 standards and includes linguistic QA to ensure medical terminology is accurate, culturally appropriate, and meets readability guidelines.
Q4. How is data kept secure and compliant?
Security is multi-layered. Data in transit is protected with TLS 1.3, while data at rest is encrypted using AES-256. Role-based access control (RBAC) combined with OAuth 2.0/JWT ensures that clinicians, administrators, and patients see only the information relevant to their privileges. All access and data-modification events are logged to an immutable audit trail that supports PHIPA, PIPEDA, and HIPAA investigations. Infrastructure is hosted in Canadian data centres (or your private cloud) that are SOC 2 Type II and ISO 27001 certified. We run quarterly vulnerability scans, annual penetration tests, and continuous threat monitoring with automated alerting to meet evolving security landscapes.
Q5. What happens after go-live?
Post-launch, you transition into our hyper-care phase: a 30-day period during which dedicated engineers monitor system performance, triage issues in real time, and fine-tune configurations based on live user feedback. Beyond hyper-care, you receive 24/7 bilingual support via phone, email, and ticket portal, with guaranteed SLAs for incident response and resolution. Quarterly business-review meetings evaluate KPIs against original objectives, and a living roadmap captures new regulatory changes, feature requests, and optimisation ideas. We also offer optional managed-security and data-analytics services to further extend value.
Q6. Do patients need to download multiple apps?
No. Our responsive, omnichannel framework delivers a unified user experience across web, iOS, and Android from a single code base. Patients can switch devices mid-session without losing context—a video visit started on a laptop can seamlessly continue on a smartphone. Push notifications, SMS, and email reminders are centrally orchestrated so messages are never duplicated or lost. For organisations that prefer a fully branded mobile presence, we can white-label the native apps while still sharing the same backend and data layer, ensuring feature parity and reducing maintenance overhead.