Jazline360: ABDM, GST, DLT and NABH
Designed in, Not Bolted On
Jazline360 was built for Indian statutory reality from the first line of code rather than adapted to it afterwards. That is a construction difference, not a feature list.
- ABDM and ABHA
- Patients are registered against their ABHA number, so one record follows them across every desk. The Health Information Provider registration is taken in the hospital’s own name, not Jazline’s — nothing is locked to the vendor, and the credentials move with you.
- GST e-invoicing
- The discharge bill and the statutory invoice come off the same record. Tax is computed per line at the correct rate, and exempt clinical services are excluded rather than rated and reversed later. The output register is not re-derived at month end.
- DLT registered SMS
- Templates are registered under the hospital’s own sender ID. Indian carriers drop any message whose template is not registered; Jazline360 refuses to queue one that would be dropped rather than reporting it as sent and leaving it to surface a month later.
- NABH documentation
- Records, audit trails and access logs are kept in the shape an assessor asks for. Jazline360 supports the documentation; the accreditation remains the hospital’s to earn. No software makes a hospital accredited, and any vendor saying otherwise is selling something.
Check Us Against the Source
Everything above is checkable against the programmes themselves. These are the primary sources rather than our summary of them.
- Ayushman Bharat Digital Mission
The programme itself — scope, milestones and the health facility registry.
- National Health Authority
The authority that runs ABDM, and the source for integration requirements.
- ABDM sandbox for integrators
Where an integration is built and tested before production credentials are granted.
- NABH
Accreditation standards, which are the hospital’s to meet rather than the software’s.
Four Questions to Ask Any Vendor
Including us. These do more competitive work than any feature comparison, and none of them is a trap — a vendor who has done the work answers all four in under a minute.
- Is that sandbox or production?
- A demo against a sandbox proves the code runs. It does not prove a record ever reached the registry. Ask which ABDM milestones are complete in production, and who did the functional testing.
- Whose name is the registration in?
- If it is the vendor’s rather than the hospital’s, your data moves when you move — and your leverage at renewal is not what you thought it was.
- What happens when a submission fails?
- Silence is the wrong answer. A failed submission should be held, surfaced to a named person and retried, not logged somewhere nobody reads.
- Can you show the safe-to-host certificate?
- Ask everyone, including us. A vendor who has it produces it in a minute. A vendor who does not will explain why the question is unfair.
Our Own Status, Stated Plainly
The clinical, billing, inventory, insurance and finance functions are built and tested from start to finish.
What Still Depends on an Account You Hold
Four areas wait on a registration or a merchant account the hospital itself must hold — not on more software from us. This is the part a prospect would otherwise discover in month three.
- ABDM production access
- Health facility registration and production credentials. The integration is built against the sandbox.
- Imaging (PACS)
- Connection to the hospital's existing imaging store. Ordering, scheduling, dose tracking and reporting are done.
- Card and UPI payments
- A payment gateway account. Bills, receipts and the ledger are complete; collection through the gateway is the remaining link.
- SMS and WhatsApp
- A DLT registration and an aggregator account in the hospital's name. Message templates are written and ready to submit.
Sandbox and Production
Where an integration runs against a sandbox rather than production, this page says so by name. A vendor who will not draw that line is telling you something, and the precision here is the asset rather than an admission.
What a Pilot Runs Today
A single branch can run registration, queue, OPD, pharmacy, laboratory, radiology, wards, theatre, inventory, billing, insurance, finance, HR and the patient portal today. Notifications, card payments and ABDM go live as each account is granted, without changing how anybody works.
And the reference positionCompliance Questions, Answered
The questions a hospital CIO and an administrator actually type, answered specifically enough to be checked.
What is ABDM HIP registration and does our hospital need it?
A Health Information Provider registration is how a hospital joins the Ayushman Bharat Digital Mission and links patient records to ABHA numbers. It is taken in the hospital’s own name. Jazline360 is built against it, but the registration and its credentials belong to the hospital.
Is Jazline360 ABDM compliant?
Jazline360 is built against the ABDM sandbox today. Production access needs health facility registration and production credentials the hospital holds. Jazline states that distinction because a sandbox demo proves the code runs, not that a record reached the registry.
What should we ask a hospital software vendor about ABDM?
Ask three things of every vendor, Jazline included. Which milestones are complete in production rather than sandbox. Whose name the registration is held in. And what happens when a submission fails — silence is the wrong answer; it should be held, surfaced and retried.
Does Jazline360 handle GST for a hospital correctly?
Tax is computed per line at the correct rate, and exempt clinical services are excluded rather than rated and reversed later. The discharge bill and the statutory invoice come off the same record, so the output register is not re-derived at month end.
Why do our hospital SMS messages not get delivered?
Indian carriers drop any message whose template is not registered under DLT. Jazline360 holds the registered sender identity and refuses to queue a message that would be dropped, rather than reporting it as sent and leaving it to be discovered a month later.
Does Jazline360 make our hospital NABH accredited?
No, and no software can. Jazline360 keeps records, audit trails and access logs in the shape an assessor asks for, which supports the documentation. The accreditation itself remains the hospital’s to earn.
Who owns the ABDM and payment registrations?
The hospital does. ABDM, the DLT sender ID and the payment merchant account are all taken in the hospital’s own name rather than Jazline’s. Nothing is locked to the vendor, and the records are exportable at any time.
See the Status on the Real System
On a call, with the sandbox and production boundary shown rather than described. Bring your CIO.
Or write to Jazlinemedical@gmail.com.