Lilly v. Envoy LLC et al
Filing
40
ORDER granting in part and denying in part dfts' 26 Motion to Dismiss for Failure to State a Claim by Judge Ricardo S Martinez.(RS)
1
2
3
4
5
UNITED STATES DISTRICT COURT
WESTERN DISTRICT OF WASHINGTON
AT SEATTLE
6
7
8
9
MARC LILLY, NOT IN HIS INDIVIDUAL
CAPACITY BUT AS THE
REPRESENTATIVE FOR THE FORMER
SHAREHOLDERS OF VIEOSOFT, INC.,
12
13
v.
ENVOY, LLC; EMDEON, INC.; EMDEON
BUSINESS SERVICES, LLC; TOM GROOM
(named as an indispensable party),
Defendants.
14
15
16
ORDER GRANTING IN PART AND
DENYING IN PART DEFENDANTS’
MOTION TO DISMISS
Plaintiff,
10
11
Case No. C15-0742 RSM
I.
INTRODUCTION
THIS MATTER comes before the Court on Defendants’ Motion to Dismiss under
17
18
19
Federal Rule of Civil Procedure 12(b)(6) for failure to state a claim. Dkt. #26. Specifically,
Defendants argue that: 1) Plaintiff’s claim for breach of the implied covenant of good faith and
20
fair dealing fails as a matter of law; 2) Plaintiff fails to state a claim for breach of fiduciary duty;
21
3) Plaintiff fails to state any express breach of contract claim; and 4) Plaintiff fails to state any
22
claims against Emdeon and EBS.
23
Id.
Plaintiff opposes the motion, asserting that it has
sufficiently alleged each of his claims against all Defendants. Dkt. #31 (filed under seal). For
24
the reasons set forth below, the Court agrees in part with Plaintiff and GRANTS IN PART AND
25
DENIES IN PART Defendants’ Motion to Dismiss.
ORDER – 1
II.
1
2
3
BACKGROUND
Plaintiff alleges the following factual background:
A. The Stock Purchase Agreement
4
Defendant Emdeon provides revenue and payment cycle management and clinical
5
information exchange solutions for healthcare system payors and providers. Dkt. #1 at ¶ 14.
6
Vieosoft, a Washington corporation, was formed in 2010 and focused on developing cloud-based
7
services, information, and tools to help payers, pharmacies, vendors of electronic health records,
8
9
doctors, and patients electronically manage prescriptions. Id. at ¶ ¶ 13 and 15.
10
Beginning in 2012, Emdeon identified that Vieosoft could add significant additional
11
product value to Emdeon in terms of electronic prescription technologies. Id. at ¶ 17. As a result,
12
on February 12, 2014, Emdeon (through a special purpose entity called “Envoy, LLC”) purchased
13
14
all Vieosoft stock from Vieosoft’s shareholders (the “Shareholders”) pursuant to the “Stock
Purchase Agreement.” Id. at ¶ 20 and Dkt. #1-1. Under the Stock Purchase Agreement, in
15
16
17
addition to receiving all stock of Vieosoft, Emdeon obtained the promise of four key Shareholders
to work with Emdeon to help implement an agreed-upon development plan for the electronic
18
prescription software (the “Contributing Shareholders”).
19
Contributing Shareholders were required to accept five year non-compete provisions. Id. at ¶ 21
20
and Dkt. #1-1 at § 9.4.
21
Dkt. #1 at ¶ ¶ 20-21.
The four
The Stock Purchase Agreement contains a detailed “Development Plan” to bring the
22
software products on-line within Emdeon. Dkt. #1 at ¶ 20 and Dkt. #1-2. The Development Plan
23
24
25
is attached as Annex D to the Stock Purchase Agreement and is expressly incorporated by
reference. Dkt. #1 at ¶ 20; Dkt. #1-1 at § § 1.5 and 1.6; and Dkt. #1-2. Under the Development
ORDER – 2
1
Plan, the Contributing Shareholders were to help develop certain “Milestone Objectives,” which
2
were to be completed on or before December 31, 2014. Dkt. #1 at ¶ 30; Dkt. #1-1 at § 1.5; and
3
Dkt. 1-2 at 2.
4
Emdeon paid upfront consideration to the Shareholders in the amount of $2.75 million.
5
Dkt. 1 at ¶ 21 and Dkt. #1-1 at § 1.2. Emdeon also promised the Shareholders additional
6
consideration contingent upon realization of the Development Plan and resulting “Eligible
7
Revenue.” Dkt. # 1 at ¶ ¶ 21 and 37-38 and Dkt. #1-1 at § § 1.7-1.8.
8
B. Emdeon’s Express Obligations Under The Stock Purchase Agreement
9
10
The Stock Purchase Agreement, including the Development Plan, imposes express
11
contractual obligations on Emdeon. For example, the Development Plan required Emdeon to
12
provide certain resources, including developers, software architects, and quality assurance
13
managers (the “Development Team”).1 Dkt. #1 at ¶ 33 and Dkt. 1-2. Further, section 1.6 of the
14
Stock Purchase Agreement provided that Emdeon was to “oversee[] the management structure
15
16
17
and other personnel involved with the execution and continued performance of the Development
Plan” and “implement[] modifications of the Development Plan.” Dkt. #1 at ¶ 34 and Dkt. #1-1
18
at § 1.6. Section 1.6 also gives Emdeon the freedom to operate its business and confirms that
19
Emdeon makes no representations as to the generation of Eligible Revenue.
20
21
Together, the Milestone Objectives and Emdeon’s existing Core ePrescribing products
were to be combined into a “Solution,” which would be marketed to existing and new Emdeon
22
customers seeking an end-to-end (provider to payer) electronic pharmacy prescription solution.
23
24
25
1
Other confidential obligations have been omitted from this discussion as they are contained in
documents filed under seal in this Court. However, the Court has considered the entire,
unredacted Complaint and its Exhibits on this motion.
ORDER – 3
1
Dkt. #1 at ¶ 35 and Dkt. #1-1 at § 1.5. The Contributing Shareholders were obligated to “develop,
2
customize, test and deliver to Emdeon the Solution as set forth herein and in the Development
3
Plan.” Dkt. 1 at ¶ 36 and Dkt. #1-1 at § 1.5. The Shareholders would then share in Eligible
4
Revenue flowing from the Solution.2 Dkt. #1 at ¶ ¶ 37-38 and Dkt. #1-1 at § § 1.7(b) and (c).
5
6
C. Emdeon Fails To Comply With The Development Plan And Frustrates/Prevents The
Contributing Shareholders’ Performance
7
Following execution of the Stock Purchase Agreement, the Contributing Shareholders
8
recruited and built a talented Development Team, many of whom had previously helped the
9
10
Contributing Shareholders complete similar projects. Dkt. 1 at ¶ ¶ 32 and 40. The Development
Team immediately began working on the Milestone Objectives.3 Dkt. #1 at ¶ 43.
11
Shortly after executing the Stock Purchase Agreement, Emdeon announced that it was
12
13
going to change its systems hosting platform, the platform upon which all of its operating
14
software depends. Dkt. #1 at ¶ 44. Prior to execution of the Stock Purchase Agreement, Emdeon
15
was using a traditional Microsoft Windows-based internal server hosting platform. Id. Shortly
16
thereafter, Emdeon announced the decision to move all of its operations to a cloud-based hosting
17
platform offered by Amazon Web Services. Id. Plaintiff alleges that this posed significant
18
challenges for Emdeon overall, as well as for timely development of the Solution because any
19
20
Solution would have to be built in a new hosting environment. Id. As a result, the Development
21
Team was diverted from working on the Milestone Objectives; instead, the Development Team
22
was forced to work on Emdeon's deliverables under the Stock Purchase Agreement. (Dkt. #1 at ¶
23
2
24
3
25
Plaintiff alleges this amount to be up to $43 million.
This discussion omits some specific undertakings as those actions are contained in documents
filed under seal in this Court. However, as noted above, the Court has considered the entire,
unredacted Complaint and its Exhibits on this motion.
ORDER – 4
1
47.
Plaintiff asserts that Emdeon’s decision to switch hosting platforms (internal servers
2
migrating to cloud) made the process of completing the Core ePrescribing products more time-
3
consuming and difficult, because the products had to be re-coded to function in Emdeon’s new
4
cloud environment. Dkt. 1 at ¶ 47. Plaintiff alleges that this decision by Emdeon prevented the
5
Contributing Shareholders from completing the Milestone Objectives by December 31, 2014. Id.
6
Further, when the Stock Purchase Agreement was executed, Emdeon was using IBM Initiate as its
7
MPI tool. Dkt. #1 at ¶ 49. However, in or around the second quarter of 2014, shortly after the
8
9
Stock Purchase Agreement was executed, Emdeon decided to replace IBM Initiate with an
10
alternative MPI created by Oracle, known as the Oracle Master Person Index. Id. The transition
11
from IBM Initiate to Oracle Master Person Index also required substantial new work. This
12
development task was not anticipated in the Development Plan. Id. and Dkt. #1-2. This, Plaintiff
13
14
alleges that in failing to adjust the Development Plan to reflect the fact of these fundamental
changes to Emdeon’s operations, Emdeon breached its express obligations under section 1.6 to
15
16
17
administer the Development Plan and modify the Development Plan to reflect the changed
circumstances caused by its own conduct. Dkt. #1 at ¶ 76(d) and (e) and Dkt. #1-1 at § 1.6.
18
Plaintiff further alleges that in making these decisions, Emdeon also breached the Development
19
Plan.
20
21
D. Emdeon Terminates The Stock Purchase Agreement
On April 29, 2015, Emdeon issued a notice formally “terminating” the Stock Purchase
22
Agreement, citing the Contributing Shareholders’ alleged breach of the Stock Purchase
23
24
25
Agreement by failing to timely complete the Milestone Objectives. Dkt. #1 at ¶ 65. Plaintiff
alleges that because Emdeon is solely responsible for the failure to timely complete the Milestone
ORDER – 5
1
Objectives, Emdeon’s termination of the Stock Purchase Agreement on this ground represents a
2
breach of the agreement by Emdeon. Dkt. #1 at ¶ 76(h). Plaintiff further alleges that as a result
3
of the termination, the Shareholders stand to lose the vast majority of the purchase price
4
bargained for in the Stock Purchase Agreement. Dkt. #1 at ¶ 68. Plaintiff asserts that Emdeon
5
continues to move forward with plans to develop, implement, and sell the Solution. Dkt. #1 at ¶
6
67.
7
III.
8
9
DISCUSSION
A. Standard of Review Under 12(b)(6)
10
On a motion to dismiss for failure to state a claim under Federal Rule of Civil Procedure
11
12(b)(6), all allegations of material fact must be accepted as true and construed in the light most
12
favorable to the nonmoving party. Cahill v. Liberty Mut. Ins. Co., 80 F.3d 336, 337-38 (9th Cir.
13
14
1996). However, the court is not required to accept as true a “legal conclusion couched as a
factual allegation.” Ashcroft v. Iqbal, 556 U.S. 662, 678 (2009) (quoting Bell Atl. Corp. v.
15
16
17
Twombly, 550 U.S. 544, 555 (2007)). The Complaint “must contain sufficient factual matter,
accepted as true, to state a claim to relief that is plausible on its face.” Id. at 678. This
18
requirement is met when the plaintiff “pleads factual content that allows the court to draw the
19
reasonable inference that the defendant is liable for the misconduct alleged.” Id. Absent facial
20
plausibility, a plaintiff’s claims must be dismissed. Twombly, 550 U.S. at 570.
21
B. Applicable Law
22
The parties appear to agree that this matter is governed by Delaware law. Accordingly,
23
24
the Court applies such law to the instant motion.
25
ORDER – 6
1
C. Plaintiff’s Claim for Breach of Implied Covenant of Good Faith and Fair Dealing
2
Defendants first argue that Plaintiff’s claim for breach of the implied covenant of good
3
faith and fair dealing fails as a matter of law because Delaware courts narrowly construe this
4
covenant and will not apply it to displace explicit contract terms or to insert terms that a party
5
could have obtained through negotiation. Dkt. #26 at 9. Defendants primarily rely on Winshall v.
6
Viacom International, Inc., 76 A.3d 808 (Del. 2013) and Nemec v. Shrader, 991 A.2d 1120 (Del.
7
2010) in support of its argument. Plaintiff responds that Winshall actually supports his position,
8
9
10
and that he has pled a valid claim. Dkt. #31 at 13-19. The Court finds that Plaintiff has
adequately pled his claim at this time.
11
Delaware courts recognize that the “implied covenant of good faith and fair dealing
12
involves a ‘cautious enterprise,’ inferring contractual terms to handle developments or contractual
13
14
gaps that the asserting party pleads neither party anticipated.” Nemec, 991 A.2d at 1125. Indeed,
the Supreme Court of Delaware has noted that “one generally cannot base a claim for breach of
15
16
17
the implied covenant on conduct authorized by the agreement.”
Id. at 1125-1126 (citation
omitted). Thus, Delaware courts will only imply contract terms when the party asserting the
18
implied covenant proves that the other party has acted arbitrarily or unreasonably, thereby
19
frustrating the fruits of the bargain that the asserting party reasonably expected. Id. at 1126. The
20
Supreme Court of Delaware has also noted that when conducting this analysis, the Court must
21
assess the parties’ reasonable expectations at the time of contracting and not rewrite the contract
22
to appease a party who later wishes to rewrite a contract he now believes to have been a bad deal.
23
24
Id. “Parties have a right to enter into good and bad contracts, the law enforces both.” Id.
25
ORDER – 7
1
Here, Plaintiff has clearly pled that Defendants have acted unreasonably, thereby
2
frustrating the fruits of the bargain that Plaintiff reasonably expected. Dkt. #1 at ¶ ¶ 73-78. While
3
it is true, as Defendants argue, that the contract at issue provides Defendants with the freedom to
4
run their business as desired, the resolution of Plaintiff’s claim also requires an analysis of the
5
parties’ expectations of the contract they bargained. Nemec, 991 A.2d at 1126. That is a question
6
that requires a more developed factual record and cannot be resolved at this stage. As a result, the
7
Court finds that, accepting Plaintiff’s allegations as true for purposes of this motion, Plaintiff has
8
9
10
11
12
13
14
sufficiently pled a claim for breach of the implied covenant of good faith and fair dealing based
on frustration, and the claim will not be dismissed at this stage of the proceedings.
D. Breach of Fiduciary Duty
The Court next turns to Plaintiff’s claim for breach of fiduciary duty. Defendants argue
that Plaintiff’s claim fails because it arises from obligations that are expressly addressed by
contract. Dkt. #26 at 14. Plaintiff responds that the “joint venture” nature of the relationship
15
16
17
between the Contributing Shareholders and Defendants provide a basis for the claim, and the
claim should be allowed to move forward. Dkt. #31 at 20-23. The Court disagrees.
18
Under Delaware law, “[i]t is a well-settled principle that where a dispute arises from
19
obligations that are expressly addressed by contract, that dispute will be treated as a breach of
20
contract claim. In that specific context, any fiduciary claims arising out of the same facts that
21
underlie the contract obligations would be foreclosed as superfluous.” Nemec, 991 A.2d at 1129.
22
Here, as in Nemec, Plaintiff’s claim essentially “seeks to enforce obligations that are expressly
23
24
25
addressed by contract (the Stock Plan), and that, therefore, must be adjudicated within the
analytical framework of a breach of contract claim.” Id.
ORDER – 8
1
Plaintiff’s argument that there is somehow a joint venture between the Contributing
2
Shareholders and Defendants is not persuasive. It is clear that the transaction at issue here
3
constituted an acquisition where Defendants purchased all of the equity of Vieosoft, not a joint
4
venture where the former shareholders retained any ownership or right of control. See Dkt. #1 at
5
¶ 20 and Dkt. #1-1 at § 1.1. Accordingly, the Court agrees that this claim must be dismissed as
6
superfluous.
7
8
9
E. Breach of Contract
Defendants next argue that Plaintiff has failed to state any express breach of contract
10
claim. Specifically, Defendants argue that Plaintiff has failed to state that Defendants have
11
breached any obligation imposed by the contract. The Court disagrees. Plaintiff has pled a valid
12
breach of contract claim on its face. Indeed, Plaintiff has alleged the breach of eight obligations
13
14
under the contract. Dkt. #31 at 10. Whether or not the alleged breaches are in fact breaches is a
factual matter not appropriate for resolution at this stage. Further, Plaintiff’s claim based on
15
16
17
frustration will not be dismissed, the resolution of which impacts the breach of contract claim as
well, and Plaintiff’s breach of fiduciary duty claim is being treated as one for breach of contract as
18
discussed above. For these reasons, the Court will not dismiss this claim at this stage of the
19
proceedings.
20
21
F. Defendants Emdeon and EBS
Finally, Defendants move to dismiss Emdeon and EBS from this action on the basis that
22
neither was a party to the contract and therefore neither owes any contractual duties to Plaintiff.
23
24
25
Dkt. #26 at 22. Plaintiff argues that it is not appropriate to dismiss these Defendants as Envoy,
LLC, the entity that executed the agreement, was established solely as an acquisition vehicle and
ORDER – 9
1
Emdeon was the entity that paid the Contributing Shareholders and remained responsible for
2
future payments to those Shareholders. Dkt. #31 at 24. Plaintiff further argues that it has
3
sufficiently pled claims against these entities. Id. The Court agrees with Plaintiff.
4
In examining similar situations, Delaware courts have declined to dismiss Defendants who
5
were not a signatory to the contract. For example, in Cerberus Int’l, Ltd. v. Apollo Mgmt., L.P.,
6
1999 Del Ch. LEXIS 207, *6-7 (Del. Ch. Nov. 2, 1999), the Court of Chancery of Delaware
7
explained:
8
9
10
11
12
13
14
15
16
17
18
19
20
under either standard Apollo would qualify [as a party Defendant], at least
for purposes of this motion. If the broader (“interested person”) standard is
the test, then Apollo would be a proper party, because the Complaint alleges
(at P 6) that Apollo acquired MTI through Newco, a shell corporation newly
formed by Apollo for that purpose. Thus, the Amended Complaint may
fairly be read to claim that Apollo is the true owner of MTI, and as such was
the real purchaser in interest.
Even if the narrower standard were applicable Apollo would be a proper
defendant, because the Amended Complaint alleges facts from which an
extra contractual basis for Apollo’s joinder can be inferred, namely, that
Newco – the nominal purchaser and Merger Agreement signatory – was the
agent and/or ego of Apollo and acted solely on Apollo’s behalf. That is a
reasonable inference from the allegations that Apollo (i) made the offer to
acquire MTI and (ii) in fact acquired MTI, through a shell subsidiary
(Newco) that was formed at the direction of, and was either directly or
indirectly controlled by, Apollo.
Accordingly, in these circumstances and at this stage, I find that Apollo is a
proper party defendant.
21
Id. The Court finds the same reasoning persuasive in the instant matter and declines to dismiss
22
Emdeon and EBS at this time.
23
E. Leave to Amend
24
25
Ordinarily, leave to amend a complaint should be freely given following an order of
dismissal, “unless it is absolutely clear that the deficiencies of the complaint could not be cured
ORDER – 10
1
by amendment.” Noll v. Carlson, 809 F.2d 1446, 1448 (9th Cir. 1987); see also DeSoto v. Yellow
2
Freight Sys., Inc., 957 F.2d 655, 658 (9th Cir. 1992) (“A district court does not err in denying
3
leave to amend where the amendment would be futile.” (citing Reddy v. Litton Indus., Inc., 912
4
F.2d 291, 296 (9th Cir. 1990)). Given the basis for dismissing Plaintiff’s breach of fiduciary duty
5
claim, discussed above, the Court finds that the claim cannot be cured by further amendment.
6
IV.
CONCLUSION
7
Having reviewed Plaintiff’s Complaint and the Exhibits thereto, the parties’ briefing on
8
9
10
11
12
13
14
the instant motion, and the remainder of the record, the Court hereby finds and ORDERS:
1. Defendants’ Motion to Dismiss (Dkt. #26) is GRANTED IN PART AND DENIED IN
PART as set forth above.
2. Plaintiff’s claims for breach of the implied covenant of good faith and fair dealing and
breach of contract shall proceed.
3. Plaintiff’s claim for breach of fiduciary duty is dismissed without leave to amend.
15
16
DATED this 17th day of September 2015.
17
A
18
19
RICARDO S. MARTINEZ
UNITED STATES DISTRICT JUDGE
20
21
22
23
24
25
ORDER – 11
Disclaimer: Justia Dockets & Filings provides public litigation records from the federal appellate and district courts. These filings and docket sheets should not be considered findings of fact or liability, nor do they necessarily reflect the view of Justia.
Why Is My Information Online?