Integrating an AI Dermatology Tool with OSCAR EMR and Telus PS Suite

As of February 25, 2025.

Canadian primary-care and dermatology clinics rarely run on a single software platform. The average family physician uses one electronic medical record (EMR) system while the dermatologist they refer to uses another, and neither system was designed to talk to each other out of the box. Integrating any AI-assisted dermatology tool with a referring physician's EMR — whether OSCAR or Telus PS Suite — involves a predictable set of technical, administrative, and compliance steps.

This article explains how those integrations work in general, what data moves across them, and what your IT team or clinic manager needs to know before going live.

What is OSCAR EMR and who uses it in Canada?

OSCAR (Open Source Clinical Application Resource) is a free, open-source electronic medical record (EMR) built at McMaster University and used by approximately 14,000 Canadian physicians. It is most prevalent in British Columbia, Ontario, and Alberta, particularly in community health centres and academic family medicine clinics. Because OSCAR is open-source, multiple regional deployments exist under different names, including OscarBC and OSCAR Pro. Each deployment may run a different software version, which any connecting platform must account for during setup and configuration.

OSCAR was originally developed at McMaster University in 2001. Because it is open-source, dozens of regional deployments exist — including OscarBC, OSCAR Pro (now commercialized by WELL Health), and various self-hosted instances maintained by provincial health authorities. This fragmentation is the first challenge any integration must address: the version of OSCAR at a Vancouver community health centre may differ substantially from the one running at a Toronto academic clinic.

The Canadian Institute for Health Information (CIHI) tracks EMR adoption across provinces. According to CIHI's national physician survey data, the proportion of Canadian physicians using any EMR system has grown above 85% in recent years, with OSCAR representing a meaningful share in western and central provinces. For current adoption figures, see the CIHI EMR adoption report at CIHI physician data.

For dermatology use specifically, OSCAR's strength is its open application programming interface (API) layer. Third-party tools — including dermatology image capture tools like DermEngine — have published OSCAR integration guides that illustrate the general approach.

What is Telus PS Suite and how does it differ from OSCAR?

Telus PS Suite is a commercially licensed electronic medical record (EMR) owned by Telus Health, with more than 20,000 users across Canada. Unlike OSCAR, PS Suite operates on a closed, subscription-based model with structured vendor support and a formal integration partner program. It is particularly strong in Ontario and Quebec private practices, where OHIP (Ontario Health Insurance Plan) billing integration and 24/7 vendor support are priorities. PS Suite exposes integration points through HL7 (Health Level Seven) v2 messaging and the Telus Health Connect program rather than an open API.

Telus Health acquired PS Suite as part of a broader strategy to consolidate Canadian digital health platforms. The product is particularly strong in Ontario and Quebec private practices where administrative features, billing integration with Ontario Health Insurance Plan (OHIP), and 24/7 vendor support are priorities. PS Suite's integration layer relies on HL7 v2 messaging and a proprietary API exposed through the Telus Health Connect program.

The table below compares the two platforms on dimensions relevant to an AI dermatology tool integration:

EMR	Vendor	Estimated Canadian Users	Integration Method
OSCAR EMR	OSCAR Pro / WELL Health (commercial); community-hosted (open-source)	~14,000 physicians	HL7 v2, REST API via OSCAR integration layer
Telus PS Suite	Telus Health	~20,000+ physicians	HL7 v2 via Telus Health Connect; PS Suite API
OSCAR BC	OscarBC (BC-specific fork)	~3,500 physicians	HL7 v2, subset of OSCAR API
OSCAR (self-hosted)	Various community deployments	Variable	HL7 v2 (version-dependent)

Both platforms support bidirectional HL7 messaging for demographics, referral notes, and lab results. That shared standard is the foundation for any EMR integration a dermatology tool would build.

How does an AI dermatology tool exchange data with OSCAR and PS Suite?

Most AI dermatology platforms use HL7 FHIR (Fast Healthcare Interoperability Resources) and HL7 v2 messages to pull patient demographics at the point of referral and push consultation summaries back to the referring physician chart. Patient data should be stored exclusively on Canadian servers, and all transfers should use TLS 1.3 encryption. A well-designed integration covers three stages: demographic pull when the referral is created, image and note transfer during the consultation, and result push when the dermatologist finishes the report — eliminating manual re-entry and reducing transcription errors on both sides of the referral.

