slug: verato
provider: Verato
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: 14
edges:
- tag: AddRelationshipService
  spec_file: verato-addrelationshipservice-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.8
  evidence: '"Merge and link operations: Consolidate duplicate organizations, manage master data relationships,
    and maintain data lineage"; "Relationship management: Define and query relationships between organizations
    (parent-child, affiliations, etc.)"'
  reason: Operation adds relationships between organization identity records in an MDM/golden-record platform
    — organization master data management, a cross-industry data capability rather than a patient-index
    capability (this is the Organization API, not Person).
- tag: LinkIdentities
  spec_file: verato-linkidentities-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.8
  evidence: '"Link two identities (linkIdentities)"; "Merge and link operations: Consolidate duplicate
    organizations, manage master data relationships, and maintain data lineage"'
  reason: Explicit master data linking/consolidation to maintain a single golden record.
- tag: MergeIdentities
  spec_file: verato-mergeidentities-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.8
  evidence: '"Merge two identities (mergeIdentities)"; "Consolidate duplicate organizations, manage master
    data relationships"'
  reason: Duplicate resolution/merge of master identity records — canonical master data management operation.
- tag: PostIdentity
  spec_file: verato-postidentity-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.8
  evidence: '"Add an Identity (postIdentity)"; "Ingest and manage organization identities"'
  reason: Ingestion of source identity records into the master data hub for matching and golden-record
    creation.
- tag: IdentityIdQuery
  spec_file: verato-identityidquery-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.75
  evidence: '"Query using link ID (identityIdQuery)"; "link IDs (Verato''s golden identifier)"'
  reason: Lookup of the golden record by its master identifier — master data management/identity resolution.
- tag: DeleteSourceIdentity
  spec_file: verato-deletesourceidentity-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.72
  evidence: '"Hard Delete a Source (deleteSourceIdentity)"; "Add, update, and delete organization records
    with rich demographic and contact information"'
  reason: Deletion of a source-contributed master record within the identity hub — master data lifecycle
    management.
- tag: DemographicsQuery
  spec_file: verato-demographicsquery-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.72
  evidence: '"Query using demographic information (demographicsQuery)"; schemas MergedSourceRecord, alternateIdentifiers,
    Domain'
  reason: Retrieval of merged golden records by demographic attributes — identity resolution/master data
    query. Spec is the Organization API, so patient-index mapping is not warranted.
- tag: DemographicsSearch
  spec_file: verato-demographicssearch-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.72
  evidence: '"Search using demographic information (demographicsSearch)"; DemographicsSearchWsRequest,
    MergedSourceRecord'
  reason: Probabilistic search over master identity records to resolve entities — core MDM identity resolution
    capability.
- tag: NativeIdQuery
  spec_file: verato-nativeidquery-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.72
  evidence: '"Query using native ID (nativeIdQuery)"; "Find organizations using demographic data, native
    IDs, or link IDs"'
  reason: Cross-reference lookup from a source-system native key to the master record — MDM identity cross-referencing.
- tag: RestoreSource
  spec_file: verato-restoresource-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.72
  evidence: '"Restore a soft-deleted source (restoreSource)" within "Lifecycle management: Soft-delete
    and restore organization records while preserving data history"'
  reason: Operation restores soft-deleted organization identity source records in Verato's master data
    platform. This is master data record lifecycle stewardship for organizations (not patients), so Master
    Data Management fits rather than the patient-specific MPI capability.
  recovered_from: healthcare-vertical-edges.json
- tag: SoftDeleteSource
  spec_file: verato-softdeletesource-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.72
  evidence: '"Soft delete a source from identities (softDeleteSource)"'
  reason: Removes a contributing source record from an organization identity in the MDM golden-record
    platform — master data record lifecycle stewardship.
  recovered_from: healthcare-vertical-edges.json
- tag: UnlinkIdentities
  spec_file: verato-unlinkidentities-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.72
  evidence: 'POST /unlinkIdentities  "Unlink two identities (unlinkIdentities)"; "Merge and link operations:
    Consolidate duplicate organizations, manage master data relationships, and maintain data lineage"'
  reason: Identity linking/unlinking to maintain the golden record for organizations is core master data
    management / identity resolution. Organizations, not patients, so MPI-specific capability would be
    wrong.
- tag: UnmergeIdentities
  spec_file: verato-unmergeidentities-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.72
  evidence: POST /unmergeIdentities  "Unmerge two identities (unmergeIdentities)"; "Consolidate duplicate
    organizations, manage master data relationships, and maintain data lineage"
  reason: Merge/unmerge of duplicate organization identities is duplicate resolution within a master data
    hub — cross-industry MDM is the correct frame for organization (not patient) records.
- tag: SearchRelationshipsService
  spec_file: verato-searchrelationshipsservice-api-openapi.yml
  capability_id: BC-610.20
  capability_id_l1: BC-610
  capability_name: Master Data Management
  confidence: 0.7
  evidence: '"Searches for relationships (searchRelationshipsService)"; description: "Relationship management:
    Define and query relationships between organizations (parent-child, affiliations, etc.)"'
  reason: Querying parent-child/affiliation hierarchies among organization master records is organizational
    master data (hierarchy) management. Not patient-facing, so MDM rather than a Healthcare Providers
    capability.
  recovered_from: healthcare-vertical-edges.json