abstractbaseDefinitioncopyrightdate- Values Differ
descriptionexperimentalfhirVersion- Values Differ
jurisdiction
jurisdiction[0]kindnamepublisherpurposestatustitletypeurlversion- Values Differ
| Left: | Medication Recommendation (http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/medication-recommendation) |
| Right: | Medication Recommendation (http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/medication-recommendation) |
| Error | StructureDefinition.version | Values for version differ: '3.0.0' vs '4.0.0-ballot' |
| Information | StructureDefinition.date | Values for date differ: '2024-12-12T20:43:36+00:00' vs '2025-10-16T23:38:27+00:00' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '4.0.1' vs '6.0.0-ballot3' |
| Information | StructureDefinition.definition | Values for definition differ: 'A task to be performed.' vs 'A task to be performed as a part of a workflow and the related informations like inputs, outputs and execution progress. While very simple workflows can be implemented with [Request](http://hl7.org/fhir/R5/request.html) alone, most workflows would require a Task (explicit or contained) as a means to track the execution progress (i.e. inputs, outputs, status). Please refer to [Fulfillment/Execution](http://hl7.org/fhir/R5/request.html#fulfillment).' |
| Information | StructureDefinition.comment | Values for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' vs 'Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a 'text blob' or where text is additionally entered raw or narrated and encoded information is added later.' |
| Information | StructureDefinition.definition | Values for definition differ: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.' vs 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.' |
| Information | StructureDefinition.comment | Values for comment differ: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels. Contained resources may be a resource type defined in the FHIR specification, or an [additional resource](http://build.fhir.org/resource.html#additional).' |
| Information | StructureDefinition.definition | Values for definition differ: 'May 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.' vs 'May 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 managable, 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Enables a formal definition of how he task is to be performed, enabling automation.' vs 'Enables a formal definition of how the task is to be performed, enabling automation.' |
| Information | StructureDefinition.requirements | Values for requirements differ: '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.' vs 'Enables a formal definition of how the task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation.' |
| Information | StructureDefinition.definition | Values for definition differ: 'BasedOn 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.' vs 'BasedOn refers to a higher-level authorization that triggered the creation of the task. It references a 'request' resource such as a ServiceRequest, MedicationRequest, CarePlan, etc. which is distinct from the 'request' resource the task is seeking to fulfill. This latter resource is referenced by focus. For example, based on a CarePlan (= basedOn), a task is created to fulfill a ServiceRequest ( = focus ) to collect a specimen from a patient.' |
| Error | Task.basedOn | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Resource]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Resource|6.0.0-ballot3]]) |
| Information | StructureDefinition.definition | Values for definition differ: 'An identifier that links together multiple tasks and other requests that were created in the same context.' vs 'A shared identifier common to multiple independent Task and Request instances that were activated/authorized more or less simultaneously by a single author. The presence of the same identifier on each request ties those requests together and may have business ramifications in terms of reporting of results, billing, etc. E.g. a requisition number shared by a set of lab tests ordered together, or a prescription number shared by all meds ordered at one time.' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'Indicates the 'level' of actionability associated with the Task, i.e. this a proposed task, a planned task, an actionable task, etc.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The request being actioned or the resource being manipulated by this task.' vs 'The request being fulfilled or the resource being manipulated (changed, suspended, etc.) by this task.' |
| Error | Task.for | Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Resource]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Resource|6.0.0-ballot3]]) |
| Information | StructureDefinition.definition | Values for definition differ: 'Individual organization or Device currently responsible for task execution.' vs 'Party responsible for managing task execution.' |
| Information | StructureDefinition.definition | Values for definition differ: 'Principal physical location where the this task is performed.' vs 'Principal physical location where this task is performed.' |
| Information | StructureDefinition.requirements | Values for requirements differ: '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).' vs 'Provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting).' |
| Information | StructureDefinition.definition | Values for definition differ: 'Free-text information captured about the task as it progresses.' vs 'Free-text information about the task during its lifecycle.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. 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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.short | Values for short differ: 'When fulfillment sought' vs 'When fulfillment is sought' |
| Information | StructureDefinition.definition | Values for definition differ: 'Over what time-period is fulfillment sought.' vs 'The time-period for which fulfillment is sought. This must fall within the overall time period authorized in the referenced request. E.g. ServiceRequest.occurance[x].' |
| Information | StructureDefinition.comment | Values for comment differ: 'Note that period.high is the due date representing the time by which the task should be completed.' vs 'This is distinct from Task.executionPeriod. ExecutionPeriod indicates when the task needs to be initiated, while Task.restriction.period specifies the subset of the overall authorization that this period covers. For example, a MedicationRequest with an overall effective period of 1 year might have a Task whose restriction.period is 2 months (i.e. satisfy 2 months of medication therapy), while the execution period might be 'between now and 5 days from now' - i.e. If you say yes to this, then you're agreeing to supply medication for that 2 month period within the next 5 days. Note that period.high is the due date representing the time by which the task should be completed.' |
| Information | StructureDefinition.definition | Values for definition differ: 'For requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought?' vs 'For requests that are targeted to more than one potential recipient/target, to identify who is fulfillment is sought for.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. 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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.definition | Values for definition differ: 'A code or description indicating how the input is intended to be used as part of the task execution.' vs 'A code or description to distinguish between inputs.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs 'The type of the input may affect how it is used in the task. 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. 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.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.definition | Values for definition differ: 'The name of the Output parameter.' vs 'A code or description to distinguish between outputs.' |
| Name | Value | Comments | |
|---|---|---|---|
| abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/Task | ||
| copyright | This material contains content from LOINC (http://loinc.org). LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license at http://loinc.org/license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc. | ||
| date | 2024-12-12T20:43:36+00:00 | 2025-10-16T23:38:27+00:00 |
|
| description | Task proposing medication recommendations based on the implications of genomic findings. | ||
| experimental | |||
| fhirVersion | 4.0.1 | 6.0.0-ballot3 |
|
| jurisdiction | |||
| jurisdiction[0] | http://unstats.un.org/unsd/methods/m49/m49.htm#001 | ||
| kind | resource | ||
| name | MedicationRecommendation | ||
| publisher | HL7 International / Clinical Genomics | ||
| purpose | |||
| status | active | ||
| title | Medication Recommendation | ||
| type | Task | ||
| url | http://hl7.org/fhir/uv/genomics-reporting/StructureDefinition/medication-recommendation | ||
| version | 3.0.0 | 4.0.0-ballot |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Task | C | 0..* | Task | A task to be performed | C | 0..* | Task | A task to be performed | |||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (required): IETF language tag for a human language
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored | |||||||||
| identifier | 0..* | Identifier | Task Instance Identifier | 0..* | Identifier | Task Instance Identifier | |||||||||||
| instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | Formal definition of task | Σ | 0..1 | canonical(ActivityDefinition) | Formal definition of task | |||||||||
| instantiatesUri | Σ | 0..1 | uri | Formal definition of task | Σ | 0..1 | uri | Formal definition of task | |||||||||
| basedOn | Σ | 0..* | Reference(Resource) | Request fulfilled by this task | Σ | 0..* | Reference(Resource) | Request fulfilled by this task |
| ||||||||
| groupIdentifier | Σ | 0..1 | Identifier | Requisition or grouper id | Σ | 0..1 | Identifier | Requisition or grouper id | |||||||||
| partOf | Σ | 0..* | Reference(Task) | Composite task | Σ | 0..* | Reference(Task) | Composite task | |||||||||
| status | ?!Σ | 1..1 | code | draft | requested | received | accepted | + Binding: ?? (required): The current status of the task. Required Pattern: requested | ?!Σ | 1..1 | code | draft | requested | received | accepted | + Binding: ?? (required): The current status of the task. Required Pattern: requested | |||||||||
| statusReason | Σ | 0..1 | CodeableConcept | Reason for current status Binding Description: (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow. | Σ | 0..1 | CodeableReference() | Reason for current status Binding: ?? (example): Codes to identify the reason for current status. These will typically be specific to a particular workflow. | |||||||||
| businessStatus | Σ | 0..1 | CodeableConcept | E.g. "Specimen collected", "IV prepped" Binding Description: (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. | Σ | 0..1 | CodeableConcept | E.g. "Specimen collected", "IV prepped" Binding: ?? (example): The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. | |||||||||
| intent | Σ | 1..1 | code | unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order. Required Pattern: proposal | Σ | 1..1 | code | unknown | proposal | plan | order | original-order | reflex-order | filler-order | instance-order | option Binding: ?? (required): Distinguishes whether the task is a proposal, plan or full order. Required Pattern: proposal | |||||||||
| priority | 0..1 | code | routine | urgent | asap | stat Binding: ?? (required): The task's priority. | 0..1 | code | routine | urgent | asap | stat Binding: ?? (required): The priority of a task (may affect service level applied to the task). | |||||||||||
| code | Σ | 0..1 | CodeableConcept | Task Type Binding: ?? (required) | ΣC | 0..1 | CodeableConcept | Task Type Binding: ?? (required) | |||||||||
| description | Σ | 0..1 | string | Human-readable explanation of task | Σ | 0..1 | markdown | Human-readable explanation of task | |||||||||
| focus | Σ | 0..1 | Reference(MedicationStatement) | What task is acting on | ΣC | 0..1 | Reference(MedicationStatement) | What task is acting on | |||||||||
| for | Σ | 0..1 | Reference(Resource) | Beneficiary of the Task | Σ | 0..1 | Reference(Resource) | Beneficiary of the Task |
| ||||||||
| encounter | Σ | 0..1 | Reference(Encounter) | Healthcare event during which this task originated | Σ | 0..1 | Reference(Encounter) | Healthcare event during which this task originated | |||||||||
| executionPeriod | Σ | 0..1 | Period | Start and end time of execution | Σ | 0..1 | Period | Start and end time of execution | |||||||||
| authoredOn | C | 0..1 | dateTime | Task Creation Date | 0..1 | dateTime | Task Creation Date | ||||||||||
| lastModified | ΣC | 0..1 | dateTime | Task Last Modified Date | Σ | 0..1 | dateTime | Task Last Modified Date | |||||||||
| requester | Σ | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | Who is asking for task to be done | Σ | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | Who is asking for task to be done | |||||||||
| performerType | 0..* | CodeableConcept | Requested performer Binding: ?? (preferred): The type(s) of task performers allowed. |
| |||||||||||||
| owner | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | Responsible individual | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | Responsible individual | |||||||||
| location | Σ | 0..1 | Reference(Location) | Where task occurs | Σ | 0..1 | Reference(Location) | Where task occurs | |||||||||
| reasonCode | 0..1 | CodeableConcept | Why task is needed Binding Description: (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. |
| |||||||||||||
| reasonReference | 0..1 | Reference(Therapeutic Implication) | Why task is needed |
| |||||||||||||
| insurance | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | 0..* | Reference(Coverage | ClaimResponse) | Associated insurance coverage | |||||||||||
| note | 0..* | Annotation | Comments made about the task | 0..* | Annotation | Comments made about the task | |||||||||||
| relevantHistory | 0..* | Reference(Provenance) | Key events in history of the Task | 0..* | Reference(Provenance) | Key events in history of the Task | |||||||||||
 restriction | 0..1 | BackboneElement | Constraints on fulfillment tasks | C | 0..1 | BackboneElement | Constraints on fulfillment tasks | ||||||||||
 id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| repetitions | 0..1 | positiveInt | How many times to repeat | 0..1 | positiveInt | How many times to repeat | |||||||||||
| period | 0..1 | Period | When fulfillment sought | 0..1 | Period | When fulfillment is sought | |||||||||||
| recipient | 0..* | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) | For whom is fulfillment sought? | 0..* | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) | For whom is fulfillment sought? | |||||||||||
| input | 0..* | BackboneElement | Information used to perform task | 0..* | BackboneElement | Information used to perform task | |||||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| type | 1..1 | CodeableConcept | Label for the input Binding Description: (example): 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. | 1..1 | CodeableConcept | Label for the input Binding: ?? (example): 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. | |||||||||||
| value[x] | 1..1 | base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, Meta | Content to use in performing the task | 1..1 | base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, integer64, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, CodeableReference(), Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, RatioRange, Reference(), SampledData, Signature, Timing, ContactDetail, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Availability, ExtendedContactDetail, Dosage, Meta | Content to use in performing the task | |||||||||||
| output | 0..* | BackboneElement | Information produced as part of task | 0..* | BackboneElement | Information produced as part of task | |||||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| type | 1..1 | CodeableConcept | Label for output Binding Description: (example): 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. | 1..1 | CodeableConcept | Label for output Binding: ?? (example): 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. | |||||||||||
| value[x] | 1..1 | base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, Reference(), SampledData, Signature, Timing, ContactDetail, Contributor, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Dosage, Meta | Result of output | 1..1 | base64Binary, boolean, canonical(), code, date, dateTime, decimal, id, instant, integer, integer64, markdown, oid, positiveInt, string, time, unsignedInt, uri, url, uuid, Address, Age, Annotation, Attachment, CodeableConcept, CodeableReference(), Coding, ContactPoint, Count, Distance, Duration, HumanName, Identifier, Money, Period, Quantity, Range, Ratio, RatioRange, Reference(), SampledData, Signature, Timing, ContactDetail, DataRequirement, Expression, ParameterDefinition, RelatedArtifact, TriggerDefinition, UsageContext, Availability, ExtendedContactDetail, Dosage, Meta | Result of output | |||||||||||
| doNotPerform | ?!Σ | 0..1 | boolean | True if Task is prohibiting action |
| ||||||||||||
| requestedPeriod | Σ | 0..1 | Period | When the task should be performed |
| ||||||||||||
| requestedPerformer | 0..* | CodeableReference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | Who should perform the Task Binding: ?? (preferred): The type(s) of task performers allowed. |
| |||||||||||||
| performer | Σ | 0..* | BackboneElement | Who or what performed the task |
| ||||||||||||
| reason | 0..* | CodeableReference(Therapeutic Implication) | Why task is needed Binding: ?? (example): Indicates why the task is needed. E.g. Suspended because patient admitted to hospital. |
| |||||||||||||
| Documentation for this format | |||||||||||||||||