Provider Booking Journey
After triage determines a GP or physio referral, the member searches for a matching in-network provider. Scheduling is not yet implemented — booking intent is captured client-side only.
Sequence Diagram
API Reference
| Step | Service | Method | Path | Auth | Response |
|---|---|---|---|---|---|
| Get token | Keycloak | POST | /realms/olly/protocol/openid-connect/token | None | access_token |
| List providers | provider | GET | /providers | Member JWT | 200 [{Locator, Name, Specialty}] |
| Filter by specialty | provider | GET | /providers?specialty=GP | Member JWT | 200 filtered list |
| Provider detail | provider | GET | /providers/{locator} | Member JWT | 200 {Locator, Name, ...} |
Notes
- Provider search returns all providers when called with no query params; use
specialtyand/ornetwork_statusto filter. - No booking/scheduling endpoint exists — appointment booking is a P3 gap.
- Credentialing routes (
/credentialing) are admin-only and not part of the member journey.