Patients
Update Patient
Update an existing patient record
PUT
Authentication
This endpoint requires authentication with a Bearer token.Bearer token for authentication
Permissions
- Superusers: Can update any patient record
- Regular users: Can only update their own patient record
Path Parameters
The unique identifier of the patient to updateExample:
1Request Body
All fields from the patient schema must be provided. The request replaces the entire patient record.Patient’s full nameExample:
João SilvaPatient’s email addressExample:
[email protected]Patient’s password (will be hashed before storage)Example:
nova_senhaPatient’s phone numberExample:
11999999999Patient’s CPFExample:
12345678901Patient’s date of birth in ISO format (YYYY-MM-DD)Example:
1990-01-01Street addressExample:
Rua das FloresStreet numberExample:
123Address complement (optional)Example:
Apto 101NeighborhoodExample:
CentroCityExample:
São PauloState (2-letter code)Example:
SPPostal codeExample:
01001000User typeExample:
PACIENTEWhether the patient account is activeExample:
trueWhether the patient has superuser privilegesExample:
falseResponse
Unique identifier for the patient
Patient’s full name
Patient’s email address
Patient’s phone number
Patient’s CPF
Patient’s date of birth
Street address
Street number
Address complement
Neighborhood
City
State
Postal code
User type
Account active status
Superuser status
Error Codes
Patient successfully updated
User does not have permission to update this patient record
Patient with the specified ID does not exist
CPF or email conflicts with another existing user
Notes
- The password field will be automatically hashed before storage
- All fields must be provided even if only updating specific fields
- Email and CPF must remain unique across all users