Inbound first.
Selected partners next.
Fax, email, portal, and manual upload work on day one. Deeper EMR and referral connectors follow customer pull, not vendor roadmaps. Provincial conformance work is sequenced after the wedge proves out.
The wedge that works
at pilot start.
Every inbound channel a B.C. community clinic actually uses today — normalized into one queue. No EMR change, no roadmap dependency.
Secure fax gateway
Inbound fax via a commercial fax API gateway. PDF capture, OCR, and direct landing in the operations queue.
Shared email inbox
Forward or BCC inbound clinic email to a Nidl address. Attachments and bodies parse into structured requests.
Manual upload
Front-desk staff drop documents into the queue manually. OCR runs, classification runs, the rest follows.
Embedded web form
A configurable patient-facing form (with explicit consent and notice) that posts directly into the queue.
One real connector per quarter.
Driven by customer pull.
Deeper integrations begin where the pilot signal is strongest. We sequence one partner at a time so each integration is real, supported, and durable.
TELUS CHR
Enterprise API and EMR add-ons are publicly documented. Integration requires a commercial relationship and TELUS approval.
OceanMD / DRO
OceanMD positions itself as an open, standards-based integration layer and powers B.C.'s Digital Referral Order program. Strong fit for B.C. referrals.
Accuro (QHR)
Common in community clinics. Supported in the B.C. DRO setup materials. Integration begins via customer-specific workflows.
OSCAR EMR
Open-source and operationally flexible. Integration via HL7, fax, or document drop patterns where customer pull justifies it.
Strategic, not quick.
Important national + provincial systems. They move when a pilot customer wants them and the regulatory/security work is properly funded.
PrescribeIT
National e-prescribing service. Important strategically; integration involves a certification process that we sequence after pilot wedge.
PharmaNet / B.C. Health API Gateway
Provincial systems require formal registration, self-testing, cloud/security disclosure, and conformance testing. Strategic, not quick.
We don’t pretend
to integrate with everything.
These are off the roadmap until the situation changes. Honest constraints, not strategic silence.
Jane
No open APIJane is commercially attractive in allied health but has publicly stated it does not currently offer an open API. We avoid a hard dependency in MVP and pursue commercial dialogue separately.
Health Gateway
No public API pathPatient-facing value is real, but no documented public API path was found. Treat as partnership exploration, not roadmap dependency.
Pilot first. Then partners.
Prove the wedge with inbound channels every clinic already uses. Then add one real partner connector per quarter, driven by customer pull, not vendor enthusiasm. Provincial conformance work sequences after the wedge has measurable revenue.
Get a real answer
in five business days.
Send us your EMR, your inbound volumes, and your biggest follow-through pain. We’ll reply with what works on day one, what we’d sequence next, and where we’d say no.