One of the most common questions we receive during product demonstrations is whether Delphyr integrates with existing electronic health record (EHR) systems. It is a practical and important question.

Healthcare professionals already rely on multiple digital tools in their daily work. We've been told that adding another standalone platform leads to low adoption, because it increases complexity, requires additional logins, and disrupts established workflows. For many organizations, the priority is not adding more software, but ensuring that new technology works seamlessly within the systems already in place.

Delphyr is designed with this reality in mind. From the outset, it has been built as an integration-first platform.

What Does It Mean That Delphyr Is “Integration-First”?

In healthcare, professionals already work within digital systems that store and manage patient information. These are commonly called electronic health record (EHR) or patient management systems. They contain clinical notes, lab results, medication lists, imaging reports, referral letters, and other essential patient data.

An integration-first solution means that Delphyr does not function as a separate platform outside of those systems. Instead, it is built to operate directly within the environment clinicians already use.

This approach matters because healthcare workflows are complex. Logging into an additional tool, copying information between systems, or switching between screens can interrupt clinical focus and increase administrative burden. By integrating directly into the existing system, Delphyr avoids creating an extra step in the workflow.

In practice, this means that when a clinician opens their EHR, Delphyr appears as an embedded feature, such as a tab or button. When activated, the assistant opens inside the same interface. There is no separate dashboard and no need to re-enter patient information.

Because Delphyr operates within the EHR, it can access the patient data that is already documented there. This includes structured data (such as medications or lab values) and unstructured data (such as clinical notes). Rather than estimating context, Delphyr uses the documented record as its source of truth.

An integration-first design is therefore not only a technical choice. It is a workflow decision intended to support clinicians within the systems they already trust and use every day.

Example: Integration with Bricks for Primary Care

A recent example of this integration-first approach is Delphyr’s integration into Bricks, developed by Tetra. Bricks is widely used in primary care and includes solutions such as Bricks GP, Bricks Patient, and Bricks Specialist.

Through this integration, Delphyr’s AI assistants are embedded directly within the Bricks environment. General practitioners do not need to log into a separate application. Instead, AI support is available inside their existing HIS (GP information system). Within Bricks, clinicians can use Delphyr for:

• Searching guidelines and retrieving patient information across fragmented records

• Preparing consultations by summarizing relevant patient history

• Drafting referral letters and follow-up correspondence

  
  

All functionality operates within the secure environment of the existing system. Patient data remains in the trusted infrastructure, while Delphyr transforms available information into structured, actionable support.

This example illustrates what integration-first means in practice: AI that strengthens clinical workflows without adding another layer of complexity.