Regulatory Tracker — ACME Health / Cumberland Valley Integration

Issued March 13, 2023 — two weeks after Charter approval, during the formal regulatory approval process. This tracker monitors progress toward two critical gates: HSR clearance (federal antitrust, expected mid-year) and Form A approval (state insurance regulator, expected by early September). Conditions may be imposed; management is preparing to negotiate proactively on likely items before they arrive. Owner: R. Cadwallader (Regulatory Affairs).

The regulatory path consists of three gates: Hart-Scott-Rodino (federal antitrust clearance), state insurance regulator approval of the Form A (change of control), and satisfaction of any conditions the regulator imposes. The transaction cannot close without both HSR clearance and Form A approval. If conditions are imposed, they must be satisfied, though conditions do not prevent closing unless they include a suspension trigger.

Gate	Status	Timeline	Owner	Notes
HSR Clearance (Antitrust)	PENDING	Application filed: February 2023 Waiting period expected: May 30, 2023	R. Cadwallader	Standard 30-day waiting period. Filing complete. No Second Request anticipated given transaction structure. Clearing on scheduled date allows Form A filing in June.
Form A Approval (State Insurance Regulator)	PENDING	Application filing: June 2023 (after HSR clears) Decision expected: September 12, 2023	R. Cadwallader, L. Hollingsworth (General Counsel)	Tennessee Department of Insurance (domiciliary regulator) review. Typical review period 90 days. Some carriers impose conditions on approval; Legal and Regulatory are preparing negotiation positions for likely items.
Condition Negotiation (If Imposed)	PLANNED	If conditions imposed: September 2023 Satisfaction expected by: Day 30 post-close	R. Cadwallader, B. Trammell (Tech) L. Hollingsworth (Legal)	Conditions, if any, will be negotiated to ensure they do not block integration strategy. Primary concern: data location restrictions. See anticipated conditions assessment below. Non-blocking conditions can extend into operational integration.

A slip in either HSR or Form A approval delays the entire program. HSR clearing late compresses the Form A review window and may shift closing. Form A approval late or conditioned is the critical path gate. The regulatory affairs team is tracking both in real time and has escalation protocols to the Steering Committee if either milestone appears at risk.

Anticipated Regulatory Conditions

Based on regulatory trends in insurance acquisitions and the Tennessee Department of Insurance's recent guidance on data handling, several conditions are anticipated if Form A approval includes conditions. Management is preparing to negotiate positions on these items proactively — before they are imposed — which is a stronger posture than reactive negotiation after approval is on the table.

Item 1: Member Data Processing Location (Highest Probability)

Anticipated condition: All member-level personal data must be processed, stored, and analyzed exclusively on-shore (within the United States). No member data may be sent to offshore locations for processing, analysis, or storage without prior written approval from the Tennessee Department of Insurance.

Effect on integration if imposed: This would constrain where the integration layer can run matching analysis and where any analytical data warehouse components are hosted. All member-level profiling, identity resolution, and analytical processing must occur on ACME's U.S.-based infrastructure.

Integration response: The Cloud Migration Strategy (Artifact 24, currently in draft) is being shaped with U.S.-only processing as the default assumption. Vendor contracts for data services are being structured to flag any offshore processing as requiring regulatory approval. The architecture can accommodate this condition without rework; proactive design means if the condition is imposed, it arrives as a confirmation of what was already planned, not a constraint that forces redesign.

Item 2: Reporting Requirements on Member Complaint Data

Possible condition: Quarterly or semi-annual regulatory reporting on member complaints and resolution times during the integration period (12 months post-close).

Effect if imposed: Requires infrastructure to track and report complaint metrics across the two legacy systems and the new integration layer. This is low complexity; most carriers maintain this data for state reporting already.

Preparedness: No design changes needed. Member services and compliance teams are already tracking complaint data for the existing businesses.

Item 3: Hold on Certain System Consolidations

Less likely, but possible: A regulator might impose a temporary hold on consolidating specific core systems (e.g., claims processing) until integration stability is demonstrated. Regulator wants to confirm no destabilization of member services.

Effect if imposed: Extends coexistence period for affected systems. This would increase the TSA term or require extended parallel run costs.

Risk mitigation: This is the only anticipated condition that would materially affect cost or schedule. If imposed, it is escalated immediately to the Steering Committee as a constraint that may require tradeoff with other priorities.

Anticipating conditions before they arrive is how integration strategies become proactive rather than reactive. The integration strategy is not being built to accommodate this onshore restriction — it is being built WITH the assumption that the restriction will likely be imposed. If the regulator does not impose it, the integration design is stronger than required. If the regulator does impose it, the integration design was already ready. Reactive negotiation after approval creates pressure to bend; proactive preparation creates an option to concede as part of strategy, not as capitulation.

Slip Scenarios and Consequence

If HSR clears late (after June 2023): Form A application is delayed by 30 days, pushing the expected approval to approximately October 2023. A closing expected in October 2023 rather than September 2023 means losing one month of TSA run-in before the holiday period and compressing the operational integration into December. This is manageable but increases risk.

If Form A approval is delayed past the anticipated October 15, 2023 window: This cuts into the Q4 2023 window for closing. A delayed closing anticipated for February 15, 2024 is operationally harder (holiday coverage still in effect, budgeting cycle compressed) and eats directly into the TSA term. This is escalated immediately to Corporate Development and the CFO.

If Form A approval includes unexpected conditions beyond those above: Depends on severity. Non-blocking conditions are negotiated to Day 30 satisfaction. Conditions that would materially change the TSA term or require system architecture rework trigger an emergency Steering Committee meeting for go/no-go decision.

Current Status (March 13, 2023)

HSR application is filed and in waiting period. Form A filing is scheduled for June 2023, after HSR clearance. No adverse signals from either regulator at this time. Regulatory Affairs is monitoring for any requests for additional information from the HSR team. Legal and Regulatory are in pro-active communication with Tennessee DOI on the transaction, with no unexpected signals to date.