slug: tuva-health
provider: Tuva Health
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: 4
edges:
- tag: matches
  spec_file: tuva-health-matches-api-openapi.yml
  capability_id: BC-2900.10
  capability_id_l1: BC-2900
  capability_name: Master Patient Index Management
  confidence: 0.85
  evidence: POST /api/v1/matches  matches_create  Create match; schemas CreateMatchRequest, PersonUpdate,
    PersonRecordComment
  reason: 'Tuva EMPI (enterprise master patient index): creating a match links person records into a single
    person identity — this is master patient index stewardship / duplicate resolution.'
- tag: potential-matches
  spec_file: tuva-health-potential-matches-api-openapi.yml
  capability_id: BC-2900.10
  capability_id_l1: BC-2900
  capability_name: Master Patient Index Management
  confidence: 0.85
  evidence: GET /api/v1/potential-matches; schemas PotentialMatchDetail, PredictionResult
  reason: Candidate duplicate-record pairs with match prediction scores for review — squarely MPI duplicate/overlay
    resolution.
- tag: persons
  spec_file: tuva-health-persons-api-openapi.yml
  capability_id: BC-2900.10
  capability_id_l1: BC-2900
  capability_name: Master Patient Index Management
  confidence: 0.8
  evidence: GET /api/v1/persons  Retrieve persons; schemas PersonRecord, PersonDetail, PersonSummary
  reason: Retrieval of resolved person identities and their constituent records from the Tuva EMPI — master
    patient index management.
- tag: person-records
  spec_file: tuva-health-person-records-api-openapi.yml
  capability_id: BC-2900.10
  capability_id_l1: BC-2900
  capability_name: Master Patient Index Management
  confidence: 0.75
  evidence: POST /api/v1/person-records/import  Import person records; POST /api/v1/person-records/export  Export
    person records
  reason: Import/export of person records into the EMPI is the data-loading side of master patient index
    stewardship. Slight ambiguity as it is generic bulk data movement, hence moderate confidence.