Referral Network & DHIS2/FHIR Offline Workflow Guide
An operational technical manual detailing offline-first store-and-forward protocols, open-standard data exchange, and closed-loop patient referral tracking between primary healthcare clinics and referral hospitals in Timor-Leste.
1. Interoperability Mandate & Operational Rationale
Bridging Municipal Primary Care & National Tertiary Hospitals
A central challenge facing the Ministério da Saúde (MdS) in Timor-Leste is the disconnect between primary care clinical encounters at municipal Centros de Saúde Comunitários (CSCs) and tertiary care management at Hospital Nacional Guido Valadares (HNGV) and regional referral hospitals.
The Referral Network & DHIS2/FHIR Offline Workflow Guide defines the standard operating procedures for bridging these health system tiers. By combining Fast Healthcare Interoperability Resources (FHIR) data standards with the national District Health Information Software 2 (DHIS2) aggregate database, this protocol ensures that patient referrals, laboratory orders, and clinical summaries sync seamlessly—even during severe electrical grid disruptions or telecommunication network outages in rural municipalities.
2. Core Technical Workflows & Data Exchange Protocols
Click on each workflow below to expand operational procedures and data schemas.
Workflow 1: Offline-First Store-and-Forward Syncing Engine
Operational Mechanism: Manages local database queuing during internet connection loss in municipal health centers.
- Local Encrypted Caching: Patient encounter logs, maternal health registers, and referral slips are encrypted (AES-256) and saved locally on solar-powered tablet nodes.
- Automated Heartbeat & Sync Trigger: The mobile client detects network recovery (3G/4G or Wi-Fi) and initiates background data synchronization without disrupting nurse workflows.
- Conflict Resolution Rules: Server-side timestamp reconciliation resolves data collisions when duplicate offline edits occur across multiple devices.
Workflow 2: Closed-Loop Referral Tracking (CSC to HNGV)
Operational Mechanism: Connects primary care clinic transfers with hospital emergency and specialist admissions.
- Digital Referral Generation: CSC nurses issue a standardized FHIR-compliant digital referral resource detailing vital signs, preliminary diagnosis, and urgency level.
- Hospital Admission Check-In: HNGV triage officers scan the patient's digital QR code or search the national health registry ID to instantly retrieve clinical history.
- Automated Counter-Referral Feedback: Upon patient discharge from HNGV, a discharge summary automatically routes back to the originating CSC for post-acute community follow-up.
Workflow 3: Open API Integration (FHIR to DHIS2 Data Exchange)
Operational Mechanism: Translates granular point-of-care patient transactions into national aggregate health statistics.
- Application Programming Interface (API) Middleware: An automated broker converts FHIR JSON clinical payloads into DHIS2 Data Value Sets.
- Automated Monthly Aggregate Tallying: Replaces manual paper tallying sheets at CSCs by automatically compiling disease incidence and maternal visit totals into DHIS2.
- Data Quality Validation Rules: Pre-submission validation checks filter out impossible values (e.g., age-incompatible diagnoses) before data enters the national database.
Workflow 4: Laboratory Sample Routing & Diagnostic Results Return
Operational Mechanism: Coordinates specimen transport and digital lab result transmission between rural clinics and central laboratories.
- Specimen Tracking Barcodes: Sputum, blood, and diagnostic samples are tagged with unique barcode identifiers linked to the patient's electronic record.
- Digital Result Push Notification: As soon as HNGV or regional hospital labs finalize diagnostic tests (e.g., TB GeneXpert or HIV viral load), results automatically push to the requesting CSC nurse terminal.
| System Architecture Tier | Data Exchange Protocol | Primary Technical Tool / Middleware | Synchronization Frequency |
|---|---|---|---|
| Point of Care (CSCs) | Offline-First FHIR JSON Payload | Ruggedized Android Tablets & Local SQLite Cache | Instant when online; queued store-and-forward when offline |
| Regional Referral Nodes | RESTful API / FHIR Engine | Regional Hospital Server Node & OpenHIE Broker | Real-time background transaction processing |
| National Repository (MdS) | DHIS2 Data Value Sets / Web API | National Health Information System Database Server | Automated daily & monthly aggregation cycles |
3. Disaster Resilience & Cybersecurity Architecture
AES-256 Device Encryption
All offline tablets and local server nodes employ full-disk hardware encryption to safeguard patient confidentiality in the event of device theft or loss in remote municipalities.
Role-Based Access Control (RBAC)
Strict user permission levels restrict patient clinical details to authorized attending nurses and physicians, while providing anonymized data streams for public health planners.
Redundant Solar-Backed Nodes
Local data caching hubs at municipal health centers are wired to auxiliary solar PV systems, preserving database query capabilities during multi-day regional power blackouts.
Immutable Data Audit Logs
Every creation, edit, or referral status update generates an immutable, timestamped audit log entry to support clinical quality assurance and system security monitoring.
Need API Specifications or Technical Schemas?
For complete FHIR implementation guides, DHIS2 database mapping tables, or software middleware specifications, contact Masese Consulting Group.
Contact Senior Technical Advisor →