Integrations
Connect VannahHealthCloud with RIS, EMR/EHR, HMS, and diagnostic devices using HL7, FHIR, and DICOM protocols.
Integration Overview
VannahHealthCloud is designed to integrate seamlessly with your existing healthcare ecosystem. It supports industry-standard protocols and can connect with virtually any healthcare information system.
Supported Protocols
| Protocol | Version | Use Case |
|---|---|---|
| DICOM | 3.0 | Medical image transfer and query |
| HL7 v2 | 2.3 – 2.7 | ADT, ORM, ORU messaging |
| FHIR | R4 | Modern RESTful healthcare API |
| DICOMweb | 1.0 | Web-based DICOM services |
| IHE Profiles | Multiple | Interoperability workflows |
Healthcare System Integrations
RIS (Radiology Information System)
VannahHealthCloud integrates with RIS for:
- Order Management — Receive radiology orders via HL7 ORM messages
- Modality Worklist — Populate modality worklists from RIS schedules
- Status Updates — Send study status back to RIS (in-progress, completed, reported)
- Report Distribution — Deliver finalized reports to RIS
RIS System
│
│ HL7 ORM^O01 (New Order)
▼
VannahHealthCloud
│
├── Create Worklist Entry
├── Assign to Modality
│
│ HL7 ORU^R01 (Report)
▼
RIS System (Report Received)EMR / EHR Integration
Connect with Electronic Medical Record systems:
- Patient Sync — Bidirectional patient demographics via FHIR Patient resource
- Study Links — Launch viewer from EMR context (IHE XDS-I.b)
- Results Delivery — Push imaging reports to patient charts
- Order Entry — Receive imaging orders from EMR CPOE
FHIR Resources Used
| Resource | Direction | Purpose |
|---|---|---|
Patient | Bidirectional | Patient demographics |
ImagingStudy | Outbound | Study metadata |
DiagnosticReport | Outbound | Radiology reports |
ServiceRequest | Inbound | Imaging orders |
Practitioner | Inbound | Referring/reading physicians |
Endpoint | Outbound | WADO-RS retrieval URLs |
HMS (Hospital Management System)
Hospital-level integration for:
- Billing — Procedure codes and billing data for imaging studies
- Scheduling — Sync appointment schedules for imaging departments
- Bed Management — Patient location for portable imaging workflows
- Inventory — Contrast media and consumables tracking
HL7 v2 Message Flows
ADT Messages (Patient Administration)
MSH|^~\&|HMS|HOSPITAL|VHC|VANNAHCLOUD|20260101120000||ADT^A01|MSG001|P|2.5
EVN|A01|20260101120000
PID|1||PAT001^^^HOSPITAL^MR||DOE^JOHN^||19800101|M
PV1|1|I|WARD-A^101^AORM Messages (Orders)
MSH|^~\&|RIS|RADIOLOGY|VHC|VANNAHCLOUD|20260101120000||ORM^O01|MSG002|P|2.5
PID|1||PAT001^^^HOSPITAL^MR||DOE^JOHN^||19800101|M
ORC|NW|ORD001|
OBR|1|ORD001||71020^CHEST XRAY^CPT|||20260101120000ORU Messages (Results)
MSH|^~\&|VHC|VANNAHCLOUD|RIS|RADIOLOGY|20260101130000||ORU^R01|MSG003|P|2.5
PID|1||PAT001^^^HOSPITAL^MR||DOE^JOHN^||19800101|M
OBR|1|ORD001||71020^CHEST XRAY^CPT
OBX|1|TX|REPORT||Normal chest radiograph. No acute cardiopulmonary findings.FHIR API Integration
Base URL
https://api.teledokta.co.tz/fhir/r4Example: Query Imaging Studies
GET /fhir/r4/ImagingStudy?patient=PAT001&_sort=-date&_count=10
Authorization: Bearer <token>
Accept: application/fhir+jsonExample: Create Service Request
{
"resourceType": "ServiceRequest",
"status": "active",
"intent": "order",
"category": [{
"coding": [{
"system": "http://snomed.info/sct",
"code": "363679005",
"display": "Imaging"
}]
}],
"code": {
"coding": [{
"system": "http://loinc.org",
"code": "36643-5",
"display": "XR Chest 2 Views"
}]
},
"subject": {
"reference": "Patient/PAT001"
},
"requester": {
"reference": "Practitioner/DR001"
}
}IHE Profiles
VannahHealthCloud supports these IHE Integration Profiles:
| Profile | Description |
|---|---|
| SWF | Scheduled Workflow — Order to report lifecycle |
| PIR | Patient Information Reconciliation |
| CPI | Consistent Presentation of Images |
| KIN | Key Image Note — Flagging significant images |
| XDS-I.b | Cross-Enterprise Document Sharing for Imaging |
| WADO | Web Access to DICOM Objects |
| MWL | Modality Worklist Management |
Diagnostic Device Integration
Modality Configuration
To connect a new modality to VannahHealthCloud:
- Register the AE Title in Orthanc configuration
- Configure network — Set VHC IP and DICOM port (4242) on the modality
- Test connectivity — Run C-ECHO verification
- Configure worklist — Set MWL query parameters
- Send test images — Verify C-STORE operation
- Validate routing — Confirm images appear in the study list
{
"DicomModalities": {
"CT_SCANNER_01": ["CT_SCANNER_01", "192.168.1.100", 4242],
"MR_SCANNER_01": ["MR_SCANNER_01", "192.168.1.101", 4242],
"US_STATION_01": ["US_STATION_01", "192.168.1.102", 4242]
}
}