PrescribeIT® Specification and Guide Version 3.0 Revision C

 

Definitions for the ext-task-group-identifier Extension

1. Extension
Definition

This is the common identifier that represents a paper order. It may be shared by multiple Task instances for various Medication Orders, reflecting multiple requests that are authorized simultaneously for a patient by a single prescriber

Control0..1
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. The following scenarios provide further detail:

Scenario 1) Single Task allowed within a Bundle: There are some business scenarios where a given task will be managed individually and only a single task is allowed in a bundle. This is true for the Adapt (p170) and the Pharmacist Prescribe (p190). Multiple tasks of the same type are not allowed, nor are any other task type.

Scenario 2) Single Task is sent. For any task type, the source system may send a single task within the bundle.

Scenario 3) In either scenario 1 or 2, the task will be assigned its own Group Identifier and will be handled as a group of one.

Scenario 4) Bundle restricted to same task type only: There are cases when only tasks of the same type can be grouped together. This is true for the cancel request (e140), Dispense Notifications (p200), Cancel RX Dispense Notification (p210). In this scenario, no other task types are allowed within the bundle.

Scenario 5) Same or Mixed Task Types within a single group: There are cases when either all the tasks within a group happen to have the same task type (p160) which are not necessary restricted due to 4 or certain task types that are different can be grouped together. This is true for new (e110) and renewal (e120) where these are part of the same prescription. Another scenario is that renewal responses (e161, e162, e163, e164) may be sent with an e110 and/or an e120.

Scenario 6) In either scenario 4 and 5, the same Group Identifier must be assigned to the multiple tasks as they are all part of the same group. All task resources sharing a Group Identifier must be transmitted in the same message bundle and should be treated as a group by the receiving system.

Scenario 7) The p160 task type can only be sent within it's own bundle.

Multiple Group Identifiers within the same Bundle is not allowed.

The Task.extension:groupIdentifier.valueIdentifier.system element will be an OID of the form [Vendor root].[Application instance node].3 expressed as a uri (e.g. urn:oid:1.2.3.4). The branch “.3” is appended to create a unique namespace for the Group Identifer. The Task.extension:groupIdentifier.valueIdentifier.value element will be assigned by the sending system and must be a unique business identifier.

2. Extension.id
Definition

unique id for the element within a resource (for internal references).

Control0..1
Typeid
3. Extension.extension
Definition

An Extension

Control0..0
TypeExtension
4. Extension.url
Definition

Source of the definition for the extension code - a logical name or a URL.

Control1..1
Typeuri
Must Supporttrue
Comments

Fixed value: http://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier

Fixed Valuehttp://hl7.org/fhir/StructureDefinition/extension-Task.groupIdentifier
5. Extension.value[x]
Definition

Value of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).

Control1..1
TypeIdentifier
[x] NoteSee Choice of Data Types for further information about how to use [x]
SlicingThis element introduces a set of slices on Extension.value[x]. The slices are unordered and Closed, and can be differentiated using the following discriminators:
  • type @ $this
6. Extension.value[x]:valueIdentifier
SliceNamevalueIdentifier
Definition

The group that this particular task was initiated as part of

Control1..1
TypeIdentifier(Shared Health Identifier)
[x] NoteSee Choice of Data Types for further information about how to use [x]
Must Supporttrue
Comments

Links multiple separate MedicationOrder, DeviceRequest and other requests that originated at the same time. In PrescribeIT® v2.0, this was formerly called Requisition Identifier.

Max Length0