Readiness includes the workstation where the task happens. CLINOPILOT WORKFLOW CHECK A task can depend on a workstation, role, peripheral and destination. Testing only a screen can miss a dependency further along that path. Proposed steps 1. Map the task path: approved workstation, intended role, required peripheral and expected destination. 2. Ask the authorized local team to run the path with a synthetic or blank training example. Record the failure point. 3. Assign the failed dependency to its local or vendor owner. Repeat the complete path after the approved response. Checklist [ ] The intended workstation and role are included. [ ] The required peripheral is included where relevant. [ ] Output reaches the expected approved destination. [ ] The full path is retested after the change. Illustrative example, not a client record Task: Produce a blank training output Path: Approved workstation → intended role → training printer → expected destination Block: Output reaches an unexpected training destination Owner: Authorized endpoint or application support Verification: Repeat the same safe path end to end Test Use a fictional task that includes a peripheral or output destination. Record whether the entire path completes, beyond a successful login. Candidate local measure For agreed task paths, record pass/fail and the failed dependency. A device count alone does not establish readiness. Scope This dependency check excludes physical repair, production access and unapproved configuration changes. Independent published evidence Unity Health Toronto Project Connect launch (Published implementation announcement) Unity Health reported more than 21,000 new Epic-compatible devices. A deployment count shows investment and scale, not proof that every local task path works. https://unityhealth.to/2024/12/unity-health-launches-new-electronic-patient-record-system/ https://clinopilot.com/proof/device-readiness/ Use approved tools and fictional or process-level examples. Do not add patient information to public requests.