PrescribeIT™ Specification and Guide Version 2.0 Revision F

 

The official URL for this profile is:

http://prescribeit.ca/fhir/StructureDefinition/profile-task

Download Excel representation

Description of Profiles, Differentials, Snapshots and how the different presentations work.

>

This structure is derived from Task

NameCard.TypeConstraints and Usage
.  Task 0..*inv-2: A Failure reason may be present only when a task has failed.
inv-1: Last modified date must be greater than or equal to created date.
Definition:
A task to be performed.

..  id 1..1idDefinition:
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.


Comments:
Usage Note: This will usually be a GUID and is assigned by the requesting application.

..  meta 1..1MetaDefinition:
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

...  profile 1..*uriDefinition:
A list of profiles [[[StructureDefinition]]]s that this resource claims to conform to. The URL is a reference to [[[StructureDefinition.url]]].


Comments:
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time.

..  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

..  extension
     (requisitionIdentifier)
1..1Task Requisition IDDefinition:
This is the common number that represents a paper order. It may be shared by multiple MedicationOrder, DeviceRequest and Task instances, reflecting multiple requests that are authorized simultaneously for a patient by a single prescriber


Comments:
Usage Note: This business identifier is assigned by the sending application and is used to group tasks together that need to be processed and managed together. There are some business scenarios where a given task will be managed individually (eg cancel request). If a particular task is not part of a logical group, it will have its own requisition identifier (i.e. it will be handled as a group of 1). In other scenarios, the same requisition identifier is assigned to multiple tasks as they are considered to be part of a group. Example: medications that would be part of the same written paper Prescription or Renewal request will share the same Requisition Identifier.

Usage Note: Tasks corresponding to different requisition identifiers may be present in the same Bundle. The recipient must take this into account when grouping content for display/actioning by requisition identifier.

Suggested Structure: Assigned by the EMR; scoped by the application instance; this is an OID. An OID may be structured as Vendor.ApplicationInstance.RX#Branch Ext = Requisition Id.

Conformance Rule: All task resources sharing a common requisition number must be transmitted in the same message bundle.

Conformance Rule: All medication orders sharing the same requisition identifier in a renewal request must be viewed, managed and responded to together.

Conformance Rule: Different task types can share a requisition identifier when a task was performed in the shared context of other tasks with the same requisition id. For example, medication 1 was discontinued in the same context that medication 2 was prescribed. Receiving systems SHOULD display/manage tasks that are part of the same requisition together when this is feasible.

Conformance Rule: In the context of a 401 - Execute deferred (prescription) tasks from an EMR, this will map to the 'PrescribeIT™ RX ID' on the printed Patient Copy.

Usage Note: Requisition ID would be used by PMS to establish which medications belong to the same prescription.

..  type 1..1Shared Health CodeableConcept CodeBinding: PrescriptionTaskType (required)
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
This will be a fixed code for each type of task. Review usage comments on child elements.

..  priority 0..1codeBinding: PrescriptionTaskPriority (required)
Definition:
The priority of the task among other tasks of the same type.


Comments:
This element does not apply to either Task p200-m - RX Dispense Notification or Task p210-m - RX Dispense Cancel Notification

Conformance Rule: If one of the medications within a requisition is a high priority, the EMR should present the entire renewal request (based on requisision.id) as a high priority item within the queue.

Conformance Rule: For Task p166-m - RX Renewal Remindar, if the priority has escalated to high, the EMR must present this to the Prescriber.

..  status 1..1codeBinding: TaskStatus (required)
Definition:
The current status of the task.


Comments:
This will be fixed based on the task code being used as the architecture calls for different tasks for each state rather than updating of existing tasks.

..  subject 0..1Reference(Resource)Definition:
The subject of the task.

..  for 1..1Reference(Shared Health Patient) {b}Definition:
The entity who benefits from the performance of the service specified in the task (e.g., the patient).


Comments:
Identifies the patient tied to the task. (FHIR prohibits inheritance of context, so this must be explicitly declared rather than inferred from the presence of the Patient resource in the message)

...  reference 1..1stringDefinition:
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.


Comments:
This is a reference to the Patient associated with the task. It will be a URN pointing to the id of the patient record in the message

..  created 1..1dateTimecreated-full: Must be at least a full date. i.e. yyyy-mm-dd
Definition:
The date and time this task was created.


Comments:
This indicates when the request was created. This will generally be the same as the date of message construction.

Conformance Rule: Date-Time must be specified down to the day. Time is optional and may be ignored.

