slug: zocdoc
provider: Zocdoc
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Healthcare Providers
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 3
edges:
- tag: appointments
  spec_file: zocdoc-appointments-api-openapi.yml
  capability_id: BC-2800.10
  capability_id_l1: BC-2800
  capability_name: Scheduling & Appointment Management
  confidence: 0.95
  evidence: '''Endpoints for booking, cancelling, and rescheduling appointments''; createAppointment,
    cancelAppointment, rescheduleAppointment, confirmAppointment'
  reason: Plainly patient appointment booking and lifecycle management, which is Scheduling & Appointment
    Management under Patient Access.
- tag: calendar-integration-timeslots
  spec_file: zocdoc-calendar-integration-timeslots-api-openapi.yml
  capability_id: BC-2800.10
  capability_id_l1: BC-2800
  capability_name: Scheduling & Appointment Management
  confidence: 0.88
  evidence: '''Endpoints to manage timeslots for providers''; GET /v1/providers/{provider_id}/calendar/timeslots
    ''Get timeslots for provider on date'''
  reason: Provider calendar timeslot publication and retrieval is provider/resource scheduling feeding
    appointment booking.
- tag: schedulable-entities
  spec_file: zocdoc-schedulable-entities-api-openapi.yml
  capability_id: BC-2800.10
  capability_id_l1: BC-2800
  capability_name: Scheduling & Appointment Management
  confidence: 0.75
  evidence: 'Retrieve the schedulable entities currently in your directory with availability information
    ... schemas: AvailabilityStatus, AvailabilityInfo, SchedulableEntity'
  reason: Operations manage which providers are schedulable and expose their availability, which directly
    supports provider/resource scheduling and appointment booking. Some ambiguity remains as the surface
    is partly directory/master-data oriented rather than booking itself.
  recovered_from: healthcare-vertical-edges.json