Automated Portal Transmission Sync Audit
Every morning, WebRun signs into each manufacturer portal, lists the transmissions received overnight, checks whether each one has synced into the Octagos triage queue, logs any missing transmission to a Google Sheet, and posts your team a Microsoft Teams audit so nothing sits stranded on a vendor site outside your workflow.
How do I reconcile manufacturer-portal transmissions with my monitoring platform?
WebRun signs into each manufacturer portal every morning, lists the transmissions received overnight, and checks whether each one synced into the Octagos triage queue. It logs any missing transmission to Google Sheets and posts your team a Microsoft Teams audit grouped by manufacturer, so no transmission stays stranded on a vendor site outside your workflow.
- Transmissions stranded on a vendor portal surface every morning
- A failing portal connection is obvious from the grouped audit
- The team sees reconciled and missing counts in Teams within seconds
Built for remote monitoring coordinators · device clinics · cardiac electrophysiology practices · allied professionals
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.octagos.comin a real browser with your saved login - no setup, no API keys. -
1
Octagos - confirm transmissions synced
- Sign into each manufacturer portal on the allowlist and list transmissions received since the last audit
- Open Octagos and check whether each portal transmission has synced into the triage queue
- Flag any transmission present in a portal but absent from Octagos, and any Octagos record with no source portal match
- Capture the manufacturer, patient initials, transmission time, and which side is missing it
Done when Every overnight portal transmission is confirmed present in Octagos or flagged as missing.
-
2
Google Sheets - log the missing transmissions
WebRun opens Google Sheets to log the missing transmissions. - Open the Portal Sync Audit sheet and add a dated block
- Append one row per transmission that did not reconcile, noting the manufacturer and which side is missing it
- Skip transmissions that reconciled cleanly so only exceptions are listed
- Keep prior days so a portal that repeatedly fails to sync stands out
Done when The audit sheet lists every unreconciled transmission with its manufacturer and gap side.
-
3
Microsoft Teams - post the sync audit
WebRun opens Microsoft Teams to post the portal sync audit. - Post an audit summary to the device clinic Microsoft Teams channel with the count reconciled and the count missing
- Break out the gaps by manufacturer so a failing portal connection is obvious
- Link the full Google Sheet for the team to chase each missing transmission
Done when The team has a Teams audit of reconciled and missing transmissions grouped by manufacturer.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it change anything in the manufacturer portals?
No. WebRun only reads each portal to list transmissions and compares them against Octagos. It logs the gaps internally and never edits, deletes, or re-sends anything in a vendor portal, so the audit is read-only.
How does it decide a transmission is missing?
It matches each overnight portal transmission against the Octagos triage queue by patient and time, so any transmission present in a vendor portal but absent from Octagos, or the reverse, is flagged as unreconciled.
Does patient information leave your tools?
No. The audit references patients by initials and manufacturer only, and posts to your own internal Microsoft Teams channel, so no protected health information beyond initials leaves your environment.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.