ReteLabTaskStatoRichiesta
Descrizione
Il profilo ReteLabTaskStatoRichiesta è stato strutturato a partire dalla risorsa generica FHIR Task utilizzata per tenere traccia dello stato di avanzamento delle richieste di prestazioni.
Di seguito è presentato il contenuto del profilo in diversi formati. La corrispondente definizione è consultabile al seguente link: ReteLabTaskStatoRichiesta.
Snapshot View
| ReteLabTaskStatoRichiesta (Task) | C | Task | Element idTaskShort description Stato di avanzamento delle prestazioni DefinitionRisorsa per tenere traccia dello stato di avanzamento delle prestazioni. Questo profilo può può essere presente nei seguenti flussi: "Risposta accettazione richiesta e istruzioni per etichette da LS a OMr", "Inoltro Risposta accettazione richiesta da OMr a LR", "Check-in da LR a LS", "Check-out da LR a LS", "Check-in da LS a LR", "Risposta accettazione messaggio di cancellazione/modifica da LS a LR", "Risposta alla notifica di eseguito da LR a LS", "Risposta alla notifica di completato da LR a LS", "Risposta Notifica risultati disponibili da LR a LS", "Risposta Notifica refertato da LR a LS"
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idTask.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idTask.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idTask.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idTask.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idTask.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idTask.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.extensionShort description 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| identifier | 0..* | Identifier | There are no (further) constraints on this element Element idTask.identifierShort description Task Instance Identifier DefinitionThe business identifier for this task. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | There are no (further) constraints on this element Element idTask.instantiatesCanonicalShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| instantiatesUri | Σ | 0..1 | uri | There are no (further) constraints on this element Element idTask.instantiatesUriShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| basedOn | Σ C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idTask.basedOnShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idTask.groupIdentifierShort description Requisition or grouper id DefinitionAn identifier that links together multiple tasks and other requests that were created in the same context. Billing and/or reporting can be linked to whether multiple requests were created as a single unit. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| partOf | Σ C | 0..* | Reference(Task) | There are no (further) constraints on this element Element idTask.partOfShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| status | Σ ?! | 1..1 | codeBinding | Element idTask.statusShort description Stato della prestazione DefinitionPuò assumere i seguenti valori:
These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks. Corrispondente campo HL7 secondo specifiche regionali: ORC-5 The current status of the task. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| statusReason | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.statusReasonShort description Reason for current status DefinitionAn explanation as to why this task is held, failed, was refused, etc. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| businessStatus | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.businessStatusShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| intent | Σ | 1..1 | codeBinding | Element idTask.intentShort description Intento del task DefinitionDue casistiche:
L'intent del Task deve essere concorde all'intent della ServiceRequest che referenzia. Distinguishes whether the task is a proposal, plan or full order. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| priority | 0..1 | codeBinding | There are no (further) constraints on this element Element idTask.priorityShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.codeShort description Task Type DefinitionA name or code (or both) briefly describing what the task involves. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| description | Σ | 0..1 | string | There are no (further) constraints on this element Element idTask.descriptionShort 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| focus | Σ C | 1..1 | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element idTask.focusShort description Richiesta di cui si sta notificando il cambio stato DefinitionReference al profilo ReteLabServiceRequestRichiestaEsamiLab Used to identify the thing to be done. If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.). Reference(ReteLabServiceRequestRichiestaEsamiLab) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| for | Σ C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idTask.forShort description Beneficiary of the Task Alternate namesPatient DefinitionThe entity who benefits from the performance of the service specified in the task (e.g., the patient). 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| encounter | Σ C | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idTask.encounterShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| executionPeriod | Σ C | 0..1 | Period | There are no (further) constraints on this element Element idTask.executionPeriodShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| authoredOn | C | 0..1 | dateTime | There are no (further) constraints on this element Element idTask.authoredOnShort description Task Creation Date Alternate namesCreated Date DefinitionThe date and time this task was created. Most often used along with lastUpdated to track duration of task to supporting monitoring and management. The cardinality or value of this element may be affected by these constraints: ele-1, inv-1 Constraints
| ||
| lastModified | Σ C | 0..1 | dateTime | There are no (further) constraints on this element Element idTask.lastModifiedShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1, inv-1 Constraints
| ||
| requester | Σ C | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.requesterShort description Who is asking for task to be done DefinitionThe creator of the task. 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(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| performerType | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idTask.performerTypeShort description 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) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| owner | Σ C | 0..1 | Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.ownerShort description Responsible individual Alternate namesPerformer, Executer DefinitionIndividual organization or Device currently responsible for task execution. Identifies who is expected to perform this task. Tasks may be created with an owner not yet identified. Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| location | Σ C | 0..1 | Reference(Location) | There are no (further) constraints on this element Element idTask.locationShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| reasonCode | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.reasonCodeShort description Why task is needed DefinitionA description or code indicating why this task needs to be performed. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| reasonReference | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idTask.reasonReferenceShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| insurance | C | 0..* | Reference(ClaimResponse | Coverage) | There are no (further) constraints on this element Element idTask.insuranceShort description 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(ClaimResponse | Coverage) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| note | 0..* | Annotation | Element idTask.noteShort description Commenti sul task DefinitionQuesto campo viene utilizzato per fornire ulteriori informazioni sullo stato della prestazione. Ad esempio, quando la task viene utilizzata per notificare il rifiuto di una modifica. Corrisponde al campo HL7 NTE 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| relevantHistory | C | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element idTask.relevantHistoryShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| restriction | 0..1 | BackboneElement | There are no (further) constraints on this element Element idTask.restrictionShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.restriction.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.restriction.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.restriction.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| repetitions | 0..1 | positiveInt | There are no (further) constraints on this element Element idTask.restriction.repetitionsShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| period | C | 0..1 | Period | There are no (further) constraints on this element Element idTask.restriction.periodShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| recipient | C | 0..* | Reference(Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.restriction.recipientShort description 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(Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| input | 0..* | BackboneElement | There are no (further) constraints on this element Element idTask.inputShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.input.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.input.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.input.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.input.typeShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idTask.input.value[x]Short description Content to use in performing the task DefinitionThe value of the input parameter as a basic type. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| 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 | ||||
| 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 | ||||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
| valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
| valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
| valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
| valueCount | Count | There are no (further) constraints on this element Data type | ||||
| valueDataRequirement | DataRequirement | 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 | ||||
| valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
| valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
| valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
| valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
| valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
| valueId | id | There are no (further) constraints on this element Data type | ||||
| valueIdentifier | Identifier | 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 | ||||
| valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
| valueMoney | Money | There are no (further) constraints on this element Data type | ||||
| valueOid | oid | There are no (further) constraints on this element Data type | ||||
| valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
| valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
| valuePositiveInt | positiveInt | 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 | ||||
| valueReference | Reference | There are no (further) constraints on this element Data type | ||||
| valueRelatedArtifact | RelatedArtifact | 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 | ||||
| valueString | string | There are no (further) constraints on this element Data type | ||||
| valueTime | time | There are no (further) constraints on this element Data type | ||||
| valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
| valueTriggerDefinition | TriggerDefinition | 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 | ||||
| valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
| valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
| output | 0..* | BackboneElement | There are no (further) constraints on this element Element idTask.outputShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.output.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.output.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.output.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.output.typeShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idTask.output.value[x]Short description Result of output DefinitionThe value of the Output parameter as a basic type. Task outputs can take any form. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| 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 | ||||
| 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 | ||||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
| valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
| valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
| valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
| valueCount | Count | There are no (further) constraints on this element Data type | ||||
| valueDataRequirement | DataRequirement | 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 | ||||
| valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
| valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
| valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
| valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
| valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
| valueId | id | There are no (further) constraints on this element Data type | ||||
| valueIdentifier | Identifier | 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 | ||||
| valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
| valueMoney | Money | There are no (further) constraints on this element Data type | ||||
| valueOid | oid | There are no (further) constraints on this element Data type | ||||
| valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
| valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
| valuePositiveInt | positiveInt | 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 | ||||
| valueReference | Reference | There are no (further) constraints on this element Data type | ||||
| valueRelatedArtifact | RelatedArtifact | 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 | ||||
| valueString | string | There are no (further) constraints on this element Data type | ||||
| valueTime | time | There are no (further) constraints on this element Data type | ||||
| valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
| valueTriggerDefinition | TriggerDefinition | 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 | ||||
| valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
| valueUuid | uuid | There are no (further) constraints on this element Data type |
Differential View
| ReteLabTaskStatoRichiesta (Task) | C | Task | Element idTaskShort description Stato di avanzamento delle prestazioni DefinitionRisorsa per tenere traccia dello stato di avanzamento delle prestazioni. Questo profilo può può essere presente nei seguenti flussi: "Risposta accettazione richiesta e istruzioni per etichette da LS a OMr", "Inoltro Risposta accettazione richiesta da OMr a LR", "Check-in da LR a LS", "Check-out da LR a LS", "Check-in da LS a LR", "Risposta accettazione messaggio di cancellazione/modifica da LS a LR", "Risposta alla notifica di eseguito da LR a LS", "Risposta alla notifica di completato da LR a LS", "Risposta Notifica risultati disponibili da LR a LS", "Risposta Notifica refertato da LR a LS"
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idTask.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idTask.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idTask.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idTask.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idTask.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idTask.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.extensionShort description 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| identifier | 0..* | Identifier | There are no (further) constraints on this element Element idTask.identifierShort description Task Instance Identifier DefinitionThe business identifier for this task. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | There are no (further) constraints on this element Element idTask.instantiatesCanonicalShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| instantiatesUri | Σ | 0..1 | uri | There are no (further) constraints on this element Element idTask.instantiatesUriShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| basedOn | Σ C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idTask.basedOnShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idTask.groupIdentifierShort description Requisition or grouper id DefinitionAn identifier that links together multiple tasks and other requests that were created in the same context. Billing and/or reporting can be linked to whether multiple requests were created as a single unit. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| partOf | Σ C | 0..* | Reference(Task) | There are no (further) constraints on this element Element idTask.partOfShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| status | Σ ?! | 1..1 | codeBinding | Element idTask.statusShort description Stato della prestazione DefinitionPuò assumere i seguenti valori:
These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks. Corrispondente campo HL7 secondo specifiche regionali: ORC-5 The current status of the task. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| statusReason | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.statusReasonShort description Reason for current status DefinitionAn explanation as to why this task is held, failed, was refused, etc. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| businessStatus | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.businessStatusShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| intent | Σ | 1..1 | codeBinding | Element idTask.intentShort description Intento del task DefinitionDue casistiche:
L'intent del Task deve essere concorde all'intent della ServiceRequest che referenzia. Distinguishes whether the task is a proposal, plan or full order. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| priority | 0..1 | codeBinding | There are no (further) constraints on this element Element idTask.priorityShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.codeShort description Task Type DefinitionA name or code (or both) briefly describing what the task involves. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| description | Σ | 0..1 | string | There are no (further) constraints on this element Element idTask.descriptionShort 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| focus | Σ C | 1..1 | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element idTask.focusShort description Richiesta di cui si sta notificando il cambio stato DefinitionReference al profilo ReteLabServiceRequestRichiestaEsamiLab Used to identify the thing to be done. If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.). Reference(ReteLabServiceRequestRichiestaEsamiLab) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| for | Σ C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idTask.forShort description Beneficiary of the Task Alternate namesPatient DefinitionThe entity who benefits from the performance of the service specified in the task (e.g., the patient). 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| encounter | Σ C | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idTask.encounterShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| executionPeriod | Σ C | 0..1 | Period | There are no (further) constraints on this element Element idTask.executionPeriodShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| authoredOn | C | 0..1 | dateTime | There are no (further) constraints on this element Element idTask.authoredOnShort description Task Creation Date Alternate namesCreated Date DefinitionThe date and time this task was created. Most often used along with lastUpdated to track duration of task to supporting monitoring and management. The cardinality or value of this element may be affected by these constraints: ele-1, inv-1 Constraints
| ||
| lastModified | Σ C | 0..1 | dateTime | There are no (further) constraints on this element Element idTask.lastModifiedShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1, inv-1 Constraints
| ||
| requester | Σ C | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.requesterShort description Who is asking for task to be done DefinitionThe creator of the task. 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(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| performerType | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idTask.performerTypeShort description 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) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| owner | Σ C | 0..1 | Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.ownerShort description Responsible individual Alternate namesPerformer, Executer DefinitionIndividual organization or Device currently responsible for task execution. Identifies who is expected to perform this task. Tasks may be created with an owner not yet identified. Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| location | Σ C | 0..1 | Reference(Location) | There are no (further) constraints on this element Element idTask.locationShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| reasonCode | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.reasonCodeShort description Why task is needed DefinitionA description or code indicating why this task needs to be performed. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| reasonReference | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idTask.reasonReferenceShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| insurance | C | 0..* | Reference(ClaimResponse | Coverage) | There are no (further) constraints on this element Element idTask.insuranceShort description 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(ClaimResponse | Coverage) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| note | 0..* | Annotation | Element idTask.noteShort description Commenti sul task DefinitionQuesto campo viene utilizzato per fornire ulteriori informazioni sullo stato della prestazione. Ad esempio, quando la task viene utilizzata per notificare il rifiuto di una modifica. Corrisponde al campo HL7 NTE 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| relevantHistory | C | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element idTask.relevantHistoryShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| restriction | 0..1 | BackboneElement | There are no (further) constraints on this element Element idTask.restrictionShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.restriction.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.restriction.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.restriction.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| repetitions | 0..1 | positiveInt | There are no (further) constraints on this element Element idTask.restriction.repetitionsShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| period | C | 0..1 | Period | There are no (further) constraints on this element Element idTask.restriction.periodShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| recipient | C | 0..* | Reference(Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.restriction.recipientShort description 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(Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| input | 0..* | BackboneElement | There are no (further) constraints on this element Element idTask.inputShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.input.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.input.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.input.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.input.typeShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idTask.input.value[x]Short description Content to use in performing the task DefinitionThe value of the input parameter as a basic type. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| 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 | ||||
| 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 | ||||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
| valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
| valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
| valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
| valueCount | Count | There are no (further) constraints on this element Data type | ||||
| valueDataRequirement | DataRequirement | 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 | ||||
| valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
| valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
| valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
| valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
| valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
| valueId | id | There are no (further) constraints on this element Data type | ||||
| valueIdentifier | Identifier | 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 | ||||
| valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
| valueMoney | Money | There are no (further) constraints on this element Data type | ||||
| valueOid | oid | There are no (further) constraints on this element Data type | ||||
| valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
| valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
| valuePositiveInt | positiveInt | 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 | ||||
| valueReference | Reference | There are no (further) constraints on this element Data type | ||||
| valueRelatedArtifact | RelatedArtifact | 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 | ||||
| valueString | string | There are no (further) constraints on this element Data type | ||||
| valueTime | time | There are no (further) constraints on this element Data type | ||||
| valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
| valueTriggerDefinition | TriggerDefinition | 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 | ||||
| valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
| valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
| output | 0..* | BackboneElement | There are no (further) constraints on this element Element idTask.outputShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.output.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.output.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.output.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.output.typeShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idTask.output.value[x]Short description Result of output DefinitionThe value of the Output parameter as a basic type. Task outputs can take any form. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| 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 | ||||
| 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 | ||||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
| valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
| valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
| valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
| valueCount | Count | There are no (further) constraints on this element Data type | ||||
| valueDataRequirement | DataRequirement | 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 | ||||
| valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
| valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
| valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
| valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
| valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
| valueId | id | There are no (further) constraints on this element Data type | ||||
| valueIdentifier | Identifier | 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 | ||||
| valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
| valueMoney | Money | There are no (further) constraints on this element Data type | ||||
| valueOid | oid | There are no (further) constraints on this element Data type | ||||
| valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
| valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
| valuePositiveInt | positiveInt | 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 | ||||
| valueReference | Reference | There are no (further) constraints on this element Data type | ||||
| valueRelatedArtifact | RelatedArtifact | 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 | ||||
| valueString | string | There are no (further) constraints on this element Data type | ||||
| valueTime | time | There are no (further) constraints on this element Data type | ||||
| valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
| valueTriggerDefinition | TriggerDefinition | 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 | ||||
| valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
| valueUuid | uuid | There are no (further) constraints on this element Data type |
Hybrid View
| ReteLabTaskStatoRichiesta (Task) | C | Task | Element idTaskShort description Stato di avanzamento delle prestazioni DefinitionRisorsa per tenere traccia dello stato di avanzamento delle prestazioni. Questo profilo può può essere presente nei seguenti flussi: "Risposta accettazione richiesta e istruzioni per etichette da LS a OMr", "Inoltro Risposta accettazione richiesta da OMr a LR", "Check-in da LR a LS", "Check-out da LR a LS", "Check-in da LS a LR", "Risposta accettazione messaggio di cancellazione/modifica da LS a LR", "Risposta alla notifica di eseguito da LR a LS", "Risposta alla notifica di completato da LR a LS", "Risposta Notifica risultati disponibili da LR a LS", "Risposta Notifica refertato da LR a LS"
| |||
| id | Σ | 0..1 | string | There are no (further) constraints on this element Element idTask.idShort description Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. The only time that a resource does not have an id is when it is being submitted to the server using a create operation. | ||
| meta | Σ | 0..1 | Meta | There are no (further) constraints on this element Element idTask.metaShort description Metadata about the resource DefinitionThe metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idTask.implicitRulesShort description A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idTask.languageShort description Language of the resource content DefinitionThe base language in which the resource is written. Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). A human language.
The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| text | 0..1 | Narrative | There are no (further) constraints on this element Element idTask.textShort description Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| contained | 0..* | Resource | There are no (further) constraints on this element Element idTask.containedShort description Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese 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. 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.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.extensionShort description 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.modifierExtensionShort description Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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). 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| identifier | 0..* | Identifier | There are no (further) constraints on this element Element idTask.identifierShort description Task Instance Identifier DefinitionThe business identifier for this task. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | There are no (further) constraints on this element Element idTask.instantiatesCanonicalShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| instantiatesUri | Σ | 0..1 | uri | There are no (further) constraints on this element Element idTask.instantiatesUriShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| basedOn | Σ C | 0..* | Reference(Resource) | There are no (further) constraints on this element Element idTask.basedOnShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element idTask.groupIdentifierShort description Requisition or grouper id DefinitionAn identifier that links together multiple tasks and other requests that were created in the same context. Billing and/or reporting can be linked to whether multiple requests were created as a single unit. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| partOf | Σ C | 0..* | Reference(Task) | There are no (further) constraints on this element Element idTask.partOfShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| status | Σ ?! | 1..1 | codeBinding | Element idTask.statusShort description Stato della prestazione DefinitionPuò assumere i seguenti valori:
These states enable coordination of task status with off-the-shelf workflow solutions that support automation of tasks. Corrispondente campo HL7 secondo specifiche regionali: ORC-5 The current status of the task. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| statusReason | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.statusReasonShort description Reason for current status DefinitionAn explanation as to why this task is held, failed, was refused, etc. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| businessStatus | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.businessStatusShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| intent | Σ | 1..1 | codeBinding | Element idTask.intentShort description Intento del task DefinitionDue casistiche:
L'intent del Task deve essere concorde all'intent della ServiceRequest che referenzia. Distinguishes whether the task is a proposal, plan or full order. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| priority | 0..1 | codeBinding | There are no (further) constraints on this element Element idTask.priorityShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.codeShort description Task Type DefinitionA name or code (or both) briefly describing what the task involves. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| description | Σ | 0..1 | string | There are no (further) constraints on this element Element idTask.descriptionShort 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| focus | Σ C | 1..1 | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element idTask.focusShort description Richiesta di cui si sta notificando il cambio stato DefinitionReference al profilo ReteLabServiceRequestRichiestaEsamiLab Used to identify the thing to be done. If multiple resources need to be manipulated, use sub-tasks. (This ensures that status can be tracked independently for each referenced resource.). Reference(ReteLabServiceRequestRichiestaEsamiLab) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| for | Σ C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idTask.forShort description Beneficiary of the Task Alternate namesPatient DefinitionThe entity who benefits from the performance of the service specified in the task (e.g., the patient). 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| encounter | Σ C | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idTask.encounterShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| executionPeriod | Σ C | 0..1 | Period | There are no (further) constraints on this element Element idTask.executionPeriodShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| authoredOn | C | 0..1 | dateTime | There are no (further) constraints on this element Element idTask.authoredOnShort description Task Creation Date Alternate namesCreated Date DefinitionThe date and time this task was created. Most often used along with lastUpdated to track duration of task to supporting monitoring and management. The cardinality or value of this element may be affected by these constraints: ele-1, inv-1 Constraints
| ||
| lastModified | Σ C | 0..1 | dateTime | There are no (further) constraints on this element Element idTask.lastModifiedShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1, inv-1 Constraints
| ||
| requester | Σ C | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.requesterShort description Who is asking for task to be done DefinitionThe creator of the task. 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(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| performerType | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element idTask.performerTypeShort description 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) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| owner | Σ C | 0..1 | Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.ownerShort description Responsible individual Alternate namesPerformer, Executer DefinitionIndividual organization or Device currently responsible for task execution. Identifies who is expected to perform this task. Tasks may be created with an owner not yet identified. Reference(CareTeam | Device | HealthcareService | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| location | Σ C | 0..1 | Reference(Location) | There are no (further) constraints on this element Element idTask.locationShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| reasonCode | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.reasonCodeShort description Why task is needed DefinitionA description or code indicating why this task needs to be performed. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| reasonReference | C | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element idTask.reasonReferenceShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| insurance | C | 0..* | Reference(ClaimResponse | Coverage) | There are no (further) constraints on this element Element idTask.insuranceShort description 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(ClaimResponse | Coverage) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| note | 0..* | Annotation | Element idTask.noteShort description Commenti sul task DefinitionQuesto campo viene utilizzato per fornire ulteriori informazioni sullo stato della prestazione. Ad esempio, quando la task viene utilizzata per notificare il rifiuto di una modifica. Corrisponde al campo HL7 NTE 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). The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| relevantHistory | C | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element idTask.relevantHistoryShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| restriction | 0..1 | BackboneElement | There are no (further) constraints on this element Element idTask.restrictionShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.restriction.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.restriction.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.restriction.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| repetitions | 0..1 | positiveInt | There are no (further) constraints on this element Element idTask.restriction.repetitionsShort description 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 The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| period | C | 0..1 | Period | There are no (further) constraints on this element Element idTask.restriction.periodShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| recipient | C | 0..* | Reference(Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element idTask.restriction.recipientShort description 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(Group | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| input | 0..* | BackboneElement | There are no (further) constraints on this element Element idTask.inputShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.input.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.input.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.input.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.input.typeShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idTask.input.value[x]Short description Content to use in performing the task DefinitionThe value of the input parameter as a basic type. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| 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 | ||||
| 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 | ||||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
| valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
| valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
| valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
| valueCount | Count | There are no (further) constraints on this element Data type | ||||
| valueDataRequirement | DataRequirement | 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 | ||||
| valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
| valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
| valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
| valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
| valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
| valueId | id | There are no (further) constraints on this element Data type | ||||
| valueIdentifier | Identifier | 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 | ||||
| valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
| valueMoney | Money | There are no (further) constraints on this element Data type | ||||
| valueOid | oid | There are no (further) constraints on this element Data type | ||||
| valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
| valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
| valuePositiveInt | positiveInt | 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 | ||||
| valueReference | Reference | There are no (further) constraints on this element Data type | ||||
| valueRelatedArtifact | RelatedArtifact | 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 | ||||
| valueString | string | There are no (further) constraints on this element Data type | ||||
| valueTime | time | There are no (further) constraints on this element Data type | ||||
| valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
| valueTriggerDefinition | TriggerDefinition | 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 | ||||
| valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
| valueUuid | uuid | There are no (further) constraints on this element Data type | ||||
| output | 0..* | BackboneElement | There are no (further) constraints on this element Element idTask.outputShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| id | 0..1 | string | There are no (further) constraints on this element Element idTask.output.idShort description Unique id for inter-element referencing DefinitionUnique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |||
| extension | C | 0..* | Extension | There are no (further) constraints on this element Element idTask.output.extensionShort description 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 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. 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) Extensions are always sliced by (at least) url ConditionsThe cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| modifierExtension | Σ ?! C | 0..* | Extension | There are no (further) constraints on this element Element idTask.output.modifierExtensionShort description Extensions that cannot be ignored even if unrecognized Alternate namesextensions, user content, modifiers DefinitionMay 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). 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. 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||
| type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idTask.output.typeShort description 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. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| |||
| value[x] | 1..1 | There are no (further) constraints on this element Element idTask.output.value[x]Short description Result of output DefinitionThe value of the Output parameter as a basic type. Task outputs can take any form. The cardinality or value of this element may be affected by these constraints: ele-1 Constraints
| ||||
| 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 | ||||
| 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 | ||||
| valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data type | ||||
| valueCoding | Coding | There are no (further) constraints on this element Data type | ||||
| valueContactDetail | ContactDetail | There are no (further) constraints on this element Data type | ||||
| valueContactPoint | ContactPoint | There are no (further) constraints on this element Data type | ||||
| valueContributor | Contributor | There are no (further) constraints on this element Data type | ||||
| valueCount | Count | There are no (further) constraints on this element Data type | ||||
| valueDataRequirement | DataRequirement | 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 | ||||
| valueDistance | Distance | There are no (further) constraints on this element Data type | ||||
| valueDosage | Dosage | There are no (further) constraints on this element Data type | ||||
| valueDuration | Duration | There are no (further) constraints on this element Data type | ||||
| valueExpression | Expression | There are no (further) constraints on this element Data type | ||||
| valueHumanName | HumanName | There are no (further) constraints on this element Data type | ||||
| valueId | id | There are no (further) constraints on this element Data type | ||||
| valueIdentifier | Identifier | 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 | ||||
| valueMeta | Meta | There are no (further) constraints on this element Data type | ||||
| valueMoney | Money | There are no (further) constraints on this element Data type | ||||
| valueOid | oid | There are no (further) constraints on this element Data type | ||||
| valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data type | ||||
| valuePeriod | Period | There are no (further) constraints on this element Data type | ||||
| valuePositiveInt | positiveInt | 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 | ||||
| valueReference | Reference | There are no (further) constraints on this element Data type | ||||
| valueRelatedArtifact | RelatedArtifact | 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 | ||||
| valueString | string | There are no (further) constraints on this element Data type | ||||
| valueTime | time | There are no (further) constraints on this element Data type | ||||
| valueTiming | Timing | There are no (further) constraints on this element Data type | ||||
| valueTriggerDefinition | TriggerDefinition | 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 | ||||
| valueUsageContext | UsageContext | There are no (further) constraints on this element Data type | ||||
| valueUuid | uuid | There are no (further) constraints on this element Data type |
Table View
| Task | .. | |
| Task.status | .. | |
| Task.intent | .. | |
| Task.focus | Reference(ReteLabServiceRequestRichiestaEsamiLab) | 1.. |
| Task.note | .. |
XML View
JSON View
Esempi
ValueSet
Attualmente non sono definiti value set specifici per il profilo ReteLabTaskStatoRichiesta.