EMR and system integration
EMR integration for clinics: the complete guide
How a clinic connects its EMR to intake, forms, phones, faxes, labs and a CRM: the five ways to integrate, what each EMR exposes, and what to ask a vendor.
Read the guideResources EMR and system integration
Jane App integration: what connects, and how
How third-party systems connect to Jane App through the Jane Developer Platform: what the API covers, how clinics authorize it, and what to ask a partner.
Mahmoud ElHewaheyFounder, PulseAI Solutions28 October 2026 · 3 min read
The short version
- Jane App connects to other systems through the Jane Developer Platform, for approved Technology Partners.
- There is no self-serve access: a partner's integration is registered with Jane, then each clinic authorizes it.
- Authorization uses OAuth 2.0 with short-lived tokens, granted per clinic and per practitioner, with scopes the user approves.
- Published resources include appointments, patients, staff, locations, disciplines, treatments and medical-record observations.
- Clinic Conductor is live in production with Jane App.
Jane App in brief
Jane is a practice management and charting platform used widely by Canadian clinics, from physiotherapy and wellness practices to multidisciplinary and preventative health clinics. It handles booking, charting, billing and a patient portal in one place, which is why clinics running it often want the rest of their systems connected to it.
How integrations reach Jane
Jane's public route for third-party software is the Jane Developer Platform. Integrations built on it are called Jane Extensions, and the companies that build them are Technology Partners. The model has three properties a clinic should understand.
- Partner registration. Before an extension can call the API, it has to be registered with Jane's identity and access management service through Jane's partnerships team. There is no self-serve sign-up.
- Clinic and practitioner authorization. Access is granted by the clinic, through OAuth 2.0 with PKCE. Tokens belong to one clinic and one practitioner and cannot be reused elsewhere.
- Explicit scopes. The person authorizing the extension approves exactly what it may read or create, scope by scope.
How a Jane Extension is authorized
- 1Partner registeredThe integration partner registers the extension with Jane.
- 2Clinic connectsAn authorized user at the clinic starts the connection.
- 3Scopes approvedThe user approves what the extension may read and create.
- 4Short-lived accessTokens last minutes and are refreshed, per clinic and practitioner.
- 5RevocableThe clinic can revoke access at any time.
What the API covers
Jane's published API is versioned by date and describes resources for appointments, patients, staff members, locations, disciplines and treatments, along with medical-record observations that can be read and, with the right scope, created. Coverage grows over time, so the first question for any workflow is whether the records it needs are exposed today.
Common clinic workflows and the Jane records they touch
| Workflow | Records involved | What to confirm |
|---|---|---|
| New patient intake | Patients, appointments | That the partner can match existing patients and create new ones |
| Pre-visit forms | Patients, observations | Where answers land in the chart, and how they are labelled |
| Assessment results | Observations | Which values are written, with units and dates |
| Reporting on bookings | Appointments, locations, disciplines | Read access for the locations you run |
What to ask a Jane integration partner
- Are you an approved Jane Technology Partner, and is your extension registered?
- Which scopes will you ask my clinic to approve, and why does each one need them?
- Do you write information back into Jane, or only read from it?
- How do you avoid creating duplicate patients?
- What happens when Jane is unavailable, or a write is rejected?
- Where does information go after it leaves Jane, and under which agreement?
Jane and the rest of the clinic
Most clinics on Jane also run a website, a phone line, a CRM or email platform, and often assessment equipment or a lab feed. Connecting each of them to Jane separately creates a web of point-to-point links. One layer that connects to Jane once and conducts the work between it and everything else is easier to run and to audit. Our EMR integration guide explains the difference.
Questions, answered
Does Jane App have an API?
Yes. The Jane Developer Platform provides a versioned API for approved Technology Partners, who build integrations called Jane Extensions. Access requires registration with Jane and authorization by each clinic.
Can I connect my own tools to Jane App?
Through an approved partner. Jane does not offer self-serve API access, so integrations are built and registered by Technology Partners and then authorized by the clinic.
Is Clinic Conductor integrated with Jane App?
Yes. Clinic Conductor is live in production with Jane App.
See it running
Clinic Conductor connects intake, forms and onboarding to Jane App, live in production.
Keep reading
Related guides.
EMR and system integration
EMR write-back: where most integrations stop
Reading from an EMR is the easy half. Writing back into the chart, matched to the right patient, validated and audited, is where clinic hours are actually returned.
Read the guideEMR and system integration
CRM to EMR integration: connecting the front door to the chart
How to connect a CRM such as HubSpot or Salesforce to your EMR: what should sync, in which direction, what must never leave the chart, and how to keep it compliant.
Read the guide