Healthcare: fewer queues, faster reports, cleaner claims

The architectural centre of everything we build in healthcare is a single patient record with a stable identifier, to which every interaction attaches: appointments, registrations, consultations, prescriptions, diagnostic orders and results, admissions, procedures, pharmacy dispensing, billing and claims.

That sounds obvious and is uncommon in practice, because most institutions grew system by system. The consequence of not having it is visible everywhere — a patient asked for the same information at three counters, a doctor unable to see a result ordered by a colleague, and a claim missing a document that exists in another system.

We build it either as a complete system or, more often, as a record layer that integrates the systems you already run and cannot replace immediately. The second path is slower to full benefit and far less disruptive, and for most institutions it is the right call.

Waiting time in an outpatient department is rarely caused by consultation length. It is caused by variability — appointments booked in uniform slots against consultations that vary from four to twenty minutes, patients arriving early or late, and diagnostics inserted into the middle of a visit unpredictably.

We attack it with better sequencing rather than more staff: appointment slotting informed by the actual distribution of consultation times per doctor and per visit type, pre-registration so paperwork happens before arrival, queue management with realistic live estimates communicated to the patient, and diagnostics scheduled as part of the visit plan rather than discovered mid-consultation.

The measurable outcome across our deployments has been average waiting time falling from around thirty-eight minutes to twelve, with the bigger effect being on the tail — the patients who used to wait ninety minutes.

For pathology and imaging, turnaround time is the product. We build the workflow from order to report: order capture with clinical context, sample collection with barcode labelling at the point of collection, tracking through processing, analyser integration where instruments support it, validation with reference ranges and delta checks, and report release with digital signature.

Analyser integration matters disproportionately. Results transcribed by hand from an instrument screen are both slow and a genuine safety risk. Direct integration removes transcription entirely for the instruments that support it, which in most labs is the majority of test volume.

Delivery follows the same principle as elsewhere: the report reaches the patient and the referring doctor automatically on WhatsApp or email with a secure link, rather than waiting for collection. Report turnaround in our deployments has typically moved from around six hours to forty-five minutes for routine tests.

Claim rejection is the largest avoidable revenue loss in most Indian hospitals, and the overwhelming majority of rejections are documentation failures rather than clinical disputes — a missing pre-authorisation, an unsigned form, a discharge summary lacking a required element, or a bill breakdown not matching the package.

We handle this by making documentation completeness a checkable condition at the point of care rather than at submission. The system knows what each payer requires for each package and flags what is missing while the patient is still in the hospital and the doctor is still available to sign.

Combined with pre-authorisation tracking, package rate mapping, and structured discharge summaries, this has taken clients from rejection rates around nine per cent to just over two, which on a hospital of any size is a substantial amount of recovered revenue.

India's health data architecture is moving towards interoperability, with ABHA identifiers, health information exchange and consent-based sharing. Institutions building systems now should build to that architecture even if they are not yet participating, because retrofitting is considerably more expensive.

We build ABDM-ready: ABHA linkage at registration, records structured to FHIR profiles, consent management, and the API surface required for health information exchange. Whether an institution activates participation now or later becomes a decision rather than a project.

This also has an immediate practical benefit independent of ABDM: records structured to a standard are portable, integrable and far easier to migrate when a vendor relationship ends.

For most patients the hospital website and the booking flow are the first interaction, and in Kolkata they are frequently the weakest part of the experience — a site that does not work on a phone, a booking form that emails a request nobody monitors, and no way to see a report without visiting.

We build the front door properly: fast mobile-first site with doctor and department information structured for search, real appointment booking against live availability, pre-registration, report access, and payment. For clinics and diagnostics chains this frequently produces more measurable return than any internal system, because it directly affects volume.

We are careful about regulatory constraints. Medical advertising norms limit claims and comparisons, and we build within them — what is always permitted, and undervalued, is genuine patient education about procedures, preparation and recovery.