Skip to content

Status: OpenEvidence API / Hermes Integration

Last updated: 2026-05-29T15:30:23Z

Current state

Brain Lite project created. Research not yet completed in this setup pass.

Latest update

  • Created a dedicated project folder for OpenEvidence API/Hermes integration.
  • Set initial safety boundary: treat OpenEvidence as a potential clinical evidence retrieval tool, not automatically as a Hermes model provider.

Next actions

  1. Research official OpenEvidence API / enterprise / developer access.
  2. Determine if access is OpenAI-compatible, custom REST, MCP-accessible, or browser-only.
  3. Capture vendor/privacy/compliance terms relevant to VIM.
  4. Recommend integration pattern and approvals needed.

Blockers

  • Need verified official source or vendor response for API availability.
  • Need Jeremy/security/clinical direction before any PHI-bearing workflow.

Decisions needed from Jeremy

  • Whether this should stay exploration-only or become a formal vendor/integration evaluation.
  • Who should be clinical and security reviewers if it advances.

Risks to watch

  • Unofficial access patterns may violate terms or be unsafe for production.
  • Clinical citations and freshness must be auditable.
  • HIPAA/BAA status must be verified before any PHI-adjacent use.

Done / shipped

  • Brain Lite project scaffold created.