Sparsha · the platformSparshaCurrently in Nepal. Designed for South Asia.

A hospital should not need five systems to see one patient.

Sparsha is one platform for how a hospital runs and what its clinicians record. Registration, the clinical record, billing, pharmacy, lab orders and the government report, in a single system with a single patient record underneath.

What it replacesA hospital management system and a clinical record, bought separately, joined by hand.
In buildRegistration and front deskThe clinical recordBillingPharmacyLab orders and resultsHMIS reporting
The problem

Two systems, one patient, and a gap that a person closes by hand.

A hundred patients arrive in a morning. Registration writes a name, the doctor writes a note, the cashier writes a bill, the pharmacy writes a dispense. In most hospitals those four writings live in two or three different systems, and the thing that reconciles them is a person with a register and a pen.

So the same patient exists three times, spelled three ways. The doctor sees the visit but not the payment. The desk sees the payment but not the diagnosis. When the power goes the queue does not stop, so paper comes out, and the paper is entered again later, by whoever has time.

EHRs are largely used by hospitals at present for billing purposes rather than to facilitate clinical care.

World Bank · Electronic Health Records in Nepal: Readiness Assessment · 2023
Why Nepal

The hardest version of this problem is on our own street.

Nepal is where we work and it is also where the constraints forgive the least. A system that holds here does not need much added to hold anywhere else in South Asia.

PowerA record that cannot be written during a cut is not a record. Sparsha assumes the cut.
Two languagesNames, instructions and printouts are Nepali and English in the same visit, often on the same slip.
One name, three spellingsTransliteration makes duplicates faster than any duplicate check can catch them. One patient has to survive all three spellings.
The front deskWhoever sits there this month is who the software is really for. It has to be learnable in an afternoon.
Paper in the middleHandoffs happen on slips. The system has to accept the slip later without punishing the person who wrote it.
The government reportReporting is monthly, mandatory, and assembled by hand out of whatever each module happened to keep.
The category

Three shapes, and the seam is always in the same place.

No products named. These are the shapes the category ships in, drawn as they are sold.

01Billing core, records bolted on
Billing · admissions · cash
Records

The record exists so the bill can be raised. Clinical detail goes in only as far as billing needed it, which is why the chart reads like an invoice with symptoms attached.

02Clinical core, operations imported
Clinical record
Another system’s parts
QueueCounterStore

The chart is real. The queue, the counter and the store arrive from somewhere else, keep their own idea of who the patient is, and meet the chart in a nightly file.

03Five products, one logo
Sold as one suite

Bought as one, deployed as five. Five logins, five support queues, and five answers to the question of which record is the patient’s real one.

The platform

One record, and everything that touches it.

Drawn as a schematic, because no screen is finished enough to photograph. Two states only: in build, and designed next.

One patient recordEvery module below writes here. Nothing keeps a second copy.
01In build
Registration and front deskSearch, admit, queue, and print, with one patient identity behind all four.
02In build
The clinical recordNotes, vitals, diagnoses, prescriptions, written by the person who saw the patient.
03In build
BillingCharges raised from what actually happened in the visit, not typed again from a slip.
04In build
PharmacyDispense against the prescription in the record, so the record knows what was given.
05In build
Lab orders and resultsOrdered from the chart, returned to the chart, visible to the desk that has to chase it.
06In build
HMIS reportingAssembled from the record as the month runs, not reconstructed at the end of it.
Designed next
07Designed next
Insurance claimsClaim built from the same visit rows the bill was built from.
08Designed next
InventoryStock that decrements when the pharmacy dispenses, not when someone remembers.
No module is marked live, and no installation is named. When one is, this map gains a third state and not a sentence.
One record per patientRegistration, the chart, the bill and the dispense are views of one row, not four copies of it.
The front desk is the productThe busiest screen gets the most design attention. The demo screen gets the least.
It works through a power cutWriting continues while the power and the link are gone, and reconciles when they return.
Entry respects a hundred-patient dayAny field a clerk has to type twice is treated as a defect, not as training.
Status
In build

Sparsha is being built now. There is no installation to name and no number worth quoting, so this page quotes none. Every diagram here is a schematic. When there is something real to show, it will be shown here instead of described.

Where it runsCurrently in Nepal.Designed for South Asia.
Book a demo

Bring us the busiest morning you have.

+977 9747857291Call and ask for a walkthrough. One number, answered by the people building it.
Prefer to write
Start a project

Tell us what is breaking and we will tell you what it takes.

The first call is scoping, not sales. You will speak to the people who would build it.

RegionSouth Asia
CareersOpen roles
Budget$15k
$5k$15k$30k$50k+
Goes to the team that would build it.