HL7 FHIR integration
HL7 FHIR is the REST-based standard for exchanging healthcare information. In ALLINLET it is used for hospital operations and aggregated indicators, such as bed occupancy, location and device context, alongside building and equipment data. It is not positioned as a clinical record system.
Where it fits
A hospital digital twin may combine BACnet data for ventilation, BLE positions for mobile equipment, medical gas alarms and FHIR resources describing locations, encounters or devices. FHIR provides the clinical context that makes operational data meaningful, for example knowing that an isolation room is occupied when its pressure differential drops.
Transport and access
FHIR R4 servers expose resources over HTTPS with JSON. Access normally uses OAuth2, with SMART Backend Services and client credentials for system-to-system reading. Scopes should be limited to the resource types needed, for example system/Location.read. Queries use search parameters and _lastUpdated to retrieve changes, and Bundle paging is followed until complete.
Prerequisites
- Approval from the hospital data protection officer and information governance, with a documented purpose.
- A registered client on the FHIR server or integration engine, with minimum scopes.
- A list of resource types and fields, ideally with identifiers and personal details removed or pseudonymised at source.
- Agreement on whether aggregate projections are preferred over patient-level resources.
Payload meaning
Resources such as Location, Device, Encounter and Observation have defined elements and coded values from terminologies like LOINC or SNOMED CT. ALLINLET records the resource type, id, version, lastUpdated time and selected elements, and keeps codes with their system URI so they are not confused across code systems. Where only aggregate counts are approved, the source should provide them so personal data does not enter the platform.
Limitations
- The integration is read-only and does not write clinical data.
- ALLINLET is not a medical device and must not be used for diagnosis or treatment decisions.
- FHIR profiles and server implementations differ; each server is validated in the project.
- HL7 v2 and DICOM are separate integration paths with their own constraints.
- No healthcare certification is claimed on this page.
Further reading
- Healthcare twin guide
- Digital twin guide
- Iot devices guide
- All resources
- Connector catalogue
- Industries
- Products
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.