Correction Task Profile

Canonical	../StructureDefinition/nexus-correction-task
Status	draft · 1.26.0
Base	Task Profile (constraint)
Source	FSH · JSON

A patient's request to correct their own record, or to log a disagreement where a correction was refused, carried as an ordinary clinical task with the statutory correction vocabulary. Same worklist, same shape, narrower status set. AN ACCESS REQUEST IS NOT HELD TO THIS PROFILE. Every code in this vocabulary describes a correction or a disagreement, so a request to be given a copy of the record has no terminal state here it could truthfully reach. It shares the privacy-request worklist bin and stays on the base clinical task, which binds the wider set.

TypedFhir API / Python

The typed accessor surface Task exposes for Task — generated from this IG's compiled profile; each typed accessor has a validating raw-FHIR twin (xRaw) where marked. The three ports are parity-enforced.

class Task(ClinicalResource) — generated source

Accessor	Type	Access	Notes
effective_date	FuzzyDate | None	read-only	The resource's effective date — the first present of this profile's date elements (precedence), normalized to the canonical FuzzyDatetime f…
display	str | None	read-only	The resource's human headline — a coded concept's label, else a title / name, else undefined.
instantiates_canonical	str | None	read/write	Formal definition of task (canonical)
instantiates_uri	str | None	read/write	Formal definition of task (URI)
based_on	References	read/write · raw twin	Request fulfilled by this task (available, not must-support)
group_identifier	dict | None	read/write	Shared identifier for tasks raised together (e.g. one decision-support card)
part_of	References	read/write · raw twin	Parent task for sub-tasks and branches
status	str | None	read/write	Where the task is in its lifecycle
status_reason	Concept | None	read/write · raw twin	Reason for current status
business_status	Concept | None	read/write · raw twin	Task business status
intent	str | None	read/write	order (do this) | proposal (consider this) | option (one of these)
priority	str | None	read/write	How urgent the task is
code	Concept | None	read/write · raw twin	The category the task is filed under
description	str | None	read/write	The ask: original task content, stable throughout lifecycle
focus	Reference | None	read/write · raw twin	The chart element this task is about (form, inbox document, note, ...)
for_	Reference | None	read/write · raw twin	Patient this task is about, when it is about one
encounter	Reference | None	read/write · raw twin	Healthcare encounter during which task was created
execution_period	dict | None	read/write	Start and end time of execution
authored_on	FuzzyDate | None	read/write	When task was first created
last_modified	FuzzyDate | None	read/write	Task last modified date
requester	Reference | None	read/write · raw twin	Who originally requested this task (person, AI graph, or decision-support rule)
performer_type	Concepts	read/write · raw twin	Requested performer type
owner	Reference | None	read/write · raw twin	Who holds this task now; absent means the whole clinic holds it
location	Reference | None	read/write · raw twin	Where task should be performed
reason_code	Concept | None	read/write · raw twin	Why task is needed (coded)
reason_reference	Reference | None	read/write · raw twin	Clinical reason for this task (available, not must-support)
insurance	References	read/write · raw twin	Associated insurance coverage
note	Notes	read/write	The conversation on this task, oldest first; the ask itself is description
restriction	dict | None	read/write	Constraints on fulfillment tasks
input	dict[] | None	read/write	The contained prototype Bundle (local #id reference)