Healthcare Medication
Compatibility Assistant (Under NDA)

A clinical decision-support system that uses a fine-tuned LLM to validate prescriptions, detect drug-to-drug conflicts, and flag duplications before orders reach the pharmacy system.
Let's discuss your project
legaltech
Industry
Partnership
Since 2023
Team size
5 Engineers
How we started

A U.S. hospital network approached us following a series of medication-related incidents caused by manual cross-checks. Their existing EHR integration depended on static rule lists that could not capture complex interactions or new medications.

They needed a model capable of understanding context — dosage, timing, patient profile — rather than simple name matches.

Partners since 2023
Services Delivered
team Composition
Technology Stack
logo logo logo logo logo logo logo

Why They Chose Us

We had prior experience implementing compliant AI systems under HIPAA and ISO 13485 standards. Our privacy-first design, auditable pipelines, and explainable-AI (XAI) approach matched their governance requirements.

image
https://djangostars.com/wp-content/uploads/2025/04/badges-6.svg https://djangostars.com/wp-content/uploads/2025/04/badges-5-1.svg https://djangostars.com/wp-content/uploads/2025/04/badges-4-1.svg
Insights

Common Issues
We Identified

01 Rule Explosion:
legacy systems stored > 15 000 static interaction
rules, outdated quarterly.

02 Context Loss:
No differentiation between duplicate prescriptions
for different treatment phases.

03 Alert Fatigue:
Clinicians ignored > 60 % of alerts as irrelevant.

04 Audit Gaps:
Interaction justifications were missing from audit logs.

Solutions

What We Did

1. Knowledge Base and Normalization

  • Integrated RxNorm and local formulary data
    into a unified ontology.
  • Created embedding representations for active substances,
    dosage, and contraindications.

2. LLM Fine-Tuning

  • Fine-tuned a base transformer on de-identified clinical
    notes, pharmacist comments, and historical adverse-event reports.
  • Used retrieval-augmented prompting to ensure the model
    referenced verified sources only.

3. Explainable Inference Layer

  • Implemented a dual-channel output: concise alert + traceable
    reasoning graph (drug → pathway → conflict).
  • Stored every inference trace in PostgreSQL for audit and review.

4. Integration & Deployment

  • Built a REST interface to embed directly into the hospital’s EHR UI.
  • Deployed using containerized microservices
    on Azure with VNET isolation..
Impact and Results

Impact and Results

01/
Medication conflict detection accuracy ↑ 28 % vs rule-based baseline.
02/
False-positive
alerts ↓ 43 %.
03/
Average verification time per prescription ↓ 65 %.
04/
Clinician trust score (survey) ↑ from
3.1 → 4.6/5.