Facility

A facility in Care is a single care site — a hospital, clinic, lab, or telemedicine endpoint — and the boundary that everything inside a deployment is scoped to. Patients are registered, staff are organized, locations and devices are added, and billing is configured all within one facility.

What it represents

In Care's FHIR-aligned model, a facility maps to the Organization resource, specialized as a physical or virtual care site. It captures:

• Identity — a name, description, and a facility type (Private Hospital, Primary Health Centres, Govt Labs, TeleMedicine, and many more)
• Place — address, pincode, latitude/longitude, and a contact number
• Capabilities — what the site can offer, such as CT Scan, Maternity Care, X-Ray, Neonatal Care, Operation Theater, or Blood Bank
• Geographic placement — the government/administrative region it sits under, which is how deployments roll facilities up into districts and states
• Billing — its own discount codes, tax components, and invoice-number format

A facility is not a department or a ward — those are locations and facility organizations within it. The facility is the outer container; the same patient can be seen across many facilities while remaining one person, but staff roles, inventory, and invoices never cross the facility line.

Lifecycle

A facility comes with its administrative scaffolding pre-built — you never assemble the hierarchy by hand.

Create → Administration org provisioned → Active → (soft) Deleted

• Create — the record is created with its name, type, address, and the geographic region it belongs under
• Administration org provisioned — Care automatically creates a root Administration organization inside the facility and grants the creator the Facility Admin role over it, so the site has a working tree from day one
• Active — patients are registered, staff are assigned, locations and devices are added, and encounters happen
• Deleted — removal is a soft delete; the facility and its child organizations are kept for history and audit, never erased

How it connects

The facility is the hub most other primitives hang off of:

• People — staff gain access through the facility's organizations; every role and permission is scoped to a facility
• Places & equipment — locations (wards, beds, rooms), healthcare services, and devices are registered under it
• Care delivery — encounters take place at a facility, anchoring where care was given
• Geography — each facility sits under a geographic organization, the bridge that connects it to the wider administrative map
• Billing — discounts, taxes, and invoice numbering are set per facility (see Facility config)

Permissions

Access to a facility is governed by a small set of permissions, granted to staff through their facility organization roles.

Permission	Description	System Roles
can_create_facility	Create a new facility	Administrator, Admin, Facility Admin
can_update_facility	Edit a facility's details and configuration, including its cover image, monetary config, and invoice expression	Facility Admin, Administrator, Admin, Staff

Reading a facility is not gated by a dedicated permission — the list and retrieve endpoints return only the facilities a user can reach through their organization memberships. Deleting a facility is restricted to super admins.

Permissions cascade down the organization tree: a role held at a parent organization applies to the facilities and sub-organizations beneath it.

Related

• Reference: Facility (technical)
• Reference: Facility config
• Concept: Organization