Hospitals data integration
Hospitals combine clinical systems, building automation, medical gases, imaging and equipment tracking, and many of these are safety critical or contain personal data.
Example use case
An estates team monitors isolation room pressure and air changes from BACnet controllers, relates them to room occupancy from FHIR Location data and tracks infusion pumps via BLE tags, so cleaning and maintenance can be scheduled without disturbing patient care.
Typical sources and transports
BACnet/IP for HVAC, BLE gateways publishing to MQTT, HL7 FHIR R4 with OAuth2 for operational context, DICOMweb for imaging metadata, and change-data capture from CMMS databases.
What the data means
Building values carry units and setpoints; equipment positions are zone-level estimates; FHIR fields are kept with code systems. Patient-level data should be pseudonymised or aggregated at source.
Prerequisites
Before connecting hospitals sources, prepare an inventory of systems and owners, interface documentation for each one, read-only credentials and approved network paths. Agree identifiers, units and time zones early, and name a person who can confirm values against the source during commissioning.
Integration scope
ALLINLET collects and normalises hospital data through read-only integrations. It does not control medical equipment or provide clinical decisions. FHIR and DICOM connections require authorisation from the hospital and validation against its systems before use.
Catalogue entries for this domain
The connector catalogue lists 48 entries for this domain. A selection is shown below. Listing indicates a possible integration path, not that it is implemented, validated or installed for your environment.
- BACnet/IP
- BLE advertising / iBeacon / Eddystone · gateway
- BLE GATT · MQTT gateway
- CMMS CDC · Debezium JSON
- CSV
- DATEX II
- DICOM DIMSE · C-FIND · mTLS
- DICOM Modality Worklist · read-only
- DICOMweb · QIDO-RS · HTTPS
- DLMS / COSEM
- Dry contacts · HTTPS snapshot
- ERP / HR CDC · Debezium Avro
- FHIR R4 · OAuth2 · resource metadata
- GS1 EPCIS 2.0 · HTTPS
- Hand-hygiene gateway
- HL7 v2 ADT · HTTP export
- HL7 v2 ORM / OML · HTTP export
- HL7 v2 ORU^R01 · HTTP export
Further reading
Catalogue listings describe possible integration paths. Implementation and validation status is confirmed for each source during project scoping; no certification, service level or price is implied by this page.
Plan your data integration
Share your devices, protocols and network constraints, and we will propose a first validated connection.