
<p><strong>Onboarding a hospital onto CareLite runs in a set order because each step depends on the last: account and users, then masters, then tariffs, then a parallel run, then go-live. A hospital with its data ready can be billing live within days rather than months.</strong></p>

<h2>1. Account and administrator</h2>
<p>CareLite creates the hospital account with its plan, bed and user limits and enabled modules, and issues one administrator login. That password is shown once and must be changed at first sign-in.</p>

<h2>2. Masters, in dependency order</h2>
<p>Departments and specialities, then doctors; wards, then rooms, then beds; service groups, then services; companies. Each level references the one above it, so loading them out of order produces rows that cannot resolve. Anything over about twenty rows should come in through the Excel template rather than being typed.</p>

<h2>3. Tariffs</h2>
<p>At least one general tariff is required — it is what the counter bills from. Corporate tariffs follow, either with their own rates or derived from the general one with a blanket discount. Bed charges are priced per ward.</p>

<h2>4. Users and roles</h2>
<p>Every person gets their own login with a role matching what they actually do. Discount ceilings are set per user at this point. This is the step hospitals are most tempted to shortcut with shared logins, and the one where that shortcut costs the most later.</p>

<h2>5. Settings</h2>
<p>Bed-charge basis, discount approval threshold, invoice and receipt header lines, and the communication channels — switched on only once credentials exist, otherwise messages queue and then fail.</p>

<h2>6. Parallel run and acceptance</h2>
<p>Run a day of real transactions and reconcile at the end of it: cash against the collection report, card against the bank, billed less received against outstanding. A written acceptance script covering OPD, IPD, emergency, corporate, payout, cancellation and audit is provided and should be signed off before go-live.</p>

<h2>7. Go-live and support</h2>
<p>Cut over during working hours so any problem is found and fixed the same day. Support runs during working hours; issues are raised from inside the application or by email.</p>
