The Technology Black Requires: From Claims Processor to Cost Management Platform

LFP-15.07

#

The technology gap from Series 13 defines what must be built. Core requires competent execution on existing commercial platforms. Plus requires platform extension through integration and workflow development. Black requires new architecture for capabilities that do not exist in the current TPA technology market. The technology build is the longest lead-time item in the product roadmap, and the sequencing of tier launches follows the technology build timeline rather than market demand.

The progression from Core to Plus to Black is not merely a capability expansion. It is an architectural transformation. Core runs on platforms designed for claims processing. Black runs on a platform designed for population health management, predictive intervention, and care coordination across geographic boundaries. The technology investment to move from one architecture to the other represents years of development, not months.

Core Technology Stack

#

Core technology is achievable on existing commercial platforms with configuration, integration, and quality implementation work. The platforms exist. The capabilities are proven. The differentiation comes from implementation quality rather than from technology that competitors cannot access.

The claims adjudication engine requires a modern commercial platform properly configured for the small group market. Configuration includes the benefit plan variations, the accumulator logic for deductibles and out-of-pocket maximums, the coordination of benefits rules, and the network discount application. The platform must process claims at an accuracy rate above 99%, with first-pass auto-adjudication rates that minimize manual intervention. Claims accuracy rates in the TPA market range from 98.5% to over 99.9%, and the difference between 99% and 99.9% accuracy on a $3 million claims book represents approximately $25,000 in mispaid claims per year (Delta Health Systems).

The eligibility management system requires small group exception handling that larger platforms sometimes neglect. Eligibility in the small group market involves owner participation rules, waiting period variations, and coverage tier changes that occur with higher frequency per capita than in large group populations. The eligibility system must interface with the stop loss carrier for accurate premium calculation and with the broker for enrollment management.

The stop loss coordination module requires carrier interfaces that transmit claims data, flag claims approaching attachment points, and manage the reimbursement process. Different stop loss carriers use different data formats and reporting requirements. The module must accommodate carrier-specific requirements without manual workarounds that introduce delay and error.

Employer reporting dashboards must deliver claims experience data, cost driver analysis, and enrollment tracking in a format that employers can interpret without TPA support. The dashboard must update on a schedule that supports employer decision-making, with monthly data at minimum and weekly or real-time data as a competitive advantage.

The member portal at Core provides basic self-service functions: ID card access, claims history, benefit explanation, provider search, and contact information. The broker dashboard at Core provides group-level enrollment management, commission tracking, and basic performance metrics. Neither portal requires innovation beyond existing market standards.

The technology investment for Core is modest relative to Plus and Black. The investment is in implementation quality: selecting the right platform, configuring it correctly, integrating it with stop loss carriers and networks, and maintaining it with continuous attention to accuracy and service levels.

Plus Technology Extensions

#

Plus technology requires platform extension beyond the Core foundation. The extensions connect the claims engine to cost management workflows, integrate provider cost and quality data, and deliver enhanced analytics to employers and members.

The care routing engine represents the critical Plus technology investment. At the point of claims adjudication or prior authorization, the system identifies procedures that are candidates for domestic facility steering and routes the case to the care coordination team. The routing logic considers the procedure type, the member’s location, the available alternative facilities, and the estimated savings potential. Routing must occur early enough in the care decision process that member redirection is practical, which means integration with prior authorization workflows rather than post-claim identification.

The provider cost and quality database supports facility steering decisions with data. The database includes facility-level cost data for steered procedures, quality metrics where available from CMS or commercial sources, and network discount information. The database must update regularly to reflect current pricing and must cover the geographic markets where Plus members reside. Building this database requires data acquisition from multiple sources, normalization across different data formats, and maintenance processes that keep the information current.

Pharmacy optimization integration connects the transparent PBM data feed with member-facing cost comparison tools. Members accessing the pharmacy portal see the cost of their prescribed medication at different pharmacies, including mail-order options. The formulary management tools allow the TPA to implement alternative medication suggestions where therapeutic equivalents are available at lower cost. The integration requires data feeds from the PBM, decision logic for alternative suggestions, and member portal functionality to present the options.

Enhanced employer analytics deliver real-time claims data with cost driver identification integrated with cost management program engagement data. The employer sees not only what claims are occurring but also which members are engaging with the cost management programs and what savings the programs are producing. This requires data integration across claims, program enrollment, and program outcomes, with presentation logic that synthesizes the data into actionable insight.

The enhanced member portal adds cost transparency tools, pharmacy cost comparison, and direct access to care coordination resources. The portal becomes an active engagement tool rather than a passive information display. Members can request care coordination support, initiate facility comparisons for upcoming procedures, and track their progress with chronic disease or lifestyle programs.

The Plus technology extensions require 12 to 18 months of integration development after the Core platform is stable. The extensions build on the Core foundation rather than replacing it. The claims engine remains the same. The eligibility system remains the same. The Plus extensions add layers of intelligence and workflow on top of the Core infrastructure.

