Frequently Asked Questions
Q1. How quickly can we launch?
The average deployment window is 12–20 weeks. Weeks 1–2 focus on discovery workshops, regulatory mapping, and KPI definition. Weeks 3–6 are dedicated to UX/UI prototyping with direct feedback from clinicians, administrators, and patient advisory panels. Development then runs in two-week agile sprints, each ending with a demo and security review. Portal-only projects that leverage our pre-built templates can go live in as little as 10 weeks, whereas multi-module rollouts with complex EHR and clearinghouse integrations trend toward the 18–20 week mark. A detailed Gantt chart, risk register, and sprint burndown reports keep you informed every step of the way.
Q2. Which EHRs do you support?
We maintain certified connectors for Epic, Cerner, MEDITECH, Allscripts (Sunrise & Paragon), Evident CPSI, Telus PS Suite, OSCAR, and multiple regional systems across Mexico and Canada. Our interoperability specialists begin with a technical assessment of your existing feeds—HL7 v2.x messages, FHIR endpoints, web-service APIs, and VPN tunnels. We then configure adapters, handle version mismatches, and validate data mappings in a mirrored sandbox to ensure bi-directional data flow without disrupting production. All interface specifications and transformation rules are fully documented for your IT and compliance teams.
Q3. Is the platform multilingual?
Yes. English and Spanish ship by default, and French-Canadian is included at no extra cost. Our content-management layer uses industry-standard i18n libraries and translation memory, allowing you to add or update languages—such as Haitian Creole or Navajo—without code changes. Language selection can be user-controlled, geofenced by region, or auto-detected via browser settings. All clinical terminology undergoes linguistic QA and back-translation to maintain accuracy and cultural relevance, in line with ISO 17100 standards.
Q4. How do you ensure ongoing compliance?
Compliance is built into every phase of our SDLC. We conduct quarterly vulnerability scans with automated remediation tracking, perform annual SOC 2 Type II audits, and maintain a live compliance dashboard that maps artifacts to HIPAA, HITECH, 21st Century Cures Act, PIPEDA, PHIPA, CCPA, and Mexico’s NOM-004-SSA3 requirements. Encryption in transit (TLS 1.3) and at rest (AES-256) is standard, as is role-based access control with OAuth 2.0/JWT. We also provide Data Processing Agreements (DPAs), Business Associate Agreements (BAAs), and assist with Privacy Impact Assessments (PIAs) where required.
Q5. What support is included after go-live?
Immediately after launch, you enter a 30-day hyper-care phase where dedicated engineers monitor performance, triage issues, and refine configurations based on live feedback. Thereafter, you receive 24/7 tri-lingual support (English, Spanish, French) via phone, email, and ticket portal, with SLA-backed response and resolution times. Quarterly business-review meetings assess KPIs versus initial objectives, and our roadmap workshops capture new feature requests, regulatory updates, and optimization ideas to keep your platform future-proof.
Q6. Can patients switch devices mid-session?
Absolutely. Our omnichannel architecture maintains the session state in a secure, stateless token, allowing patients to begin a telehealth visit on desktop and seamlessly continue on mobile or tablet without losing context. Push notifications, SMS, and email reminders are orchestrated through a unified messaging service that prevents duplicates and respects patient communication preferences. For organizations seeking a branded mobile presence, we offer white-label iOS and Android apps that share the same back-end, ensuring full feature parity and simplified maintenance.