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

2026-07-06T04:13:24Z

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

← Older revision		Revision as of 09:43, 6 July 2026
Line 84:		Line 84:

	This concept aligns with the FHIR [<nowiki/>https://hl7.org/fhir/medicationadministration.html MedicationAdministration] resource, which records the consumption or administration of a medication to a patient.		This concept aligns with the FHIR [<nowiki/>https://hl7.org/fhir/medicationadministration.html MedicationAdministration] resource, which records the consumption or administration of a medication to a patient.

			{{Navbox medications}}

	{{Related}}		{{Related}}

Admin: OHC identity seed

2026-07-04T22:43:31Z

OHC identity seed

New page

{{Doc header
|type=concept
|domain=medications
|title=Medication Administration
|order=2
|introduced=3.0
|concept=Concepts/Product Knowledge
|reference=References/Medication Administration
}}

A '''medication administration''' is the record that a dose was actually given to a patient — or that giving it was attempted and did not happen. It is the moment an order becomes a real event at the bedside, closing the loop on what a clinician prescribed.

== What it represents ==

In Care's FHIR-aligned model, this maps to the '''MedicationAdministration''' resource. A single record answers four questions about one dose: what was given, how and when it was given, who gave it, and — if it was not given — why.

The distinction that matters most is between the administration and the order behind it. The order ([[Concepts/Medication Request]]) is the plan: ''what should be given''. The administration is the event: ''was this dose actually given?'' One order produces many administrations over time, one for each scheduled dose, so the two together tell you whether the plan was followed.

This is also why recording a "not given" event matters as much as recording a completed one. It makes a gap in the patient's medication history explicit and auditable, rather than leaving it silent.

== Lifecycle ==

The <code>status</code> field tracks what happened to a single dose. A normal administration moves through the active path:

<syntaxhighlight lang="text">in_progress → completed
→ on_hold → in_progress
→ stopped
→ not_done</syntaxhighlight>
* '''in_progress''' — the dose has started but is not finished (typical for an infusion still running)
* '''on_hold''' — administration was paused and may resume
* '''completed''' — the dose was fully given
* '''stopped''' — administration was halted before completion
* '''not_done''' — the dose was deliberately not given, recorded with a reason

Three further statuses are administrative rather than clinical: '''cancelled''' (the planned dose was called off), '''entered_in_error''' (the record was a mistake and should be disregarded), and '''unknown''' (the outcome cannot be determined).

== Classification ==

The <code>category</code> marks the setting in which the dose was given, which drives reporting and reconciliation:

* '''inpatient''' — given to an admitted patient on a ward
* '''outpatient''' — given during a clinic or day visit
* '''community''' — given outside the facility, such as a home or field setting
* '''discharge''' — supplied or given as the patient leaves

== How it connects ==

A medication administration sits at the centre of the medication workflow and ties together several other records:

* '''Patient''' — every administration belongs to a [[Concepts/Patient|patient]]. The patient is derived automatically from the encounter, never entered directly, so the record can never drift from the visit it happened in.
* '''Encounter''' — the [[Concepts/Encounter|encounter]] during which the dose was given anchors it in time and place.
* '''Medication Request''' — the [[Concepts/Medication Request|order]] this administration fulfils, which is what turns a list of given doses back into "did we follow the plan?".
* '''Product''' — when a specific catalogued item was used, the administration points to that [[Concepts/Product Knowledge|product knowledge]] entry so the dose can be reconciled against supply.

A record names either a coded medication or a specific product, never both. The coded form describes the substance; the product form ties the dose to a real item that left your stores.

== Permissions ==

Access to recording and viewing administrations is governed by facility-scoped permissions.

{| class="wikitable"
|-
! Permission
! Description
! System Roles
|-
| <code>can_write_encounter_clinical_data</code>
| Create, update, and delete a medication administration on the encounter (write encounter clinical data). Blocked once the encounter is closed
| Admin, Doctor, Nurse, Facility Admin
|-
| <code>can_view_clinical_data</code>
| View a patient's clinical data, including listing and retrieving their medication administrations
| Staff, Doctor, Nurse, Admin, Facility Admin
|-
| <code>can_read_encounter_clinical_data</code>
| Read an encounter's clinical data; used as the fallback read check when a specific encounter is supplied
| Admin, Doctor, Nurse, Facility Admin
|}

Roles are granted through a user's facility and organization memberships, and permissions cascade down the organization tree — a role held high in the hierarchy carries to the facilities beneath it.

== FHIR reference ==

This concept aligns with the FHIR [<nowiki/>https://hl7.org/fhir/medicationadministration.html MedicationAdministration] resource, which records the consumption or administration of a medication to a patient.

{{Related}}

Concepts/Medication Administration - Revision history

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

Admin: OHC identity seed