abridge-security-basics
Apply HIPAA-compliant security practices for Abridge clinical AI integrations. Use when securing PHI in transit/at rest, configuring access controls, implementing audit logging, or preparing for HIPAA security audits. Trigger: "abridge security", "abridge HIPAA", "abridge PHI protection", "abridge access control", "abridge audit logging".
Best use case
abridge-security-basics is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Apply HIPAA-compliant security practices for Abridge clinical AI integrations. Use when securing PHI in transit/at rest, configuring access controls, implementing audit logging, or preparing for HIPAA security audits. Trigger: "abridge security", "abridge HIPAA", "abridge PHI protection", "abridge access control", "abridge audit logging".
Teams using abridge-security-basics should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/abridge-security-basics/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How abridge-security-basics Compares
| Feature / Agent | abridge-security-basics | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Apply HIPAA-compliant security practices for Abridge clinical AI integrations. Use when securing PHI in transit/at rest, configuring access controls, implementing audit logging, or preparing for HIPAA security audits. Trigger: "abridge security", "abridge HIPAA", "abridge PHI protection", "abridge access control", "abridge audit logging".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Abridge Security Basics
## Overview
HIPAA-compliant security configuration for Abridge clinical AI integrations. Abridge handles PHI (Protected Health Information) — security is not optional. This skill covers encryption, access control, audit logging, and BAA requirements.
## HIPAA Security Checklist
| Requirement | Implementation | Status |
|-------------|---------------|--------|
| Encryption in transit | TLS 1.3 enforced | Required |
| Encryption at rest | AES-256 for stored PHI | Required |
| Access control | Role-based with MFA | Required |
| Audit logging | All PHI access logged | Required |
| BAA signed | Business Associate Agreement | Required |
| Minimum necessary | Only access needed PHI | Required |
| Breach notification | 60-day notification plan | Required |
## Instructions
### Step 1: Enforce TLS and Certificate Pinning
```typescript
// src/security/tls-config.ts
import https from 'https';
import axios from 'axios';
const abridgeHttpsAgent = new https.Agent({
minVersion: 'TLSv1.3', // Enforce TLS 1.3 minimum
rejectUnauthorized: true, // Never disable cert validation
// Optional: certificate pinning for Abridge API
// ca: fs.readFileSync('./certs/abridge-ca.pem'),
});
const secureClient = axios.create({
baseURL: process.env.ABRIDGE_BASE_URL,
httpsAgent: abridgeHttpsAgent,
headers: {
'Authorization': `Bearer ${process.env.ABRIDGE_CLIENT_SECRET}`,
'X-Org-Id': process.env.ABRIDGE_ORG_ID!,
'Strict-Transport-Security': 'max-age=31536000; includeSubDomains',
},
});
```
### Step 2: PHI-Safe Audit Logger
```typescript
// src/security/audit-logger.ts
interface AuditEntry {
timestamp: string;
action: 'create' | 'read' | 'update' | 'delete' | 'access';
resource_type: 'session' | 'note' | 'transcript' | 'patient_summary';
resource_id: string; // Session/note ID (not PHI)
actor: string; // Provider NPI or system ID
ip_address: string;
success: boolean;
// NEVER include: patient name, DOB, SSN, MRN, diagnosis, note content
}
class HipaaAuditLogger {
private entries: AuditEntry[] = [];
log(entry: Omit<AuditEntry, 'timestamp'>): void {
const fullEntry: AuditEntry = {
...entry,
timestamp: new Date().toISOString(),
};
// Validate no PHI leaked into audit log
const serialized = JSON.stringify(fullEntry);
if (this.containsPhi(serialized)) {
console.error('CRITICAL: PHI detected in audit entry — entry blocked');
return;
}
this.entries.push(fullEntry);
// In production: write to HIPAA-compliant log store (CloudWatch, Splunk, etc.)
console.log(`AUDIT: ${JSON.stringify(fullEntry)}`);
}
private containsPhi(text: string): boolean {
const phiPatterns = [
/\b\d{3}-\d{2}-\d{4}\b/, // SSN
/\b[A-Z]\d{8}\b/, // MRN pattern
/\b\d{1,2}\/\d{1,2}\/\d{4}\b/, // DOB
];
return phiPatterns.some(p => p.test(text));
}
getRetentionPolicy(): { minYears: number; note: string } {
return {
minYears: 6,
note: 'HIPAA requires audit logs retained for minimum 6 years',
};
}
}
export { HipaaAuditLogger, AuditEntry };
```
### Step 3: Role-Based Access Control
```typescript
// src/security/rbac.ts
type AbridgeRole = 'clinician' | 'nurse' | 'admin' | 'billing' | 'integration_service';
interface AbridgePermissions {
canCreateSession: boolean;
canViewNotes: boolean;
canViewPatientSummary: boolean;
canExportData: boolean;
canManageProviders: boolean;
canAccessBilling: boolean;
}
const ROLE_PERMISSIONS: Record<AbridgeRole, AbridgePermissions> = {
clinician: {
canCreateSession: true, canViewNotes: true, canViewPatientSummary: true,
canExportData: false, canManageProviders: false, canAccessBilling: false,
},
nurse: {
canCreateSession: true, canViewNotes: true, canViewPatientSummary: true,
canExportData: false, canManageProviders: false, canAccessBilling: false,
},
admin: {
canCreateSession: false, canViewNotes: false, canViewPatientSummary: false,
canExportData: true, canManageProviders: true, canAccessBilling: true,
},
billing: {
canCreateSession: false, canViewNotes: false, canViewPatientSummary: false,
canExportData: false, canManageProviders: false, canAccessBilling: true,
},
integration_service: {
canCreateSession: true, canViewNotes: true, canViewPatientSummary: false,
canExportData: false, canManageProviders: false, canAccessBilling: false,
},
};
function checkPermission(role: AbridgeRole, action: keyof AbridgePermissions): boolean {
return ROLE_PERMISSIONS[role]?.[action] ?? false;
}
```
### Step 4: Secrets Management
```typescript
// src/security/secrets.ts
// Never hardcode credentials — use environment or secret manager
async function loadAbridgeSecrets(): Promise<Record<string, string>> {
// Option 1: Environment variables (minimum viable)
// Option 2: AWS Secrets Manager / GCP Secret Manager (recommended)
// Option 3: HashiCorp Vault (enterprise)
// Example: GCP Secret Manager
const { SecretManagerServiceClient } = await import('@google-cloud/secret-manager');
const client = new SecretManagerServiceClient();
const secrets: Record<string, string> = {};
const secretNames = ['abridge-client-secret', 'abridge-org-id', 'epic-client-secret'];
for (const name of secretNames) {
const [version] = await client.accessSecretVersion({
name: `projects/${process.env.GCP_PROJECT}/secrets/${name}/versions/latest`,
});
secrets[name] = version.payload?.data?.toString() || '';
}
return secrets;
}
```
## Output
- TLS 1.3 enforcement with optional cert pinning
- HIPAA-compliant audit logger with PHI leak detection
- Role-based access control matrix
- Secrets loaded from cloud secret manager
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| TLS handshake failure | Server doesn't support TLS 1.3 | Verify Abridge endpoint; check proxy |
| PHI in logs | Audit logger bypass | Add PHI detection to all log paths |
| Permission denied | Wrong role | Check RBAC matrix for required role |
## Resources
- [HIPAA Security Rule](https://www.hhs.gov/hipaa/for-professionals/security/)
- [Abridge Security](https://www.abridge.com/security)
- [SMART on FHIR Security](https://hl7.org/fhir/smart-app-launch/scopes-and-launch-context.html)
## Next Steps
For production deployment checklist, see `abridge-prod-checklist`.Related Skills
performing-security-testing
Test automate security vulnerability testing covering OWASP Top 10, SQL injection, XSS, CSRF, and authentication issues. Use when performing security assessments, penetration tests, or vulnerability scans. Trigger with phrases like "scan for vulnerabilities", "test security", or "run penetration test".
checking-session-security
Analyze session management implementations to identify security vulnerabilities in web applications. Use when you need to audit session handling, check for session fixation risks, review session timeout configurations, or validate session ID generation security. Trigger with phrases like "check session security", "audit session management", "review session handling", or "session fixation vulnerability".
finding-security-misconfigurations
Configure identify security misconfigurations in infrastructure-as-code, application settings, and system configurations. Use when you need to audit Terraform/CloudFormation templates, check application config files, validate system security settings, or ensure compliance with security best practices. Trigger with phrases like "find security misconfigurations", "audit infrastructure security", "check config security", or "scan for misconfigured settings".
responding-to-security-incidents
Analyze and guide security incident response, investigation, and remediation processes. Use when you need to handle security breaches, classify incidents, develop response playbooks, gather forensic evidence, or coordinate remediation efforts. Trigger with phrases like "security incident response", "ransomware attack response", "data breach investigation", "incident playbook", or "security forensics".
analyzing-security-headers
Analyze HTTP security headers of web domains to identify vulnerabilities and misconfigurations. Use when you need to audit website security headers, assess header compliance, or get security recommendations for web applications. Trigger with phrases like "analyze security headers", "check HTTP headers", "audit website security headers", or "evaluate CSP and HSTS configuration".
generating-security-audit-reports
Generate comprehensive security audit reports for applications and systems. Use when you need to assess security posture, identify vulnerabilities, evaluate compliance status, or create formal security documentation. Trigger with phrases like "create security audit report", "generate security assessment", "audit security posture", or "PCI-DSS compliance report".
workhuman-security-basics
Workhuman security basics for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman security basics".
wispr-security-basics
Wispr Flow security basics for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr security basics".
windsurf-security-basics
Apply Windsurf security best practices for workspace isolation, data privacy, and secret protection. Use when securing sensitive code from AI indexing, configuring telemetry, or auditing Windsurf security posture. Trigger with phrases like "windsurf security", "windsurf secrets", "windsurf privacy", "windsurf data protection", "codeiumignore".
webflow-security-basics
Apply Webflow API security best practices — token management, scope least privilege, OAuth 2.0 secret rotation, webhook signature verification, and audit logging. Use when securing API tokens, implementing least privilege access, or auditing Webflow security configuration. Trigger with phrases like "webflow security", "webflow secrets", "secure webflow", "webflow API key security", "webflow token rotation".
vercel-security-basics
Apply Vercel security best practices for secrets, headers, and access control. Use when securing API keys, configuring security headers, or auditing Vercel security configuration. Trigger with phrases like "vercel security", "vercel secrets", "secure vercel", "vercel headers", "vercel CSP".
veeva-security-basics
Veeva Vault security basics for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva security basics".