FHIRBridge

What FHIRBridge does

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.

How you actually use it

1. 1Read 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.
2. 2Check 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.
3. 3Build 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.
4. 4Take 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.

What it does 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.

Questions clinics ask