Drchrono

v1.0.2

DrChrono integration. Manage Patients, Appointments, ClinicalNotes, MedicationOrders, LabOrders, BillingProfiles and more. Use when the user wants to interac...

0· 100·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The skill's name/description (DrChrono integration) matches the instructions (use Membrane to manage patients, appointments, etc.). Minor metadata mismatch: registry metadata declares no required binaries but the SKILL.md expects you to install and run the 'membrane' CLI (installed via npm). This is coherent with the purpose but the metadata omission is an inconsistency to be aware of.
Instruction Scope
SKILL.md confines actions to installing/using the Membrane CLI, authenticating, running pre-built actions, and proxying requests to the DrChrono API. It does not instruct reading unrelated system files or exfiltrating data to arbitrary endpoints beyond the Membrane service it advertises.
Install Mechanism
Installation is manual/instruction-only: it recommends 'npm install -g @membranehq/cli'. Installing a global npm package is a reasonable way to get the required CLI but carries the usual npm provenance risk — the user should confirm the package/source and be comfortable installing global packages on their machine.
Credentials
The skill does not request any environment variables or unrelated credentials. However, it requires a Membrane account and will route DrChrono API calls (and the associated EHR data) through Membrane's service — ensure you trust Membrane for handling protected health information and that this data flow is acceptable for your compliance requirements.
Persistence & Privilege
The skill is user-invocable and not always-enabled; it doesn't request elevated platform privileges and does not modify other skills. The Membrane CLI may store auth tokens locally as part of normal operation, which is expected behavior for a CLI-based integration.
Assessment
This skill is coherent for connecting DrChrono through Membrane, but before installing: 1) Confirm you are comfortable installing a global npm package and verify @membranehq/cli's source (GitHub/npm page). 2) Understand that patient/EHR data will be proxied through Membrane (getmembrane.com) — verify their privacy, security, and compliance (e.g., HIPAA) policies and that you have authorization to transmit PHI. 3) The skill metadata omitted a required binary (the 'membrane' CLI); expect to need npm/node or otherwise obtain the CLI. 4) Prefer running installations in an environment you control and review Membrane's docs or the linked GitHub repo for more details before proceeding.

Like a lobster shell, security has layers — review code before you run it.

latestvk97ddv6x9ms3pk0sgrd7vdbdrh842ehd

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments