Patient frequency compliance using Report evaluation rules
Changed onFrequency compliance aggregates and the paginated patient table for patients with at least one completed clinical session. Dates select ongoing frequency violations that began in the period (Europe/Rome), not patient entry dates. The table defaults to evaluable patients. status and severity narrow the table only; path narrows the table and, together with operator_id, the aggregates. Coordinator role sees only patients under their supervisors.
Request
- Base URL: https://api.corabea.it (the document declares no server; this is the origin it was published from)
- URL: https://api.corabea.it/api/analytics/patient-frequency
- Auth: HTTP bearer
Query parameters
Start of the frequency violation period (YYYY-MM-DD, Europe/Rome).
End of the frequency evaluation period (YYYY-MM-DD), inclusive.
Supervisor of the psychologist or the nutritionist.
Psychologist or nutritionist UUID; either path unless path is set.
Operator profession constants.
Evaluate status, severity and operator_id on this path only.
Comma-separated path status keys (e.g. attivo_psi, monitoraggio).
Case-insensitive patient search.
Defaults to frequency: risk first, then earliest deadline.
Response
Successful Response
Changes
- ▲
for the
queryrequest parameterstatus, default valueevaluablewas added - ○
added
subschema #2to the/response propertyanyOflist for the response status
- ▲
- ○
endpoint added
- ○