slug: ezyvet
provider: ezyVet
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: ezyvet-appointments-api-openapi.yml
  capability_id: BC-2800.10
  capability_id_l1: BC-2800
  capability_name: Scheduling & Appointment Management
  confidence: 0.82
  evidence: POST /v1/appointment  createAppointment  Create an appointment; GET /v1/appointmentstatus  listAppointmentStatuses
  reason: Appointment booking, status and type management is squarely scheduling and appointment management
    for the practice.
- tag: Diagnostics
  spec_file: ezyvet-diagnostics-api-openapi.yml
  capability_id: BC-2860
  capability_id_l1: BC-2860
  capability_name: Diagnostic Services Management
  confidence: 0.78
  evidence: POST /v1/diagnosticrequest  createDiagnosticRequest; POST /v1/diagnosticresult  createDiagnosticResult  Push
    a diagnostic result
  reason: Diagnostic request ordering and result push (lab/diagnostic integration) is diagnostic services
    management; spans ordering and results so L2 left unset.
- tag: Contacts
  spec_file: ezyvet-contacts-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: GET /v1/contact  listContacts  List contacts (clients); GET /v1/address  listAddresses
  reason: CRUD over client (pet owner) master records with addresses — customer data management rather
    than a clinical capability.