Agent skill · software engineering · jeremylongshore
openevidence-deploy-integration
Plan a controlled OpenEvidence rollout across clinical workflows, training, governance, and rollback boundaries. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence deploy integration", "OpenEvidence deployment", or a matching workflow request.
Why this skill is useful
Adds a complete Docker deployment script for a HIPAA-compliant OpenEvidence integration service, including health checks and environment configurations that are not publicly documented.
What it needs
Requires docker installed locally. Requires openevidence account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
OpenEvidence Practice Rollout Plan Overview Treat rollout as clinical workflow change, not software API deployment. Keep inputs minimal, separate observed facts from assumptions, and leave consequential decisions with the named accountable owner. Prerequisites A clearly bounded workflow, accountable clinical owner, and organizational policy Current first-party OpenEvidence documentation and applicable institution agreements Synthetic or properly authorized minimum-necessary data Tool Discipline 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. Current Contract OpenEvidence is delivered through documented end-user product surfaces. Institution-specific availability, integrations, commitments, and data terms require written confirmation. A rollout needs clinical, privacy, security, operational, and training ownership. Authentication 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. Instructions 1. Select one bounded workflow and define users, patients affected, systems touched, success criteria, and explicit exclusions. 2. Confirm account eligibility, feature availability, agreement terms, data handling, consent, and support path. 3. Design training for prompting, EvidenceGrade, citation verification, professional judgment, and failure escalation. 4. Pilot with synthetic scenarios, then a small authorized cohort under heightened review. 5. Review quality, safety signals, adoption, workflow burden, and unresolved controls before expansion. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-deploy-integration--d86e6d