🔥
Agni by Lattice
  • 🔥Agni
  • 🏗️Technical architecture
  • 📣Key Features
    • FHIR data model
    • Access control
    • System administration
    • Representing relationships
    • Medication data
  • 📜User Stories
    • Appointment
    • Lab test
    • Consultation
    • Dispensing
    • Follow up
    • Referral out
    • Referral visit
  • 📒Detailed Scope
    • Organization
    • Practitioner
    • Scheduling and Appointments
    • Dispensing
    • Referral
Powered by GitBook
On this page

Was this helpful?

Technical architecture

PreviousAgniNextKey Features

Last updated 6 months ago

Was this helpful?

Offline-first design

Most public health systems have a tiered structure — beginning with home care, followed by community, primary, and secondary+ care. The more distributed the tier, the more interruptions it faces while accessing the internet.

Therefore, a system that supports community and primary care tiers has to be offline-first, by design. Agni achieves this through a two-way synchronization (sync) process, illustrated below.

Sync operates in the background, on a 15-minute schedule. As and when the network is available, 2-way incremental sync takes place — the mobile app sends new and updated data to the server, and the server does the same.

The app always initiates this “conversation”. This distributed architecture reduces load on the server by reducing the likelihood of concurrent requests.

🏗️