Skip to content
Bitween AI is on the way

Healthcare

Clinical and administrative data exchange that stays inside your walls.

Healthcare integration carries sensitive data between EHRs, labs, payers and patient-facing apps. Bitween runs in your own environment, records every exchange for audit, and gives each partner exactly the pipeline and the access it needs.

Talk to an architectRead the docs

The challenge

What makes healthcare integration hard.

01

Sensitive data, many parties

Referrals, results and claims travel between organisations with different systems, formats and security expectations.

02

Auditors ask who changed what

You need evidence of every configuration change and every message that moved, not just application logs.

03

Legacy meets modern

FHIR APIs, XML web services and nightly batch files all have to coexist for years.

Flows you can run today

How Bitween handles it.

Each flow below uses capabilities that exist in Bitween now, with links into the documentation that describes them.

Flow 1

Referrals, validated at the door

Clinics submit referrals to a sync API gateway. A validator rejects incomplete requests immediately with the reasons, so nothing incomplete is stored, and accepted referrals are mapped into the receiving system's format.

  1. 1Sync API gateway
  2. 2Custom validator
  3. 3Map
  4. 4Deliver · OAuth2
  5. 5Response to caller

Flow 2

Lab results from a database

A scheduled job polls the lab system's SQL Server with an incrementing cursor. Each new result becomes an exchange, is mapped to a FHIR-shaped JSON resource, and is posted to the EHR.

  1. 1Scheduled job
  2. 2Incrementing cursor
  3. 3Map to JSON resource
  4. 4Deliver to EHR

Flow 3

Batch files to and from payers

Eligibility and claims batches move over SFTP with SSH keys. Aggregations roll a day's successful exchanges into one list for batch submission, and replies are picked up on the next schedule.

  1. 1Aggregation
  2. 2Map batch
  3. 3SFTP · SSH key
  4. 4Scheduled pickup

Controls that matter here

Capabilities behind the flows.

Private exchange files

Keep payloads private in your own object storage, with lifecycle rules that expire them after the retention you choose.

Docs

An audit trail nobody can edit

Every configuration change is recorded with old and new values in the same transaction, and no API can edit or delete it.

Docs

Least-privilege roles

Fine-grained permissions let an analyst view exchanges without touching credentials, and a DBA write SQL statements without changing connection settings.

Docs

Sign in with Microsoft

Staff sign in with your Microsoft Entra ID tenant, and sessions end after 30 minutes without activity.

Docs

Good to know about formats and scope

FHIR resources in JSON or XML are mapped natively. HL7 v2 messages need a custom adapter to parse them first. Bitween is software you operate: HIPAA and other regulatory obligations depend on how you deploy and run it.

Related use cases

Go deeper on the patterns.

API gateway for partners

One HTTPS endpoint per business process: sync when partners need an answer, async when they need speed.

ERP & database sync

Poll named SQL statements into exchanges and write deliveries back to tables and procedures.

File & mailbox automation

Pick up files from S3, Azure Blob, SFTP and mailboxes; transform and deliver them safely.

Plan your healthcare integrations with us.

Share your partners, systems and volumes. We'll show you how the flows would run on Bitween in your own environment.

Talk to an integration architectRead the docs