Epic-workflow-conductor

: As health systems migrate to Epic's Hyperdrive client, note that certain legacy administration models like the Satellite client manager do not natively handle Workflow Conductor, requiring standard managed deployment scripts. 🏥 Common Use Case: Radiology

In a typical imaging deployment, Epic Workflow Conductor works behind the scenes to automate a radiologist's day: An imaging technologist completes a scan. The scan data hits the PACS, and the order resides in Epic. epic-workflow-conductor

: Pushing updates often requires sequential handling of MSIs (e.g., deploying the main Workflow Conductor application installer first, followed by specific update packs). : As health systems migrate to Epic's Hyperdrive

: Automatically assigns and pushes exams or tasks to the appropriate clinician (e.g., Radiologists) based on availability, sub-specialty, and caseload. 🛠️ Core Administrative & Configuration Tasks : Pushing updates often requires sequential handling of

evaluates the reading queue and pushes the study directly to the active workstation of a specialized radiologist.

: If a provider requests custom instructions or data views within their reading queue, specific "Print Group" records must be built and added to their profile.