Black Technology Architecture

#

Black technology requires new architecture for capabilities that do not exist in commercial platforms serving the small group TPA market. The architecture supports predictive analytics, cross-border care coordination, international pharmacy integration, and concierge service at scale.

The predictive analytics platform uses machine learning models trained on claims, pharmacy, eligibility, and external data to identify members approaching high-cost events. The models must be trained on sufficient data volume to achieve predictive validity for the small group population. The data architecture prerequisites from Series 13 apply: clean historical claims data, pharmacy data integration, eligibility data with demographic attributes, and external data sources for SDOH signals. The models identify members for proactive outreach, flagging them to concierge attention before the high-cost event occurs.

The cross-border care coordination system requires an international facility database with current credentialing, quality metrics, and pricing information. The system integrates travel logistics through partnerships with medical travel providers. Complication protocol management ensures that if a member experiences a post-procedure issue, the system triggers the appropriate response: local follow-up care, medical evacuation if necessary, and communication with the member’s US-based providers. The member communication workflow manages the cross-border care journey from initial interest through post-procedure recovery.

International pharmacy integration requires a licensed international pharmacy database with medication-specific eligibility rules. Not every medication is a candidate for international purchasing. The rules engine determines which medications qualify based on regulatory status, temperature sensitivity, and cost differential. The logistics tracking ensures that members receive their medications on schedule, with visibility into shipment status and delivery confirmation.

SDOH signal ingestion connects external data sources with claims patterns. Community resource databases, socioeconomic data, and public health data are cross-referenced with member claims to identify signals of social determinants affecting health outcomes. A member with claims patterns suggesting transportation barriers might benefit from ride service integration. A member with claims patterns suggesting food insecurity might benefit from community resource referral. The signal ingestion must be privacy-compliant, and the intervention routing must connect to available resources in the member’s geography.

The concierge platform provides the technology infrastructure that supports named concierge service. Each concierge has visibility into their panel members’ health profiles, care history, program enrollments, and communication history. The workflow management system tracks open cases, pending actions, and follow-up requirements. The platform enables the concierge to function as a care coordinator rather than a call center representative.

The broker intelligence portal presents plan-level analytics designed for broker use rather than employer reporting repurposed. The portal includes claims experience trending, cost driver analysis by category, program engagement metrics, savings attribution calculations, and renewal projection tools. The benchmarking data allows brokers to compare their clients’ performance against similar employers. The portal makes the broker more effective by providing the data that supports consultative advising.

Each Black technology component requires integration with the Plus and Core platforms. The claims data that feeds predictive analytics comes from the Core claims engine. The program enrollment data that informs concierge service comes from the Plus program integrations. The technology build sequence is linear: Core platform first, establishing the foundation; Plus extensions second, building the integration architecture; Black components third, adding advanced capabilities on the established architecture.

Build Sequence and Timeline

#

The technology build timeline drives the product launch sequence. Core platform deployment is achievable within a standard implementation timeline of 6 to 12 months using existing commercial platforms. The timeline reflects platform selection, configuration, integration with stop loss carriers and networks, testing, and deployment. Core technology does not require new development, only quality execution on proven platforms.

Plus extensions require 12 to 18 months of integration development after Core is stable. The care routing engine, the provider cost and quality database, the pharmacy optimization integration, and the enhanced analytics all require development work that cannot begin until the Core platform is operational. Testing and validation add time beyond development. The Plus launch follows Core by approximately 18 to 24 months in aggregate.

Black components require 18 to 36 months of development, running in parallel with Plus deployment. The predictive analytics platform requires data accumulation before models can be trained with validity. The cross-border care infrastructure requires facility relationships and logistics partnerships that take time to negotiate and operationalize. The concierge platform requires workflow development and staffing model validation. The Black launch follows Plus by approximately 12 to 18 months, meaning Black is operational 30 to 42 months after Core launch.

The sequencing in LFP-15.11 accounts for this timeline. Core launches first because the technology is available. Plus launches after the technology extensions are built, validated, and operational. Black launches after the new architecture is complete and the supporting infrastructure is in place. Attempting to launch all three tiers simultaneously creates technology risk that the sequential approach avoids. Each tier launch validates the technology foundation before the next tier adds complexity.

Technology Investment and Return

#

The technology investment across tiers is substantial. Core technology investment is modest because the platforms exist and the work is configuration and integration rather than new development. Plus technology investment is significant because the extensions require development, data acquisition, and integration work that does not exist off the shelf. Black technology investment is large because the architecture is new and the capabilities do not exist in the current market.

The investment return comes from two sources. First, the technology enables the margin structure described in LFP-15.06. Core, Plus, and Black each command pricing that reflects their capability level. The technology investment is recovered through the margin on enrolled lives over time. Second, the technology creates competitive differentiation that protects margin from competitive pressure. A competitor that decides to replicate the Plus or Black capability stack faces the same development timeline. The technology investment creates a moat that is measured in years rather than features.