Patient-specific literature in EHR

Cedars-Sinai turns OpenEvidence from a smart reference tool into a patient-specific decision layer inside the chart. Instead of a doctor typing a generic question and then mentally adjusting for a patient with kidney disease, a drug allergy, and prior surgery, the system can pull those facts from the EHR and shape the literature search around them. That makes the output more usable in the moment of care, and it pushes OpenEvidence closer to the clinical workflow territory long owned by Epic modules and UpToDate.1 2 3 4

• The concrete step change is context injection. Cedars-Sinai said clinicians can retrieve literature relevant to an individual patient profile, using prior procedures, comorbidities, medications, and allergies from the EHR, while OpenEvidence does not store that patient data. That is meaningfully different from a standalone medical search box.1 2
• The rollout also shows a progression in enterprise depth. Sutter Health put OpenEvidence into Epic for natural language evidence search in February 2026. Mount Sinai expanded that model in March 2026 to physicians, nurses, and pharmacists. Cedars-Sinai added patient level tailoring in May 2026, which is a harder and more valuable integration.1 3 4
• This matters commercially because OpenEvidence is moving from an ad supported clinician app toward a hospital system product that can replace time spent across separate tools like UpToDate for literature, while sitting beside documentation, coding, and prescribing workflows. That is how a reference product becomes infrastructure.2 5 6

The next step is a single screen where external studies, a hospital’s own care pathways, and patient specific chart context all show up together before an order is placed or a note is signed. Cedars-Sinai has already said it plans to layer internal protocols into the product, which points toward OpenEvidence becoming a full point of care reasoning surface inside the EHR.1 2