Usage Note: If time is present, FHIR requires the UTC offset and for time to be specified down to the seconds. If seconds aren't available, they may be filled with '00'

..  lastModified 1..1dateTimecreated-full: Must be at least a full date. i.e. yyyy-mm-dd
Definition:
The date and time of last modification to this task.


Comments:
This is required by FHIR but is not needed. It should generally be set to the same value as Task.created. This is the date of the most recent transaction as recorded in the EMR.

Usage Note: If time is present, FHIR requires the UTC offset and for time to be specified down to the seconds. If seconds aren't available, they may be filled with '00'.

Conformance Rule: PMS is not expected to display this date as it is irrelevant to the Pharmacist or to the processing of the discontinue notification.

..  creator 1..1Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Definition:
The creator of the task.


Comments:
This is who is submitting the task and asking it be done

This structure is derived from Task

Summary

Mandatory: 9 elements
Must-Support: 14 elements

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task SI0..*A task to be performed
... id SΣ1..1idLogical id of this artifact
... meta SΣ1..1MetaMetadata about the resource
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... versionId Σ0..1idVersion specific identifier
.... lastUpdated Σ0..1instantWhen the resource version last changed
.... profile SΣ1..*uriProfiles this resource claims to conform to
.... security Σ0..*CodingSecurity Labels applied to this resource
Binding: All Security Labels (extensible)
.... tag Σ0..*CodingTags applied to this resource
Binding: (unbound) (example)
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: http://tools.ietf.org/html/bcp47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
... ext-task-requisition-id S1..1Shared Health IdentifierPrescription Number
URL: http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-task-requisition-id
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..1IdentifierTask Instance Identifier
... type S1..1Shared Health CodeableConcept CodeConcept - reference to a terminology or just text
Binding: PrescriptionTaskType (required)
... description Σ0..1stringTask Description
... performerType 0..*Codingrequester | dispatcher | scheduler | performer | monitor | manager | acquirer | reviewer
Binding: TaskPerformerType (preferred)
... priority S0..1codenormal | high
Binding: PrescriptionTaskPriority (required)
... status SΣI1..1codedraft | requested | received | accepted | +
Binding: TaskStatus (required)
... failureReason ΣI0..1CodeableConceptTask Failure Reason
... subject S0..1Reference(Resource)Focus of task
... for SΣ1..1Reference(Shared Health Patient) {b}Beneficiary of the Task
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... reference SΣI1..1stringRelative, internal or absolute URL reference
.... display Σ0..1stringText alternative for the resource
... definition Σ0..1uriTask Definition
... created SI1..1dateTimeTask Creation Date
created-full: Must be at least a full date. i.e. yyyy-mm-dd
... lastModified SΣI1..1dateTimeTask Last Modified Date
created-full: Must be at least a full date. i.e. yyyy-mm-dd
... creator S1..1Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Task requestor
... owner 0..1Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Task recipient
... parent 0..1Reference(Task)Composite task
... input 0..*BackboneElementTask Input
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... name 1..1stringInput Name
.... value[x] 1..1boolean, integer, decimal, base64Binary, instant, string, uri, date, dateTime, time, code, oid, id, unsignedInt, positiveInt, markdown, Annotation, Attachment, Identifier, CodeableConcept, Coding, Quantity, Range, Period, Ratio, SampledData, Signature, HumanName, Address, ContactPoint, Timing, Reference(), MetaInput Value
... output 0..*BackboneElementTask Output
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... name 1..1stringOutput Name
.... value[x] 1..1boolean, integer, decimal, base64Binary, instant, string, uri, date, dateTime, time, code, oid, id, unsignedInt, positiveInt, markdown, Annotation, Attachment, Identifier, CodeableConcept, Coding, Quantity, Range, Period, Ratio, SampledData, Signature, HumanName, Address, ContactPoint, Timing, Reference(), MetaOutput Value

doco Documentation for this format

Grid View

This structure is derived from Task

NameCard.TypeConstraints and Usage
.  Task 0..*inv-2: A Failure reason may be present only when a task has failed.
inv-1: Last modified date must be greater than or equal to created date.
Definition:
A task to be performed.

..  id 1..1idDefinition:
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.


Comments:
Usage Note: This will usually be a GUID and is assigned by the requesting application.

..  meta 1..1MetaDefinition:
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.

...  profile 1..*uriDefinition:
A list of profiles [[[StructureDefinition]]]s that this resource claims to conform to. The URL is a reference to [[[StructureDefinition.url]]].


