Admin: Automated edit (via update-page on MediaWiki MCP Server)

2026-07-06T04:00:53Z

Automated edit (via update-page on MediaWiki MCP Server)

← Older revision		Revision as of 09:30, 6 July 2026
Line 81:		Line 81:

	Roles are granted through a user's organization and facility memberships, and cascade down the organization tree — a role held higher up applies to the facilities and resources beneath it.		Roles are granted through a user's organization and facility memberships, and cascade down the organization tree — a role held higher up applies to the facilities and resources beneath it.

			{{Navbox definitions}}

	{{Related}}		{{Related}}

Admin: OHC identity seed

2026-07-04T22:43:20Z

OHC identity seed

New page

{{Doc header
|type=concept
|domain=definitions
|title=Activity Definition
|order=6
|introduced=3.0
|concept=Concepts/Encounter
|reference=References/Activity Definition
}}

An '''activity definition''' is a reusable, facility-scoped template for a clinical activity — a lab test, an imaging study, a counselling session — holding every default needed to order it. A facility defines the activity once, then turns it into a real order for a specific patient with a single "apply" action.

== What it represents ==

In Care's FHIR-aligned model, an activity definition maps to the '''ActivityDefinition''' resource: a reusable description of an action to perform, defined independently of any patient.

The key distinction is that an activity definition is a blueprint, not a record of anything that happened. It carries the defaults — the procedure code, the specimens to collect, the observations to result, the locations and charges — but no patient. It belongs to a facility's catalog of services; the actual work for a patient lives in the [[Concepts/Service Request|service request]] it generates. Define "Complete Blood Count" once and apply it to twenty patients, and you get twenty separate orders, all sharing the same template.

== Classification ==

Every activity definition carries one classification describing the nature of the work:

{| class="wikitable"
|-
! Classification
! Typical use
|-
| <code>laboratory</code>
| Blood panels, cultures, and other lab investigations
|-
| <code>imaging</code>
| X-ray, ultrasound, CT, and similar studies
|-
| <code>counselling</code>
| Structured counselling or advisory sessions
|-
| <code>surgical_procedure</code>
| Operative and bedside procedures
|-
| <code>education</code>
| Patient education and instruction activities
|}

== How it connects ==

An activity definition is the assembly point that wires a facility's reusable pieces together, so a single order carries everything it needs without anyone reassembling it by hand:

* '''What to collect and measure''' — [[Concepts/Specimen Definition|specimen definitions]] and [[Concepts/Observation Definition|observation definitions]]
* '''Where it happens''' — the [[Concepts/Location|locations]] and [[Concepts/Healthcare Service|healthcare service]] the activity runs under
* '''What it costs''' — [[Concepts/Charge Item Definition|charge item definitions]], so applying the activity can raise the right billing lines automatically

Patient and encounter are supplied at apply time, never stored on the template. The definition is applied against an [[Concepts/Encounter|encounter]], which binds the result to a specific patient. Applying merges the stored defaults with that encounter context to produce a draft service request — plus a charge item for each linked charge, tied back to the same request.

== Lifecycle ==

<syntaxhighlight lang="text">draft → active → retired</syntaxhighlight>
* '''draft''' — being authored, not yet ready for routine use
* '''active''' — published and available to apply to encounters
* '''retired''' — withdrawn from use but kept for history and reference

A separate <code>unknown</code> status covers definitions whose state cannot be determined. Activity definitions are also versioned: editing a definition appends a new version to a chain rather than overwriting it, with one marked as the latest. Older order templates stay referenceable even after the catalog moves on.

== Permissions ==

Access is governed at the facility level — whether a role can author the catalog or only read from it and apply.

{| class="wikitable"
|-
! Permission
! Description
! System Roles
|-
| <code>can_write_activity_definition</code>
| Create and edit activity definitions on a facility
| Facility Admin, Admin
|-
| <code>can_read_activity_definition</code>
| List and view activity definitions on a facility
| Facility Admin, Administrator, Admin, Staff, Doctor, Nurse, Volunteer
|}

Roles are granted through a user's organization and facility memberships, and cascade down the organization tree — a role held higher up applies to the facilities and resources beneath it.

{{Related}}

Concepts/Activity Definition - Revision history

Admin: Automated edit (via update-page on MediaWiki MCP Server)

Admin: OHC identity seed