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
Task | I | Task | Element IdTask 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"
| |
identifier | 0..* | Identifier | There are no (further) constraints on this element Element IdTask.identifier Task Instance Identifier DefinitionThe business identifier for this task.
| |
instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | There are no (further) constraints on this element Element IdTask.instantiatesCanonical Formal definition of task DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed, enabling automation.
|
instantiatesUri | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.instantiatesUri Formal definition of task DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
basedOn | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdTask.basedOn Request fulfilled by this task DefinitionBasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ServiceRequest, MedicationRequest, ServiceRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill. This latter resource is referenced by FocusOn. For example, based on a ServiceRequest (= BasedOn), a task is created to fulfill a procedureRequest ( = FocusOn ) to collect a specimen from a patient. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.groupIdentifier 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.
|
partOf | Σ I | 0..* | Reference(Task) | There are no (further) constraints on this element Element IdTask.partOf Composite task DefinitionTask that this particular task is part of. Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task). This should usually be 0..1.
|
status | Σ ?! | 1..1 | codeBinding | Element IdTask.status 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. TaskStatus (required)Constraints
|
statusReason | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.statusReason 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. (unbound) (example)Constraints
|
businessStatus | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.businessStatus E.g. "Specimen collected", "IV prepped" DefinitionContains business-specific nuances of the business state. There's often a need to track substates of a task - this is often variable by specific workflow implementation. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. (unbound) (example)Constraints
|
intent | Σ | 1..1 | codeBinding | Element IdTask.intent 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. TaskIntent (required)Constraints
|
priority | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.priority routine | urgent | asap | stat DefinitionIndicates how quickly the Task should be addressed with respect to other requests. Used to identify the service level expected while performing a task. Note that FHIR strings SHALL NOT exceed 1MB in size If missing, this task should be performed with normal priority The task's priority. RequestPriority (required)Constraints
| |
code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.code 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. TaskCode (example)Constraints
|
description | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.description Human-readable explanation of task DefinitionA free-text description of what is to be performed. Note that FHIR strings SHALL NOT exceed 1MB in size
|
focus | Σ I | 1..1 | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element IdTask.focus 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) Constraints
|
for | Σ I | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element IdTask.for 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.
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element IdTask.encounter Healthcare event during which this task originated DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created. For some tasks it may be important to know the link between the encounter the task originated within. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
executionPeriod | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.executionPeriod Start and end time of execution DefinitionIdentifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end). A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
authoredOn | I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.authoredOn 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.
|
lastModified | Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.lastModified Task Last Modified Date Alternate namesUpdate Date DefinitionThe date and time of last modification to this task. Used along with history to track task activity and time in a particular task state. This enables monitoring and management.
|
requester | Σ I | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element IdTask.requester 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) Constraints
|
performerType | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.performerType Requested performer DefinitionThe kind of participant that should perform the task. Use to distinguish tasks on different activity queues. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The type(s) of task performers allowed. ProcedurePerformerRoleCodes (preferred)Constraints
| |
owner | Σ I | 0..1 | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | There are no (further) constraints on this element Element IdTask.owner 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(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Constraints
|
location | Σ I | 0..1 | Reference(Location) | There are no (further) constraints on this element Element IdTask.location Where task occurs DefinitionPrincipal physical location where the this task is performed. Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
reasonCode | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.reasonCode 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. (unbound) (example)Constraints
| |
reasonReference | I | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element IdTask.reasonReference Why task is needed DefinitionA resource reference indicating why this task needs to be performed. Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in
|
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element IdTask.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Coverage | ClaimResponse) Constraints
|
note | 0..* | Annotation | Element IdTask.note 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 For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
relevantHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element IdTask.relevantHistory Key events in history of the Task Alternate namesStatus History DefinitionLinks to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task. This element does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.
|
restriction | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdTask.restriction Constraints on fulfillment tasks DefinitionIf the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned. Sometimes when fulfillment is sought, you don't want full fulfillment.
| |
repetitions | 0..1 | positiveInt | There are no (further) constraints on this element Element IdTask.restriction.repetitions How many times to repeat DefinitionIndicates the number of times the requested action should occur. E.g. order that requests monthly lab tests, fulfillment is sought for 1. 32 bit number; for values larger than this, use decimal
| |
period | I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.restriction.period When fulfillment sought DefinitionOver what time-period is fulfillment sought. E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months. Note that period.high is the due date representing the time by which the task should be completed.
|
recipient | I | 0..* | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) | There are no (further) constraints on this element Element IdTask.restriction.recipient For whom is fulfillment sought? DefinitionFor requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought? References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) Constraints
|
input | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.input Information used to perform task Alternate namesSupporting Information DefinitionAdditional information that may be needed in the execution of the task. Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.
| |
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.input.type Label for the input Alternate namesName DefinitionA code or description indicating how the input is intended to be used as part of the task execution. Inputs are named to enable task automation to bind data and pass it from one task to the next. If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. (unbound) (example)Constraints
| |
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.input.value[x] Content to use in performing the task DefinitionThe value of the input parameter as a basic type.
| ||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | ||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | ||
valueCode | code | There are no (further) constraints on this element Data Type | ||
valueDate | date | There are no (further) constraints on this element Data Type | ||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | ||
valueId | id | There are no (further) constraints on this element Data Type | ||
valueInstant | instant | There are no (further) constraints on this element Data Type | ||
valueInteger | integer | There are no (further) constraints on this element Data Type | ||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | ||
valueOid | oid | There are no (further) constraints on this element Data Type | ||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | ||
valueString | string | There are no (further) constraints on this element Data Type | ||
valueTime | time | There are no (further) constraints on this element Data Type | ||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | ||
valueUri | uri | There are no (further) constraints on this element Data Type | ||
valueUrl | url | There are no (further) constraints on this element Data Type | ||
valueUuid | uuid | There are no (further) constraints on this element Data Type | ||
valueAddress | Address | There are no (further) constraints on this element Data Type | ||
valueAge | Age | There are no (further) constraints on this element Data Type | ||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | ||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
valueCoding | Coding | There are no (further) constraints on this element Data Type | ||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | ||
valueCount | Count | There are no (further) constraints on this element Data Type | ||
valueDistance | Distance | There are no (further) constraints on this element Data Type | ||
valueDuration | Duration | There are no (further) constraints on this element Data Type | ||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | ||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | ||
valueMoney | Money | There are no (further) constraints on this element Data Type | ||
valuePeriod | Period | There are no (further) constraints on this element Data Type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | ||
valueRange | Range | There are no (further) constraints on this element Data Type | ||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | ||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | ||
valueSignature | Signature | There are no (further) constraints on this element Data Type | ||
valueTiming | Timing | There are no (further) constraints on this element Data Type | ||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | ||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | ||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | ||
valueExpression | Expression | There are no (further) constraints on this element Data Type | ||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | ||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | ||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | ||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | ||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | ||
valueMeta | Meta | There are no (further) constraints on this element Data Type | ||
valueReference | Reference() | There are no (further) constraints on this element Data Type | ||
output | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.output Information produced as part of task DefinitionOutputs produced by the Task. Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.
| |
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.output.type Label for output Alternate namesName DefinitionThe name of the Output parameter. Outputs are named to enable task automation to bind data and pass it from one task to the next. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. (unbound) (example)Constraints
| |
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.output.value[x] Result of output DefinitionThe value of the Output parameter as a basic type. Task outputs can take any form.
| ||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | ||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | ||
valueCode | code | There are no (further) constraints on this element Data Type | ||
valueDate | date | There are no (further) constraints on this element Data Type | ||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | ||
valueId | id | There are no (further) constraints on this element Data Type | ||
valueInstant | instant | There are no (further) constraints on this element Data Type | ||
valueInteger | integer | There are no (further) constraints on this element Data Type | ||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | ||
valueOid | oid | There are no (further) constraints on this element Data Type | ||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | ||
valueString | string | There are no (further) constraints on this element Data Type | ||
valueTime | time | There are no (further) constraints on this element Data Type | ||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | ||
valueUri | uri | There are no (further) constraints on this element Data Type | ||
valueUrl | url | There are no (further) constraints on this element Data Type | ||
valueUuid | uuid | There are no (further) constraints on this element Data Type | ||
valueAddress | Address | There are no (further) constraints on this element Data Type | ||
valueAge | Age | There are no (further) constraints on this element Data Type | ||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | ||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
valueCoding | Coding | There are no (further) constraints on this element Data Type | ||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | ||
valueCount | Count | There are no (further) constraints on this element Data Type | ||
valueDistance | Distance | There are no (further) constraints on this element Data Type | ||
valueDuration | Duration | There are no (further) constraints on this element Data Type | ||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | ||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | ||
valueMoney | Money | There are no (further) constraints on this element Data Type | ||
valuePeriod | Period | There are no (further) constraints on this element Data Type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | ||
valueRange | Range | There are no (further) constraints on this element Data Type | ||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | ||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | ||
valueSignature | Signature | There are no (further) constraints on this element Data Type | ||
valueTiming | Timing | There are no (further) constraints on this element Data Type | ||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | ||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | ||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | ||
valueExpression | Expression | There are no (further) constraints on this element Data Type | ||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | ||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | ||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | ||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | ||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | ||
valueMeta | Meta | There are no (further) constraints on this element Data Type | ||
valueReference | Reference() | There are no (further) constraints on this element Data Type |
Differential View
Task | I | Task | Element IdTask 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"
| |
identifier | 0..* | Identifier | There are no (further) constraints on this element Element IdTask.identifier Task Instance Identifier DefinitionThe business identifier for this task.
| |
instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | There are no (further) constraints on this element Element IdTask.instantiatesCanonical Formal definition of task DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed, enabling automation.
|
instantiatesUri | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.instantiatesUri Formal definition of task DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
basedOn | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdTask.basedOn Request fulfilled by this task DefinitionBasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ServiceRequest, MedicationRequest, ServiceRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill. This latter resource is referenced by FocusOn. For example, based on a ServiceRequest (= BasedOn), a task is created to fulfill a procedureRequest ( = FocusOn ) to collect a specimen from a patient. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.groupIdentifier 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.
|
partOf | Σ I | 0..* | Reference(Task) | There are no (further) constraints on this element Element IdTask.partOf Composite task DefinitionTask that this particular task is part of. Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task). This should usually be 0..1.
|
status | Σ ?! | 1..1 | codeBinding | Element IdTask.status 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. TaskStatus (required)Constraints
|
statusReason | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.statusReason 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. (unbound) (example)Constraints
|
businessStatus | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.businessStatus E.g. "Specimen collected", "IV prepped" DefinitionContains business-specific nuances of the business state. There's often a need to track substates of a task - this is often variable by specific workflow implementation. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. (unbound) (example)Constraints
|
intent | Σ | 1..1 | codeBinding | Element IdTask.intent 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. TaskIntent (required)Constraints
|
priority | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.priority routine | urgent | asap | stat DefinitionIndicates how quickly the Task should be addressed with respect to other requests. Used to identify the service level expected while performing a task. Note that FHIR strings SHALL NOT exceed 1MB in size If missing, this task should be performed with normal priority The task's priority. RequestPriority (required)Constraints
| |
code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.code 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. TaskCode (example)Constraints
|
description | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.description Human-readable explanation of task DefinitionA free-text description of what is to be performed. Note that FHIR strings SHALL NOT exceed 1MB in size
|
focus | Σ I | 1..1 | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element IdTask.focus 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) Constraints
|
for | Σ I | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element IdTask.for 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.
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element IdTask.encounter Healthcare event during which this task originated DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created. For some tasks it may be important to know the link between the encounter the task originated within. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
executionPeriod | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.executionPeriod Start and end time of execution DefinitionIdentifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end). A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
authoredOn | I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.authoredOn 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.
|
lastModified | Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.lastModified Task Last Modified Date Alternate namesUpdate Date DefinitionThe date and time of last modification to this task. Used along with history to track task activity and time in a particular task state. This enables monitoring and management.
|
requester | Σ I | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element IdTask.requester 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) Constraints
|
performerType | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.performerType Requested performer DefinitionThe kind of participant that should perform the task. Use to distinguish tasks on different activity queues. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The type(s) of task performers allowed. ProcedurePerformerRoleCodes (preferred)Constraints
| |
owner | Σ I | 0..1 | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | There are no (further) constraints on this element Element IdTask.owner 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(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Constraints
|
location | Σ I | 0..1 | Reference(Location) | There are no (further) constraints on this element Element IdTask.location Where task occurs DefinitionPrincipal physical location where the this task is performed. Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
reasonCode | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.reasonCode 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. (unbound) (example)Constraints
| |
reasonReference | I | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element IdTask.reasonReference Why task is needed DefinitionA resource reference indicating why this task needs to be performed. Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in
|
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element IdTask.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Coverage | ClaimResponse) Constraints
|
note | 0..* | Annotation | Element IdTask.note 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 For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
relevantHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element IdTask.relevantHistory Key events in history of the Task Alternate namesStatus History DefinitionLinks to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task. This element does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.
|
restriction | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdTask.restriction Constraints on fulfillment tasks DefinitionIf the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned. Sometimes when fulfillment is sought, you don't want full fulfillment.
| |
repetitions | 0..1 | positiveInt | There are no (further) constraints on this element Element IdTask.restriction.repetitions How many times to repeat DefinitionIndicates the number of times the requested action should occur. E.g. order that requests monthly lab tests, fulfillment is sought for 1. 32 bit number; for values larger than this, use decimal
| |
period | I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.restriction.period When fulfillment sought DefinitionOver what time-period is fulfillment sought. E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months. Note that period.high is the due date representing the time by which the task should be completed.
|
recipient | I | 0..* | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) | There are no (further) constraints on this element Element IdTask.restriction.recipient For whom is fulfillment sought? DefinitionFor requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought? References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) Constraints
|
input | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.input Information used to perform task Alternate namesSupporting Information DefinitionAdditional information that may be needed in the execution of the task. Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.
| |
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.input.type Label for the input Alternate namesName DefinitionA code or description indicating how the input is intended to be used as part of the task execution. Inputs are named to enable task automation to bind data and pass it from one task to the next. If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. (unbound) (example)Constraints
| |
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.input.value[x] Content to use in performing the task DefinitionThe value of the input parameter as a basic type.
| ||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | ||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | ||
valueCode | code | There are no (further) constraints on this element Data Type | ||
valueDate | date | There are no (further) constraints on this element Data Type | ||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | ||
valueId | id | There are no (further) constraints on this element Data Type | ||
valueInstant | instant | There are no (further) constraints on this element Data Type | ||
valueInteger | integer | There are no (further) constraints on this element Data Type | ||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | ||
valueOid | oid | There are no (further) constraints on this element Data Type | ||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | ||
valueString | string | There are no (further) constraints on this element Data Type | ||
valueTime | time | There are no (further) constraints on this element Data Type | ||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | ||
valueUri | uri | There are no (further) constraints on this element Data Type | ||
valueUrl | url | There are no (further) constraints on this element Data Type | ||
valueUuid | uuid | There are no (further) constraints on this element Data Type | ||
valueAddress | Address | There are no (further) constraints on this element Data Type | ||
valueAge | Age | There are no (further) constraints on this element Data Type | ||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | ||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
valueCoding | Coding | There are no (further) constraints on this element Data Type | ||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | ||
valueCount | Count | There are no (further) constraints on this element Data Type | ||
valueDistance | Distance | There are no (further) constraints on this element Data Type | ||
valueDuration | Duration | There are no (further) constraints on this element Data Type | ||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | ||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | ||
valueMoney | Money | There are no (further) constraints on this element Data Type | ||
valuePeriod | Period | There are no (further) constraints on this element Data Type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | ||
valueRange | Range | There are no (further) constraints on this element Data Type | ||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | ||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | ||
valueSignature | Signature | There are no (further) constraints on this element Data Type | ||
valueTiming | Timing | There are no (further) constraints on this element Data Type | ||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | ||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | ||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | ||
valueExpression | Expression | There are no (further) constraints on this element Data Type | ||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | ||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | ||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | ||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | ||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | ||
valueMeta | Meta | There are no (further) constraints on this element Data Type | ||
valueReference | Reference() | There are no (further) constraints on this element Data Type | ||
output | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.output Information produced as part of task DefinitionOutputs produced by the Task. Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.
| |
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.output.type Label for output Alternate namesName DefinitionThe name of the Output parameter. Outputs are named to enable task automation to bind data and pass it from one task to the next. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. (unbound) (example)Constraints
| |
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.output.value[x] Result of output DefinitionThe value of the Output parameter as a basic type. Task outputs can take any form.
| ||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | ||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | ||
valueCode | code | There are no (further) constraints on this element Data Type | ||
valueDate | date | There are no (further) constraints on this element Data Type | ||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | ||
valueId | id | There are no (further) constraints on this element Data Type | ||
valueInstant | instant | There are no (further) constraints on this element Data Type | ||
valueInteger | integer | There are no (further) constraints on this element Data Type | ||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | ||
valueOid | oid | There are no (further) constraints on this element Data Type | ||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | ||
valueString | string | There are no (further) constraints on this element Data Type | ||
valueTime | time | There are no (further) constraints on this element Data Type | ||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | ||
valueUri | uri | There are no (further) constraints on this element Data Type | ||
valueUrl | url | There are no (further) constraints on this element Data Type | ||
valueUuid | uuid | There are no (further) constraints on this element Data Type | ||
valueAddress | Address | There are no (further) constraints on this element Data Type | ||
valueAge | Age | There are no (further) constraints on this element Data Type | ||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | ||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
valueCoding | Coding | There are no (further) constraints on this element Data Type | ||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | ||
valueCount | Count | There are no (further) constraints on this element Data Type | ||
valueDistance | Distance | There are no (further) constraints on this element Data Type | ||
valueDuration | Duration | There are no (further) constraints on this element Data Type | ||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | ||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | ||
valueMoney | Money | There are no (further) constraints on this element Data Type | ||
valuePeriod | Period | There are no (further) constraints on this element Data Type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | ||
valueRange | Range | There are no (further) constraints on this element Data Type | ||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | ||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | ||
valueSignature | Signature | There are no (further) constraints on this element Data Type | ||
valueTiming | Timing | There are no (further) constraints on this element Data Type | ||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | ||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | ||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | ||
valueExpression | Expression | There are no (further) constraints on this element Data Type | ||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | ||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | ||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | ||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | ||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | ||
valueMeta | Meta | There are no (further) constraints on this element Data Type | ||
valueReference | Reference() | There are no (further) constraints on this element Data Type |
Hybrid View
Task | I | Task | Element IdTask 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"
| |
identifier | 0..* | Identifier | There are no (further) constraints on this element Element IdTask.identifier Task Instance Identifier DefinitionThe business identifier for this task.
| |
instantiatesCanonical | Σ | 0..1 | canonical(ActivityDefinition) | There are no (further) constraints on this element Element IdTask.instantiatesCanonical Formal definition of task DefinitionThe URL pointing to a FHIR-defined protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed, enabling automation.
|
instantiatesUri | Σ | 0..1 | uri | There are no (further) constraints on this element Element IdTask.instantiatesUri Formal definition of task DefinitionThe URL pointing to an externally maintained protocol, guideline, orderset or other definition that is adhered to in whole or in part by this Task. Enables a formal definition of how he task is to be performed (e.g. using BPMN, BPEL, XPDL or other formal notation to be associated with a task), enabling automation. see http://en.wikipedia.org/wiki/Uniform_resource_identifier
|
basedOn | Σ I | 0..* | Reference(Resource) | There are no (further) constraints on this element Element IdTask.basedOn Request fulfilled by this task DefinitionBasedOn refers to a higher-level authorization that triggered the creation of the task. It references a "request" resource such as a ServiceRequest, MedicationRequest, ServiceRequest, CarePlan, etc. which is distinct from the "request" resource the task is seeking to fulfill. This latter resource is referenced by FocusOn. For example, based on a ServiceRequest (= BasedOn), a task is created to fulfill a procedureRequest ( = FocusOn ) to collect a specimen from a patient. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
groupIdentifier | Σ | 0..1 | Identifier | There are no (further) constraints on this element Element IdTask.groupIdentifier 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.
|
partOf | Σ I | 0..* | Reference(Task) | There are no (further) constraints on this element Element IdTask.partOf Composite task DefinitionTask that this particular task is part of. Allows tasks to be broken down into sub-steps (and this division can occur independent of the original task). This should usually be 0..1.
|
status | Σ ?! | 1..1 | codeBinding | Element IdTask.status 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. TaskStatus (required)Constraints
|
statusReason | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.statusReason 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. (unbound) (example)Constraints
|
businessStatus | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.businessStatus E.g. "Specimen collected", "IV prepped" DefinitionContains business-specific nuances of the business state. There's often a need to track substates of a task - this is often variable by specific workflow implementation. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The domain-specific business-contextual sub-state of the task. For example: "Blood drawn", "IV inserted", "Awaiting physician signature", etc. (unbound) (example)Constraints
|
intent | Σ | 1..1 | codeBinding | Element IdTask.intent 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. TaskIntent (required)Constraints
|
priority | 0..1 | codeBinding | There are no (further) constraints on this element Element IdTask.priority routine | urgent | asap | stat DefinitionIndicates how quickly the Task should be addressed with respect to other requests. Used to identify the service level expected while performing a task. Note that FHIR strings SHALL NOT exceed 1MB in size If missing, this task should be performed with normal priority The task's priority. RequestPriority (required)Constraints
| |
code | Σ | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.code 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. TaskCode (example)Constraints
|
description | Σ | 0..1 | string | There are no (further) constraints on this element Element IdTask.description Human-readable explanation of task DefinitionA free-text description of what is to be performed. Note that FHIR strings SHALL NOT exceed 1MB in size
|
focus | Σ I | 1..1 | Reference(ReteLabServiceRequestRichiestaEsamiLab) | Element IdTask.focus 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) Constraints
|
for | Σ I | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element IdTask.for 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.
|
encounter | Σ I | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element IdTask.encounter Healthcare event during which this task originated DefinitionThe healthcare event (e.g. a patient and healthcare provider interaction) during which this task was created. For some tasks it may be important to know the link between the encounter the task originated within. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
executionPeriod | Σ I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.executionPeriod Start and end time of execution DefinitionIdentifies the time action was first taken against the task (start) and/or the time final action was taken against the task prior to marking it as completed (end). A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). Period is not used for a duration (a measure of elapsed time). See Duration.
|
authoredOn | I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.authoredOn 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.
|
lastModified | Σ I | 0..1 | dateTime | There are no (further) constraints on this element Element IdTask.lastModified Task Last Modified Date Alternate namesUpdate Date DefinitionThe date and time of last modification to this task. Used along with history to track task activity and time in a particular task state. This enables monitoring and management.
|
requester | Σ I | 0..1 | Reference(Device | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) | There are no (further) constraints on this element Element IdTask.requester 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) Constraints
|
performerType | 0..* | CodeableConceptBinding | There are no (further) constraints on this element Element IdTask.performerType Requested performer DefinitionThe kind of participant that should perform the task. Use to distinguish tasks on different activity queues. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. The type(s) of task performers allowed. ProcedurePerformerRoleCodes (preferred)Constraints
| |
owner | Σ I | 0..1 | Reference(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) | There are no (further) constraints on this element Element IdTask.owner 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(Practitioner | PractitionerRole | Organization | CareTeam | HealthcareService | Patient | Device | RelatedPerson) Constraints
|
location | Σ I | 0..1 | Reference(Location) | There are no (further) constraints on this element Element IdTask.location Where task occurs DefinitionPrincipal physical location where the this task is performed. Ties the event to where the records are likely kept and provides context around the event occurrence (e.g. if it occurred inside or outside a dedicated healthcare setting). References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.
|
reasonCode | 0..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.reasonCode 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. (unbound) (example)Constraints
| |
reasonReference | I | 0..1 | Reference(Resource) | There are no (further) constraints on this element Element IdTask.reasonReference Why task is needed DefinitionA resource reference indicating why this task needs to be performed. Tasks might be justified based on an Observation, a Condition, a past or planned procedure, etc. This should only be included if there is no focus or if it differs from the reason indicated on the focus. Use the CodeableConcept text element in
|
insurance | I | 0..* | Reference(Coverage | ClaimResponse) | There are no (further) constraints on this element Element IdTask.insurance Associated insurance coverage DefinitionInsurance plans, coverage extensions, pre-authorizations and/or pre-determinations that may be relevant to the Task. References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Coverage | ClaimResponse) Constraints
|
note | 0..* | Annotation | Element IdTask.note 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 For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. Annotations SHOULD NOT be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible).
| |
relevantHistory | I | 0..* | Reference(Provenance) | There are no (further) constraints on this element Element IdTask.relevantHistory Key events in history of the Task Alternate namesStatus History DefinitionLinks to Provenance records for past versions of this Task that identify key state transitions or updates that are likely to be relevant to a user looking at the current version of the task. This element does not point to the Provenance associated with the current version of the resource - as it would be created after this version existed. The Provenance for the current version can be retrieved with a _revinclude.
|
restriction | 0..1 | BackboneElement | There are no (further) constraints on this element Element IdTask.restriction Constraints on fulfillment tasks DefinitionIf the Task.focus is a request resource and the task is seeking fulfillment (i.e. is asking for the request to be actioned), this element identifies any limitations on what parts of the referenced request should be actioned. Sometimes when fulfillment is sought, you don't want full fulfillment.
| |
repetitions | 0..1 | positiveInt | There are no (further) constraints on this element Element IdTask.restriction.repetitions How many times to repeat DefinitionIndicates the number of times the requested action should occur. E.g. order that requests monthly lab tests, fulfillment is sought for 1. 32 bit number; for values larger than this, use decimal
| |
period | I | 0..1 | Period | There are no (further) constraints on this element Element IdTask.restriction.period When fulfillment sought DefinitionOver what time-period is fulfillment sought. E.g. order that authorizes 1 year's services. Fulfillment is sought for next 3 months. Note that period.high is the due date representing the time by which the task should be completed.
|
recipient | I | 0..* | Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) | There are no (further) constraints on this element Element IdTask.restriction.recipient For whom is fulfillment sought? DefinitionFor requests that are targeted to more than on potential recipient/target, for whom is fulfillment sought? References SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository. Reference(Patient | Practitioner | PractitionerRole | RelatedPerson | Group | Organization) Constraints
|
input | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.input Information used to perform task Alternate namesSupporting Information DefinitionAdditional information that may be needed in the execution of the task. Resources and data used to perform the task. This data is used in the business logic of task execution, and is stored separately because it varies between workflows.
| |
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.input.type Label for the input Alternate namesName DefinitionA code or description indicating how the input is intended to be used as part of the task execution. Inputs are named to enable task automation to bind data and pass it from one task to the next. If referencing a BPMN workflow or Protocol, the "system" is the URL for the workflow definition and the code is the "name" of the required input. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Comparison source", "Applicable consent", "Concomitent Medications", etc. (unbound) (example)Constraints
| |
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.input.value[x] Content to use in performing the task DefinitionThe value of the input parameter as a basic type.
| ||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | ||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | ||
valueCode | code | There are no (further) constraints on this element Data Type | ||
valueDate | date | There are no (further) constraints on this element Data Type | ||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | ||
valueId | id | There are no (further) constraints on this element Data Type | ||
valueInstant | instant | There are no (further) constraints on this element Data Type | ||
valueInteger | integer | There are no (further) constraints on this element Data Type | ||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | ||
valueOid | oid | There are no (further) constraints on this element Data Type | ||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | ||
valueString | string | There are no (further) constraints on this element Data Type | ||
valueTime | time | There are no (further) constraints on this element Data Type | ||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | ||
valueUri | uri | There are no (further) constraints on this element Data Type | ||
valueUrl | url | There are no (further) constraints on this element Data Type | ||
valueUuid | uuid | There are no (further) constraints on this element Data Type | ||
valueAddress | Address | There are no (further) constraints on this element Data Type | ||
valueAge | Age | There are no (further) constraints on this element Data Type | ||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | ||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
valueCoding | Coding | There are no (further) constraints on this element Data Type | ||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | ||
valueCount | Count | There are no (further) constraints on this element Data Type | ||
valueDistance | Distance | There are no (further) constraints on this element Data Type | ||
valueDuration | Duration | There are no (further) constraints on this element Data Type | ||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | ||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | ||
valueMoney | Money | There are no (further) constraints on this element Data Type | ||
valuePeriod | Period | There are no (further) constraints on this element Data Type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | ||
valueRange | Range | There are no (further) constraints on this element Data Type | ||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | ||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | ||
valueSignature | Signature | There are no (further) constraints on this element Data Type | ||
valueTiming | Timing | There are no (further) constraints on this element Data Type | ||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | ||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | ||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | ||
valueExpression | Expression | There are no (further) constraints on this element Data Type | ||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | ||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | ||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | ||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | ||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | ||
valueMeta | Meta | There are no (further) constraints on this element Data Type | ||
valueReference | Reference() | There are no (further) constraints on this element Data Type | ||
output | 0..* | BackboneElement | There are no (further) constraints on this element Element IdTask.output Information produced as part of task DefinitionOutputs produced by the Task. Resources and data produced during the execution the task. This data is generated by the business logic of task execution, and is stored separately because it varies between workflows.
| |
type | 1..1 | CodeableConcept | There are no (further) constraints on this element Element IdTask.output.type Label for output Alternate namesName DefinitionThe name of the Output parameter. Outputs are named to enable task automation to bind data and pass it from one task to the next. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. Codes to identify types of input parameters. These will typically be specific to a particular workflow. E.g. "Identified issues", "Preliminary results", "Filler order", "Final results", etc. (unbound) (example)Constraints
| |
value[x] | 1..1 | There are no (further) constraints on this element Element IdTask.output.value[x] Result of output DefinitionThe value of the Output parameter as a basic type. Task outputs can take any form.
| ||
valueBase64Binary | base64Binary | There are no (further) constraints on this element Data Type | ||
valueBoolean | boolean | There are no (further) constraints on this element Data Type | ||
valueCanonical | canonical() | There are no (further) constraints on this element Data Type | ||
valueCode | code | There are no (further) constraints on this element Data Type | ||
valueDate | date | There are no (further) constraints on this element Data Type | ||
valueDateTime | dateTime | There are no (further) constraints on this element Data Type | ||
valueDecimal | decimal | There are no (further) constraints on this element Data Type | ||
valueId | id | There are no (further) constraints on this element Data Type | ||
valueInstant | instant | There are no (further) constraints on this element Data Type | ||
valueInteger | integer | There are no (further) constraints on this element Data Type | ||
valueMarkdown | markdown | There are no (further) constraints on this element Data Type | ||
valueOid | oid | There are no (further) constraints on this element Data Type | ||
valuePositiveInt | positiveInt | There are no (further) constraints on this element Data Type | ||
valueString | string | There are no (further) constraints on this element Data Type | ||
valueTime | time | There are no (further) constraints on this element Data Type | ||
valueUnsignedInt | unsignedInt | There are no (further) constraints on this element Data Type | ||
valueUri | uri | There are no (further) constraints on this element Data Type | ||
valueUrl | url | There are no (further) constraints on this element Data Type | ||
valueUuid | uuid | There are no (further) constraints on this element Data Type | ||
valueAddress | Address | There are no (further) constraints on this element Data Type | ||
valueAge | Age | There are no (further) constraints on this element Data Type | ||
valueAnnotation | Annotation | There are no (further) constraints on this element Data Type | ||
valueAttachment | Attachment | There are no (further) constraints on this element Data Type | ||
valueCodeableConcept | CodeableConcept | There are no (further) constraints on this element Data Type | ||
valueCoding | Coding | There are no (further) constraints on this element Data Type | ||
valueContactPoint | ContactPoint | There are no (further) constraints on this element Data Type | ||
valueCount | Count | There are no (further) constraints on this element Data Type | ||
valueDistance | Distance | There are no (further) constraints on this element Data Type | ||
valueDuration | Duration | There are no (further) constraints on this element Data Type | ||
valueHumanName | HumanName | There are no (further) constraints on this element Data Type | ||
valueIdentifier | Identifier | There are no (further) constraints on this element Data Type | ||
valueMoney | Money | There are no (further) constraints on this element Data Type | ||
valuePeriod | Period | There are no (further) constraints on this element Data Type | ||
valueQuantity | Quantity | There are no (further) constraints on this element Data Type | ||
valueRange | Range | There are no (further) constraints on this element Data Type | ||
valueRatio | Ratio | There are no (further) constraints on this element Data Type | ||
valueSampledData | SampledData | There are no (further) constraints on this element Data Type | ||
valueSignature | Signature | There are no (further) constraints on this element Data Type | ||
valueTiming | Timing | There are no (further) constraints on this element Data Type | ||
valueContactDetail | ContactDetail | There are no (further) constraints on this element Data Type | ||
valueContributor | Contributor | There are no (further) constraints on this element Data Type | ||
valueDataRequirement | DataRequirement | There are no (further) constraints on this element Data Type | ||
valueExpression | Expression | There are no (further) constraints on this element Data Type | ||
valueParameterDefinition | ParameterDefinition | There are no (further) constraints on this element Data Type | ||
valueRelatedArtifact | RelatedArtifact | There are no (further) constraints on this element Data Type | ||
valueTriggerDefinition | TriggerDefinition | There are no (further) constraints on this element Data Type | ||
valueUsageContext | UsageContext | There are no (further) constraints on this element Data Type | ||
valueDosage | Dosage | There are no (further) constraints on this element Data Type | ||
valueMeta | Meta | There are no (further) constraints on this element Data Type | ||
valueReference | Reference() | There are no (further) constraints on this element Data Type |
Table View
Task | .. | |
Task.status | .. | |
Task.intent | .. | |
Task.focus | Reference(ReteLabServiceRequestRichiestaEsamiLab) | 1.. |
Task.note | .. |
XML View
<StructureDefinition xmlns="http://hl7.org/fhir"> <url value="https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabTaskStatoRichiesta" /> <name value="ReteLabTaskStatoRichiesta" /> <status value="active" /> <date value="2023-12-21T14:31:53.6384566+00:00" /> <description value="Profilo che tiene traccia dello stato di avanzamento delle prestazioni." /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Task" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Task" /> <derivation value="constraint" /> <differential> <element id="Task"> <path value="Task" /> <short value="Stato di avanzamento delle prestazioni" /> <definition value="Risorsa per tenere traccia dello stato di avanzamento delle prestazioni." /> <comment value="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"" /> </element> <element id="Task.status"> <path value="Task.status" /> <short value="Stato della prestazione" /> <definition value="Può assumere i seguenti valori:\n- per la risposta dell'ente servente: "accepted"/"rejected"\n- per il checkin: "in-progress"/"failed"/"cancelled"\n- per l'esame: "completed"" /> <comment value="Corrispondente campo HL7 secondo specifiche regionali: ORC-5" /> </element> <element id="Task.intent"> <path value="Task.intent" /> <short value="Intento del task" /> <definition value="Due casistiche:\n- è valorizzato con "order" nel caso di richiesta proveniente dal laboratorio richiedente.\n- è valorizzato con "filler-order" nel caso di richiesta proveniente dal laboratorio servente." /> <comment value="L'intent del Task deve essere concorde all'intent della ServiceRequest che referenzia." /> </element> <element id="Task.focus"> <path value="Task.focus" /> <short value="Richiesta di cui si sta notificando il cambio stato" /> <definition value="Reference al profilo ReteLabServiceRequestRichiestaEsamiLab" /> <min value="1" /> <type> <code value="Reference" /> <targetProfile value="https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabServiceRequestRichiestaEsamiLab" /> </type> </element> <element id="Task.note"> <path value="Task.note" /> <short value="Commenti sul task" /> <definition value="Questo campo viene utilizzato per fornire ulteriori informazioni sullo stato della prestazione.\nAd esempio, quando la task viene utilizzata per notificare il rifiuto di una modifica" /> </element> </differential> </StructureDefinition>
JSON View
{ "resourceType": "StructureDefinition", "url": "https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabTaskStatoRichiesta", "name": "ReteLabTaskStatoRichiesta", "status": "active", "date": "2023-12-21T14:31:53.6384566+00:00", "description": "Profilo che tiene traccia dello stato di avanzamento delle prestazioni.", "fhirVersion": "4.0.1", "kind": "resource", "abstract": false, "type": "Task", "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Task", "derivation": "constraint", "differential": { "element": [ { "id": "Task", "path": "Task", "short": "Stato di avanzamento delle prestazioni", "definition": "Risorsa per tenere traccia dello stato di avanzamento delle prestazioni.", "comment": "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": "Task.status", "path": "Task.status", "short": "Stato della prestazione", "definition": "Può assumere i seguenti valori:\n- per la risposta dell'ente servente: \"accepted\"/\"rejected\"\n- per il checkin: \"in-progress\"/\"failed\"/\"cancelled\"\n- per l'esame: \"completed\"", "comment": "Corrispondente campo HL7 secondo specifiche regionali: ORC-5" }, { "id": "Task.intent", "path": "Task.intent", "short": "Intento del task", "definition": "Due casistiche:\n- è valorizzato con \"order\" nel caso di richiesta proveniente dal laboratorio richiedente.\n- è valorizzato con \"filler-order\" nel caso di richiesta proveniente dal laboratorio servente.", "comment": "L'intent del Task deve essere concorde all'intent della ServiceRequest che referenzia." }, { "id": "Task.focus", "path": "Task.focus", "short": "Richiesta di cui si sta notificando il cambio stato", "definition": "Reference al profilo ReteLabServiceRequestRichiestaEsamiLab", "min": 1, "type": [ { "code": "Reference", "targetProfile": [ "https://fhir.siss.regione.lombardia.it/StructureDefinition/ReteLabServiceRequestRichiestaEsamiLab" ] } ] }, { "id": "Task.note", "path": "Task.note", "short": "Commenti sul task", "definition": "Questo campo viene utilizzato per fornire ulteriori informazioni sullo stato della prestazione.\nAd esempio, quando la task viene utilizzata per notificare il rifiuto di una modifica" } ] } }
Esempi
ValueSet
Attualmente non sono definiti value set specifici per il profilo ReteLabTaskStatoRichiesta.