HHS Technology Group Holdings, LLC. v. State of Missouri

CourtMissouri Court of Appeals
DecidedJanuary 14, 2025
DocketWD86036
StatusPublished

This text of HHS Technology Group Holdings, LLC. v. State of Missouri (HHS Technology Group Holdings, LLC. v. State of Missouri) is published on Counsel Stack Legal Research, covering Missouri Court of Appeals primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
HHS Technology Group Holdings, LLC. v. State of Missouri, (Mo. Ct. App. 2025).

Opinion

IN THE MISSOURI COURT OF APPEALS WESTERN DISTRICT HHS TECHNOLOGY GROUP HOLDINGS, LLC, et al., ) ) RESPONDENTS, ) WD86036 ) (Consolidated with WD86055) v. ) ) OPINION FILED: ) January 14, 2025 STATE OF MISSOURI, ) ) APPELLANT. )

Appeal from the Circuit Court of Cole County, Missouri The Honorable Jon E. Beetem, Judge

Before Division Four: Anthony Rex Gabbert, Chief Judge, Presiding, Karen King Mitchell, Judge, and Alisha D. O’Hara, Special Judge

The State of Missouri appeals from a judgment in favor of EngagePoint, Inc., and

HHS Technology Group Holdings, LLC,1 arising from a contract dispute involving the

Missouri Eligibility Determination and Enrollment System (MEDES).2 The State raises

1 During the course of this litigation, HHS acquired EngagePoint’s claims and was substituted in as plaintiff, with EngagePoint remaining as a third-party defendant in the State’s claims against it. For ease of reference, we refer to HHS and EngagePoint collectively as “EngagePoint,” unless otherwise indicated. 2 MEDES resulted from the 2010 Affordable Care Act (ACA), which, among other things, set new standards for Medicaid eligibility (i.e., eligibility based on

1 four points on appeal. First, the State argues the trial court erred in entering judgment,

following a jury trial, awarding EngagePoint $18,945,341 for extra work/constructive

change because payment for extra work/constructive change outside of the parties’

written contract violated the Missouri Constitution. Second, the State asserts the court

erred in awarding prejudgment interest on the judgment for extra work/constructive

change and holdbacks because both the contract and § 408.020 barred prejudgment

interest. Third, the State contends the trial court erred in entering judgment for

EngagePoint on the State’s breach of contract claim because the jury instructions for that

claim violated the limitations of the force majeure clause in the parties’ contract. Fourth,

the State argues the trial court erred in entering a directed verdict for EngagePoint on its

claim for holdbacks because that decision violated the terms of the parties’ contract. For

the reasons set forth below, we affirm.

“Modified Adjusted Gross Income” (MAGI)), new standards for yet-to-be-built federal Medicaid-related IT systems, and new technical standards for State Medicaid systems that would need to interface with the new federal systems. The ACA also made available to participating states funding to cover up to 90 percent of the cost of achieving technical compliance. Federal funding was to be administered by the Centers for Medicare & Medicaid Services (CMS) and was conditioned on meeting certain CMS requirements, including satisfying what CMS identified as the seven critical success factors for system performance, which were largely tied to CMS’s “go-live” dates of October 2013 and January 2014.

2 Background

The State does not challenge the sufficiency of the evidence to support the

verdicts. Viewed in the light most favorable to the verdicts, the evidence, as it relates to

the issues raised on appeal, showed as follows:3

On January 22, 2013, the State issued a Request for Proposal (RFP) for MEDES.4

The RFP specified that MEDES’s core component must be a commercial off-the-shelf

(COTS) software “solution,” that is, a “commercially available” (as opposed to a custom-

built) software product that met several specific requirements outlined in the RFP. The

State’s specific COTS requirements were derived largely from IBM, which manufactured

a COTS product called “Curam.” At the time the responses to the RFP were due, Curam,

which was regarded as a fairly stable product, was the only COTS option that met the

RFP’s requirements. In April 2013, IBM demonstrated the functionality, eligibility, and

life management capabilities of Curam to the State.

On June 6, 2013, the State awarded EngagePoint, as the prime contractor, a fixed-

price contract to build MEDES using Curam.5 The contract allowed for up to $5 million

3 The record in this case is extensive. We limit our discussion of the facts to those relevant to the issues before us on appeal. 4 MEDES consisted of three sub-projects: Projects I, II, and III. The State’s RFP primarily concerned Projects I and II. 5 The contract is approximately 1,200 pages in length and consists of (1) the State’s RFP (and edits thereto), (2) EngagePoint’s response, (3) the State’s three Best- And-Final-Offer letters, (4) EngagePoint’s three responses thereto, (5) the State’s clarifications to the RFP, (6) the notice of contract award, and (7) all subsequent amendments. Only portions of the contract were entered into evidence at trial.

3 in change orders, and EngagePoint submitted change orders to the State which, when

approved, drew down on the $5 million credit.6

The contract was to last through June 30, 2018, and the total contract price was

