What we are building

A claim startsas handwriting.

The exchange wants a structured, coded record. A ward runs on a case sheet and a ballpoint pen. We are building the layer in between — so nobody has to ask a doctor to type.

Case sheetIP 40161 · Ward 3B
M. Iyer · 58 / MAdm 14 MarCardiology
c/o chest pain x 2 days. k/c/o DM-2, HTN
CAG: LAD 90%. PTCA + DES x 1 done 14/3
Rx T. Ecosprin 75 OD, T. Atorva 40 HS
Stable. adv. disch 18/3
Dr. S. Raghavan
Structured recordREADING
Diagnosis
I25.10Atherosclerotic heart disease
E11Type 2 diabetes · I10Hypertension
Procedure
PTCA with drug-eluting stent
Implant · DES × 1 · 14 Mar
Medication
Aspirin 75 mg, once daily
Atorvastatin 40 mg, at night
Discharge
18 Mar · stay of 4 days
FHIR R4 bundle — shaped for the exchange

Before any of that

Nothing arrives in the same shape.

A case sheet, a lab report on a different pad, a prescription in shorthand, a scan someone photographed at the counter. Four formats, four hospitals, no two alike. Normalising that is most of the work of getting a hospital onto the exchange. That is the part we are building.

Case sheet
Handwritten
Lab report
No codes
Prescription
Shorthand
Scan at the counter
Image only
Structured record
I25.10Atherosclerotic heart diseasecoded
E11Type 2 diabetescoded
PTCA with drug-eluting stentmapped
Aspirin 75 mg, once dailymapped
One record, one shape, one code set

How it works

From the case sheet to the settlement advice.

Four steps. The first one is the one everybody skips.

01

Capture

The sheet as the clinician wrote it — photographed at the counter, or pulled from the HIS where it already exists.

02

Structure

Free text mapped to ICD-10 and packaged as a FHIR R4 bundle. Anything the payer will ask for and cannot find gets flagged here.

03

File

Submitted on the exchange with the pre-auth trail attached, so the payer gets the clinical basis and the claim in one message.

04

Follow

Queries answered against structured fields, short-payments traced back to the line that caused them, settlement matched to the UTR.

The exchange

One connection, and everyone is on the other side of it.

NHCX is the National Health Authority’s claims exchange, part of ABDM. Instead of every hospital wiring up to every insurer, each party connects once and the exchange routes between them. A structured claim is something the payer’s system can read, answer and pay against.

Filed At the payer Settled · UTR …8841
Hospital NHCX Insurer or TPA
Run by the NHARun by the National Health Authority as part of the Ayushman Bharat Digital Mission.
FHIR R4 on the wireClaims travel as structured HL7 FHIR R4 bundles, which is why the record has to be coded before it goes.
ABHA identifies the patientThe health ID under ABDM travels with the claim, so the payer can match it without paperwork.
Consent is part of itSharing a record needs the patient’s consent, captured and recorded alongside the claim.

The platform

What actually sits between the ward and the payer.

Records come in however the hospital already produces them. They leave as one structured claim on the exchange, and everything that happens to it afterwards comes back down the same path.

Where records come from
Case sheethandwritten, at the bedside
HIS / EMRwhatever is already structured
Lab and pharmacyreports, implant invoices
Photographed at the counteran image of a page
ZicoHealth
Ingestone place for every format
Readhandwriting and free text lifted off the page
Codediagnosis and procedure mapped to ICD-10
Assemblea FHIR R4 bundle with the documents attached
Checktariff, pre-auth and missing paperwork, before filing
Trackqueries, short-payments and settlement, back down the chain
Where it goes
NHCXthe exchange
Insurers and TPAspre-auth, queries, approval
Settlementadvice matched to the claim

Who it is for

Three parties, one claim between them.

The exchange only works if every side of it is holding the same record. Each of them needs something different from it.

Hospitals

The bedside does not change. The billing desk stops re-typing.

  • Clinicians keep writing on the case sheet
  • Discharge summary, implant invoice and pharmacy list gathered before the claim is filed
  • Tariff and pre-auth checked while the patient is still admitted
  • One connection to the exchange instead of a portal login per payer

Insurers

Claims that arrive readable, with the reasoning attached.

  • FHIR R4 bundles, coded to ICD-10 before they arrive
  • Pre-auth and enhancement requests carry the clinical basis with them
  • Deficiency queries answered against the fields they refer to
  • The same shape of claim from every hospital on the exchange

TPAs

One queue instead of one portal per insurer.

  • Claims from every empanelled hospital in a single work list
  • Documents requested and returned on the claim itself
  • The same claim state visible to the hospital and the payer
  • Settlement advice matched back to the claim and the UTR
zicohealth

Coming soon.

Leave an email and you will hear from us once, on the day it opens.

Opening your mail app — send it and you are on the list.