Home / Demos / EHR write-back (sandbox)
Designed to deliver alerts into the EHR providers already use.
Providers work in their EHR, so alerts should reach them there. Health-Connect's EHR write-back is designed to deliver them into the EHR as cases, routed to the right provider or queue. It is built and tested against a vendor sandbox only, and is not live with any customer. This walkthrough covers the admin side: per-connection settings and routing by recommendation class, close-reason mapping, connection and global pause, the needs-attention list, an audited hold release, and the read-only write-back panel in the review workspace.
What you'll see
- One settings row per connection; production is not permitted and every change is audited
- Routing by class: orders to a provider, care-team items and documentation to queues
- Pause a connection, or all write-back, with held deliveries rather than failures
- A needs-attention list and bundle timeline that show ids and states, never patient data
Chapters
- 0:00 Meeting providers in their EHR
- 0:16 Health-Connect stays optional
- 0:25 Connection settings
- 0:42 Routing by recommendation class
- 0:54 Mapping close reasons
- 1:13 Connection and global pause
- 1:29 Needs-attention list
- 1:48 Bundle detail and timeline
- 2:03 Audited hold release
- 2:16 Write-back panel in the review workspace
- 2:32 Built and sandbox only
- 2:43 About this recording
Transcript
0:04 Providers work in their EHR. Health-Connect's EHR write-back is designed to deliver alerts into the provider's EHR. It is built, and it is sandbox only. It isn't live with any customer yet.
0:16 Health-Connect itself stays optional: a place to dig into the data behind an alert, or to work a prior authorization.
0:25 Each connection has one settings row, badged Sandbox. This synthetic athena sandbox connection is disabled, production isn't permitted, and every saved change is audited.
0:42 Routing works by recommendation class. Orders go to a provider, care-team items go to a queue, and documentation goes to the CDI department queue.
0:54 Close reason ids map Health-Connect outcomes, dismissed, expired, or superseded, to the EHR's own action reasons, so a sandbox case closes with the right reason.
1:13 Any connection can be paused with a reason, and a global pause stops all write-back. Pending deliveries are held, not failed.
1:29 The needs-attention list shows only the bundles an admin has to look at, with ids, states, and codes, never patient data. This seeded sandbox bundle carries fixture history: its case was created in the sandbox earlier, and it's now held after too many delivery attempts.
1:48 The bundle page explains why it's held, lists its items, and keeps an event timeline. Admin actions never send anything themselves. The dispatcher does all sending.
2:03 Releasing the hold is audited and lands on the timeline. On this local stack no dispatcher runs, so nothing new is sent and no vendor is called.
2:16 In the review workspace, the alert carries a read-only EHR write-back panel, badged Sandbox: the case number, the route, and the delivery state. That delivery is seeded sandbox fixture data, and nothing on this stack reached a vendor.
2:32 EHR write-back is built and sandbox only, designed to meet providers in the EHR they already use, with Health-Connect there for deeper review and prior authorization.
2:43 A note on this recording: the narration uses a synthetic voice, and all data shown is synthetic demo data, not a live customer deployment.
Want to see this on your workflow?
We run walkthroughs against realistic synthetic populations that match your case mix.
Request a walkthrough