Connect BBMS to your hospital information system
Caresoft BBMS connects to Caresoft HIS through its API gateway and to any other HIS through a REST API, HL7 FHIR R4 resources and signed webhooks. Orders come in from the ward; blood group, charges and transfusion events go back. Without an HIS, BBMS runs fully on its own.
What flows between BBMS and the HIS?
| Direction | Data |
|---|---|
| From HIS to BBMS | Patients, blood requests from the ward, cancellations, doctors, wards, departments and schemes |
| From BBMS to HIS | Verified blood group, charges for the bill, issue, transfusion start and end, returns, reactions, look-back alerts |
| Every message | Signed, retried until delivered, and safe to resend: a charge is never billed twice |
How does each type of HIS connect?
| Your setup | How it connects |
|---|---|
| Caresoft HIS | Through the Caresoft HIS API gateway. BBMS pulls ward orders and posts results; HIS needs only stored procedures, no code release |
| Another HIS | REST API with token authentication, HL7 FHIR R4 Patient and ServiceRequest, signed webhooks for events. OpenAPI specification provided |
| No HIS | BBMS keeps its own patients, billing and reports |
Questions people ask
Does BBMS support HL7?
BBMS supports HL7 FHIR R4 for patients and blood requests (ServiceRequest), and can send events as FHIR. HL7 version 2 interfaces can be built through an integration engine using the REST API.
What happens if the HIS is down?
BBMS keeps working. Outgoing messages wait in a queue and are delivered when the HIS is back; each is delivered once.
See it with your own stock and workflow
A 30-minute demo walks through donor to bedside, the safety stops, and how BBMS connects to your HIS.