specification: FinOps Framework specificationVersion: '1.0' schema: https://www.finops.org/framework/ provider: Tebra providerId: tebra created: '2026-07-10' modified: '2026-07-10' reconciled: false tags: - Healthcare - Practice Management - EHR - Medical Billing - FinOps - Cost Management - FOCUS description: >- FinOps view of Tebra API spend. Tebra (formerly Kareo + PatientPop) does not bill its APIs on a metered, usage-based basis. The SOAP Practice Management API is a capability of a Tebra platform subscription, which is quote-based and priced per provider per month by module (EHR, practice management, billing, growth); the dominant, controllable cost is therefore the seat/provider count and module mix rather than API call volume. Payment processing fees and certain integrations (for example e-prescribing / PDMP add-ons) are billed separately. The Clinical Data (patient-access) API is provided at no cost to patients under federal information-blocking rules and carries no line-item charge. notes: >- Because API access is bundled into the platform subscription, model Tebra cost around provider seats and enabled modules, not per-request pricing. Reconcile actual rates and any partner onboarding fees with Tebra sales. Payment processing (reported approx. 2.75% + $0.30 card-present, 3.25% + $0.30 card-not-present) is a separate charge category from software subscription. sources: - https://www.tebra.com/pricing - https://helpme.tebra.com/Tebra_PM/12_API_and_Integration - https://focus.finops.org/focus-specification/v1-3/ alignedWith: framework: FinOps Foundation Framework frameworkUrl: https://www.finops.org/framework/ dataSpec: FOCUS dataSpecVersion: '1.3' dataSpecUrl: https://focus.finops.org/focus-specification/v1-3/ publisherName: Tebra serviceCategory: Healthcare Practice Management and EHR billingModel: pricingCategory: Subscription-Based billingFrequency: Monthly billingCurrency: USD chargeCategories: - Usage - Purchase meters: - name: provider_seats description: Provider seats on the Tebra platform subscription that grants API access; the primary cost driver. unit: providers aggregation: sum dimensions: - account - module - name: enabled_modules description: Modules enabled (EHR, practice management, billing, growth) that determine subscription price. unit: modules aggregation: sum dimensions: - account - name: payment_processing description: Card payment processing fees charged on collected patient payments, separate from subscription. unit: transactions aggregation: sum dimensions: - account principles: - name: Visibility description: Track provider seat count and enabled modules; API usage itself is not separately invoiced but drives operational value. - name: Allocation description: Map provider seats and modules to practices / cost centers; separate software subscription from payment-processing fees. - name: Optimization description: Right-size provider seats and modules to actual need; batch and cache SOAP polling (5-15 min) to avoid unnecessary integration compute rather than to reduce a per-call fee. - name: Accountability description: Assign an owner for the Tebra subscription and any partner integration agreement; review module mix and payment-processing rates periodically. maintainers: - FN: Kin Lane email: kin@apievangelist.com