Task Priority Detail Extension

Canonical	../StructureDefinition/nexus-task-priority-detail
Status	draft · 1.26.0
Base	Extension (constraint)
Context	Task.priority (element)
Source	FSH · JSON

A priority refinement finer than R4's request-priority vocabulary allows, currently one concept: trivial, meaning below routine. Task.priority binds required to a value set whose floor is routine and is a bare code with no second coding slot, so a refinement cannot be carried in the element itself. When this extension is present Task.priority SHALL be routine, so a consumer that ignores the extension sorts the task as routine -- an understatement rather than a mis-sort.

Elements / Key elements

The working view: must-support, required, modifier and sliced elements from the effective (snapshot) definition.

Element	Flags	Card.	Type	Description & Constraints
Extension		0..*		Task Priority Detail Invariants: ele-1, ext-1
url		1..1	http://hl7.org/fhirpath/System.String	identifies the meaning of the extension i Fixed: ../StructureDefinition/nexus-task-priority-detail
value[x]		1..1	code	trivial (below routine) Binding: Task Priority Details (required) e.g. trivial Invariants: ele-1