Delivery journal · The context behind the implementationDiscuss a similar challenge ↗
Case study, India

Medical device integration case study: ABDM M1 to M3 for a rural screening program

Twelve devices. One record. A program that grew 14x.

We connected 12 medical devices to one offline record and certified it on India's ABDM network.

November 21, 2026 · 15 min read · Jitendra Choudhary, CTO & Co-Founder

See the outcome
Screening field app: today's checklist, a blood pressure reading and the visit summary
Business outcome

A small screening pilot became a program funders and the government can trust

Each number says where it comes from. Production numbers cover the first four months, Sep 2025 to Jan 2026.

Measured, production data

14x

More visits per month, on the same platform

185

Sep

956

Oct

1,227

Nov

2,582

Dec

Measured, production data

4,608

People screened in 4 months

5,727 visits and 9,200 prescriptions. Usage has grown several times since, as the client reports.

Measured, production data

16,592

Readings with no retyping

Saved straight from devices, so funders see the number the device read.

Verified with NHA

M1 to M3

A certified national product

On the ABDM partners page since Jul 30, 2026. Opens government programs to the client.

The screening kit

Client reported

CSR programs funders renew

Partners such as Tata Power get reach, findings and outcomes per program.

Delivery

30 to 40 days

First version in the field

Field fast, learn from real camps, then build on top.

The engagement

A foundation-backed platform screens people in villages, schools and factory towns with a kit of medical devices. Its programs include corporate health drives for Tata Power, school screening, family programs, NGO camps and doorstep care.

We built it as part of our medical device integration services and ABDM integration services.

Every device came with its own app, radio or cloud. Health workers copied numbers by hand, and visits were lost where there was no signal. The government wanted every record on the national ABDM network.

Live

First version in 30 to 40 days, from Aug 2025

Certified

ABDM M1, M2, M3 on Jul 30, 2026

Our role

Device layer, offline clinic server, ABDM, testing, field support

Team

Project manager, developers, daily QA and a dedicated support engineer

Stack

NestJS, PostgreSQL, Next.js, Android, Raspberry Pi 5

Before

Each reading stays on its own device screen

Values typed by hand, errors and all

No internet, no saved visit

Each new device is a new project

After

Every reading lands in the open visit

Nothing retyped. Device, time and unit kept

Clinic server saves offline, syncs later

New devices plug into one shared layer

Health workers screening people at a camp with the device kit
A screening camp at a corporate site.
Team at a site first aid center during field testing
Field testing at a site first aid center.

Field fast, learn, then build on top

Phase 1 was delivered in 30 to 40 days, so camps started screening right away. Every camp told us what to fix and what to build next. Phase 2 rebuilt the core for more partners, more devices and the national mandate, while phase 1 kept running and the data moved across.

Aug 2025 · 30 to 40 days

Phase 1: go live

7+ devices, mostly by webhook

Field visits from September

React, Node and Express

Nov 2025 onward

Phase 2: built to scale

12 device flows on one shared layer

Offline clinic server, ABDM, AI

1,228 commits, 74 tables, 392 API endpoints

Phase 1Phase 2
Adding a deviceCode change for each deviceSettings change when the protocol is known
No internetVisit cannot be savedClinic server keeps the full record
National networkNoneABDM M1, M2, M3, certified
StackReact, Node and ExpressNestJS, Next.js, Android app, Raspberry Pi

Any device, one path into the record

We built a device intake layer. Each device gets a small adapter for its protocol. Everything after it is shared, so a new device does not mean a new project.

Capture

Device sends

Bluetooth, SDK, USB, webhook, cloud or maker app

Adapt

Adapter reads it

One small handler per protocol, picked by device code

Map

Fields mapped

Vendor fields to standard readings, in admin screens

Check

Quality checked

Units, ranges, duplicates and retries handled once

Save

In the visit

Online or offline, ready for reports and ABDM

Settings only

A new model on a protocol we already handle: add the device type, map its fields, switch it on per facility. No app update.

Small code change

A maker with a new protocol: write one adapter. The rest of the path is reused. Omron, Chipsea, AyuSynk and Spandan were added this way.

Omron blood pressure monitor

Blood pressure

Omron, Bluetooth SDK, live

Body composition scale

Body composition

Chipsea, Omron, Bluetooth, live

anuPath glucose analyser

Blood glucose

anuPath, direct Bluetooth, live

EzeCheck haemoglobin device

Haemoglobin

EzeRx, webhook, live

AyuSynk stethoscope

Heart sounds

AyuSynk, SDK and cloud AI, live

Agatsa ECG

ECG and vitals

Agatsa, app hand-off, live

Swaasa lung health app

Lung health

Salcit Swaasa, cloud API, live

Remidio eye camera

Eye images

