SportOrtho
Notes & Review Items
How you know it worked
Every row in the response file has been triaged into one of four outcomes: (1) `MoveDocs ID` pasted onto an existing Monday row, (2) flagged for re-add from Athena, (3) skipped because the patient is marked `Sent to Leanstar`, or (4) confirmed as a correct response that the visit did not occur, with or without LOP sent. Any row where the response conflicts with the `Appointments` board has been listed and sent to the workflow owner. The annotated response XLSX is ready to return to MoveDocs.
Open review items
These items were unclear in the source recording and need confirmation from the tool owner.
The current reconciliation tool URL is distributed outside this document. Confirm with the workflow owner that the link in use matches the latest production deployment before starting.
The confirmation text displayed below `Reconciliation Complete` on the n8n form is not fully legible in the source material. The exact secondary wording is unconfirmed.
The Monday board paste action was not isolated to a single frame in the source material. The destination column is understood to be the `MoveDocs ID` field on the patient row. Confirm the exact column label on the live board.
The Athena interface is not demonstrated in the source material. This step is described verbally only. Confirm with the workflow owner where in Athena to search and what to record when flagging a row for re-add.
The source material shows multiple `Donna Rhode` entries on the Combined Board at the point where the patient is described as not being on the board. The correct disposition of those entries is not definitively resolved. Confirm the handling of duplicate name entries with the workflow owner.
The `Sent to Leanstar` column header is not fully legible in the source material. Confirm the exact column name on the live board.
The source material documents a case where the tool returned `Visit didn't occur` for a patient whose `Appointments` board entry showed a confirmed visit with both record and bill complete. The underlying automation error was not resolved within the source recording.
The tool link, response file format, or workflow behavior may have changed since the source material was recorded. Verify with the workflow owner before each use.