slug: element5
provider: Element5
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: 2
edges:
- tag: Eligibility
  spec_file: element5-eligibility-api-openapi.yml
  capability_id: BC-2800.30
  capability_id_l1: BC-2800
  capability_name: Eligibility & Benefits Verification
  confidence: 0.88
  evidence: POST /wf/v2/workflows/submit-eligibility 'Eligibility Submission Request'; 'Process X12 Eligibility
    Transaction'; schema ProcessX12EligibilityTransactionAttachment270
  reason: X12 270/271 eligibility transactions and eligibility submission workflows are exactly insurance
    coverage and benefits verification prior to service delivery.
- tag: Authorization
  spec_file: element5-authorization-api-openapi.yml
  capability_id: BC-2800.30
  capability_id_l1: BC-2800
  capability_name: Eligibility & Benefits Verification
  confidence: 0.72
  evidence: 'POST /wf/v2/workflows/submit-authorization ''Authorization Submission Request''; vendor:
    "prior authorization submission"'
  reason: Operations submit and track prior-authorisation requests to payers. In this frame, authorisation
    requirements before service delivery sit under Eligibility & Benefits Verification. Some chance a
    grader would place prior auth under revenue cycle instead, hence 0.72 rather than higher.