Remidio, cloud API, in progress

Also built: Spandan 12-lead ECG over USB, Omron body composition, Agatsa SanketLife SDK. The layer supports 9 connection types: cloud API, file, manual, HL7, FHIR, Bluetooth, maker SDK, webhook and QR scan. Status from the code on Nov 21, 2026. More on device data and FHIR in our guide to medical device integration with FHIR.

Health worker using the tablet next to the devices
The tablet app with the haemoglobin meter, BP monitor and stethoscope in the field.
The full screening kit
The full kit a health worker carries. Photo: client.

Three places, one record

Everything sits in one of three places: the camp, our cloud, or the national network. The camp never depends on the other two to keep working.

At the camp, works offline

Medical devices

12 device flows, 9 makers

Tablet app

Android, 4 languages

Clinic server

Raspberry Pi 5 with the full record

Our cloud

Platform

Records, programs, reports, device setup

Device maker clouds

Heart, lung and ECG results

AI services

Lab report reading, program assistant

WhatsApp and SMS

Reports and prescriptions to patients

National network

ABDM

Health IDs, consent and record exchange with every ABDM provider in India.

Visits go out as encrypted records, and past records come in, only with the patient's consent.

What happens when the signal drops

Save

Readings save to the clinic server, signal or not

Wait

Visits and audio wait, with a pending count on screen

Sync

The server pushes after version and disk checks

Confirm

Dashboards update, reports go out, ABDM sharing runs

How a national program is organized

Each level sees only what sits below it, so a corporate partner sees its own camps and nothing else.

Platform the foundation runs all programs
Partner organization a Tata Power CSR program, a school network, an NGO
Facility a district
Sub-facility a block or campus
Clinic a camp, a school day, a doorstep route
Kit tablet, devices, clinic server
Patients and visits
RoleSees and does
Super adminEvery program. Sets up devices, sites and users
CSR managerTheir partner's programs and outcome reports
Site adminOne facility, its clinics and staff
DoctorReviews visits, prescribes, refers
Nurse, testing staffRegisters patients, runs device tests in the camp

Certified for all three ABDM milestones

ABDM is India's national digital health network. Device readings now reach the patient's ABHA health account, with consent.

M1

Health ID

ABHA created at registration by Aadhaar or mobile OTP, then linked to the patient.

M2

Share

Each visit becomes a record. Readings go out as encrypted FHIR on consent.

M3

Fetch

Doctors pull past records from other providers into the visit, with consent.

DateMilestone
Jun 10, 2026NHA approves functional testing
Jun 16Security audit findings closed
Jul 2Functional testing passed for M1, M2, M3
Jul 13 to 16Test, Safe to Host and security certificates
Jul 27NHA demo passed
Jul 30Integration complete, listed on ABDM partners page
Aug 2026Running on ABDM production

Where the ABDM time went

Our build, M1 to M3
Feb to May
Lab testing and audit
Jun
NHA review and demo
Jul

Testing and review run on the government's calendar. Plan for about two months after the build is ready. Step by step in our ABDM certification guide.

What the client had to provide+
A registered organization and product with ABDM, a signed undertaking for NHA, an empanelled lab for functional testing and security audit, and a production facility ID, which needs a real site and its owner's ID.

Security, ownership and how we work with you

The questions a buyer asks before signing, answered from this project.

Security

Audited before go-live

The Android app passed an independent mobile security audit, with findings closed in a week. The product holds a Safe to Host certificate for ABDM.

Health records leave only with patient consent, encrypted the way ABDM requires. Every user has a role, and each role sees only its own sites.

Ownership

The client owns the product

The code lives in the client's own repository. Their tech lead merges and deploys.

Nothing is locked to us. Each device integration has its own written workflow in the repository, so another team can pick it up.

How we engaged

A monthly team

Project manager, developers and daily QA, billed monthly, with a separate support retainer after launch.

What the client ran

Shared ownership

The client's team owned field operations, device vendors and ABDM registration. Their tech lead reviewed and released our work.

A day on the platform

Thirteen screens, from the first sign-in to the funder report. Pick a step to see who uses it, why it works that way, and what happens when it goes wrong. Screens show the redesigned product with sample data.

Sign in screen

Nurse or testing staff, 7:30 am

Sign in

Staff sign in with their mobile number. The tablet then works all day without a signal.

Why it works this way

Sign-in is the only step that needs the internet, and it happens before leaving the office.

When it goes wrong

No signal at the camp: staff stay signed in on the tablet. Four languages are on the sign-in page.

Today's camp screen

Testing staff, all day

Today's camp

One queue shows every patient, their token and progress. The kit panel shows which devices are paired and ready.

Why it works this way

Three people share one queue in a noisy room. Each row names the next step as its button.

When it goes wrong

