Smithery is now a part of Arcade.dev! Read more in our announcement here
Create a minimal working OpenEvidence clinical query example. Use when starting a new OpenEvidence integration, testing your setup, or learning basic clinical query patterns. Trigger with phrases...
Verify account access and the Ask evidence-review loop using a synthetic clinical question. Keep inputs minimal, separate observed facts from assumptions, and leave consequential decisions with the named accountable owner.
Use Read, Glob, and Grep to inspect supplied policies, plans, and evidence. Use WebFetch only for current first-party OpenEvidence documentation. Use Write or Edit only when the user requests a named deliverable with an approved destination. Never expose credentials, PHI, recordings, or unrestricted environment output.
Use only the official OpenEvidence web/mobile sign-in or an institution-approved access path. Do not invent API keys, OAuth clients, SDK credentials, service accounts, or private endpoints. Never ask a user to reveal a password, session token, cookie, or recovery code.
Do not create or share accounts; change access, roles, agreements, consent, retention, or security settings; enter PHI; record a conversation; copy content into another system; contact a patient; make a diagnosis or treatment decision; submit billing; transmit a support packet; run a production pilot; or represent vendor capabilities without explicit approval from the accountable owner. A qualified professional remains responsible for clinical decisions.
Return scope, current first-party evidence and date, data classification, workflow or findings, citations reviewed, assumptions rejected, clinical and governance owners, approval state, unresolved risk, and the exact next action. Redact patient and credential data.
| Condition | Response |
|---|---|
| Verification blocked | Use the official account/support path; do not impersonate a professional. |
| No citations visible | Treat onboarding as failed and capture a redacted support packet. |
| Real patient details supplied | Stop, remove them through approved means if possible, and notify the privacy owner. |
This compact example shows the minimum reviewable handoff; adapt fields to the approved workflow without adding sensitive data.
Input:
surface=web; user=verified clinician; question=synthetic guideline comparison
Expected handoff:
access=verified; answer=received; citation=open; patient-data=none
