3.31 Extension: Task Requisition ID
The official URL for this extension is:
http://prescribeit.ca/fhir/StructureDefinition/ext-task-requisition-id
Status: draft
Extension maintained by:
The group/requisition that this particular task was initiated as part of
Context of Use
This extension may be used on the following element(s):
- {"type"=>"Task"}
Usage info
Yet to be done: xref
3.31.2 Formal Views of Extension Content
Download Excel representation
Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work.
This structure is derived from Task.groupIdentifier DSTU2 extension
| Name | Card. | Type | Constraints and Usage |
|---|---|---|---|
 Extension | 0..1 | Definition: 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. | |
 url | 1..1 | uri | "http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier" |
 valueIdentifier(Requisition ID) | 1..1 | Shared Health Identifier | Definition: The group/requisition that this particular task was initiated as part of Comments: Links multiple separate MedicationOrder, DeviceRequest and other requests that originated at the same time |
This structure is derived from Task.groupIdentifier DSTU2 extension
This structure is derived from Task.groupIdentifier DSTU2 extension
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
 Extension | S | 0..1 | Prescription Number | |
 extension | 0..0 | |||
| url | S | 1..1 | uri | "http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier" |
 valueIdentifier | S | 1..1 | Shared Health Identifier | |
| Documentation for this format | ||||
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Extension | S | 0..1 | Prescription Number | |
 id | 0..1 | id | xml:id (or equivalent in JSON) | |
| url | S | 1..1 | uri | "http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier" |
| valueIdentifier | S | 1..1 | Shared Health Identifier | An identifier intended for computation |
| Documentation for this format | ||||
Grid View
This structure is derived from Task.groupIdentifier DSTU2 extension
| Name | Card. | Type | Constraints and Usage |
|---|---|---|---|
| Extension | 0..1 | Definition: 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. | |
| url | 1..1 | uri | "http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier" |
| valueIdentifier (Requisition ID) | 1..1 | Shared Health Identifier | Definition: The group/requisition that this particular task was initiated as part of Comments: Links multiple separate MedicationOrder, DeviceRequest and other requests that originated at the same time |
This structure is derived from Task.groupIdentifier DSTU2 extension
Differential View
This structure is derived from Task.groupIdentifier DSTU2 extension
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Extension | S | 0..1 | Prescription Number | |
| extension | 0..0 | |||
| url | S | 1..1 | uri | "http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier" |
| valueIdentifier | S | 1..1 | Shared Health Identifier | |
| Documentation for this format | ||||
Snapshot View
| Name | Flags | Card. | Type | Description & Constraints |
|---|---|---|---|---|
| Extension | S | 0..1 | Prescription Number | |
| id | 0..1 | id | xml:id (or equivalent in JSON) | |
| url | S | 1..1 | uri | "http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier" |
| valueIdentifier | S | 1..1 | Shared Health Identifier | An identifier intended for computation |
| Documentation for this format | ||||
Other representations of extension: Schematron
3.31.3 Terminology Bindings
3.31.4 Constraints
Constraints
| Id | Path | Details | Requirements |