Agent skill · data analytics · jeremylongshore
openevidence-data-handling
Design a minimum-necessary OpenEvidence data-handling workflow for questions, Visits recordings, notes, and exports. Use when working with OpenEvidence in a healthcare organization. Trigger with "openevidence data handling", "OpenEvidence privacy", or a matching workflow request.
Why this skill is useful
Adds executable scripts for data handling, compliance checks, and de-identification processes specific to healthcare data management.
What it needs
Requires node 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 PHI and Consent Boundary Overview Establish whether data may enter OpenEvidence, who authorizes it, and how outputs move into governed systems. 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 terms recommend removing identifying information before submission and assign users responsibility for lawful content. Covered entities choosing to transmit PHI are governed by the applicable BAA or customer-specific agreement. Visits records conversations; required notice and consent depend on law and organizational policy. 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. Classify the workflow, data elements, users, systems, jurisdiction, retention needs, and whether recording occurs. 2. Read the current Terms, Privacy Policy, Security page, applicable BAA/MSA, and institutional policy. 3. Minimize identifiers and free text; prefer synthetic or de-identified content when patient identity is unnecessary. 4. Document authorization, recording notice and consent, role access, approved export destination, and deletion/retention owner. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/openevidence-data-handling