Deploy OpenEvidence securely across your organization.
Institutional workspaceInstitutional access active
OpenEvidence is available within the clinical workflow using your organization’s identity and access controls.
Memorial Sloan Kettering Cancer CenterAdvancing precision oncology at the point of careRead announcement 
Mount Sinai Health SystemBringing evidence-based knowledge into the medical recordRead announcement 
Cedars-SinaiEnhancing clinical decision-making with OpenEvidenceRead announcement 
OneOncologyPartnering to improve cancer care nationwideRead announcement 
Boston Children’s HospitalAdvancing AI-powered analysis of clinical practice patternsRead announcement 
Sutter HealthBringing evidence-based insights into physician workflowsRead announcement The evidence for OpenEvidence
“OpenEvidence is currently the best AI tool for medical information.”
Clinician adoption
70%Institutional network
500+Cedars-Sinai Medical Center · NewYork-Presbyterian · Mount Sinai Health System · Penn Medicine · UTMB Health · The Ohio State University Wexner Medical Center · Mass General Brigham · Hurley Medical Center
Evidence foundation
Comprehensive evidenceSelected sources
What institutional access includes
Enterprise deployments establish clear boundaries around PHI, clinician-entered prompts, retention, and deletion. Sensitive data is used to provide the service—not to train models—and your organization's controls are documented before launch.
Visit the Trust Center SOC 2 Type II · HIPAAMake access simple with SSO and a standard institutional login path.
Put a Business Associate Agreement and standard terms in place.
Patient context and clinician-entered prompts may contain PHI. They are handled under your organization’s BAA and used only to deliver, secure, and support the service.
Unlock powerful tools for your physicians with contextual evidence at the point of care.
Set an organization-specific retention policy for PHI and clinician prompts, including an agreed deletion schedule when the relationship ends.
Patient-context records will live in a dedicated clinical data layer, partitioned by FHIR issuer and separated from the primary application database.
OpenEvidence Enterprise brings the full OpenEvidence experience to your organization. Clinicians get secure institutional access, EHR launch, and—where supported—relevant context for your organization; your organization gets one set of agreements, security documentation, data controls, and launch support. Setup can be completed in a day, and most organizations go live within days or weeks.
Your clinicians are already choosing OpenEvidence. Enterprise makes it easier to use at work—integrated into the clinical workflow and supported by one institutional identity, one set of agreements, and clear controls for your organization. It is available at no cost.
Anyone in clinical, technology, security, legal, or administration can start. You do not need to assemble an implementation team first—we will help bring in the right people at each stage and guide your organization through launch.
Share with your organizationOpenEvidence Enterprise is built for organizations that deliver patient care. It is currently available to health systems and provider organizations supporting verified U.S. clinicians. Other types of businesses are not currently eligible for institutional access.
Yes. OpenEvidence supports health systems across EHR environments, and we will identify the integration path available for yours. Your organization can establish institutional access first and add EHR integration when ready.
EHR integration puts OpenEvidence directly in the clinical workflow. Clinicians can launch using their institutional identity, without separately signing in to OpenEvidence at each workstation. Where supported, relevant context for your organization can accompany the launch.
The answer depends on the integration your organization selects. An EHR launch may provide patient context, and clinicians may enter prompts that contain PHI. OpenEvidence uses that information only to provide, secure, and support the requested service. Enterprise PHI and prompts are not used to train models.
Your organization selects an Enterprise retention policy during implementation. The applicable policy covers patient context and clinician-entered prompts, and the agreements document how that data is deleted after termination, subject to limited legal or security obligations.
The Enterprise architecture is designed around a dedicated clinical data layer. Patient-context records will be partitioned by FHIR issuer and kept separate from the primary application database, adding another boundary around sensitive clinical data.
Not without your approval. Institutional access does not by itself authorize OpenEvidence to use your organization’s name or logo or issue an announcement. Any publicity is handled through a separate, mutually approved process.