Frequently Asked Questions
1. Do you support both HL7 v2 and FHIR?
Absolutely. Our integration engine natively handles HL7 v2.x, v3, and every published FHIR release (DSTU2 through R5). We can:
- Translate messages in real time (e.g., HL7 ORU-R01 to FHIR DiagnosticReport).
- Expose RESTful FHIR APIs while continuing to consume classic HL7 feeds.
- Maintain version-specific conformance profiles so downstream systems always get data in the exact structure they expect.
This means you can modernize at your own pace—adopting FHIR where it creates value without disrupting existing interfaces that still depend on HL7 v2.
2. Where is patient data hosted?
All data is processed and stored exclusively in Canadian data centres certified to SOC 2 Type II and ISO 27001. We operate active-active clusters in geographically separate regions to ensure high availability while keeping data sovereignty within Canada. Encryption is applied:
- In transit — TLS 1.3 with forward secrecy.
- At rest — AES-256 with keys managed by a Canadian-hosted HSM.
Only you control data-access policies, and our audit logs provide complete traceability for compliance reporting.
3. How long does a typical integration project take?
Timelines vary with scope, but our proven accelerators keep things predictable:
| Project Type | Average Duration |
|---|
| Single-interface (e.g., LIS → EMR) | 6–8 weeks |
| Multi-system hospital integration | 3–4 months |
| Province-wide data hub | 6–9 months |
Key factors affecting duration include the number of systems, vendor responsiveness, and the availability of test environments. We provide a detailed Gantt chart during project kickoff so you know exactly what to expect.
4. What security certifications do you hold?
Security is non-negotiable. PAC’s platform and processes are:
- SOC 2 Type II audited annually.
- Aligned with ISO 27001 controls (formal certification in progress).
- Subjected to third-party penetration testing twice per year.
- Benchmarked against NIST 800-53 and CIS Level 1 hardening guides.
Additionally, every member of our engineering team completes annual HIPAA/PHIPA privacy training, and our DevOps pipeline blocks deployments that fail automated security scans.
5. Can you work with our in-house IT team?
Yes, collaboration is at the heart of our methodology. We can adapt to:
- Co-development—our engineers pair-program with yours, sharing repositories and CI/CD pipelines.
- Shared operations—you retain first-line support while we handle escalation and platform maintenance.
- Full outsourcing—we take on end-to-end responsibility with agreed-upon SLAs.
You decide how much control to keep; we supply the tools, documentation, and knowledge transfer to make the partnership friction-free.
6. Is bilingual (English/French) support available?
Oui. All customer-facing teams—support desk, onboarding, and training—are staffed with fluent English and French speakers. Support channels include:
- 24/7 phone and secure portal ticketing.
- Live chat during business hours (08:00–18:00 ET).
- On-site workshops anywhere in Canada.
This ensures language is never a barrier to resolving issues quickly or maximizing the value of your interoperability investment.
