Interoperability

Standards in.
Standards out.

Echo One reads, receives and exports the record in FHIR R4. A connection starts from a standard interface.

See how it connects
One record,
FHIR R4.
  1. Read
  2. Receive
  3. Export
  4. Held for review

In plain language

Every connection speaks a standard.
Nothing outside writes to the chart on its own.

Four connections

01 / 04

Registered systems read the record.

The practice registers a system and issues it a token it can revoke. The system reads the record over FHIR R4, and every read is tied to that token.

02 / 04

Incoming records arrive as proposals.

Another system can send FHIR resources in. They land in a review queue and touch no clinical record.

03 / 04

Nothing writes straight into the chart.

A submission is held in its own queue, apart from the clinical record. Arriving is not the same as being accepted.

04 / 04

The clinical record leaves in a standard format.

A practice-wide FHIR R4 Bulk Data export that any HL7-capable system can load, with a report of anything that didn’t map.

What’s covered

The clinical record,
as FHIR resources.

Read over FHIR R4

  • Patient
  • Encounter
  • Condition
  • Observation
  • AllergyIntolerance
  • Immunization
  • MedicationStatement
  • MedicationRequest
  • MedicationAdministration
  • Task
  • Communication
  • DiagnosticReport
  • Specimen
  • DetectedIssue
  • Questionnaire
  • QuestionnaireResponse
  • Location
  • Organization

In the practice export

  • Patient
  • Encounter
  • Condition
  • Observation
  • AllergyIntolerance
  • Immunization
  • MedicationStatement
  • MedicationRequest
  • MedicationAdministration
  • Task
  • Communication

Note text, documents, correspondence, form responses and appointments are not in the export. Its report names each one, so nothing is left out silently.

National services

My Health Record: a preview is not a live connection. Provider messaging networks are coming soon; secure link and email work today.

Per deployment

Connections, hosting and retention are confirmed with each organisation before go-live.

Clear boundaries

  1. 01

    Standards, not bespoke extracts.

    FHIR R4 in and out, so a connection doesn’t start as a custom project.

  2. 02

    Nothing writes straight in.

    Incoming data is held in its own queue. Nothing from outside writes straight into the clinical record.

  3. 03

    Your data comes with you.

    The structured clinical record exports in a format any HL7-capable system can load, and the report names what it leaves out.

For IT and digital leads Security and data

Questions

Common questions.

Does Echo One support FHIR?

Yes. Systems the practice registers can read the record over FHIR R4, covering patients, encounters, conditions, observations, allergies, immunisations, medicines, tasks, results and forms. Records another system sends in are held apart from the chart; nothing from outside writes straight into the clinical record.

Can we take our data with us if we leave?

The structured clinical record exports in FHIR R4 Bulk Data format, which any HL7-capable system can load: patients, encounters, conditions, observations, allergies, immunisations, medicines and tasks. Note text, documents, correspondence, form responses and appointments are not in the export, and its report names each thing left out.

Next

Bring your integration
questions.

Registering interest is not a commitment to purchase.

Join the waiting list