3.31.6 Extension: Task Requisition ID - Detailed Descriptions
Definitions for the ext-task-requisition-id Extension
| Extension | |
| 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 |
| Control | 0..1 |
| Must Support | true |
| 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. |
| Extension.id | |
| Definition | unique id for the element within a resource (for internal references). |
| Control | 0..1 |
| Type | id |
| Max Length | 0 |
| Extension.extension(extension) | |
| Definition | An Extension |
| Control | 0..0 |
| Type | Extension |
| Extension.url | |
| Definition | Source of the definition for the extension code - a logical name or a URL. |
| Control | 1..1 |
| Type | uri |
| Must Support | true |
| Comments | Fixed value: http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier |
| Max Length | 0 |
| Fixed Value | http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier |
| Extension.valueIdentifier(Requisition ID) | |
| Definition | The group/requisition that this particular task was initiated as part of |
| Control | 1..1 |
| Type | Identifier(Shared Health Identifier) |
| Must Support | true |
| Comments | Links multiple separate MedicationOrder, DeviceRequest and other requests that originated at the same time |
| Max Length | 0 |