Internet drops: a banner says visits are saving on the camp server and how many wait to sync.

Register and ABHA screen

Registration desk, 2 minutes

Register and ABHA

The mobile number is checked first. A new patient gets ABHA by Aadhaar OTP, mobile OTP, an existing ABHA, or later.

Why it works this way

Duplicates ruin follow-up, so the number check comes first. ABHA never blocks screening.

When it goes wrong

OTP never arrives: switch to mobile OTP or skip. ABHA is added at the next visit.

Readings screen

Testing staff, 10 to 15 minutes

Readings

Each reading lands from the device with its result band, the last value and its source device.

Why it works this way

The source builds trust in the number. The last value turns one reading into a trend.

When it goes wrong

Device fails or battery dies: mark the test Not done with a reason. It counts in completion.

Doctor review screen

Doctor, often remote

Doctor review

Readings, history and rule-based suggestions that name the rule, values and limit. Prescriptions start from a preset.

Why it works this way

Suggestions explain themselves so doctors can trust or reject them quickly. Presets keep prescribing consistent.

When it goes wrong

Doctor disagrees: they dismiss it with a reason, which feeds the next review of the rules.

Follow-up screen

Program coordinator, weekly

Follow-up

Everyone flagged who has not returned, oldest first, with the reason in plain words and every call logged.

Why it works this way

A screening program is judged on what happens after the camp.

When it goes wrong

No answer: the call is logged and the patient stays on the list, ready to book into the next camp.

Patients screen

Any staff member

Patients

Search by name, mobile, ABHA or ID across every site, with risk flags and ABHA status.

Why it works this way

Staff should never need to know which site a patient was first seen at.

When it goes wrong

Two records for one person: flagged for an admin to review.

Kits and devices screen

Program admin

Kits and devices

Every device type, what it measures, how it connects and which programs use it.

Why it works this way

The device intake layer made visible. Programs grow by adding devices, not by waiting for a release.

When it goes wrong

A kit has not synced for 48 hours: it is listed at the top so someone calls the camp lead.

Integration health screen

Support engineer, every day

Integration health

Every device cloud, webhook, ABDM, WhatsApp and camp link, with failures, queue and last success.

Why it works this way

Field teams should hear about a problem from us first.

When it goes wrong

A maker cloud goes down: readings queue, support is alerted, and the queue clears on its own.

Clinical rules screen

Medical lead

Clinical rules

Result bands, limits and actions per reading, versioned and checked on past data before saving.

Why it works this way

Rules decide who gets flagged, so they belong to doctors and every change is recorded.

When it goes wrong

A new limit would flag far more people: the 30-day check shows it before it goes live.

Program overview screen

Program manager, weekly

Program overview

Reach, completion, findings, care and outcomes, each with a target and the previous period.

Why it works this way

Every number has a comparison, so a manager knows at once if it is good news.

When it goes wrong

A site has not synced: its last sync shows in amber so nobody reads stale numbers.

Analytics screen

Program analyst

Analytics

Symptoms, conditions, family history, age, busy hours and medicines.

Why it works this way

It brings the separate analytics tool from phase 1 inside the product.

When it goes wrong

A question not in the library: ask it in plain words. Answers are read-only and limited to your sites.

Reports screen

Program lead, monthly

Reports

Funder reports, patient reports on WhatsApp and exports, with what was sent and when.

Why it works this way

Funders pay for proof of reach and outcomes. Patients deserve their own results.

When it goes wrong

A report waits on unsynced kits, or WhatsApp fails: both show, with Send anyway and Resend failed.

Adoption in the first four months

From the production database on Jan 8, 2026, counted by row, no personal data read. Some sites are test sites, so read these as upper limits.

4,608

patients registered

5,727

visits

13,260

tests ordered

9,200

prescriptions

Readings by device

16,592 readings saved straight from devices

Body composition
4,952
Vitals (Health360)
4,733
Haemoglobin
4,014
Blood glucose
2,473
Heart sounds
294
ECG
126

591

referrals to a doctor or hospital

109

clinics set up

77

staff users

4

languages: English, Hindi, Marathi, Gujarati

Built to fail safely, and to tell us first

Field programs fail in small ways every day. No reading is ever lost, and the support team hears about a problem before the camp does.

Detect

Every call logged: started, called back, failed, timed out, retrying, done

Retry

Three tries with duplicate protection

Queue

Raw data kept, reading waits with a clear status

Alert

The link turns red and support is alerted

Recover

Queued items process once the link is back

