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

2026-07-06T04:17:07Z

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

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

	This concept aligns with the FHIR '''SupplyDelivery''' resource, which records the dispatch and receipt of supplies. Care stores coded values (status, condition) as plain snake_case enums rather than FHIR URIs.		This concept aligns with the FHIR '''SupplyDelivery''' resource, which records the dispatch and receipt of supplies. Care stores coded values (status, condition) as plain snake_case enums rather than FHIR URIs.

			{{Navbox supply}}

	{{Related}}		{{Related}}

Admin: OHC identity seed

2026-07-04T22:43:44Z

OHC identity seed

New page

{{Doc header
|type=concept
|domain=supply
|title=Supply Delivery
|order=5
|introduced=3.0
|concept=Concepts/Invoice
|reference=References/Supply Delivery
}}

A '''supply delivery''' records stock actually moving — a product arriving at a location, whether shipped in from an outside supplier or transferred between rooms inside a facility. It is the "stock in" side of inventory: everything delivered, minus everything dispensed, equals what is on the shelf right now.

== What it represents ==

In Care's FHIR-aligned model, a supply delivery maps to the '''SupplyDelivery''' resource. Each delivery is a single line of received goods, capturing:

* '''What moved''' — the product, or a specific batch already in stock, and how much, counted as whole units or as packs times pack-size
* '''Condition''' — whether the items arrived <code>normal</code> or <code>damaged</code>
* '''Where it came from and went''' — carried by the delivery order it belongs to, which names a source and a destination
* '''Why''' — an optional link to the supply request this delivery fulfils, and to a billing invoice when stock is handed to a patient
* '''Cost''' — the total purchase price of the line

The key distinction is between a request and a delivery. A request is someone ''asking'' for stock; a delivery is stock ''changing hands''. They are not one-to-one: a single request can be met by several deliveries, and a delivery can also happen with no prior request at all — so Care treats the delivery, not the request, as the event that moves inventory.

== How it connects ==

A delivery never stands alone — each one belongs to a '''delivery order''', the shipment that gives it context. The order answers a single question, ''where is this stock coming from and going to'', and its answer shapes everything underneath it:

* '''Origin and destination''' — an order always names a destination. If it also names an origin location, it is an internal transfer between two places in the facility. If it has no origin, the stock is entering from outside, and the order names an external '''supplier''' organization instead.
* '''Internal vs. external''' — this one distinction decides what each delivery line must carry. An internal move draws down a specific inventory item, a known batch already on hand; an external delivery names a product being received for the first time. A line is one or the other, never both.
* '''Patient dispense''' — an order can instead be aimed at a patient, optionally tied to a billing invoice. An order is either a location-to-location move or a patient dispense, never both — so an order with a patient has no origin.

== Lifecycle ==

A delivery moves through a short lifecycle as goods are received and reconciled:

<syntaxhighlight lang="text">in_progress → completed
in_progress → abandoned
in_progress → entered_in_error</syntaxhighlight>
* '''in_progress''' — the delivery is being recorded but not yet finalized
* '''completed''' — goods are received and counted into stock; only completed lines contribute to inventory totals
* '''abandoned''' — started but will not be finished
* '''entered_in_error''' — created by mistake and should be disregarded

The delivery order that groups these lines has its own status track. Every order begins as <code>draft</code> or <code>pending</code>, moves to <code>in_progress</code>, and settles into one terminal state: <code>completed</code>, <code>abandoned</code>, or <code>entered_in_error</code>.

== Condition ==

Each line records the state the goods arrived in, so damaged stock is flagged rather than silently counted:

* '''normal''' — items arrived intact and usable
* '''damaged''' — items arrived compromised; the flag supports returns, write-offs, and supplier follow-up

== Permissions ==

Access to supply deliveries is governed by facility-scoped permissions.

{| class="wikitable"
|-
! Permission
! Description
! System Roles
|-
| <code>can_write_supply_delivery</code>
| Create or update deliveries on internal transfer orders (an order with an origin location); gates both the create and update actions for in-facility moves
| Facility Admin, Admin
|-
| <code>can_write_external_supply_delivery</code>
| Create or update deliveries on external orders (no origin, stock arriving from an outside supplier); gates both create and update for inbound deliveries
| Facility Admin, Admin
|-
| <code>can_read_supply_delivery</code>
| List and retrieve deliveries and their delivery orders
| Facility Admin, Administrator, Admin, Staff, Doctor, Nurse, Volunteer, Pharmacist
|}

Roles are granted to users through their facility and organization memberships, and permissions cascade down the organization tree — so a role held at a parent organization carries to the facilities beneath it.

== FHIR reference ==

This concept aligns with the FHIR '''SupplyDelivery''' resource, which records the dispatch and receipt of supplies. Care stores coded values (status, condition) as plain snake_case enums rather than FHIR URIs.

{{Related}}

Concepts/Supply Delivery - Revision history

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

Admin: OHC identity seed