OperationsLive · in the productQueue & board

FHIRBridge

FHIR R4 in and out, mapped in the open and every exchange logged.

Get FHIRBridge Open the appAvailable nowHow pricing works →

What it is

FHIR R4 for the seven resources this product actually holds records for — Patient, Encounter, Observation, Condition, MedicationRequest, DiagnosticReport and DocumentReference. Build a bundle for one patient and hand it to whoever asked; take a bundle in against a patient this hospital already holds. The mapping is published on the screen element by element, naming the exact column each field comes from, so an argument with a receiving system is settled by pointing at a line. Coded values leave exactly as the clinician coded them; where FHIR wants a terminology this deployment has never imported, the value travels in this system’s own vocabulary and the exchange says which value set would be needed. Every exchange is a row — the ones that failed too — with what came in, what was written, what was held and every validation finding anchored to its FHIR path.

Who uses it: Built for: Every specialty
Reads: The patient record, visits, results, prescriptions and documents
Writes: Exchange log, validation findings, imported observations
Never: It never guesses a code: a field whose terminology is not loaded goes out in this system’s own vocabulary, labelled, rather than under a nearest-looking national code.
Access: Only people whose role includes it — the clinic owner decides who
Your data: Full PHI. Hosted in Boston, United States. On uninstall: All clinical data stays in the record.

How it works

Read the exchange logEvery bundle sent or taken in, the failed ones included, with how many of its resources were accepted and how many are held. Open one for its findings, each anchored to a FHIR path, and for what became of every resource — written, held or rejected, with the table it went to or the reason it did not. The bundle itself is not stored — only its SHA-256.
Check the mappingThe Mappings tab lists element by element which column each FHIR field comes from, the value sets this deployment has never imported — fields bound to them travel in this system’s own vocabulary, labelled — and how many of each list one bundle carries.
Build a bundleOn Send or take in, name the patient, who it goes to, and either everything the bridge maps or one resource type. When a patient has more records than the cap, the exchange says so, naming the type and how many were left behind.
Take a bundle inPaste an R4 bundle. It lands against the patient named on the form, never whoever the bundle names. Observations are written and marked imported; a diagnosis, prescription, report or document is held for a person to read. The same bundle delivered twice for the same patient within thirty days is recorded and writes nothing the second time.

Rules it keeps

What it does not do, by design. A listing with only benefits is an advertisement.

It never guesses a code: a field whose terminology is not loaded goes out in this system’s own vocabulary, labelled, rather than under a nearest-looking national code.

It writes only observations from an inbound bundle — a diagnosis, prescription, report or document written elsewhere is held for a person to read rather than filed in this hospital’s chart under nobody’s signature.

It sends the reference to a document and never the file behind it.

And a bundle cannot choose whose chart it lands on: the patient is the one the caller named and this organisation owns.

AI in FHIRBridge

AskQuestions about what is on screen — “What needs attention in FHIRBridge today?” — answered with the records it read.

DraftSummaries and notes for the team, marked as drafts until a person signs.

Every answer shows its sources. Nothing AI writes is saved until a person accepts it.

See it on screen

FHIRBridge — FHIR Exchange — Send records to another system in FHIR, and take theirs in — 01FHIR Exchange — Send records to another system in FHIR, and take theirs inCaptured from the running demo clinic

01FHIR Exchange — Send records to another system in FHIR, and take theirs inCaptured from the running demo clinic

1 of 1

Connected to

Read out of the code, not the brochure: each app below is here because one service queries the other’s tables. Install either side and the hand-over is already wired.

Reads from · 5

BillDesk CaseNotes LabBridge Patient Registry RxCanvas

Hands to · 1

CaseNotes

See the whole clinic →

Questions clinics ask

What does FHIRBridge do?

FHIR R4 in and out, mapped in the open and every exchange logged. FHIR R4 for the seven resources this product actually holds records for — Patient, Encounter, Observation, Condition, MedicationRequest, DiagnosticReport and DocumentReference. Build a bundle for one patient and hand it to whoever asked; take a bundle in against a patient this hospital already holds. The mapping is published on the screen element by element, naming the exact column each field comes from, so an argument with a receiving system is settled by pointing at a line. Coded values leave exactly as the clinician coded them; where FHIR wants a terminology this deployment has never imported, the value travels in this system’s own vocabulary and the exchange says which value set would be needed. Every exchange is a row — the ones that failed too — with what came in, what was written, what was held and every validation finding anchored to its FHIR path.

What data does FHIRBridge read and write?

FHIRBridge reads the patient record, visits, results, prescriptions and documents and writes exchange log, validation findings, imported observations. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

What does FHIRBridge deliberately not do?

It never guesses a code: a field whose terminology is not loaded goes out in this system’s own vocabulary, labelled, rather than under a nearest-looking national code. It writes only observations from an inbound bundle — a diagnosis, prescription, report or document written elsewhere is held for a person to read rather than filed in this hospital’s chart under nobody’s signature. It sends the reference to a document and never the file behind it. And a bundle cannot choose whose chart it lands on: the patient is the one the caller named and this organisation owns.

What happens to our data if we uninstall FHIRBridge?

All clinical data stays in the record.

Is FHIRBridge available today?

Yes — FHIRBridge is live in clinics today. Set up your practice on MedAppz and install it from your dashboard.

Want to see FHIRBridge running on your own patients?

Tell us what you run and we will show you this app inside a practice shaped like yours — or answer the question the page above did not.

More in Operations

All 143 →