GGG.2 Implementation Examples
Prev | GGG Unified Worklist and Procedure Step - UPS (Informative) | Next

## GGG.2 Implementation Examples

The following sections describe ways UPS workflows could be used to address some typical scenarios.

### GGG.2.1 Typical SOP Class Implementations

The decision of which SOP Classes to implement in which systems will revolve partly around where it makes the most sense for the business logic to reside, what information each system would have access to, and what kind of workflow is most effective for the users.

Table GGG.1-1 shows a number of hypothetical systems and the combination of SOP Classes they might implement. For example, a typical worklist manager would support all four SOP Classes as an SCP. A typical scheduling system might want to be a UPS Push SCU to submit work items to the worklist manager, a UPS Watch SCU to subscribe for notifications and get details of the results, and a UPS Event SCU to receive the progress notifications. A simple "pull performer" might only be a UPS Pull SCU, similar to modalities today.

Other examples are listed for:

- "Minimal Scheduler", a requesting system that is not interested in monitoring progress or results.

- "Watcher", a system interested in tracking the progress and/or results of Unified Procedure Steps.

- "General Contractor", a system that accepts work items pushed to it, then uses internal business logic to subdivide/create work items that it pushes or makes available to systems that will actually perform the work.

- "Push Performer", a system, for example a CAD system, that has work pushed to it, and provides status and results information to interested observers.

- "Self-Scheduled Performer", which internally schedules it's own work, but supports notifications and N-GET so the details of the work can be made available to other departmental systems.

- "Self-Scheduled Pull Performer", which pushes a workitem onto a worklist manager and then pulls it off to perform it. This allows it to work on "unscheduled" procedures without taking on the responsibility of being an SCP for notifications and events.

Table GGG.1-1. SOP Classes for Typical Implementation Examples

SOP Classes | SCU | SCP
--- | --- | ---
UPS Push | UPS Watch | UPS Event | UPS Pull | UPS Push | UPS Watch | UPS Event | UPS Pull
Non-Performing SCUs
Minimal Scheduler | X |  |  |  |  |  |  |
Typical Scheduler | X | X | X |  |  |  |  |
Watcher |  | X | X |  |  |  |  |
Worklist SCPs
Worklist Manager |  |  |  |  | X | X | X | X
General Contractor | X | X | X |  | X | X | X | X
Performing SCPs
Push Performer |  |  |  |  | X | X | X |
Self-Scheduled Performer |  |  |  |  |  | X | X |
Performing SCUs
Pull Performer |  |  |  | X |  |  |  |
Self-Scheduled Pull Performer | X |  |  | X |  |  |  |

A system that implements UPS Watch as an SCP will also need to implement UPS Event as an SCP to be able to send Event Reports to the systems from whom it accepts subscriptions.

Prev | Up | Next
GGG Unified Worklist and Procedure Step - UPS (Informative) | Home | GGG.2.2 Typical Pull Workflow