Skip to main content

17Integration HubPlatform foundation

Integration with external systems

Integration Hub routes every exchange between Fastclinic and external systems, including laboratory instruments, imaging archives and other hospitals' records, through one gateway.

Designed for
  • Integration engineers
  • CIOs
  • Security teams
  • Compliance officers
  • Clinical informatics leads
A software developer smiling at his laptop in a bright office
Integration Hub

Exchange status

  1. 1Received
  2. 2Validated
  3. 3Accepted
  4. 4Delivered
  5. 5Applied
  6. 6Reconciled
A lab scientist in a navy hijab loading a sample into an analyser

Capabilities by role

Integration Hub is the single gateway for all data Fastclinic exchanges with external systems.

Integration engineers

  • Engineers configure each connector with its own purpose, profile version and limits on rate, volume and retries.
  • Each connector has a stop switch and a circuit breaker.
  • Integration Hub quarantines any exchange that fails validation and does not apply it in part.

Security and compliance teams

  • Original messages are stored encrypted, with a digest that shows they are unaltered.
  • Each format conversion records its source, and corrections are linked in a chain.
  • Clinical content is excluded from logs, metrics and web addresses.
  • Each connector has its own data minimisation rule.

Laboratory, imaging and records teams

  • Health records are exchanged as FHIR R4 (4.0.1).
  • Admissions, orders and results are exchanged as HL7 v2.5.1 messages, and each receives an acknowledgement of accepted, error or rejected.
  • Integration Hub finds, retrieves and stores images over DICOMweb and does not control imaging devices.
  • Large image transfers are encrypted, resume after an interruption and are verified by digest.

Built-in controls

These controls are enforced by the software and apply in both deployment editions and on every plan.

Quarantine of failed exchanges

Integration Hub quarantines an exchange that fails validation and does not deliver it, so no partial or malformed exchange reaches a clinical record.

Clinical content excluded from logs

Message contents are excluded from logs, metrics and web addresses.

Connector stop switches and limits

Each connector can be stopped without affecting the others.

Standards supported
  • FHIR R4
  • HL7 v2.5.1
  • DICOMweb

Frequently asked questions

For other questions, email contact@getfastclinic.com.

What happens when an incoming message fails validation?

Integration Hub quarantines it and does not deliver it.

Does patient information appear in logs?

No. Message contents are excluded from logs, metrics and web addresses.

Can one connection be stopped without affecting the others?

Yes. Each connector has its own stop switch and its own limits on rate, volume and retries, with a circuit breaker.

Arrange a demonstration of Integration Hub

We will demonstrate how Integration Hub would operate in your facility alongside the components it works with.