Group Health Insurance Administration: A Guide for HR and Admin

What HR is actually administering

A group health policy has three moving parts that HR controls: who is covered, from when, and for how much. Everything else — the hospital network, the claim rules, the exclusions — is fixed at placement. The daily work is keeping the list of covered lives accurate and making sure each of them can use the cover when they need it.

The parties are the insurer, which carries the risk; the third-party administrator (TPA), which keeps enrolment records, issues cards and processes claims; the broker, if there is one; and HR, the only party that knows who joined on Monday and whose spouse is expecting in March.

Group health usually shares its employee list with group personal accident and group term life, and the three are best administered together.

Enrolment and dependants

Enrolment at inception is the one moment when the whole list is built from scratch. The insurer needs, for each employee: name, date of birth, gender, employee ID, date of joining, the sum insured band, and the same details for each dependant. Dependant rules vary: most policies cover spouse and children; many cover parents or parents-in-law as an option, sometimes with a separate sum insured, sometimes on an employee-paid voluntary basis.

Common enrolment problems, all avoidable:

• Dates of birth missing or in inconsistent formats, so the TPA cannot rate parent cover correctly.
• Dependants listed under a category the policy does not cover (a sibling, an adult child above the age limit).
• Employees who joined during the placement window and fall between last year’s list and this year’s.
• Names that do not match ID documents, which surfaces later at the hospital desk.

The fix is a single enrolment template, a short collection window with a hard close, and a reconciliation against the HRMS headcount before the list goes to the insurer. Once the premium is paid, the list is the contract: anyone not on it is not covered.

Mid-term additions and deletions

People join, leave, marry and have children all year. Each change is made by endorsement, with the premium adjusted pro-rata for the remaining period.

Additions. A new joiner is added from their date of joining, provided HR submits the request within the window the policy allows. The pro-rata premium is the annual premium for that life multiplied by the fraction of the policy year remaining. A new spouse or child is added from the date of marriage or birth on the same basis. Miss the window and the insurer may decline to backdate.

Deletions. A leaver is deleted from their last working day and the pro-rata premium for the unexpired period is refunded, usually against a deposit rather than by cheque. Most insurers work from such a premium deposit: additions draw it down, deletions top it up, and the balance is settled at intervals. HR should reconcile that account, because errors in it are invisible until renewal. The mechanics are covered in the guide to insurance endorsements.

E-cards, cashless and reimbursement

Once a life is enrolled, the TPA issues an e-card carrying the member ID, the policy number and the TPA helpline. It is what the hospital’s insurance desk asks for. Employees should have it on their phones before they need it, and dependants should have their own. There are two ways a claim is paid:

Cashless. The employee is treated at a hospital in the TPA’s network. The hospital sends a pre-authorisation request with the diagnosis and estimated cost; the TPA approves an amount against the policy terms; the hospital bills the TPA directly, and the employee pays only what the policy does not cover. Planned admissions are pre-authorised in advance; emergencies are notified shortly after admission.

Reimbursement. The employee pays the hospital, collects the discharge summary, itemised bills, receipts, prescriptions and reports, and submits a claim to the TPA within the policy’s time limit. The TPA pays the admissible amount to the employee’s bank account. This is the route when the hospital is out of network, when cashless was declined, or for pre- and post-hospitalisation expenses.

HR’s job is to make both routes obvious: a one-page guide with the network link, helpline, document list and deadlines, sent at enrolment.

Working with the TPA

The TPA is where most group health frustration lives, and most of it comes down to data and response times. Set the working relationship up at the start of the policy year, not during the first escalation.

• Agree turnaround times in writing for endorsements, e-card issue, cashless pre-authorisation and reimbursement settlement. Measure against them monthly.
• Fix a single format for addition and deletion requests, sent from one HR mailbox or through the TPA’s portal.
• Get a monthly member list back from the TPA and reconcile it to your own. Discrepancies found in month two are easy; discrepancies found at a hospital desk are not.
• Get a monthly claims MIS: lodged, approved, rejected, pending, and the reasons for rejection. A clean year-by-year record of premium against claims is the company’s strongest card at renewal.
• Keep a named escalation contact at the TPA and at the insurer for cases the helpline cannot resolve.

Employee queries and health data privacy

Most employee queries are predictable: am I covered, is my mother covered, is this hospital in the network, where is my card, when will my claim be paid. A good FAQ answers the majority. The rest need a person who can see the employee’s enrolment and claim status without asking the TPA.

Health information is the most sensitive data HR handles, and group health generates a great deal of it: diagnoses, discharge summaries, claim histories, family details. Some basic rules:

• HR needs enrolment status and claim status, not diagnoses. Ask the TPA to report claims at the level of amounts and categories, not conditions, unless a specific case requires more.
• Keep enrolment data and claims correspondence in a system with access control, not in a shared mailbox or a spreadsheet on a network drive.
• Limit who can see dependant details to the people who administer the policy.
• Never forward an employee’s claim documents to managers, however well-meaning the reason.
• Retain claims documents only as long as the policy and any dispute requires.

What to do when a claim is rejected is covered in the corporate insurance claims process.

What an employee self-service portal changes

Everything above can be run on email and spreadsheets, and in most companies it is. The cost is that HR sits in the middle of every transaction: every card request, dependant addition and “is this hospital covered” question passes through the same two or three people.

An employee self-service portal moves the routine transactions to the employee. They see their own cover and dependants, download e-cards, submit an addition when a child is born with the birth certificate attached, look up the network and track a reimbursement claim. HR approves requests from a queue, and the endorsement goes to the TPA in the agreed format without being retyped. What changes in practice:

• Enrolment data is entered once by the person who knows it, which removes most date-of-birth and name-mismatch errors.
• Addition and deletion requests carry their own documents and land inside the policy window, because the employee is prompted rather than reminded.
• HR stops being the helpline for questions the portal already answers.
• Health data lives in one controlled system with an access log, rather than in inboxes.
• The company’s own member list becomes the master, and the TPA’s list is reconciled to it rather than the other way round.

Platforms such as SAIBA Corporate pair the portal with the employer’s policy register, so group health is administered alongside the rest of the company’s cover.