Please report security issues privately via GitHub Security Advisories (Report a vulnerability) rather than opening a public issue. You'll get an acknowledgement within a few business days.
The latest 0.x release receives security fixes. Older versions do not.
This server touches Protected Health Information, so its security posture is part of its design, not an afterthought:
- Read-only. No tool writes, schedules, or creates data. The FHIR scope
defaults to
system/*.read. - No data at rest. The server ships code, not a hosted data service. It holds only a short-lived access token in memory, minted per run from a signed JWT assertion (SMART backend-services). Nothing is persisted.
- Audit logging. Every tool call is logged (stderr, plus an optional file) with an outcome. Long free-text parameters are redacted, and tokens and private keys are never logged.
- Sanitized errors. FHIR errors surface as status codes, not raw upstream payloads, so PHI can't leak through an error message.
- Secrets via env only. The private key is provided through
PF_PRIVATE_KEYand validated at startup; it is never committed and is gitignored.
You, the deployer, are the covered entity or business associate. You are responsible for your own Business Associate Agreement (BAA) with Veradigm/Practice Fusion and for running this in a HIPAA-appropriate environment. This document is not legal advice.