A hospital can advertise a service before the roster, equipment, lab support, pharmacy stock, referral route, or emergency plan is ready. The scope register exists to stop that gap. It describes the approved boundary and forces each dependent team to acknowledge a change.
Takeaways
- Name the service, site, hours, population, limits, and owner.
- Link clinical scope to the departments that support it.
- Put additions and temporary suspensions through change control.
- Show patients the current boundary in plain language.
This is a governance template, not an official NABH checklist or advice on licensing a particular service.
The service name is only the first field
NABH’s official Hospital Accreditation Standards, 6th Edition repeatedly connects care and support services to the organisation’s scope. The licensed standard is the source for exact objective elements. The hospital’s licences, authorities, and clinical governance add facility-specific constraints.
SCOPE OF SERVICES RECORD
Service name and code: ___________________________________
Plain-language description: ______________________________
Site, building, and department: __________________________
Hours and availability: __________________________________
Patient group and eligibility: ___________________________
Included procedures or activities: _______________________
Explicit exclusions and limits: __________________________
Clinical owner and authorised roles: _____________________
Required staffing and competency evidence: ______________
Required equipment, supplies, and support: ______________
Emergency and transfer route: ____________________________
External referral arrangement: ___________________________
Approval, effective date, review date: ___________________
One record should be readable by a registrar at 8 p.m., a nurse on the ward, a clinician receiving a referral, and a finance team building a service list. If each person interprets the service differently, the boundary isn’t controlled.
Map the dependencies before go-live
| Dependent area | Readiness evidence | Boundary question |
|---|---|---|
| registration and patient information | current service label, hours, eligibility, price route | what may staff promise? |
| clinical staffing | roster, credentials, privileges, escalation | who may provide which part? |
| diagnostics and pharmacy | available support and external arrangement | what happens when support is unavailable? |
| records and consent | approved form, record structure, retention route | where is the service documented? |
| emergency and referral | transfer criteria, contacts, acceptance route | when must the hospital refer out? |
| billing and payer work | approved catalogue and authorisation path | does the bill match the delivered scope? |
NABH’s E-Mitra publishes official implementation resources across hospital functions. Use the applicable current material with the licensed standard and local requirements; don’t copy a service list from another facility.
Treat suspension as a controlled state
A service may become temporarily unavailable because a qualified person, device, medicine, utility, or support department isn’t available. Record the effective time, patient impact, referrals, communications, system changes, and authority to restore it.
SCOPE CHANGE RECORD
Change: add / modify / suspend / restore / retire
Reason and risk review: __________________________________
Authority/licence check: _________________________________
Affected departments: ____________________________________
Patient and referrer communication: ______________________
System and catalogue changes: ____________________________
Training completed: ______________________________________
Approved effective time: _________________________________
Post-change check: ________________________________________
We think the temporary suspension row is the best test. Hospitals are good at launching service names. They need equal discipline when reality narrows the service at short notice.
The HMS module boundary guide separates software scope from hospital responsibility. The HIS vs HMS guide helps buyers decode system labels.
Patient Square is an AI clinical platform. Hospital Copilot may be evaluated as a record-system path or alongside an incumbent system within the published scope. It does not authorise a hospital service or grant NABH accreditation. Patient Square makes no NABH or ABDM certification claim. Review the India security page before storing governance records.