Overlay Rollout Playbook
Scope the connection, review the workflow, and evaluate the pilot before deciding on a transition.
Overview
Integration availability depends on your EHR and the workflow you want to use. We confirm the data source, permissions, and any read or write connection before a pilot begins.
This playbook describes evaluation steps, not a promise that every connection or transition is available. Clinical outputs require clinician review before use or signing.
Day one
Three setup questions to resolve before a pilot.
Confirm the specific EHR, supported data access, and permissions.
Agree which data the selected workflow needs and how it will be reviewed.
Confirm whether a specific write connection is supported. The physician reviews the draft and decides what happens next.
Week by week rollout
An illustrative checklist for a 30-day, one-provider pilot. The schedule depends on confirmed connections and scope; it is not a deployment promise.
Week 0: Success criteria and scope
- Define success metrics: time saved, inbox throughput, CGM capture rate
- Select one provider and a focused workflow for the published pilot
- Confirm required access, permissions, and supported connections before setting dates
- Identify pilot champion and operations lead
Week 1: Evaluate the agreed workflow
- Begin the agreed workflow only after setup and review requirements are met
- Daily check ins with pilot pod for first 3 days
- Collect baseline metrics before Thyra vs after
- Identify friction points and adjust configuration
Week 2: Review pilot findings
- Review findings within the agreed one-provider pilot scope
- Measure inbox throughput improvement
- Measure time saved per visit
- Record additional workflow needs for a separate scope discussion
Week 3: Review output handling
- Confirm any supported note connection and required clinician review
- Confirm supported task handling and follow-up responsibilities
- Verify clinician review before any clinical output is used or signed
- Audit outputs for quality and completeness
Week 4: Decide migrate timeline
- Review pilot metrics with leadership
- Decide: continue overlay, or set transition date
- If transition: plan template migration, staff training, billing cutover
- Sign post pilot agreement if continuing
Write back modes
The following are scopes to evaluate, not universally available modes. Any read or write connection must be confirmed for the specific EHR and workflow before setup.
| Mode | When to use | Risk control |
|---|---|---|
| Read only | Initial pilot validation. Clinicians test without affecting source chart. | Confirm access scope and logging; read-only access still requires data-handling review. |
| Note write back | Only after the specific write connection and clinician review workflow are confirmed. | Review workflow ensures clinician approval before write. |
| Tasks and follow ups | When inbox throughput is stable and routing rules are tuned. | Confirm ownership, escalation, and tracking before use. |
| Orders and billing ready packet | Only within a confirmed transition scope and reviewed clinical workflow. | Order sets and charge capture require explicit clinician sign off. |
Security model
Review the data-handling requirements and available documentation for the selected connection before sharing patient information.
- Scoped access: Confirm the resources and permissions required by the selected workflow.
- Audit trails: Confirm what events are logged, who can access them, and how long they are retained.
- Least privilege: Agree the access boundaries and any synchronization behavior before setup.
- SSO: Confirm supported authentication; do not assume existing sign-on is available.
Transition plan
Consider a transition only after evaluating the pilot and confirming operational requirements.
What triggers transition?
- Clinicians prefer Thyra workflows to current EHR
- Time saved metrics are consistent and measurable
- Leadership approves migration timeline
- Operations has capacity for cutover
What migrates?
- Templates and note structures
- Problem lists and medication reconciliation
- Staff workflows and routing rules
- Patient demographics and encounter history
What stays stable?
- Billing operations until cutover date
- Patient portal access during transition
- Scheduling system until you choose to switch
FAQ
How long does overlay setup take?
Integration availability depends on your EHR and the workflow you want to use. We confirm the data source, permissions, and any read or write connection before a pilot begins.
Can we limit which clinicians see Thyra?
Confirm the supported authentication method, roles, and access limits for the selected workflow before setup.
What if we decide not to transition?
You can use Thyra as an overlay indefinitely. Transition is a choice, not a requirement.
What data does Thyra access?
Confirm the required data source, permissions, fields, and retention for the selected workflow before sharing data.
Is there a minimum contract?
Pilot is 30 days. After pilot, month to month or annual options are available.
Ready to start?
Request a walkthrough to see how Thyra fits your current EHR.