🔥
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?

  1. Key Features

Medication data

PreviousRepresenting relationshipsNextUser Stories

Last updated 6 months ago

Was this helpful?

We are in the process of incorporating the WHO’s essential medicine list into a FHIR-friendly format; a quarter has been completed. The dataset does not contain brand names; it only contains formulations.

Given the complexity of pharmacological data, we have taken care to translate drug information into a FHIR structure that fully captures its nuances. This information is available while prescribing, and while dispensing.

Consider a combination drug commonly used to treat hypertension: Amlodipine 5 mg + Lisinopril 10 mg tablet. This drug is deconstructed as follows:

As demonstrated above, each ingredient, and even the salt form, is encoded. Drug strength (by ingredient) and are also captured. Since this drug is commonly prescribed, the combination itself has a SNOMED-CT code. If it were more esoteric, we would have coded the individual ingredients, rather than the combination.

This structure also enables us to connect to drug-drug interactions (DDI) and adverse drug reaction (ADR) databases — if we are given access to such a dataset.

📣