Connect your systems, automate your care pathways.

The Braver orchestrator runs your integrations and automations. Connecting an EHR or EMR to the rest of the ecosystem usually takes several months. With the shared foundation in place, it takes weeks.

Request a technical demo For your architects ↓
What the orchestrator does

One engine, for your communications and your systems.

With Braver’s communication tools, the orchestrator runs your automations and connects your systems, depending on your plan. It can also run on its own, with communication tools added whenever you choose.

What it orchestrates
Integrations

Connect your systems: EHR, EMR, directory, pharmacy and AI scribe.

The foundation of every integration ↓ Automations

Move work forward according to your rules: notify a team, send a form or flag a situation.

Clinical pathways ↓
How it is used
With Braver’s tools

It supports the tool’s pathways, forms and notifications, depending on your plan. AI agents use it directly.

On its own

Without Braver’s communication platform. Clinical messaging and video calls are optional: they can be enabled later, like any other integration.

Integrations

The foundation of every integration.

Authentication, encryption, auditing and error recovery are in place, and each system keeps its own API. What remains is the logic specific to each integration: from translating formats such as HL7 or FHIR to more complex rules and workflows. That is what brings an integration down to a few weeks.

01 Authentication and identity

SSO, OIDC and SMART launch connect with your systems’ identity mechanisms.

02 Encryption

Clinical content is encrypted end to end. Authentication information is protected and access to it is controlled.

03 Auditing and traceability

Authorized teams can search the audit log by date range, actor, action and target.

04 Error recovery

Errors are visible, exchanges are tracked and retry mechanisms allow work to resume.

Proven in production

In production across the public healthcare network.

10CISSS, CIUSSS and university hospitals use the Braver platform
61public healthcare sites in production in 2026
≈ −90%cost per integration, using the shared foundation

Delivered integrationsEpicFHIR R4SMART on FHIRGustav SantéPointClickCareQGendaPrescribeITOfysLeomedMicrosoft Identity

Clinical pathways

Better-coordinated care pathways, at every step.

Braver helps your teams organize and follow clinical pathways according to your practices, so everyone knows what needs their attention.

Discuss your clinical pathway
Example · a request for advice
  1. A request for advice is recordedRequest
  2. The relevant team is notifiedNotification
  3. A professional takes responsibility for the caseAssignment
  4. An alert flags a situation that needs reviewAlert
  5. The team takes action and documents the next stepsIntervention

At every step, configurable rules support coordination, follow-up and traceability.

See the pathway

See a pathway’s status, priority, assigned professional and alerts in a tailored view.

Coordinate interventions

Bring the professionals involved together in collaboration spaces and share the information needed to provide care.

Support follow-up

Based on the rules you define, Braver can send forms, notify a team or flag a situation that requires action.

Data sovereignty

Quebec technology, already deployed across the network. Your organization has a dedicated instance: the keys, configuration and audit log belong to you, and every access to clinical content is explicit and revocable. Exchanges use standard formats such as HL7, FHIR and GraphQL, so your data remains readable and retrievable.

For your architects

How an integration runs.

An authenticated request, an event or a scheduled task triggers processing. The orchestrator checks permissions and runs the integration code. That code transforms data and calls partner APIs. The orchestrator tracks the execution and its result.

  • Synchronous or asynchronousA response within the request, deferred processing or event streams.

    An incoming request can receive a response within the same call or be queued for later processing. Events can also be sent to a connected client, and processing can be scheduled. The appropriate mode depends on the partner interface and the workflow being supported.

  • Logic and stateServer-side code that can retain state between executions.

    Integration code can chain calls, apply business rules and retain state between executions. Data transformations and the actions to perform are defined in that code. The orchestrator continues to handle authentication, permissions and auditing.

  • Access boundariesPermissions govern the operations and fields an integration can access.

    Permissions limit the operations and fields available to an integration. Unauthorized operations are rejected. Access to clinical content requires explicit, revocable authorization. Clinical content remains encrypted end to end, and authentication information is protected.

  • Execution trackingStatus, results and history retained for each execution.

    Each execution is tracked as a persistent task with its state and outputs. Retry rules are adapted to the operation and partner system. Technical traces support troubleshooting without containing clinical data. The audit log allows actions to be reviewed by date range, actor, action and target.

A technical demo, with a real use case.

Bring your system and its API. We will show you an integration’s path, from authentication to auditing.

Request a technical demo Security and compliance