Prepare a site for go-live

Available to

Configuration managers and HIS managers.

Use this checklist before a facility starts treating real patients. Each item has its own guide.

Check	Where	Guide
Facility and departments are set up with licence details	HIS Administration → Facilities, Departments	Set up facilities and departments
Wards, beds and operating rooms exist	HIS Administration → Wards, Bed Board Setup, Operating Rooms	Set up wards and beds
A production code system is approved and loaded	HIS Administration → Code Systems	Manage clinical code systems
The country pack is reviewed, applied and approved for pilot	HIS Administration → Country Packs	Apply a country pack
The laboratory, imaging and surgery catalogues are loaded and approved	HIS Administration → Laboratory Tests, Imaging Procedures, Procedure Catalogue	Create and follow a laboratory order
The pharmacy formulary is approved	Pharmacy → Configuration	Manage the pharmacy formulary
Label printers are set up and tested	HIS Administration → Label Printers	Set up label printers
Integration endpoints are registered	HIS Administration → Integration Endpoints	Register an integration endpoint
Users have the right roles and facilities	Settings → Users	Understand roles and access
Charging triggers and payment flows are set if billing is on	Facility; Insurance → Payment Flows	How services are charged
Privacy officers know the review routines	HIS Administration → Emergency Access Review, Clinical Audit	Review emergency access

Jurisdiction and governance: the legal entities, licensed facilities, hosting and backup locations are documented, and clinical owners approve dictionaries, order sets, alerts, formularies, critical values, escalation policies and print templates.
Technical and security: single sign-on and multi-factor sign-in, least-privilege roles and facility rules, encryption, backups, recovery exercises and monitoring are in place, and every integration has an owner, a contract and a downtime procedure.
Clinical workflow acceptance: patient-mismatch, duplicate, allergy, wrong-specimen, medication barcode, critical-result, sensitive-record and audit-trail tests are run and kept as evidence, and users are trained before a supervised pilot.
Data and migration: approved code-system versions are loaded, migration is rehearsed twice with counts reconciled, and there is a rollback plan.
Blood bank, portal and payers, where used: the medical director approves component types and rules, portal release delays and hidden tests are approved, and each payer connector is signed off in its sandbox.