NHSDigital-Task
Conformance url | FHIR Module | Maturity Level |
---|---|---|
https://fhir.nhs.uk/StructureDefinition/NHSDigital-Task | trial-use |
Task | I | Task | Element IdTask A task to be performed DefinitionFHIR Task usage and scope is defined as
A Task resource often exists in parallel with clinical resources. For example, a Task could request fulfillment of a ServiceRequest ordering a Procedure that would result in a Procedure, Observation, DiagnosticReport, ImagingStudy or similar resource. Another example would be a Task that requests fulfillment of a CommunicationRequest to be performed between various actors. Task has three main uses:
Order FulfilmentCentres on the fulfilment of the order. It does not contain the order details which are held in a referenced request resource.
In the diagram below the recipient or fulfiller of the order uses FHIR Task to accept or reject the order, it also uses Task to send Examples:
See the section on Minor Workflow RequestsThis is used to implement additional around an order or to record specific workflow requests. These may not have a focused resource reference. It is anticipated they are coded using SNOMED CT. Examples:
The Task.status can be used to indicate fulfilment/delivery status. Workflow SupportMore advanced workflow is supported, this adds in the use of Task.input and Task.output. This allows the passage of inputs and outputs which may be found in automated workflow activities. The diagram below is from an acute trusts handling of a received eRS referral request. Each process communicates via the FHIR Task, the first process takes the eRS referral and gets the referral letter from eRS, these are then passed to the clinician for triage. Once triaged, the clinician creates a book appointment Task which the admin's action.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
extension | I | 0..* | Extension | Element IdTask.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
agent | S I | 0..1 | Extension(Reference(NHSDigitalPractitionerRole | NHSDigitalPractitioner | NHSDigitalHealthcareService)) | Element IdTask.extension:agent Provenance of the resource Alternate namesextensions, user content DefinitionIs used as the author on request resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(NHSDigitalPractitionerRole | NHSDigitalPractitioner | NHSDigitalHealthcareService)) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-Provenance-agent Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
prescription | S I | 0..1 | Extension(Complex) | Element IdTask.extension:prescription EPS Patient Tracker extension Alternate namesextensions, user content Definition
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-EPS-Prescription Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
repeatInformation | S I | 0..1 | Extension(Complex) | Element IdTask.extension:repeatInformation Used in the EPS Prescription Tracker Alternate namesextensions, user content Definition
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-EPS-RepeatInformation Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | S | 0..* | Identifier | Element IdTask.identifier Task Instance Identifier DefinitionFor EPS A single identifier MUST be present and the value must be a UUID.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | There are no (further) constraints on this element Element IdTask.instantiatesCanonical Formal definition of task DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed, enabling automation.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
instantiatesUri | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.instantiatesUri Formal definition of task DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
basedOn | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdTask.basedOn Request fulfilled by this task DefinitionBasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ServiceRequest, MedicationRequest, ServiceRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill. This latter resource is referenced by FocusOn. For example, based on a ServiceRequest (= BasedOn), a task is created to fulfill a procedureRequest ( = FocusOn ) to collect a specimen from a patient. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.basedOn.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.basedOn.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.basedOn.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.basedOn.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.basedOn.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.basedOn.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.basedOn.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.basedOn.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.basedOn.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.basedOn.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
groupIdentifier | S Σ | 0..1 | Identifier | Element IdTask.groupIdentifier Requisition or grouper id DefinitionEPS Only An identifier to the original
Billing and/or reporting can be linked to whether multiple requests were created as a single unit.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
partOf | Σ I | 0..* | Reference(UK Core Task) | There are no (further) constraints on this element Element IdTask.partOf Composite task DefinitionTask that this particular task is part of. Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task). This should usually be 0..1.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.partOf.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.partOf.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.partOf.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.partOf.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.partOf.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.partOf.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.partOf.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.partOf.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.partOf.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.partOf.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
status | S Σ ?! | 1..1 | codeBinding | Element IdTask.status draft | requested | received | accepted | + DefinitionThese workflow tasks have The following diagram reflects the "typical" state machine for Task. Note that not all states will be supported by all workflows and that some workflows may support additional transitions, including transitions from terminal states (e.g. back to "in-progress" from "failed" or "completed"). For example: A patient requesting a repeat prescription would ask for task with code These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks. For EPS Only
The current status of the task. TaskStatus (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
statusReason | Σ | 0..1 | CodeableConcept | Element IdTask.statusReason Reason for current status DefinitionFor EPS only
This applies to the current status. Look at the history of the task to see reasons for past statuses. Codes to identify the reason for current status. These will typically be specific to a particular workflow. (unbound) (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
businessStatus | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.businessStatus E.g. "Specimen collected", "IV prepped" DefinitionContains business-specific nuances of the business state. There's often a need to track substates of a task - this is often variable by specific workflow implementation. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. (unbound) (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
intent | S Σ | 1..1 | codeBinding | Element IdTask.intent unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option DefinitionIndicates the "level" of actionability associated with the Task, i.e. i+R[9]Cs this a proposed task, a planned task, an actionable task, etc. Is not processed by EPS and is included for FHIR compliance reasons. The value should always be Distinguishes whether the task is a proposal, plan or full order. TaskIntent (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
priority | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.priority routine | urgent | asap | stat DefinitionIndicates how quickly the Task should be addressed with respect to other requests. Used to identify the service level expected while performing a task. Note that FHIR strings SHALL NOT exceed 1MB in size If missing, this task should be performed with normal priority The task's priority. RequestPriority (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | S Σ | 1..1 | CodeableConcept | Element IdTask.code Task Type Definitione-RS A SNOMED CT procedure code to indicate the action
EPS The SNOMED action codes are complemented with For example: The code
The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code. Codes to identify what the task involves. These will typically be specific to a particular workflow. TaskCode (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
coding | Σ | 0..* | Coding | Element IdTask.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
(All Slices) | There are no (further) constraints on this element | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdTask.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 1..1 | code | There are no (further) constraints on this element Element IdTask.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNOMED | Σ | 0..* | CodingBinding | Element IdTask.code.coding:SNOMED Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. NHSDigital Action Code (extensible) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uriFixed Value | Element IdTask.code.coding:SNOMED.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://snomed.info/sct
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:SNOMED.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdTask.code.coding:SNOMED.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:SNOMED.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.code.coding:SNOMED.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Fulfilment | Σ | 0..* | CodingBinding | Element IdTask.code.coding:Fulfilment Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. NHSDigital Task Code (extensible) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uriFixed Value | Element IdTask.code.coding:Fulfilment.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://hl7.org/fhir/CodeSystem/task-code
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:Fulfilment.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdTask.code.coding:Fulfilment.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:Fulfilment.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.code.coding:Fulfilment.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Worflow | Σ | 0..* | CodingBinding | Element IdTask.code.coding:Worflow Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. NHSDigital Workflow Code (extensible) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uriFixed Value | Element IdTask.code.coding:Worflow.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
https://fhir.nhs.uk/CodeSystem/Workflow-Code
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:Worflow.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdTask.code.coding:Worflow.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:Worflow.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.code.coding:Worflow.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
description | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.description Human-readable explanation of task DefinitionA free-text description of what is to be performed. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
focus | S Σ I | 0..1 | Reference(NHSDigitalAppointment | NHSDigitalServiceRequest | NHSDigitalBundleFHIRMessage | NHSDigitalMedicationRequest | UK Core Patient) | Element IdTask.focus What task is acting on Definitione-RS Reference to the resource which is the focus of the action
** EPS Only** This will be the
Used to identify the thing to be done. Tasks are often generated as a consequence of other workflows or relate to FHIR Workflow resources. For example a repeat medication request will be related to a previous
Reference(NHSDigitalAppointment | NHSDigitalServiceRequest | NHSDigitalBundleFHIRMessage | NHSDigitalMedicationRequest | UK Core Patient) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.focus.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.focus.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.focus.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.focus.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.focus.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.focus.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.focus.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.focus.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.focus.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.focus.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
for | S Σ I | 1..1 | Reference(Resource) | Element IdTask.for Beneficiary of the Task Alternate namesPatient DefinitionA reference to the patient the Task is for. This will always be an identifier reference using the Patients NHSNumber.
Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.for.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.for.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 1..1 | Identifier | There are no (further) constraints on this element Element IdTask.for.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.for.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.for.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdTask.for.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.nhs.uk/Id/nhs-number
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdTask.for.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.for.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.for.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.for.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
encounter | Σ I | 0..1 | Reference(UK Core Encounter) | There are no (further) constraints on this element Element IdTask.encounter Healthcare event during which this task originated DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created. For some tasks it may be important to know the link between the encounter the task originated within. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.encounter.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.encounter.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.encounter.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.encounter.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.encounter.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.encounter.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.encounter.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.encounter.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.encounter.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.encounter.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
executionPeriod | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.executionPeriod Start and end time of execution DefinitionIdentifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end). A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
authoredOn | S I | 0..1 | dateTime | Element IdTask.authoredOn Task Creation Date Alternate namesCreated Date DefinitionDate and time the task was created.
Most often used along with lastUpdated to track duration of task to supporting monitoring and management.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
lastModified | Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.lastModified Task Last Modified Date Alternate namesUpdate Date DefinitionThe date and time of last modification to this task. Used along with history to track task activity and time in a particular task state. This enables monitoring and management.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
requester | S Σ I | 0..1 | Reference(NHSDigitalPractitionerRole) | Element IdTask.requester Who is asking for task to be done DefinitionWho is created the Request or the Event. In NHSDigital API's this SHOULD always be a PractitionerRole role reference.
This will reference a
Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(NHSDigitalPractitionerRole) Allowed aggregation: contained Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.requester.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.requester.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.requester.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.requester.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.requester.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdTask.requester.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdTask.requester.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.requester.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.requester.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.requester.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
performerType | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.performerType Requested performer DefinitionThe kind of participant that should perform the task. Use to distinguish tasks on different activity queues. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The type(s) of task performers allowed. ProcedurePerformerRoleCodes (preferred)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
owner | S Σ I | 0..1 | Reference(NHSDigitalPractitionerRole | NHSDigitalOrganization) | Element IdTask.owner Responsible organisation Alternate namesPerformer, Executer DefinitionEPS Who is responsible for actioning the request Task (e.g. for a prescription-order this will be the pharmacy).
e-RS
Identifies who is expected to perform this task. Tasks may be created with an owner not yet identified. Reference(NHSDigitalPractitionerRole | NHSDigitalOrganization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.owner.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.owner.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.owner.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.owner.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.owner.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdTask.owner.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdTask.owner.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.owner.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.owner.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.owner.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
location | Σ I | 0..1 | Reference(UK Core Location) | There are no (further) constraints on this element Element IdTask.location Where task occurs DefinitionPrincipal physical location where the this task is performed. Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.location.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.location.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.location.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.location.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.location.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.location.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.location.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.location.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.location.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.location.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reasonCode | S | 0..1 | CodeableConcept | Element IdTask.reasonCode Why task is needed DefinitionIn FHIR Task these types of workflow would be represented via reasonCode and/or reasonReference For medication this is probably SNOMED CT based using codes under the SNOMED CT 182832007 Medication management and includes codes such as:
For referral management
This should only be included if there is no focus or if it differs from the reason indicated on the focus. Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. (unbound) (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
coding | Σ | 0..* | Coding | Element IdTask.reasonCode.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
(All Slices) | There are no (further) constraints on this element | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdTask.reasonCode.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 1..1 | code | There are no (further) constraints on this element Element IdTask.reasonCode.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 1..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.reasonCode.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNOMED | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uriFixed Value | Element IdTask.reasonCode.coding:SNOMED.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://snomed.info/sct
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reasonReference | I | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element IdTask.reasonReference Why task is needed DefinitionA resource reference indicating why this task needs to be performed. Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonReference.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.reasonReference.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.reasonReference.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonReference.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element IdTask.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Coverage | ClaimResponse) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.insurance.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.insurance.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.insurance.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.insurance.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.insurance.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.insurance.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.insurance.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.insurance.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.insurance.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.insurance.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
note | S | 0..* | Annotation | Element IdTask.note Comments made about the task DefinitionEPS Only This may contain cancellation reason. e-RS Used to add notes to the worklist items
For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
relevantHistory | I | 0..* | Reference(UK Core Provenance) | There are no (further) constraints on this element Element IdTask.relevantHistory Key events in history of the Task Alternate namesStatus History DefinitionLinks to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task. This element does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.relevantHistory.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.relevantHistory.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.relevantHistory.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
restriction | S | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdTask.restriction Constraints on fulfillment tasks DefinitionIf the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned. Sometimes when fulfillment is sought, you don't want full fulfillment.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
repetitions | 0..1 | positiveInt | There are no (further) constraints on this element Element IdTask.restriction.repetitions How many times to repeat DefinitionIndicates the number of times the requested action should occur. E.g. order that requests monthly lab tests, fulfillment is sought for 1. 32 bit number; for values larger than this, use decimal
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.restriction.period When fulfillment sought DefinitionOver what time-period is fulfillment sought. E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months. Note that period.high is the due date representing the time by which the task should be completed.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
start | Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.restriction.period.start Starting time with inclusive boundary DefinitionThe start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
end | S Σ I | 0..1 | dateTime | Element IdTask.restriction.period.end End time with inclusive boundary, if not ongoing DefinitionIn e-RS this is also known as the review date due. e-RS
If the end of the period is missing, it means that the period is ongoing
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
recipient | I | 0..* | Reference(UK Core Organization | UK Core Patient | UK Core Practitioner | UK Core PractitionerRole | UK Core RelatedPerson | Group) | There are no (further) constraints on this element Element IdTask.restriction.recipient For whom is fulfillment sought? DefinitionFor requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought? References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(UK Core Organization | UK Core Patient | UK Core Practitioner | UK Core PractitionerRole | UK Core RelatedPerson | Group) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.restriction.recipient.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.restriction.recipient.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.restriction.recipient.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
input | S | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.input Information used to perform task Alternate namesSupporting Information DefinitionAdditional information that may be needed in the execution of the task. Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.input.type Label for the input Alternate namesName DefinitionA code or description indicating how the input is intended to be used as part of the task execution. Inputs are named to enable task automation to bind data and pass it from one task to the next. If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. (unbound) (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.input.value[x] Content to use in performing the task DefinitionThe value of the input parameter as a basic type.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCode | code | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDate | date | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueId | id | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueInstant | instant | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueInteger | integer | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueOid | oid | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueString | string | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTime | time | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUri | uri | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUrl | url | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUuid | uuid | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAddress | Address | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAge | Age | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCoding | Coding | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCount | Count | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDistance | Distance | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDuration | Duration | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMoney | Money | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valuePeriod | Period | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRange | Range | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueSignature | Signature | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTiming | Timing | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueExpression | Expression | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMeta | Meta | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueReference | Reference() | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
output | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.output Information produced as part of task DefinitionOutputs produced by the Task. Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.output.type Label for output Alternate namesName DefinitionThe name of the Output parameter. Outputs are named to enable task automation to bind data and pass it from one task to the next. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. (unbound) (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.output.value[x] Result of output DefinitionThe value of the Output parameter as a basic type. Task outputs can take any form.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCode | code | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDate | date | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueId | id | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueInstant | instant | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueInteger | integer | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueOid | oid | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueString | string | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTime | time | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUri | uri | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUrl | url | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUuid | uuid | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAddress | Address | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAge | Age | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCoding | Coding | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCount | Count | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDistance | Distance | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDuration | Duration | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMoney | Money | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valuePeriod | Period | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRange | Range | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueSignature | Signature | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTiming | Timing | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueExpression | Expression | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMeta | Meta | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueReference | Reference() | There are no (further) constraints on this element Data Type |
Task | I | Task | Element IdTask A task to be performed DefinitionFHIR Task usage and scope is defined as
A Task resource often exists in parallel with clinical resources. For example, a Task could request fulfillment of a ServiceRequest ordering a Procedure that would result in a Procedure, Observation, DiagnosticReport, ImagingStudy or similar resource. Another example would be a Task that requests fulfillment of a CommunicationRequest to be performed between various actors. Task has three main uses:
Order FulfilmentCentres on the fulfilment of the order. It does not contain the order details which are held in a referenced request resource.
In the diagram below the recipient or fulfiller of the order uses FHIR Task to accept or reject the order, it also uses Task to send Examples:
See the section on Minor Workflow RequestsThis is used to implement additional around an order or to record specific workflow requests. These may not have a focused resource reference. It is anticipated they are coded using SNOMED CT. Examples:
The Task.status can be used to indicate fulfilment/delivery status. Workflow SupportMore advanced workflow is supported, this adds in the use of Task.input and Task.output. This allows the passage of inputs and outputs which may be found in automated workflow activities. The diagram below is from an acute trusts handling of a received eRS referral request. Each process communicates via the FHIR Task, the first process takes the eRS referral and gets the referral letter from eRS, these are then passed to the clinician for triage. Once triaged, the clinician creates a book appointment Task which the admin's action.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
extension | I | 0..* | Extension | Element IdTask.extension Additional content defined by implementations Alternate namesextensions, user content DefinitionMay be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
agent | S I | 0..1 | Extension(Reference(NHSDigitalPractitionerRole | NHSDigitalPractitioner | NHSDigitalHealthcareService)) | Element IdTask.extension:agent Provenance of the resource Alternate namesextensions, user content DefinitionIs used as the author on request resources. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(NHSDigitalPractitionerRole | NHSDigitalPractitioner | NHSDigitalHealthcareService)) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-Provenance-agent Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
prescription | S I | 0..1 | Extension(Complex) | Element IdTask.extension:prescription EPS Patient Tracker extension Alternate namesextensions, user content Definition
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-EPS-Prescription Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
repeatInformation | S I | 0..1 | Extension(Complex) | Element IdTask.extension:repeatInformation Used in the EPS Prescription Tracker Alternate namesextensions, user content Definition
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.nhs.uk/StructureDefinition/Extension-EPS-RepeatInformation Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | S | 0..* | Identifier | Element IdTask.identifier Task Instance Identifier DefinitionFor EPS A single identifier MUST be present and the value must be a UUID.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | There are no (further) constraints on this element Element IdTask.instantiatesCanonical Formal definition of task DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed, enabling automation.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
instantiatesUri | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.instantiatesUri Formal definition of task DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
basedOn | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdTask.basedOn Request fulfilled by this task DefinitionBasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ServiceRequest, MedicationRequest, ServiceRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill. This latter resource is referenced by FocusOn. For example, based on a ServiceRequest (= BasedOn), a task is created to fulfill a procedureRequest ( = FocusOn ) to collect a specimen from a patient. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.basedOn.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.basedOn.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.basedOn.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.basedOn.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.basedOn.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.basedOn.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.basedOn.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.basedOn.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.basedOn.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.basedOn.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
groupIdentifier | S Σ | 0..1 | Identifier | Element IdTask.groupIdentifier Requisition or grouper id DefinitionEPS Only An identifier to the original
Billing and/or reporting can be linked to whether multiple requests were created as a single unit.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
partOf | Σ I | 0..* | Reference(UK Core Task) | There are no (further) constraints on this element Element IdTask.partOf Composite task DefinitionTask that this particular task is part of. Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task). This should usually be 0..1.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.partOf.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.partOf.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.partOf.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.partOf.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.partOf.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.partOf.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.partOf.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.partOf.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.partOf.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.partOf.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
status | S Σ ?! | 1..1 | codeBinding | Element IdTask.status draft | requested | received | accepted | + DefinitionThese workflow tasks have The following diagram reflects the "typical" state machine for Task. Note that not all states will be supported by all workflows and that some workflows may support additional transitions, including transitions from terminal states (e.g. back to "in-progress" from "failed" or "completed"). For example: A patient requesting a repeat prescription would ask for task with code These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks. For EPS Only
The current status of the task. TaskStatus (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
statusReason | Σ | 0..1 | CodeableConcept | Element IdTask.statusReason Reason for current status DefinitionFor EPS only
This applies to the current status. Look at the history of the task to see reasons for past statuses. Codes to identify the reason for current status. These will typically be specific to a particular workflow. (unbound) (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
businessStatus | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.businessStatus E.g. "Specimen collected", "IV prepped" DefinitionContains business-specific nuances of the business state. There's often a need to track substates of a task - this is often variable by specific workflow implementation. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. (unbound) (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
intent | S Σ | 1..1 | codeBinding | Element IdTask.intent unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option DefinitionIndicates the "level" of actionability associated with the Task, i.e. i+R[9]Cs this a proposed task, a planned task, an actionable task, etc. Is not processed by EPS and is included for FHIR compliance reasons. The value should always be Distinguishes whether the task is a proposal, plan or full order. TaskIntent (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
priority | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.priority routine | urgent | asap | stat DefinitionIndicates how quickly the Task should be addressed with respect to other requests. Used to identify the service level expected while performing a task. Note that FHIR strings SHALL NOT exceed 1MB in size If missing, this task should be performed with normal priority The task's priority. RequestPriority (required)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | S Σ | 1..1 | CodeableConcept | Element IdTask.code Task Type Definitione-RS A SNOMED CT procedure code to indicate the action
EPS The SNOMED action codes are complemented with For example: The code
The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code. Codes to identify what the task involves. These will typically be specific to a particular workflow. TaskCode (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
coding | Σ | 0..* | Coding | Element IdTask.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
(All Slices) | There are no (further) constraints on this element | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdTask.code.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 1..1 | code | There are no (further) constraints on this element Element IdTask.code.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.code.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNOMED | Σ | 0..* | CodingBinding | Element IdTask.code.coding:SNOMED Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. NHSDigital Action Code (extensible) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uriFixed Value | Element IdTask.code.coding:SNOMED.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://snomed.info/sct
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:SNOMED.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdTask.code.coding:SNOMED.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:SNOMED.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.code.coding:SNOMED.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Fulfilment | Σ | 0..* | CodingBinding | Element IdTask.code.coding:Fulfilment Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. NHSDigital Task Code (extensible) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uriFixed Value | Element IdTask.code.coding:Fulfilment.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://hl7.org/fhir/CodeSystem/task-code
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:Fulfilment.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdTask.code.coding:Fulfilment.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:Fulfilment.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.code.coding:Fulfilment.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
Worflow | Σ | 0..* | CodingBinding | Element IdTask.code.coding:Worflow Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. NHSDigital Workflow Code (extensible) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uriFixed Value | Element IdTask.code.coding:Worflow.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
https://fhir.nhs.uk/CodeSystem/Workflow-Code
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:Worflow.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdTask.code.coding:Worflow.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.coding:Worflow.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.code.coding:Worflow.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.code.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
description | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.description Human-readable explanation of task DefinitionA free-text description of what is to be performed. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
focus | S Σ I | 0..1 | Reference(NHSDigitalAppointment | NHSDigitalServiceRequest | NHSDigitalBundleFHIRMessage | NHSDigitalMedicationRequest | UK Core Patient) | Element IdTask.focus What task is acting on Definitione-RS Reference to the resource which is the focus of the action
** EPS Only** This will be the
Used to identify the thing to be done. Tasks are often generated as a consequence of other workflows or relate to FHIR Workflow resources. For example a repeat medication request will be related to a previous
Reference(NHSDigitalAppointment | NHSDigitalServiceRequest | NHSDigitalBundleFHIRMessage | NHSDigitalMedicationRequest | UK Core Patient) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.focus.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.focus.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.focus.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.focus.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.focus.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.focus.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.focus.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.focus.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.focus.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.focus.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
for | S Σ I | 1..1 | Reference(Resource) | Element IdTask.for Beneficiary of the Task Alternate namesPatient DefinitionA reference to the patient the Task is for. This will always be an identifier reference using the Patients NHSNumber.
Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.for.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.for.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 1..1 | Identifier | There are no (further) constraints on this element Element IdTask.for.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.for.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.for.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uriFixed Value | Element IdTask.for.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
https://fhir.nhs.uk/Id/nhs-number
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdTask.for.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.for.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.for.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.for.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
encounter | Σ I | 0..1 | Reference(UK Core Encounter) | There are no (further) constraints on this element Element IdTask.encounter Healthcare event during which this task originated DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created. For some tasks it may be important to know the link between the encounter the task originated within. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.encounter.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.encounter.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.encounter.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.encounter.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.encounter.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.encounter.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.encounter.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.encounter.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.encounter.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.encounter.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
executionPeriod | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.executionPeriod Start and end time of execution DefinitionIdentifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end). A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
authoredOn | S I | 0..1 | dateTime | Element IdTask.authoredOn Task Creation Date Alternate namesCreated Date DefinitionDate and time the task was created.
Most often used along with lastUpdated to track duration of task to supporting monitoring and management.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
lastModified | Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.lastModified Task Last Modified Date Alternate namesUpdate Date DefinitionThe date and time of last modification to this task. Used along with history to track task activity and time in a particular task state. This enables monitoring and management.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
requester | S Σ I | 0..1 | Reference(NHSDigitalPractitionerRole) | Element IdTask.requester Who is asking for task to be done DefinitionWho is created the Request or the Event. In NHSDigital API's this SHOULD always be a PractitionerRole role reference.
This will reference a
Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(NHSDigitalPractitionerRole) Allowed aggregation: contained Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.requester.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.requester.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.requester.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.requester.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.requester.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdTask.requester.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdTask.requester.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.requester.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.requester.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.requester.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
performerType | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.performerType Requested performer DefinitionThe kind of participant that should perform the task. Use to distinguish tasks on different activity queues. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The type(s) of task performers allowed. ProcedurePerformerRoleCodes (preferred)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
owner | S Σ I | 0..1 | Reference(NHSDigitalPractitionerRole | NHSDigitalOrganization) | Element IdTask.owner Responsible organisation Alternate namesPerformer, Executer DefinitionEPS Who is responsible for actioning the request Task (e.g. for a prescription-order this will be the pharmacy).
e-RS
Identifies who is expected to perform this task. Tasks may be created with an owner not yet identified. Reference(NHSDigitalPractitionerRole | NHSDigitalOrganization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.owner.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.owner.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.owner.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.owner.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.owner.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdTask.owner.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 1..1 | string | There are no (further) constraints on this element Element IdTask.owner.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.owner.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.owner.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.owner.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
location | Σ I | 0..1 | Reference(UK Core Location) | There are no (further) constraints on this element Element IdTask.location Where task occurs DefinitionPrincipal physical location where the this task is performed. Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.location.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.location.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.location.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.location.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.location.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.location.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.location.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.location.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.location.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.location.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reasonCode | S | 0..1 | CodeableConcept | Element IdTask.reasonCode Why task is needed DefinitionIn FHIR Task these types of workflow would be represented via reasonCode and/or reasonReference For medication this is probably SNOMED CT based using codes under the SNOMED CT 182832007 Medication management and includes codes such as:
For referral management
This should only be included if there is no focus or if it differs from the reason indicated on the focus. Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. (unbound) (example)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
coding | Σ | 0..* | Coding | Element IdTask.reasonCode.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
(All Slices) | There are no (further) constraints on this element | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 1..1 | uri | There are no (further) constraints on this element Element IdTask.reasonCode.coding.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.coding.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 1..1 | code | There are no (further) constraints on this element Element IdTask.reasonCode.coding.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 1..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.coding.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.reasonCode.coding.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
SNOMED | Σ | 0..* | Coding | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for alternative encodings within a code system, and translations to other code systems. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uriFixed Value | Element IdTask.reasonCode.coding:SNOMED.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
http://snomed.info/sct
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
version | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
code | Σ | 0..1 | code | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Note that FHIR strings SHALL NOT exceed 1MB in size
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element IdTask.reasonCode.coding:SNOMED.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
text | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonCode.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reasonReference | I | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element IdTask.reasonReference Why task is needed DefinitionA resource reference indicating why this task needs to be performed. Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonReference.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.reasonReference.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.reasonReference.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.reasonReference.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.reasonReference.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element IdTask.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Coverage | ClaimResponse) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.insurance.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.insurance.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.insurance.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.insurance.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.insurance.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.insurance.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.insurance.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.insurance.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.insurance.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.insurance.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
note | S | 0..* | Annotation | Element IdTask.note Comments made about the task DefinitionEPS Only This may contain cancellation reason. e-RS Used to add notes to the worklist items
For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
relevantHistory | I | 0..* | Reference(UK Core Provenance) | There are no (further) constraints on this element Element IdTask.relevantHistory Key events in history of the Task Alternate namesStatus History DefinitionLinks to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task. This element does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.relevantHistory.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.relevantHistory.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.relevantHistory.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.relevantHistory.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
restriction | S | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdTask.restriction Constraints on fulfillment tasks DefinitionIf the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned. Sometimes when fulfillment is sought, you don't want full fulfillment.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
repetitions | 0..1 | positiveInt | There are no (further) constraints on this element Element IdTask.restriction.repetitions How many times to repeat DefinitionIndicates the number of times the requested action should occur. E.g. order that requests monthly lab tests, fulfillment is sought for 1. 32 bit number; for values larger than this, use decimal
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.restriction.period When fulfillment sought DefinitionOver what time-period is fulfillment sought. E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months. Note that period.high is the due date representing the time by which the task should be completed.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
start | Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.restriction.period.start Starting time with inclusive boundary DefinitionThe start of the period. The boundary is inclusive. If the low element is missing, the meaning is that the low boundary is not known.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
end | S Σ I | 0..1 | dateTime | Element IdTask.restriction.period.end End time with inclusive boundary, if not ongoing DefinitionIn e-RS this is also known as the review date due. e-RS
If the end of the period is missing, it means that the period is ongoing
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
recipient | I | 0..* | Reference(UK Core Organization | UK Core Patient | UK Core Practitioner | UK Core PractitionerRole | UK Core RelatedPerson | Group) | There are no (further) constraints on this element Element IdTask.restriction.recipient For whom is fulfillment sought? DefinitionFor requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought? References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(UK Core Organization | UK Core Patient | UK Core Practitioner | UK Core PractitionerRole | UK Core RelatedPerson | Group) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
reference | Σ I | 0..1 | string | There are no (further) constraints on this element Element IdTask.restriction.recipient.reference Literal reference, Relative, internal or absolute URL DefinitionA reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | uriBinding | There are no (further) constraints on this element Element IdTask.restriction.recipient.type Type the reference refers to (e.g. "Patient") DefinitionThe expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources). This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified. Aa resource (or, for logical models, the URI of the logical model). ResourceType (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
identifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier Logical reference, when literal reference is not known DefinitionAn identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.use usual | official | temp | secondary | old (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
system | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Identifier.system is always case sensitive.
General http://www.acme.com/identifiers/patient Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
value | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.
General 123456 Mappings
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
period | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
assigner | Σ I | 0..1 | Reference(UK Core Organization) | There are no (further) constraints on this element Element IdTask.restriction.recipient.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(UK Core Organization) Constraints
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
display | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.restriction.recipient.display Text alternative for the resource DefinitionPlain text narrative that identifies the resource in addition to the resource reference. This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
input | S | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.input Information used to perform task Alternate namesSupporting Information DefinitionAdditional information that may be needed in the execution of the task. Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.input.type Label for the input Alternate namesName DefinitionA code or description indicating how the input is intended to be used as part of the task execution. Inputs are named to enable task automation to bind data and pass it from one task to the next. If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. (unbound) (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.input.value[x] Content to use in performing the task DefinitionThe value of the input parameter as a basic type.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCode | code | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDate | date | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueId | id | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueInstant | instant | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueInteger | integer | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueOid | oid | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueString | string | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTime | time | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUri | uri | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUrl | url | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUuid | uuid | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAddress | Address | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAge | Age | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCoding | Coding | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCount | Count | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDistance | Distance | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDuration | Duration | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMoney | Money | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valuePeriod | Period | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRange | Range | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueSignature | Signature | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTiming | Timing | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueExpression | Expression | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMeta | Meta | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueReference | Reference() | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
output | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.output Information produced as part of task DefinitionOutputs produced by the Task. Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.output.type Label for output Alternate namesName DefinitionThe name of the Output parameter. Outputs are named to enable task automation to bind data and pass it from one task to the next. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. (unbound) (example)Constraints
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.output.value[x] Result of output DefinitionThe value of the Output parameter as a basic type. Task outputs can take any form.
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCode | code | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDate | date | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueId | id | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueInstant | instant | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueInteger | integer | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueOid | oid | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueString | string | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTime | time | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUri | uri | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUrl | url | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUuid | uuid | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAddress | Address | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAge | Age | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCoding | Coding | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueCount | Count | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDistance | Distance | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDuration | Duration | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMoney | Money | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valuePeriod | Period | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRange | Range | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueSignature | Signature | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTiming | Timing | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueExpression | Expression | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueMeta | Meta | There are no (further) constraints on this element Data Type | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||
valueReference | Reference() | There are no (further) constraints on this element Data Type |
key | human | severity | expression |
---|---|---|---|
nhsd-taskfocus | focus - An identifier reference or resource reference must be provided | error | (reference.exists() or identifier.exists()) |
patient-reference | An identifier reference or resource reference must be provided | error | (reference.exists() or identifier.exists()) |
patient-nhs | NHS Number must be in the English and Welsh NHS Number range or length of the number is wrong. | error | identifier.where(system='https://fhir.nhs.uk/Id/nhs-number').exists().not() or (identifier.where(system='https://fhir.nhs.uk/Id/nhs-number').exists() and identifier.where(system='https://fhir.nhs.uk/Id/nhs-number').value.matches('^([456789]{1}[0-9]{9})$')) |
Constraint Profiles
name | profile | purpose |
---|---|---|
NHSDigitalTaskEPS | https://fhir.nhs.uk/StructureDefinition/NHSDigital-Task-EPS | Constraint profile for Electronic Prescription System |
NHSDigitalTaskPatientCare | https://fhir.nhs.uk/StructureDefinition/NHSDigital-Task-PatientCare | Profile on NHSDigital-Task for NHS App/e-RS PatientCare |
Definition
FHIR Task usage and scope is defined as
A task resource describes an activity that can be performed and tracks the state of completion of that activity. It is a representation that an activity should be or has been initiated, and eventually, represents the successful or unsuccessful completion of that activity. Note that there are a variety of processes associated with making and processing orders. Some orders may be handled immediately by automated systems but most require real world actions by one or more humans. Some orders can only be processed when other real world actions happen, such as a patient presenting themselves so that the action to be performed can actually be performed. Often these real world dependencies are only implicit in the order details.
A Task resource often exists in parallel with clinical resources.
For example, a Task could request fulfillment of a ServiceRequest ordering a Procedure that would result in a Procedure, Observation, DiagnosticReport, ImagingStudy or similar resource. Another example would be a Task that requests fulfillment of a CommunicationRequest to be performed between various actors.
Comment
Task has three main uses:
- basic delivery of an order resource (e.g. MedicationRequest or ServiceRequest)
- minor workflow requests (e.g. phone patient, complete form or validate a referral)
- workflow support (centred around complex workflow support and may involves a workflow engine)
Order Fulfilment
Centres on the fulfilment of the order. It does not contain the order details which are held in a referenced request resource.
In the diagram below the recipient or fulfiller of the order uses FHIR Task to accept or reject the order, it also uses Task to send event
updates.
Note the fulfiller will use other resources to record the details of the fulfilment such as MedicationDispense for a MedicationRequest.
Examples:
Task.code | Task.status | Task.focus | Task.requester | Meaning |
---|---|---|---|---|
fulfill | rejected | MedicationRequest | dispenser | The dispenser is rejecting the fulfilment/deliver of a referenced MedicationRequest. The MedicationRequest is not cancelled |
fullfill | cancelled | MedicationRequest | any | The requested fulfilment of the MedicationRequest is cancelled. The referenced MedicationRequest is not cancelled |
fullfill | accepted | MedicationRequest | dispenser | The dispenser is taking responsibility of fulfilling the referenced MedicationRequest. |
fullfill | completed | MedicationRequest | dispenser | The requested fulfilment of the MedicationRequest is completed. The referenced MedicationRequest can now be changed to completed. |
See the section on status
for more details.
Minor Workflow Requests
This is used to implement additional around an order or to record specific workflow requests. These may not have a focused resource reference. It is anticipated they are coded using SNOMED CT.
Examples:Task.code | Task.focus | Task.requester | Task.owner | Task.reasonCode | Meaning |
---|---|---|---|---|---|
413292001 Assessment for referral | ServiceRequest | referrer | clinician | 3457005 Patient Referral | Check the referenced referral is valid. |
182836005 Review of medication | clinician | GP | 151715009 Emergency admission, asthma | Request to review medication following an emergency admission. | |
103742009 Renewal of prescription | MedicationRequest | patient | GP | Request for a reissue/refill of a medication | |
324861000000109 Review of patient laboratory test report | DiagnosticReport | consultant | Request for a lab report to be reviewed. See also UHS Lab Reports |
The Task.status can be used to indicate fulfilment/delivery status.
Workflow Support
More advanced workflow is supported, this adds in the use of Task.input and Task.output. This allows the passage of inputs and outputs which may be found in automated workflow activities.
The diagram below is from an acute trusts handling of a received eRS referral request. Each process communicates via the FHIR Task, the first process takes the eRS referral and gets the referral letter from eRS, these are then passed to the clinician for triage. Once triaged, the clinician creates a book appointment Task which the admin's action.
Constraints
inv-1 (ERROR) Last modified date must be greater than or equal to authored-on date.
extension:agent
Element Id | Task.extension:agent |
Cardinality | 0..1 |
Slice Name | agent |
type | Extension(ExtensionProvenanceAgent) |
Definition
Is used as the author on request resources.
extension:prescription
Element Id | Task.extension:prescription |
Cardinality | 0..1 |
Slice Name | prescription |
type | Extension(ExtensionEPSPrescription) |
Definition
"extension": [ { "url": "https://fhir.nhs.uk/StructureDefinition/Extension-EPS-Prescription", "extension": [ { "url": "courseOfTherapyType", "valueCoding": { "system": "http://terminology.hl7.org/CodeSystem/medicationrequest-course-of-therapy", "code": "acute", "display": "Acute" } } ] } ],
extension:repeatInformation
Element Id | Task.extension:repeatInformation |
Cardinality | 0..1 |
Slice Name | repeatInformation |
type | Extension(ExtensionEPSRepeatInformation) |
Definition
"extension": [ { "url": "https://fhir.nhs.uk/StructureDefinition/Extension-EPS-RepeatInformation", "extension": [ { "url": "numberOfRepeatsAllowed", "valueUnsignedInt": 6 }, { "url": "numberOfRepeatsIssued", "valueUnsignedInt": 2 } ] },
identifier
Element Id | Task.identifier |
Cardinality | 0..* |
type | Identifier |
Definition
For EPS
A single identifier MUST be present and the value must be a UUID.
"identifier": [ { "system": "https://tools.ietf.org/html/rfc4122", "value": "5AC84C11-DB8B-44DA-8FCF-8980B3D13596" } ],
groupIdentifier
Element Id | Task.groupIdentifier |
Cardinality | 0..1 |
type | Identifier |
Definition
EPS Only
An identifier to the original prescription-order
MUST be present. Only the short form identifier needs to be supplied.
"groupIdentifier": { "system": "https://fhir.nhs.uk/Id/prescription-order-number", "value": "88AF6C-C81007-00001C" },
Requirements
Billing and/or reporting can be linked to whether multiple requests were created as a single unit.
status
Element Id | Task.status |
Cardinality | 1..1 |
Terminology Binding | TaskStatus (Required) The current status of the task. |
type | code |
Definition
These workflow tasks have status
which indicates the Task status.
The following diagram reflects the "typical" state machine for Task. Note that not all states will be supported by all workflows and that some workflows may support additional transitions, including transitions from terminal states (e.g. back to "in-progress" from "failed" or "completed").
For example:
A patient requesting a repeat prescription would ask for task with code fulfil
used with 103742009 | Renewal of prescription
and a status of requested
.
Once reviewed (by a clinician), the task status would be changed to accepted
. When the task is then picked up (in-progress
) and the related MedicationRequest is sent, the status would change to completed
.
Requirements
These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks.
Comment
For EPS
Only in-progress
is currently supported for reasonCode = 373784005 (Dispensing medication) and focus is a dispense-notification
.
rejected
/ cancelled
/ failed
are supported for reasonCode = 33633005 (Prescription of drug) and focus is a prescription-order
.
intent
Element Id | Task.intent |
Cardinality | 1..1 |
Terminology Binding | TaskIntent (Required) Distinguishes whether the task is a proposal, plan or full order. |
type | code |
Definition
Indicates the "level" of actionability associated with the Task, i.e. i+R[9]Cs this a proposed task, a planned task, an actionable task, etc.
Comment
Is not processed by EPS and is included for FHIR compliance reasons. The value should always be order
.
code
Element Id | Task.code |
Cardinality | 1..1 |
Terminology Binding | NHSDigitalTaskCode (Extensible) |
type | CodeableConcept |
Definition
e-RS
A SNOMED CT procedure code to indicate the action
"code": { "coding": [ { "system": "http://snomed.info/sct", "code": "386053000", "display": "Evaluation procedure" } ] },
EPS
The SNOMED action codes are complemented with order delivery
task-code which indicates the type of action to be performed against the focal resource.
For example:
The code fulfil
used with 182836005 | Review of medication
means a task to review medication.
The code approve
used with 103742009 | Renewal of prescription
is a task for a clinician to approve the issue of a repeat medication.
"code": { "coding": [ { "system": "http://hl7.org/fhir/CodeSystem/task-code", "code": "fulfill", "display": "Fulfill the focal request" } ]
Comment
The title (eg "My Tasks", "Outstanding Tasks for Patient X") should go into the code.
focus
Element Id | Task.focus |
Cardinality | 0..1 |
type | Reference(NHSDigitalAppointment NHSDigitalServiceRequest NHSDigitalBundleFHIRMessage NHSDigitalMedicationRequest UKCorePatient) |
Definition
e-RS
Reference to the resource which is the focus of the action
"focus": { "reference": "https://server.fire.ly/ServiceRequest/eb13327f-e990-4667-b37a-89eb93a94c47" },
** EPS Only**
This will be the Bundle.identifier
of the message this Task is acting on.
For Tasks with a reasonCode of 373784005 - Dispensing medication
this will be a dispense-notification
message.
For Tasks with a reasonCode of 33633005 - Prescription of drug
this will be the prescription-order
message from the Task/$release operation.
"focus": { "type": "Bundle", "identifier": { "system": "https://tools.ietf.org/html/rfc4122", "value": "334a3195-1f6c-497a-8efe-d272ca9c4e38" } },
Requirements
Used to identify the thing to be done.
Comment
Tasks are often generated as a consequence of other workflows or relate to FHIR Workflow resources. For example a repeat medication request will be related to a previous MedicationRequest
or a medication reconciliation may relate to a hospital admissions Encounter/EpisodeOfCare
. This is carried in the focus
element.
focus
can be omitted. For example if an ED generated a Medication Review as a result of COPD Emergency encounter they may chose to include a reference to the Encounter but they may decide instead to use a more specific reasonCode such as 394720003 | Asthma medication review
.
Constraints
- nhsd-taskfocus (ERROR) focus - An identifier reference or resource reference must be provided
for
Element Id | Task.for |
Cardinality | 1..1 |
type | Reference(Resource) |
Definition
A reference to the patient the Task is for. This will always be an identifier reference using the Patients NHSNumber.
"for": { "identifier": { "system": "https://fhir.nhs.uk/Id/nhs-number", "value": "9446368138" } },
Requirements
Used to track tasks outstanding for a beneficiary. Do not use to track the task owner or creator (see owner and creator respectively). This can also affect access control.
Constraints
- patient-reference (ERROR) An identifier reference or resource reference must be provided
- patient-nhs (ERROR) NHS Number must be in the English and Welsh NHS Number range or length of the number is wrong.
for.identifier.system
Element Id | Task.for.identifier.system |
Cardinality | 1..1 |
Fixed Value | https://fhir.nhs.uk/Id/nhs-number |
type | uri |
Definition
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
Requirements
There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.
Comment
Identifier.system is always case sensitive.
authoredOn
Element Id | Task.authoredOn |
Cardinality | 0..1 |
type | dateTime |
Definition
Date and time the task was created.
"authoredOn": "2020-12-21T17:03:20-00:00",
Requirements
Most often used along with lastUpdated to track duration of task to supporting monitoring and management.
requester
Element Id | Task.requester |
Cardinality | 0..1 |
type | Reference(NHSDigitalPractitionerRole) Aggregation - contained |
Definition
Who is created the Request or the Event. In NHSDigital API's this SHOULD always be a PractitionerRole role reference.
"requester": { "reference": "#requester" },
This will reference a contained
PractitionerRole (note: this resource only contains limited user metadata such as ODS Code, professional code and SDS User Profile Id). This resource should not hold data which is held in SDS, only enough information to identify the SDS Entry,
{ "resourceType": "Task", "id": "bd1ca5c4-ff49-4f2a-9db4-f5dda0112084", "meta": { "lastUpdated": "2016-07-11T11:07:22+00:00" }, "contained": [ { "resourceType": "PractitionerRole", "id": "requester", "practitioner": { "identifier": { "system": "https://fhir.hl7.org.uk/Id/gmp-number", "value": "G8123456" }, "display": "DR AA BHATIA" }, "organization": { "identifier": { "system": "https://fhir.nhs.uk/Id/ods-organization-code", "value": "C81007" }, "display": "VERNON STREET MEDICAL CTR" }, "telecom": [ { "system": "phone", "use": "work", "value": "01234567890" } ] } ],
Requirements
Identifies who created this task. May be used by access control mechanisms (e.g., to ensure that only the creator can cancel a task).
owner
Element Id | Task.owner |
Cardinality | 0..1 |
type | Reference(NHSDigitalPractitionerRole NHSDigitalOrganization) |
Definition
EPS
Who is responsible for actioning the request Task (e.g. for a prescription-order this will be the pharmacy).
"owner": { "identifier": { "system": "https://fhir.nhs.uk/Id/ods-organization-code", "value": "FB444" }, "display": "Freds Pharmacy" },
e-RS
"owner": { "identifier": { "system": "https://fhir.nhs.uk/Id/ers-service", "value": "12444" } },
Requirements
Identifies who is expected to perform this task.
Comment
Tasks may be created with an owner not yet identified.
reasonCode
Element Id | Task.reasonCode |
Cardinality | 0..1 |
type | CodeableConcept |
Definition
In FHIR Task these types of workflow would be represented via reasonCode and/or reasonReference
For medication this is probably SNOMED CT based using codes under the SNOMED CT 182832007 Medication management and includes codes such as:
SNOMED CT | Display |
---|---|
33633005 | Prescription of drug |
373784005 | Dispensing medication |
For referral management
SNOMED CT | Display |
---|---|
3457005 | Patient Referral |
185499000 | Expedite appointment |
Comment
This should only be included if there is no focus or if it differs from the reason indicated on the focus.
reasonCode.coding:SNOMED
Element Id | Task.reasonCode.coding:SNOMED |
Cardinality | 0..* |
Slice Name | SNOMED |
type | Coding |
Definition
A reference to a code defined by a terminology system.
Requirements
Allows for alternative encodings within a code system, and translations to other code systems.
Comment
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
reasonCode.coding:SNOMED.system
Element Id | Task.reasonCode.coding:SNOMED.system |
Cardinality | 0..1 |
Fixed Value | http://snomed.info/sct |
type | uri |
Definition
The identification of the code system that defines the meaning of the symbol in the code.
Requirements
Need to be unambiguous about the source of the definition of the symbol.
Comment
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
note
Element Id | Task.note |
Cardinality | 0..* |
type | Annotation |
Definition
EPS Only
This may contain cancellation reason.
e-RS
Used to add notes to the worklist items
"note": [ { "text": "Optional comments" } ]
restriction
Element Id | Task.restriction |
Cardinality | 0..1 |
type | BackboneElement |
Definition
If the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned.
Requirements
Sometimes when fulfillment is sought, you don't want full fulfillment.
restriction.period.end
Element Id | Task.restriction.period.end |
Cardinality | 0..1 |
type | dateTime |
Definition
In e-RS this is also known as the review date due.
Comment
e-RS
- If deferred to provider (because there were no appointments available for a directly bookable service) then this is the date by which the provide should resolve the appointment slot issue; or
- If the referral was sent to a triage service then this is the date by which the provider should have reviewed the referral
input
Element Id | Task.input |
Cardinality | 0..* |
type | BackboneElement |
Definition
Additional information that may be needed in the execution of the task.
Requirements
Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.