Skip to main content
DELETE
/
api
/
patients
/
:id
curl -X DELETE "https://api.saludya.com/api/patients/pat_1a2b3c4d5e6f" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"
{
  "id": "pat_1a2b3c4d5e6f",
  "deleted": true,
  "deleted_at": "2024-03-06T17:00:00Z"
}

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/DUVAN100/saludya-api/llms.txt

Use this file to discover all available pages before exploring further.

This is a destructive operation that permanently removes Protected Health Information (PHI). Ensure you have proper authorization and consider data retention policies before deletion. This action is irreversible and logged for compliance.

Path Parameters

id
string
required
Unique patient identifier (e.g., pat_1a2b3c4d5e6f)

Query Parameters

force
boolean
default:"false"
Force delete even if patient has associated appointments. If false, deletion will fail when active appointments exist.

Response

id
string
ID of the deleted patient
deleted
boolean
Confirmation that the patient was deleted
deleted_at
string
Timestamp when the patient was deleted
curl -X DELETE "https://api.saludya.com/api/patients/pat_1a2b3c4d5e6f" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json"
{
  "id": "pat_1a2b3c4d5e6f",
  "deleted": true,
  "deleted_at": "2024-03-06T17:00:00Z"
}

Data Retention and Compliance

When a patient is deleted:
  • All PHI is permanently removed from active databases
  • Audit logs are retained for compliance (minimum 7 years per HIPAA)
  • Associated appointments may be anonymized rather than deleted
  • Billing records are retained per regulatory requirements
  • Backup data follows your organization’s retention policy
Consider implementing a “soft delete” or “archive” feature for your application to maintain data integrity while marking records as inactive. Contact support for information about data archival options.

Build docs developers (and LLMs) love