The data flow typically works in three stages:

Stage 1: Demographic pull. When a referring physician creates a referral, the integration retrieves the patient's name, date of birth, health card number, and active problem list from the EMR. This avoids manual re-entry and reduces transcription errors.

Stage 2: Image and note transfer. The dermatologist reviews AI-assisted triage results and any uploaded skin images within the dermatology platform. Consultation notes are structured using standard SNOMED-CT and ICD (International Classification of Diseases) codes so they map cleanly to the referring EMR's chart fields.

Stage 3: Result push. The consultation summary — including diagnosis, recommended follow-up, and any prescription notes — is pushed back as an HL7 message into the referring physician's OSCAR or PS Suite chart. The referring physician sees it as an incoming result, the same way they receive a lab report.

For a deeper look at how patient images should be protected during these transfers, see the DermaDex article on encrypting patient images at rest and in transit.

What compliance rules apply to Canadian EMR integration?

Any integration that moves patient health information between systems in Ontario must comply with PHIPA (Personal Health Information Protection Act). Federally, PIPEDA (Personal Information Protection and Electronic Documents Act) also applies to private-sector health data. A dermatology platform operating as a health information custodian under PHIPA must sign a data-sharing agreement with each connected clinic before any live data flows across the integration. Patients have the right to know where their data goes and to request corrections, and this must be reflected in the clinic privacy policy and, where required, in patient consent forms.

Key compliance checkpoints before enabling any such integration:

• Data residency: Patient data must remain on Canadian servers. No patient data should cross the border.
• Audit logging: Every data access event should be logged with a timestamp, user ID, and purpose of access.
• Access control: Only the treating dermatologist and the referring physician should be able to view the shared record. Administrative staff access requires a separate consent flag.
• Breach notification: Both the dermatology platform and the clinic share breach notification obligations under PHIPA and any applicable provincial regulation.

For more on what these rules mean for patients, read the DermaDex guide to PHIPA, PIPEDA and skin health data.

The National Institutes of Health (NIH) also publishes interoperability guidance relevant to FHIR implementations at FHIR interoperability in electronic health records (PubMed), which Canadian developers use as a technical reference alongside HL7 Canada standards.

What does the setup process look like for a clinic IT team?

Setup typically takes one to three business days for most clinics once credentials are in place and the data-sharing agreement is signed. The steps differ by EMR:

OSCAR EMR setup:

1. Confirm your OSCAR version with your hosting provider or internal IT team. Most third-party integrations require OSCAR 15.x or later.
2. Enable the third-party integration module inside OSCAR's Administration panel.
3. Generate a service account with read/write access to the Demographics and Documents modules.
4. Share the endpoint URL and credentials with the dermatology platform's onboarding team via a secure credential portal.
5. Run a test referral using a dummy patient record to confirm bidirectional data flow.

Telus PS Suite setup:

1. Contact Telus Health to register the dermatology platform as an integration partner via the PS Suite integration program. Not all platforms hold approved-partner status; confirm this with the vendor before beginning.
2. Telus Health provisions an HL7 endpoint and provides connection parameters.
3. Share those parameters with the platform's onboarding team.
4. Test with a dummy patient record before going live.

Clinic managers who are not IT-trained can generally follow the same process. The dermatology platform's onboarding team handles the technical configuration on their side. The clinic's role is primarily administrative: obtaining credentials and confirming that the privacy officer has reviewed the data-sharing agreement. Health Canada's digital health resources at Health Canada health care system provide additional guidance on privacy requirements for connected health tools.

Sources

• Canadian Institute for Health Information (CIHI). Physicians in Canada. https://www.cihi.ca/en/physicians
• Jiang G et al. Electronic health record interoperability using FHIR and blockchain. BMC Medical Informatics and Decision Making (2023). https://pubmed.ncbi.nlm.nih.gov/38025292/
• Health Canada. Health Care System. https://www.canada.ca/en/health-canada/services/health-care-system.html