HL7 v2
Message-based exchange common in existing hospital systems.
Technology
Architecture that adapts.
A modular, standards-oriented architecture designed to coexist with existing healthcare infrastructure and grow progressively.
Modular architecture
Layered by design
- L5ExperienceProfessional, operational and patient-facing interfaces
- L4CapabilitiesModular ecosystem areas — clinical, operational, biomedical, supply
- L3IntelligenceAnalytics, AI models and decision support
- L2IntegrationAdapters, standards, canonical model and events
- L1Existing environmentHIS / EHR, LIS, RIS / PACS, devices — kept in place
Interoperability
One integration layer, many systems.
Intelink integration layer
Adapters · HL7 v2 · FHIR · DICOM / DICOMweb · APIs · canonical data model · events
Each system connects once, to the integration layer — not through a web of point-to-point links. Standards shown describe the architecture's design direction, not a list of completed integrations.
Standards
Standards the architecture is designed to support
This list describes integration direction and capability design — it is not a list of completed integrations.
HL7 FHIR
Resource-based APIs for modern healthcare data exchange.
DICOM & DICOMweb
Medical imaging objects and web-based imaging access.
HIS / EHR / KIS
Core hospital and clinical information systems.
LIS
Laboratory information systems.
RIS / PACS
Radiology information and image archiving systems.
Medical device connectivity
Bringing device data and equipment status into context.
APIs & adapters
Integration adapters that connect systems to one layer.
Canonical data & events
A shared data model and event-based integration.
Deployment
Standalone, modular, integrated.
Selected components connect with each other and with existing hospital systems through the integration layer.
Intelink Intelligence & integration layer
Community
Patient
Clinical AI
Medical Board
Clinical Research
Hospital Operations
Biomedical Engineering
Supply Chain & Procurement
Medication & Pharmacy Intelligence
Regional Intelligence
National Intelligence
Decision Intelligence
Existing systems remain in place — HIS / EHR · LIS · RIS / PACS · devices
Illustrative of the architectural principle — not a live product simulation.
Local / edge
Architecture direction for processing close to where care happens.
Low-connectivity
Designed with constrained connectivity in mind. Offline behaviour is subject to verification.
Hybrid
A combination of local and cloud components, according to organisational needs.
Advanced cloud
Cloud-based deployment for organisations with mature connectivity and infrastructure.
Security & governance
Principles we build on
Identity & access
Role-based access, scoped to what each user is authorised to see.
Authorised exchange
Information moves between areas only within defined authorisation.
Auditability
Designed so that access and exchange can be traced.
Data governance
Respecting organisational, local and regulatory requirements.
Talk architecture with our team.
Bring your current systems landscape — we'll discuss how Intelink could connect with it.