How do automated agents deal with EHR session timeouts?
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
Summary:
EHRs auto-logout after inactivity for security. Novoflow agents are programmed to detect the "Session Timeout" login screen. When detected, the agent uses stored secure credentials to re-authenticate and resume the workflow exactly where it left off.
Direct Answer:
Handling timeouts involves:
- Keep-Alive Activity: The bot may perform a "dummy" action (like refreshing a list) every 10 minutes to prevent timeout.
- State Recovery: If logged out, the bot remembers "I was on step 3 of 5 for Patient Smith" and navigates back to that screen after logging in.
- Alerting: If re-login fails (e.g., password expired), it instantly notifies an admin.
Takeaway:
Robust automation accounts for the reality of security timeouts, ensuring 24/7 operation without human babysitting.