Video Call supports SMART on FHIR launch, enabling it to be launched directly from a clinical system with patient and clinician context already in place. In practice, the clinical system initiates an EHR launch: it can open Video Call with a launch token and the iss (issuer) parameter identifying the EHR's FHIR server. Video Call then can complete the standard SMART authorisation code flow against that server, exchanging the launch token for an access token scoped to the relevant context, typically launch, patient, encounter, openid and fhirUser.

Once that exchange completes, Video Call can receive back the FHIR identifiers for the active Patient, Encounter and the launching Practitioner, along with an access token it can use to call the EHR's FHIR API directly. This means the clinician moves into the consultation with the correct patient and encounter already resolved, no re-identification or manual patient search required.

At the August 2026 Connectathon, Video Call was successfully SMART-launched from three connected clinical systems:

• CSIRO's reference implementation
• Beda Software's EMR
• Epic

This demonstrates that the launch and context-resolution flow work consistently across multiple vendor environments.

Video Call supports FHIR-based data retrieval, allowing Video Call applications to use the access token obtained at launch to securely read relevant patient information directly from the connected clinical system's FHIR API. Rather than the clinician manually looking things up in a second system, the relevant clinical context is pulled into the Video Call workflow automatically.

Depending on what an application needs, this can include:

• Patient demographics: name, date of birth, identifiers
• Conditions: active diagnoses (e.g. via AU Core Condition)
• Medications: current medication statements
• Allergies and intolerances
• Observations: recent vital signs and social history (e.g. smoking status)
• Immunisations

This context is surfaced to the clinician within the Video Call interface itself, so they can reference a patient's history, allergies or current medications mid-consultation without switching windows or systems.

Video Call supports FHIR-based write-back, enabling information generated or exchanged during a Video Call consultation to be written back to the clinical system as structured FHIR resources, using the same authenticated session established at launch.

In a live demonstration at the August Connectathon, the Remote Vitals application captured heart rate and blood oxygen saturation readings via a connected pulse oximeter, packaged them as FHIR Observation resources (LOINC-coded, categorised as vital-signs) and wrote them back into the patient's encounter in a connected EMR, showing the full loop from consultation to clinical record with no double handling.

Video Call consultations can generate a write-back bundle including numerous resources, including:

Each resource is linked back to the same Patient and Encounter context resolved at SMART launch, and observations are annotated (e.g. "Captured via Healthdirect Video Call connected devices") so the source is traceable in the patient record, giving the EMR a coherent bundle to file directly against the encounter, rather than disconnected data points.

Video Call already currently supports over 1.8M virtual consultations annually, across virtual emergency, hospital, primary and community care. At that scale, even small friction in clinical workflows, a manual patient search, a missed allergy, a note that never makes it back to the GP, adds up to a meaningful amount of avoidable risk and rework across the system.

FHIR interoperability closes that gap. It means a clinician can move from their own clinical system into a consultation without re-identifying the patient, can see relevant history without switching screens, and can trust that what happens on the call gets recorded where it belongs, without typing it twice. Multiply that across the volume Video Call already handles, and the benefit is not incremental; it compounds.

This is why interoperability is not a side project for Video Call, it's central to Healthdirect's goal of being the virtual front door for the Australian health system: safer care, less administrative duplication for clinicians, and a more connected health system built on shared national standards. The use cases below illustrate the real-world impact and importance of FHIR-based interoperability.

• Remote monitoring and follow-up: Retrieval of Continuous Glucose Monitoring (CGM) data to support virtual consultations, clinical review, and follow-up appointment scheduling.
• Vitals and diagnostic data exchange: Retrieval and write-back of clinical observations, including blood pressure, ECGs, and device-generated physiological data.
• Consultation summary generation: Creation of structured encounter reports and patient consultation summaries that can be rendered, shared, and stored within EMR/EHR systems.
• Consent management: Capture and upload of patient consent forms as FHIR-compatible clinical documents linked to the patient record.
• AI-assisted clinical documentation: Review and write-back of AI-generated consultation notes and structured clinical information into EMR/EHR systems