Comments:
It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time.

..  extension 0..*ExtensionSlice: Unordered, Open by value:url
Definition:
An Extension

..  extension
     (requisitionIdentifier)
1..1Task Requisition IDDefinition:
This is the common number that represents a paper order. It may be shared by multiple MedicationOrder, DeviceRequest and Task instances, reflecting multiple requests that are authorized simultaneously for a patient by a single prescriber


Comments:
Usage Note: This business identifier is assigned by the sending application and is used to group tasks together that need to be processed and managed together. There are some business scenarios where a given task will be managed individually (eg cancel request). If a particular task is not part of a logical group, it will have its own requisition identifier (i.e. it will be handled as a group of 1). In other scenarios, the same requisition identifier is assigned to multiple tasks as they are considered to be part of a group. Example: medications that would be part of the same written paper Prescription or Renewal request will share the same Requisition Identifier.

Usage Note: Tasks corresponding to different requisition identifiers may be present in the same Bundle. The recipient must take this into account when grouping content for display/actioning by requisition identifier.

Suggested Structure: Assigned by the EMR; scoped by the application instance; this is an OID. An OID may be structured as Vendor.ApplicationInstance.RX#Branch Ext = Requisition Id.

Conformance Rule: All task resources sharing a common requisition number must be transmitted in the same message bundle.

Conformance Rule: All medication orders sharing the same requisition identifier in a renewal request must be viewed, managed and responded to together.

Conformance Rule: Different task types can share a requisition identifier when a task was performed in the shared context of other tasks with the same requisition id. For example, medication 1 was discontinued in the same context that medication 2 was prescribed. Receiving systems SHOULD display/manage tasks that are part of the same requisition together when this is feasible.

Conformance Rule: In the context of a 401 - Execute deferred (prescription) tasks from an EMR, this will map to the 'PrescribeIT™ RX ID' on the printed Patient Copy.

Usage Note: Requisition ID would be used by PMS to establish which medications belong to the same prescription.

..  type 1..1Shared Health CodeableConcept CodeBinding: PrescriptionTaskType (required)
Definition:
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.


Comments:
This will be a fixed code for each type of task. Review usage comments on child elements.

..  priority 0..1codeBinding: PrescriptionTaskPriority (required)
Definition:
The priority of the task among other tasks of the same type.


Comments:
This element does not apply to either Task p200-m - RX Dispense Notification or Task p210-m - RX Dispense Cancel Notification

Conformance Rule: If one of the medications within a requisition is a high priority, the EMR should present the entire renewal request (based on requisision.id) as a high priority item within the queue.

Conformance Rule: For Task p166-m - RX Renewal Remindar, if the priority has escalated to high, the EMR must present this to the Prescriber.

..  status 1..1codeBinding: TaskStatus (required)
Definition:
The current status of the task.


Comments:
This will be fixed based on the task code being used as the architecture calls for different tasks for each state rather than updating of existing tasks.

..  subject 0..1Reference(Resource)Definition:
The subject of the task.

..  for 1..1Reference(Shared Health Patient) {b}Definition:
The entity who benefits from the performance of the service specified in the task (e.g., the patient).


Comments:
Identifies the patient tied to the task. (FHIR prohibits inheritance of context, so this must be explicitly declared rather than inferred from the presence of the Patient resource in the message)

...  reference 1..1stringDefinition:
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.


Comments:
This is a reference to the Patient associated with the task. It will be a URN pointing to the id of the patient record in the message

..  created 1..1dateTimecreated-full: Must be at least a full date. i.e. yyyy-mm-dd
Definition:
The date and time this task was created.


Comments:
This indicates when the request was created. This will generally be the same as the date of message construction.

Conformance Rule: Date-Time must be specified down to the day. Time is optional and may be ignored.

Usage Note: If time is present, FHIR requires the UTC offset and for time to be specified down to the seconds. If seconds aren't available, they may be filled with '00'

..  lastModified 1..1dateTimecreated-full: Must be at least a full date. i.e. yyyy-mm-dd
Definition:
The date and time of last modification to this task.


Comments:
This is required by FHIR but is not needed. It should generally be set to the same value as Task.created. This is the date of the most recent transaction as recorded in the EMR.

Usage Note: If time is present, FHIR requires the UTC offset and for time to be specified down to the seconds. If seconds aren't available, they may be filled with '00'.

Conformance Rule: PMS is not expected to display this date as it is irrelevant to the Pharmacist or to the processing of the discontinue notification.

