Automating CGHS Emergency Admission Intimation

For a CGHS-empanelled hospital, treating the patient is only half the job. The other half is telling CGHS, through the prescribed channel and within the prescribed time, that the patient has been admitted. Miss that step and a fully justified admission can turn into a disputed or delayed claim.

This article explains what emergency and referral intimation is meant to achieve, why hospitals miss it, and how an automation agent can make intimation a routine that happens on time, with proof.

What emergency and referral intimation is

Conceptually, intimation is a formal notice from the hospital to CGHS that a beneficiary has been admitted. It gives the scheme visibility of the admission while it is happening, rather than learning about it only when a bill arrives after discharge.

There are two broad situations:

• Emergency admissions — the beneficiary arrives without a prior referral because the condition required immediate treatment. The hospital treats first and must then inform CGHS about the emergency admission.
• Referral-based admissions — the beneficiary comes with a referral from a CGHS wellness centre or authorised authority. The hospital records the admission against that referral on the portal.

The exact fields, the portal workflow and the time window for intimation are defined by the current CGHS guidelines and your hospital's empanelment terms. These are revised from time to time, so treat your latest circulars and memorandum of agreement as the reference — not an old SOP pinned on the billing office wall.

Why hospitals miss intimations

Almost every hospital knows intimation is required. The failures come from how the work is organised.

Admissions do not follow office hours

Emergency admissions happen at 2 a.m., on Sundays and during festivals. The person trained to submit intimations on the portal usually works a day shift. By the time they arrive, the night's admissions are waiting — and if the morning is busy, some get pushed further.

Manual double entry

The patient is already registered in the HIS with name, beneficiary details, admission time and department. Staff then retype the same details into the CGHS portal. That is slow, and every retyped field is a chance for a spelling or ID mismatch that causes trouble later.

Staff turnover and single points of failure

In many hospitals, one or two people know exactly how to file an intimation. When one of them is on leave or moves on, the knowledge goes with them. New staff learn by trial and error, often on live cases.

No reliable record of what was sent

Even when an intimation is submitted on time, the hospital may not keep a clear record: the reference number, the time of submission, a screenshot of the confirmation. When a dispute comes up weeks later, nobody can show what was filed and when.

No one sees the gap until billing

A missed intimation is usually discovered at discharge or at final bill upload, when it is too late to fix cleanly. There is rarely a daily view that says "these CGHS admissions from yesterday have no intimation yet".

How an intimation agent works

An intimation agent takes the repetitive part of the job — noticing new admissions and entering them on the portal — and runs it continuously. A typical workflow looks like this:

1. Pick up admissions from the HIS. The agent reads new inpatient admissions at regular intervals and filters those marked as CGHS beneficiaries, separating emergency cases from referral cases.
2. Validate the data. Before touching the portal, it checks that required fields are present — beneficiary ID, patient name, admission date and time, department or treating doctor, and referral details for referral cases. Records with gaps are sent to an exception list instead of being submitted with bad data.
3. Submit on the portal. For complete records, the agent fills the emergency or referral intimation form with data from the HIS, working under the hospital’s own portal login. Staff approve the submission and complete any CAPTCHA or OTP step the portal requires — no retyping.
4. Capture proof. It stores the portal's acknowledgement or reference number, the timestamp, and a screenshot of the confirmation, linked to the patient's admission record.
5. Report. A dashboard shows every CGHS admission with its intimation status: submitted, pending, failed or needs review — with the time taken from admission to intimation.

Because the agent runs around the clock, a night-time emergency admission is intimated in the same cycle as any other, instead of waiting for the next morning shift.

COPPERJAM's Billing Desk Automation include separate emergency intimation and referral intimation automation agents, alongside a CGHS final bill upload agent, so the same admission can be followed from intimation to bill submission.

Keeping humans in the loop

Automation should not mean nobody is watching. A well-designed intimation process keeps people responsible for the decisions an automation agent should not make on its own.

Patient category at registration

The agent can only act on what the HIS tells it. If a CGHS beneficiary is registered as a cash patient, or a referral case is marked as an emergency, the intimation will be wrong or missing. Front-desk training and a simple category check at registration matter as much as the agent itself.

Exception queue with an owner

Records that fail validation — missing beneficiary ID, unclear referral, mismatched name — should land in an exception queue that a named person reviews every shift. The target is to clear it before the intimation window closes, not at the end of the week.

Failure alerts

Portals go down, sessions expire and forms change. When a submission fails, the agent should retry and then alert a person, not fail silently. A simple rule works well: any CGHS admission without a confirmed intimation after a set period triggers an alert to the billing supervisor.

Periodic reconciliation

Once a day, compare the list of CGHS admissions in the HIS with the list of intimations logged by the agent. Any admission on the first list but not the second is investigated. This takes minutes and catches problems that neither the agent nor the staff noticed.

Watching for guideline changes

When CGHS issues a new circular that changes the intimation process or required fields, someone in billing needs to review it and ask for the agent to be updated. Automation follows the rules it is given; keeping those rules current is a human job.

Connecting intimation to the rest of the claim

Intimation is the first step in a chain that ends with payment. A missed or late intimation affects everything after it, so it pays to link it to the rest of your workflow:

• Show intimation status on the discharge tracker, so no CGHS patient is discharged and billed without confirmed intimation.
• Store the intimation reference and proof with the claim file, so it is ready if a query comes back.
• Track CGHS receivables by claim and ageing in a debtor management system, and look at whether claims with late intimations take longer to settle.

Getting started

If your hospital currently handles intimations manually, start by listing last month's CGHS admissions and checking, for each one, when the intimation was filed and whether you can show proof. That exercise alone usually shows where the gaps are — nights, weekends, particular departments or particular staff.

From there, fix registration categories, set up an exception owner, and bring in an automation agent to handle the routine submissions. The goal is simple: every CGHS admission intimated on time, with a record you can produce whenever it is asked for.