HL7 Electronic Health Record System Functional Model, Release 2.1.1
2.1.1-ballot - Normative Ballot

Publication Build: This will be filled in by the publication tooling

## Requirements: TI.7 Workflow Management (Function)

Page standards status: Informative

Statement N:

Support workflow management functions including both the management and set up of work queues, personnel lists, and system interfaces as well as the implementation functions that use workflow-related business rules to direct the flow of work assignments.

Description I:

Workflow management functions that an EHR-S supports include:

- Distribution of information to and from internal and external parties;
- Support for task-management as well as parallel and serial task distribution;
- Support for notification and task routing based on system triggers; and
- Support for task assignments, escalations and redirection in accordance with business rules.

Workflow definitions and management may be implemented by a designated application or distributed across an EHR-S.

Actors:
ehr Criteria N:

TI.7#01 | SHALL | The system SHALL provide the ability to manage workflow business rules including work queues, personnel lists, and system interfaces.
TI.7#02 | SHOULD | The system SHOULD provide the ability to determine workflow assignments based on workflow-related business rules.
TI.7#03 | MAY | The system MAY provide the ability to manage human resources (i.e., personnel lists) for workflow queues.
TI.7#04 | MAY | The system MAY exchange information with external systems (for example, Human Resources system or Staff Management system) to support the management of human resources.
TI.7#05 | MAY | The system MAY exchange information with external systems (for example, Human Resources system or Staff Management system ) to support the management of workflow queues (task lists).
TI.7#06 | MAY | The system MAY provide the ability to exchange workflow related information with an external system.
TI.7#07 | MAY | The system MAY provide the ability to render notifications and tasks based on system triggers.
TI.7#08 | dependent MAY | The system MAY determine and render an updated priority of tasks on the workflow (task list) queue in accordance with business rules, and according to scope of practice, organizational policy, and/or jurisdictional law.
TI.7#09 | dependent MAY | The system MAY determine and render an update to the tasks, and/or execution path on the workflow (task list) queue in accordance with business rules, and according to scope of practice, organizational policy, and/or jurisdictional law.
TI.7#10 | dependent MAY | The system MAY determine and render an update to the assignment of the resources to workflow (task list) queue in accordance with business rules, and according to scope of practice, organizational policy, and/or jurisdictional law.
TI.7#11 | SHOULD | The system SHOULD provide the ability to render a notification of a workflow update.
TI.7#12 | MAY | The system MAY provide the ability to render a notification of a workflow update including the details of the update.
TI.7#13 | SHOULD | The system SHOULD provide the ability to transmit a workflow (task list) queue update request to an external system.
TI.7#14 | SHOULD | The system SHOULD provide the ability to receive a workflow (task list) queue update response from an external system.