$147,000,000. On June 21, 2013, the State licensed Curam directly from IBM, as

opposed to having EngagePoint license Curam during the term of the contract. The

project kicked off in July 2013.

When MEDES went live in October 2013, Curam did not function as promised by

IBM, and EngagePoint spent most of 2014 creating workarounds for Curam’s defects. In

fall 2014, IBM released an upgraded version of Curam intended to fix many of the

problems, but that meant the upgraded version of Curam had to be integrated into

MEDES. As a result of Curam’s defects, the resulting upgrade, and—among other

things—changes to MEDES by CMS and the State, EngagePoint performed substantial

additional work at the State’s direction.

Under the contract, the State was to make payments in arrears to EngagePoint.

Upon acceptance of each deliverable by the State, the State was to withhold a defined

percentage of the deliverable amounts due pending final completion of the respective

project (holdbacks).

On May 18, 2015, the State terminated EngagePoint as the prime contractor and

replaced EngagePoint with IBM, Curam’s manufacturer. In addition to hiring four

EngagePoint employees as independent contractors to manage MEDES, the State

6 EngagePoint submitted change requests for between $300,000 and $400,000. The State approved approximately $365,000 to $367,000 in change orders.

4 identified 27 other EngagePoint employees who were “critical” to MEDES; thus, the

State retained EngagePoint as a MEDES subcontractor for three more years until Project

I (the MAGI portion of MEDES) was completed.

In 2016, EngagePoint filed the underlying lawsuit to (1) collect payment for the

extra work EngagePoint completed at the State’s direction and (2) recover the contractual

“holdbacks” the State did not pay out when it terminated EngagePoint as the prime

contractor. In 2017, the State countersued for breach of contract.

A jury trial was held from July 7, 2022, to August 11, 2022. On August 8, 2022,

the State filed a motion for directed verdict at the close of all the evidence; the court

denied the motion as to the issues relevant to this appeal. On August 10, 2022, the trial

court granted EngagePoint’s oral motion for directed verdict for $4,097,169 on

EngagePoint’s contractual holdback claim. EngagePoint’s extra work/constructive

change claim went to the jury. On August 11, 2022, the jury awarded EngagePoint

$18,945,341 on its extra work/constructive change claim and rejected the State’s

counterclaims, including the State’s claim for breach of contract related to Project I.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Mathes v. Sher Express, L.L.C.
200 S.W.3d 97 (Missouri Court of Appeals, 2006)
Davis v. Stewart Title Guaranty Co.
726 S.W.2d 839 (Missouri Court of Appeals, 1987)
J. E. Hathman, Inc. v. Sigma Alpha Epsilon Club of Columbia
491 S.W.2d 261 (Supreme Court of Missouri, 1973)
City of Peculiar v. Hunt Martin Materials, LLC
274 S.W.3d 588 (Missouri Court of Appeals, 2009)
Children International v. Ammon Painting Co.
215 S.W.3d 194 (Missouri Court of Appeals, 2006)
Dunn Industrial Group, Inc. v. City of Sugar Creek
112 S.W.3d 421 (Supreme Court of Missouri, 2003)
Manfield v. Auditorium Bar & Grill, Inc.
965 S.W.2d 262 (Missouri Court of Appeals, 1998)
Brown v. Donham
900 S.W.2d 630 (Supreme Court of Missouri, 1995)
State Ex Rel. Vincent v. Schneider
194 S.W.3d 853 (Supreme Court of Missouri, 2006)
D.R. Sherry Construction, Ltd. v. American Family Mutual Insurance Co.
316 S.W.3d 899 (Supreme Court of Missouri, 2010)
Dunn v. Enterprise Rent-A-Car Co.
170 S.W.3d 1 (Missouri Court of Appeals, 2005)
Hart v. City of Butler
393 S.W.2d 568 (Supreme Court of Missouri, 1965)
Lindsey Masonry Co. v. Jenkins & Associates Inc.
897 S.W.2d 6 (Missouri Court of Appeals, 1995)
Edgewater Health Care, Inc. v. Health Systems Management, Inc.
752 S.W.2d 860 (Missouri Court of Appeals, 1988)
Harland Hawley v. Edward D. Tseona
453 S.W.3d 837 (Missouri Court of Appeals, 2014)
Boyd McGathey v. Matthew K. Davis Trust
457 S.W.3d 867 (Missouri Court of Appeals, 2015)
Spitcaufsky v. State Highway Commission
159 S.W.2d 647 (Supreme Court of Missouri, 1941)
State of Missouri v. Sidney L. Clark III
503 S.W.3d 235 (Missouri Court of Appeals, 2016)
Christa Reed v. The Curators of the University of Missouri
509 S.W.3d 816 (Missouri Court of Appeals, 2016)

Cite This Page — Counsel Stack

Bluebook (online)
HHS Technology Group Holdings, LLC. v. State of Missouri, Counsel Stack Legal Research, https://law.counselstack.com/opinion/hhs-technology-group-holdings-llc-v-state-of-missouri-moctapp-2025.