How It Works — nBogne

The Insight

Data Layer, Not Application Layer

Most interoperability solutions work at the application layer — they require internet to function. When internet fails, they fail.

nBogne works at the transport layer. We don't touch your protocols, your data formats, or your workflows. We just move the packets — over whatever path is available.

Internet → GPRS → SMS. Automatic fallback. Seamless switching.

1

Your EHR sends data Any format: FHIR, HL7, JSON, XML

2

nBogne compresses 80–97% smaller for low bandwidth

3

Auto-select channel Best available: internet, GPRS, or SMS

4

Deliver & confirm Retry until confirmed delivery

Core Capabilities

🔗 Vendor-Agnostic

Works with existing systems without modification.

OpenMRS, OpenEMR
DHIS2, OpenHIM
FHIR R4 compatible
HL7v2 (2.3, 2.5, 2.7)
JSON / REST APIs

🔄 Automatic Fallback

Seamless switching between channels.

Internet (when available)
GPRS/2G (primary fallback)
SMS (ultimate fallback)
No manual intervention

📦 Intelligent Compression

Optimized for low-bandwidth environments.

80–97% payload reduction
5–15 KB typical packet size
Works on 20–50 kbps
Z-Standard algorithm

✅ Guaranteed Delivery

Messages persist until successfully delivered.

Local queue (survives power loss)
Exponential backoff retry
Delivery confirmation
Dead letter inspection

Technical Scope

What we handle today — and what's coming.

📋 Today: Medical Records

Text-based health records averaging 5–15 KB after compression. This covers 90%+ of routine health data needs.

Patient demographics
Lab results (text)
Prescriptions
Visit summaries
Surveillance data

🔭 Future: Medical Imaging

Medical images require different infrastructure. We're exploring mesh networks and LEO satellite options.

X-rays, CT scans
Ultrasound images
Mesh network transmission
Low Earth Orbit options
Coming 2027+

Security by Design

Stateless architecture means we can't lose what we don't store.

🛡 No Data at Rest

Clinical data passes through RAM only. Never touches disk. 60-second maximum processing window.

🔒 End-to-End Encryption

Data encrypted from source to destination. We route but cannot read.

📝 Metadata-Only Audit

Logs contain: timestamp, source, destination, size, hash. Never clinical content.

⚖ Compliance Ready

Ghana DPA, HIPAA, GDPR compatible. Architecture handles compliance by default.

Integration

Days to weeks, not months

nBogne is designed for rapid deployment. For EMRs with standard APIs, integration typically takes days. For complex legacy systems, we work with your team on custom adapters.

Either way, faster than building offline capability in-house. And we handle the maintenance, updates, and carrier relationships.

Discuss your integration

Integration Options

REST API (recommended)
FHIR R4 native
HL7v2 adapter
Custom webhook
SDK (Python, Node.js)

Don't see your stack? Contact us — we're flexible.

Partnership Model

We're not competing with EMR vendors. We're making you win.

💻

For EMR Vendors

Bundle nBogne with your solution. Add "works offline" to your feature list without building it. Win bids in connectivity-challenged markets.

🏥

For Hospital Networks

Stop paying $640+/facility/year for Starlink. nBogne works on existing cellular infrastructure at $110–510/yr per facility.

🔬

For Research Organizations

Field trials in remote areas? Maintain 100% data flow to sponsors even without internet. No more batch uploads.

🏛

For Governments

National health information exchange without centralized storage risk. Real-time disease surveillance. Scales from pilot to nationwide.

How nBogne Works