Collect a complete symptom assessment
Availability: proposed. Atlas has patient assessment use cases; partner delegation and assessment access policy are release prerequisites.
Read the versioned catalog
GET /symptoms returns selectable definitions and a catalog version. Present that defined catalog to the patient and preserve its version for submission.
Confirm a complete assessment
PUT /users/{userId}/symptom-assessment
Authorization: Bearer <authorized-delegated-token>
Idempotency-Key: synthetic-assessment-001
Content-Type: application/json
{
"catalogVersion": "synthetic-catalog-v1",
"expectedRevision": 0,
"selected": [{ "symptomId": "synthetic-symptom-1", "score": 6 }]
}
Catalog and symptom IDs above are illustrative; use returned catalog values. expectedRevision: 0 creates the first assessment. Selected symptoms have scores 1–10 and unique IDs. Every unselected symptom in that catalog records score 0. Symptoms outside the catalog remain unassessed.
This is a complete assessment, not a patch to a small subset of symptoms. Show the patient a confirmation step before submitting. A partner backend cannot invent patient authorship through request fields.
Read confirmed evidence
Use GET /users/{userId}/symptom-assessment for the current assessment, and GET /users/{userId}/symptom-assessments/{assessmentId} for an immutable revision. Preserve the assessment ID when it is used as interview evidence.
Handle concurrent edits
On a stale revision, the proposed endpoint returns 409. Re-read the current assessment, reconcile with the patient, and submit a new confirmed revision. Network retries reuse the original idempotency key and payload. Do not automatically overwrite another confirmed submission.