..  creator 1..1Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Definition:
The creator of the task.


Comments:
This is who is submitting the task and asking it be done

This structure is derived from Task

Summary

Mandatory: 9 elements
Must-Support: 14 elements

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Task SI0..*A task to be performed
... id SΣ1..1idLogical id of this artifact
... meta SΣ1..1MetaMetadata about the resource
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... versionId Σ0..1idVersion specific identifier
.... lastUpdated Σ0..1instantWhen the resource version last changed
.... profile SΣ1..*uriProfiles this resource claims to conform to
.... security Σ0..*CodingSecurity Labels applied to this resource
Binding: All Security Labels (extensible)
.... tag Σ0..*CodingTags applied to this resource
Binding: (unbound) (example)
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: http://tools.ietf.org/html/bcp47 (required)
... text I0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension S0..*ExtensionExtension
Slice: Unordered, Open by value:url
... ext-task-requisition-id S1..1Shared Health IdentifierPrescription Number
URL: http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier profiled by http://prescribeit.ca/fhir/StructureDefinition/ext-task-requisition-id
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier 0..1IdentifierTask Instance Identifier
... type S1..1Shared Health CodeableConcept CodeConcept - reference to a terminology or just text
Binding: PrescriptionTaskType (required)
... description Σ0..1stringTask Description
... performerType 0..*Codingrequester | dispatcher | scheduler | performer | monitor | manager | acquirer | reviewer
Binding: TaskPerformerType (preferred)
... priority S0..1codenormal | high
Binding: PrescriptionTaskPriority (required)
... status SΣI1..1codedraft | requested | received | accepted | +
Binding: TaskStatus (required)
... failureReason ΣI0..1CodeableConceptTask Failure Reason
... subject S0..1Reference(Resource)Focus of task
... for SΣ1..1Reference(Shared Health Patient) {b}Beneficiary of the Task
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... reference SΣI1..1stringRelative, internal or absolute URL reference
.... display Σ0..1stringText alternative for the resource
... definition Σ0..1uriTask Definition
... created SI1..1dateTimeTask Creation Date
created-full: Must be at least a full date. i.e. yyyy-mm-dd
... lastModified SΣI1..1dateTimeTask Last Modified Date
created-full: Must be at least a full date. i.e. yyyy-mm-dd
... creator S1..1Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Task requestor
... owner 0..1Reference(Device | Organization | Patient | Practitioner | RelatedPerson)Task recipient
... parent 0..1Reference(Task)Composite task
... input 0..*BackboneElementTask Input
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... name 1..1stringInput Name
.... value[x] 1..1boolean, integer, decimal, base64Binary, instant, string, uri, date, dateTime, time, code, oid, id, unsignedInt, positiveInt, markdown, Annotation, Attachment, Identifier, CodeableConcept, Coding, Quantity, Range, Period, Ratio, SampledData, Signature, HumanName, Address, ContactPoint, Timing, Reference(), MetaInput Value
... output 0..*BackboneElementTask Output
.... id 0..1idxml:id (or equivalent in JSON)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored
.... name 1..1stringOutput Name
.... value[x] 1..1boolean, integer, decimal, base64Binary, instant, string, uri, date, dateTime, time, code, oid, id, unsignedInt, positiveInt, markdown, Annotation, Attachment, Identifier, CodeableConcept, Coding, Quantity, Range, Period, Ratio, SampledData, Signature, HumanName, Address, ContactPoint, Timing, Reference(), MetaOutput Value

doco Documentation for this format

 

Other representations of profile: Schematron

Terminology Bindings

PathNameConformanceValueSet
Task.meta.securityAll Security LabelsextensibleAll Security Labels
Task.meta.tag?extexample
Task.language?extrequiredhttp://tools.ietf.org/html/bcp47
Task.typePrescriptionTaskTyperequiredPrescriptionTaskType
Task.performerTypeTaskPerformerTypepreferredTaskPerformerType
Task.priorityPrescriptionTaskPriorityrequiredPrescriptionTaskPriority
Task.statusTaskStatusrequiredTaskStatus

Constraints

IdPathDetailsRequirements
inv-2TaskA Failure reason may be present only when a task has failed.
: failureReason.empty() or status = 'failed'
inv-1TaskLast modified date must be greater than or equal to created date.
: lastModified >= created
created-fullTask.createdMust be at least a full date. i.e. yyyy-mm-dd
: length()>=10
created-fullTask.lastModifiedMust be at least a full date. i.e. yyyy-mm-dd
: length()>=10