Skip to main content
DELETE
/
prontuario
/
{prontuario_id}
Delete Medical Record
curl --request DELETE \
  --url https://api.example.com/prontuario/{prontuario_id}
{
  "message": "Prontuário deletado com sucesso."
}
This endpoint is currently commented out in the VidaPlus API codebase and is not available for use. Medical record deletion has been disabled, likely for data integrity and compliance reasons.

​
Current Implementation Status

The delete endpoint is disabled in the source code. According to the implementation:
  • The endpoint would require superuser permissions
  • It would permanently delete the medical record and all associated data (consultations, prescriptions, exams) due to cascade delete rules
  • The functionality is currently commented out for safety

​
Path Parameters

​
prontuario_id
integer
required
The unique identifier of the medical record to delete

​
Expected Behavior (When Enabled)

If this endpoint were enabled, it would:

​
Authentication

Require a valid JWT token with superuser permissions.

​
Response

{
  "message": "Prontuário deletado com sucesso."
}

​
Error Responses

{
  "detail": "Prontuário não encontrado."
}

{
  "detail": "Você não tem permissão para deletar este prontuário"
}

​
Notes

  • This endpoint is disabled in production for data protection
  • Deleting a medical record would cascade delete all associated consultations, prescriptions, and exams
  • Only superusers would have permission to delete medical records
  • For data compliance and audit trail purposes, consider marking records as inactive rather than deleting them

​
Alternative Approach

Instead of deleting medical records, consider:
  • Implementing a soft delete mechanism with an is_active flag
  • Archiving old records rather than removing them
  • Maintaining audit trails for compliance with healthcare regulations (HIPAA, GDPR, etc.)

Build docs developers (and LLMs) love

Get started for freeTalk to us