medplum / medplum / 26911287540

92%

push

github

Include requested time slot in scheduling availability error message (#9306)

* Include blocking Slot references in scheduling availability error

When a requested appointment time slot is not available, the error
response now includes structured diagnostics indicating which existing
Slot resources are blocking the request and which Schedule they belong
to. This allows clients to decide whether to retry with a different
time slot or choose an alternative Schedule.

The OperationOutcome now uses:
- code: 'conflict' (more semantically accurate than 'invalid')
- diagnostics: includes Slot references, their time ranges, and the
  Schedule reference (e.g., 'Blocked by 2 existing slot(s) on
  Schedule/123: Slot/456 (2024-01-15T09:00 - 2024-01-15T09:30), ...')

This is particularly useful when booking against multiple Schedule
resources, as clients can identify which specific schedule has the
conflict.

Addresses the TODO:
  'tie back to specific slot that has problem'

Signed-off-by: Rohith Vangalla <Reachrohithv@gmail.com>

* Use structured JSON in diagnostics for blocking slot details

Per reviewer feedback, replace the human-readable diagnostics string
with a JSON string that automated tooling can parse programmatically.

The diagnostics field now contains:
{
  "schedule": "Schedule/abc-123",
  "blockingSlots": [
    { "reference": "Slot/slot-1", "start": "...", "end": "...", "status": "busy" }
  ]
}

This follows the existing Medplum pattern of putting structured JSON
in OperationOutcome.issue.diagnostics for machine readability.

Signed-off-by: Rohith Vangalla <Reachrohithv@gmail.com>

---------

Signed-off-by: Rohith Vangalla <Reachrohithv@gmail.com>

22880 of 25654 branches covered (89.19%)

Branch coverage included in aggregate %.

5 of 5 new or added lines in 1 file covered. (100.0%)

36091 of 38334 relevant lines covered (94.15%)

23591.51 hits per line