FailureWhat staff seeWhat the system does
Device maker's cloud downReading saved, analysis pendingRetries 3 times, queues, alerts support, processes when back. Happened in June 2026, fixed in 4 days.
Webhook never arrivesTest shows waiting, then timed outThe raw request is kept, staff can retake.
Camp offline for daysBanner with pending countCamp server keeps everything. Sync runs with version and disk checks.
Camp server problemNothing, in most casesWatchdog restarts it. Nightly backup. Self-update when online.
Device not paired or battery lowKit panel shows it before the patient arrivesTest marked Not done with a reason, counted in completion.
ABHA OTP or ABDM failsClear message and another routeScreening continues. Sharing retries and is logged.
WhatsApp report not deliveredFailed count on ReportsDelivery tracked per message, one click to resend.
Bad data from the fieldError beside the field, input keptLimits checked on save. Seen in production and fixed with a migration.
Integration health screen

Proactive support, not a ticket queue

Our support engineer checked the failure logs every morning, before camps opened. When a vendor link broke or a kit stopped syncing, the client heard it from us with a plan, not from a health worker in the field. The redesigned Integration health screen turns that daily routine into automatic alerts.

Every case a camp meets

ScenarioWhat the system does
Returning patientMobile check finds the record. Last readings appear next to today's.
No phone or AadhaarScreened in full. ABHA offered at the next visit.
Child at a school campGuardian consent recorded. Linked to the school report.
Pregnant womanPregnancy tracked and linked to the maternal health program.
Urgent readingBP 180/120 or above: retake in 5 minutes, then refer the same day.
First-time high sugarDoctor prompted to confirm at the PHC before any medicine.
Patient does not returnStays on the follow-up list with days overdue and a call log.
Records from another hospitalWith consent, pulled in through ABDM and shown in the visit.
New device for a programAdded in kit setup, switched on per site, no app update on known protocols.

Real incidents, and how we fixed them

A vendor changed its login

Heart-sound analysis failed on every upload when the maker began requiring the real device ID. We added it for each kit and shipped the fix four days after the first failure.

An update disrupted a camp

An ABDM change reached the field mid-camp. We brought back release notes before every field build.

Real data broke field limits

Medicine names were longer than the field allowed. We widened it to match the catalog with a migration.

Production needed a real facility

Until the production facility ID arrived, we ran production through NHA's testing facility, then switched by one setting.

A product team, not a ticket queue

We worked beside the client's field team, tested every day, supported every camp, and brought back what we saw on the ground.

Daily testing

A QA tester ran the field flows every day on fresh Android builds, so issues were caught before they reached a camp.

Dedicated support

A support engineer handled field issues, device pairing and data fixes on a fixed monthly retainer, and warned the client before problems reached a camp.

Ground-level input

We pushed for offline mode for low-signal camps, release notes before every field build, and quick device fixes when vendors changed their APIs.

Clear reporting

Weekly updates and a monthly report with work done, open issues and next steps.

Nirmitee and client teams after a planning session

Code activity by month

Commits, Nov 2025 to Sep 2026. Peaks match the ABDM build and certification fixes.

NDJFMAMJJAS
School eye screening Haemoglobin screening of a student Dental screening at a school Blood test at a screening camp

“You have been great partners and always there when we needed you. Really appreciate it.”

Client team, Sep 5, 2026

Where the same device layer fits

Our view, not delivered work. The intake layer does not care which country or program it runs in.

US rural clinics and mobile units

Screening vans and rural health clinics that carry point-of-care devices and need readings in the EHR as FHIR.

Remote patient monitoring

Home BP cuffs, scales and glucose meters feeding one record, with offline buffering.

Employer and CSR drives

Corporate camps that screen thousands of workers and need reportable data.

School and community screening

Health worker programs in low-signal areas across India, Africa and Southeast Asia.

Device makers

Makers who want their device in EHRs and national networks without building it.

Have devices that need to talk to your record?

Tell us the devices and where they run. We will map the adapters, the offline plan and the standards you need.

Book a 30-min call

Sources: production database snapshot, 8 Jan 2026 (row counts only); project emails Feb to Sep 2026; team chats Jun to Nov 2026; code history Nov 2025 to Sep 2026. Device photos are maker product images. Field photos by the client and our team.

Questions buyers ask

How long does medical device integration take?
Weeks, for devices with an open protocol or SDK. In this project the first version was delivered in 30 to 40 days. Each further device on a protocol we already handle is a settings change, not a new release.
How long does ABDM M1 to M3 certification take?
About four months to build M1 to M3 into an existing product, then about two months of lab testing, security audit and NHA review, which run on government schedules.
Can the screening app work without internet?
Yes. Each camp runs a small server with the full record. Visits and readings save on site and sync to the cloud when the connection returns.
What slows a device integration down?
Waiting on the device maker for SDK access, test devices and API keys. Vendors also change APIs without notice, so someone must watch the integrations after go-live.
Who owns the code?
The client. The code lives in the client's own repository, and each device integration has its own written workflow so another team can pick it up.