Exam pendency

A Pendency represents an occupational exam obligation for an employee — hiring, dismissal, periodic, return to work or risk change. It is the record that tracks the lifecycle from the exam request to completion (ASO issued) or cancellation.

Exam types (`type_exam`)

Code	Meaning	When it happens
`HIRING`	Pre-employment	On employee hiring.
`DISMISSAL`	Dismissal	On dismissal.
`PERIODIC`	Periodic	Periodically, per the organization’s parameters.
`RETURN`	Return to work	When returning after leave.
`RISK_CHANGE`	Risk change	When the employee’s hierarchy/risk changes.

The table above covers the most common types. The response may carry others, such as INTERN_HIRING, PUNCTUAL, CRITICAL_ACTIVITY, APPOINTMENT, APPOINTMENT_RETURN, MEDICAL_LEAVE, INFIRMARY and THIRD_PARTY, plus ANAMNESE and EMPLOYEE_ACTION, which are legacy from the source system and must not be used. The full list, with the meaning of each one, is in the pendency listing.

Lifecycle

`status`	Meaning (EN)	What it means
`ON_HOLD`	On hold	Created with the employee notification scheduled for a future date.
`PENDING`	Pending	Awaiting scheduling.
`PRE_SCHEDULED`	Pre-scheduled	Scheduling under negotiation, with no confirmed date.
`SCHEDULED`	Scheduled	Exam booked at a clinic.
`MISSING_OHC`	Missing ASO	The exam was performed and Salú is chasing the ASO at the clinic.
`DONE`	Done	ASO received, validated and attached; `concluded_at` is filled.
`ABSENT`	Absent	The employee did not show up for the booked exam.
`NO_RESPONSE`	No response	The employee did not answer the scheduling contacts.
`CANCELED`	Canceled	Closed without the exam being performed.

A performed exam is not a completed pendency. Performing the exam moves the pendency to MISSING_OHC; it only becomes DONE when the ASO is received, validated and attached. The ohc_status field tracks that document stage in parallel with status.

Clinic scheduling and performing the exam are managed inside the Salú platform — there is no public endpoint to schedule. Through the public API you create, list and cancel pendencies, and track the status.

Create fields

Field	Required	Description
`employee_id`	yes	Employee the exam targets.
`type_exam`	yes	Exam type (see table above).
`send_email`	yes	If `true`, triggers communication to the employee.
`send_date`	no	Send date/time (defaults to “now” when `send_email = true`).
`exam_date`	no	Expected exam date.

To cancel, provide the pendency_id and, optionally, a note with the reason.

Deadlines: `sla` vs `due_date`

They are two different dates and are not interchangeable:

Field	Whose deadline it is	How it is defined
`sla`	Internal to Salú — by when operations must handle and schedule the pendency.	An operational target agreed with the client. It is not a legal deadline.
`due_date`	The exam’s — by when the exam must happen.	The event’s reference date (hiring, dismissal, etc.) plus the exam type’s window, skipping weekends. By default the pre-employment exam is due one day before hiring and the dismissal exam ten days after dismissal; each organization may have its own windows.

due_date is computed when the pendency is created and is not recomputed afterwards. Changing the employee’s admission or dismissal date does not move the stored deadline.

Dates and time zone

Every date/time field of a pendency is returned in UTC and without an offset (e.g. 2026-09-11T13:45:02). sla and due_date are dates, served as date/times at midnight.

Field	Question it answers	Watch out
`schedule_appointment_time`	”When was the exam booked for?”	It comes filled on open pendencies, with a future date. Do not use it as the completion date.
`concluded_at`	”When was the pendency completed?”	Only filled when `status = DONE`.

Início

PT-BR

EN

Exam types (`type_exam`)

Lifecycle

Create fields

Deadlines: `sla` vs `due_date`

Dates and time zone

Endpoints

List pendencies

Create pendency

Cancel pendency

​Exam types (type_exam)

​Lifecycle

​Create fields

​Deadlines: sla vs due_date

​Dates and time zone

​Endpoints

List pendencies

Create pendency

Cancel pendency

Exam types (`type_exam`)

Lifecycle

Create fields

Deadlines: `sla` vs `due_date`

Dates and time zone

Endpoints