In Basket Message Drafts
Epic and Microsoft
Generates draft replies to patient portal messages inside the EHR inbox, with the clinician editing and sending.
At A Glance
- Vendor
- Epic and Microsoft
- Category
- Inbox and Patient Communication
- Where it runs
- EHR-embedded
- Primary user
- Physicians and care teams
- Regulatory status
- Not a regulated device
Patient messaging volume grew enormously after portals became standard and no corresponding time was created to answer it. Inbox burden now rivals documentation burden as a burnout driver, which is why this arrived immediately behind ambient documentation.
Published early evaluations have been mixed on time saved and more positive on perceived effort and message quality, which is a real finding rather than a disappointing one. Reducing the cognitive cost of composing a careful reply is worth something even when the clock does not move.
Where It Is Used
- Drafting replies to routine patient portal messages
- Reducing inbox time outside clinic hours
- Standardizing tone and completeness in written patient communication
Limitations Worth Knowing
Drafts are generated from chart context and can include or imply clinical content the clinician did not intend to communicate. Empathetic phrasing generated by a model and sent under a physician's name raises a disclosure question the field has not settled. Every draft needs to be read as if you wrote it, because you are about to have.
This tool is not an FDA-cleared medical device. Nothing here is a procurement recommendation, and product capabilities in this category change quickly ... confirm current functionality, data handling, and contractual terms directly with the vendor.