T09 · Insecure Skill Coding Practices
- Location
references/examples.md:1191- Finding
DICOM data is persisted before de-identification
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This healthcare coding skill is domain-relevant, but its production-like examples handle patient data, recordings, billing, and clinical records with important safeguards missing or overstated.
Install only if you want a healthcare-development reference skill and will treat its code as illustrative, not production-ready. Review and harden any generated healthcare code with qualified security, clinical, legal, and compliance experts before it touches real patient data, telemedicine recordings, billing, or operational systems.
references/examples.md:1191DICOM data is persisted before de-identification
references/examples.md:1291Telemedicine consultation operations lack participant authorization
references/examples.md:974Raw HL7 message content may disclose PHI through application logs
references/examples.md:296Password hashes are compared using non-constant-time string equality
Referenced artifact was not completely inspected
> 📎 **Code example 1** (typescript) — see [references/examples.md](references/examples.md)
Referenced artifact was not completely inspected
> 📎 **Code example 1** (typescript) — see [references/examples.md](references/examples.md)
The example explicitly claims HIPAA-compliant comprehensive audit logging, but several clinically significant flows mutate records without corresponding immutable audit events. In a healthcare context, missing audit coverage undermines breach investigation, non-repudiation, and regulatory accountability, and can let unauthorized changes or access go undetected.
This markdown file embeds code that reads sensitive environment variables such as JWT and database secrets and configures database connectivity, but the surrounding markdown provides no warning that the example handles credentials and protected health information. Under the markdown-file criteria, the description should disclose behaviors that affect privacy or system integrity when presenting code that accesses secrets and persists sensitive data.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
},
fhir: {
version: 'R4',
baseUrl: process.env.FHIR_BASE_URL || 'https://api.healthcare.org/fhir',
supportedFormats: ['application/fhir+json', 'application/fhir+xml'],
},
security: {
The example writes audit activity to a local file and also logs to the console, which can expose sensitive metadata about PHI access through process logs, terminals, aggregators, or misconfigured collectors. In healthcare systems, even access metadata can be sensitive and local file/console sinks are often insufficiently protected or retained.
The manifest describes a healthcare technology specialist focused on standards, compliance, EHR/EMR systems, device integration, and healthcare analytics/AI. This section goes further by creating and managing video consultations, recording sessions, sending notifications, generating consultation summaries, and creating billing records, which are product-level operational capabilities not clearly implied by the stated scope.
The code conditionally records telemedicine consultations based only on an environment flag, without any demonstrated consent capture, jurisdiction checks, participant notification, or retention safeguards. In a telehealth context this can lead to unlawful recording of highly sensitive patient interactions and large-scale privacy exposure.