Healthcare integrations between your EHR, portals and other systems.

We connect EHRs, portals, CRMs and billing systems using FHIR, HL7 and vendor APIs. We have shipped Epic and athenahealth integrations, and for other systems we work from the vendor's documentation and sandbox.

Create Referral form with date of service, surgery center and provider fields

What does EHR integration involve?

Onix Health connects EHRs, portals, CRMs and billing systems through FHIR R4, HL7v2 and vendor APIs. We have shipped Epic and athenahealth integrations, and for other systems we work from the vendor's documentation and sandbox. Each connection is built against the sandbox, tested with missing, late and wrong data, and goes live after a BAA is signed and a penetration test is passed. In our provider portal project, claims and referrals now process three times faster.

What we build: interoperability

1

EHR integrations

We have shipped Epic and athenahealth integrations. For Oracle Health (Cerner) or other EHRs we work from the vendor's documentation and sandbox.

2

FHIR R4 APIs

Read and write patient data through FHIR, the modern standard most EHRs now support.

3

HL7v2 messages

Admissions, orders and results from older systems, with retries when a message fails.

4

Automatic data entry

Claims and referrals checked against your rules and entered into the EHR without retyping.

5

CRM connections

Data shared between your portal and Salesforce, so staff stop copying it by hand.

6

Testing with failure cases

Each connection is tested with missing, late and wrong data before it goes live.

How the project runs

  1. 1

    Free technical audit

    Five working days. We look at your current system, data and plans, and you get a written report with what we found and what we would do.

  2. 2

    Map the data

    We list each system, what data moves between them and in which format, and agree the first connection. You get a dated plan.

  3. 3

    Sandbox first, BAA before PHI

    We build against the vendor's sandbox and test data. We sign a BAA before any real patient data flows.

  4. 4

    Build, test, launch

    Each connection is tested with failure cases, then the system passes a penetration test before launch.

Technology and standards

  • FHIR R4
  • HL7v2
  • SMART on FHIR
  • Node.js
  • Python
  • PHP
  • Angular
  • PostgreSQL
  • AWS
  • Salesforce
  • Built to the HIPAA Security Rule
  • BAA signed before any patient data is shared
  • Penetration test passed before launch
  • Built against FHIR R4 and HL7v2 specifications

Questions about interoperability

1

What is the difference between FHIR and HL7?

HL7v2 is an older message format that most hospital systems still send, and FHIR is a newer web API standard from the same organization. Most projects use both: FHIR where the EHR supports it, HL7v2 for older feeds.

2

Do you have Epic integration experience?

Yes, we have shipped Epic and athenahealth integrations. For any part of Epic we have not used before, we work from Epic's documentation and sandbox.

3

Can you integrate with Oracle Health (Cerner)?

Yes, we can build it from Oracle Health's documentation and sandbox. The plan says up front which parts are new to us.

4

Should we use an integration platform or connect directly?

It depends on how many EHRs you need and how much you want to own. The free audit compares both for your case and gives you a written answer.

5

Can claims and referrals go into the EHR automatically?

Yes. In our provider portal project, claims and referrals are checked against set rules and entered into the EHR automatically, and the claims team reviews only the unclear ones.

6

How do you test an integration before going live?

We build against the vendor's sandbox, test with missing and wrong data, and run a penetration test before launch. Real patient data flows only after a BAA is signed.

Guides on this topic

EHR integration guides