The Community Clinic Inc. v. Health Grid, LLC

CourtDistrict Court, D. Maryland
DecidedAugust 20, 2021
Docket8:20-cv-03208
StatusUnknown

This text of The Community Clinic Inc. v. Health Grid, LLC (The Community Clinic Inc. v. Health Grid, LLC) is published on Counsel Stack Legal Research, covering District Court, D. Maryland primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
The Community Clinic Inc. v. Health Grid, LLC, (D. Md. 2021).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF MARYLAND

THE COMMUNITY CLINIC INC., *

Plaintiff, *

v. * Civil Action No. 8:20-cv-3208-PX

HEALTHGRID, LLC, et al., *

Defendants. * *** MEMORANDUM OPINION Pending before the Court in this breach of contract action is the motion to dismiss filed by Defendants HealthGrid, LLC, and Allscripts Healthcare, LLC, and brought pursuant to Federal Rule of Civil Procedure 12(b)(6). ECF No. 22. The matter has been fully briefed, and no hearing is necessary. See Loc. R. 105.6. For the following reasons, the motion to dismiss is granted in part and denied in part. I. Background Plaintiff the Community Clinic Inc., (“CCI”), a community health center, primarily serves indigent patients in Prince George’s and Montgomery counties in Maryland. ECF No. 21 ¶¶ 1-2. Defendant Health Grid, LLC, (“HealthGrid”) is a healthcare technology company headquartered in Orlando, Florida. Id. ¶ 3. Defendant Allscripts Healthcare, LLC, (“Allscripts”) is the parent company of HealthGrid. Id. ¶ 5; ECF No. 11 at 2. Allscripts acquired HealthGrid in May 2018, and in a related press release, touted that Allscripts would “integrate the HealthGrid capabilities into its FollowMyHealth platform, enabling provider organizations to reach 100% of their patient populations without requiring their healthcare customers to sign into a portal.” ECF No. 21 ¶¶ 7, 23. Throughout the business relationship between CCI and HealthGrid at the heart of this case, HealthGrid employees identified themselves as working for Allscripts; they used Allscripts email accounts and Allscripts signature blocks. See, e.g., ECF No. 23-4. When CCI had questions about billing terms, HealthGrid directed such inquiries to Allscripts. ECF No. 23-9 at 2. And when CCI needed certification of its collaboration with HealthGrid, CCI was directed to

Allscripts’ legal department who produced the certification. Id. In July 2018, HealthGrid and CCI began negotiations to provide updated computer software for CCI’s Patient Appointments & Reminders (“PAR”) system, a program that scans CCI’s medical records and sends patients automatic reminders for upcoming appointments, and its Patient Portal, which provides patients digital access to their medical records. ECF No. 21 ¶¶ 14–15, 19. On July 17, 2018, Dr. Sonya Bruton, Associate Chief Executive Officer and Chief Operating Officer for CCI, met with HealthGrid representatives to discuss their proposed updates to the PAR system. Id. ¶ 24. At that meeting, Dr. Bruton made clear that the upgrades CCI sought must not only provide patients with reminders but must also interface with CCI’s existing patient portal and scheduling systems. Id. ¶¶ 27–28. Put differently, CCI required a “bi-

directional” system that would automatically populate CCI’s existing medical records with the information that patients provided using the updated PAR system. Id. HealthGrid confirmed that it could meet these demands. Id. ¶ 30. In September 2018, CCI and HealthGrid struck a deal, as memorialized in the “Solution Agreement” (the “Agreement”) and incorporated “Statement of Work,” (“SOW”). ECF Nos. 21 ¶¶ 34–37; 22-2. The parties agreed that “HealthGrid will provide use of applicable software and mutually agreed upon services to [CCI] as described in the attached SOW(s).” ECF No. 22-2 ¶ 1. Specifically, HealthGrid would provide such patient-centered applications as a mobile electronic appointment reminder system; a secure mobile messaging system; mobile check-in and appointment cancellation services; deployment of satisfaction surveys to patients; and creation of a secure patient portal for patients to view, download, and transmit health information. Id. For staff, CCI expected to receive an on-demand messaging system that staff could use to communicate with patients, and an internal “gap-in-care” engine to identify patient

subpopulations for quality improvement measures. Id. As for the timing of the services, the SOW provided that the parties would “mutually agree to an implementation and deployment plan . . . [that would] be live with at least one service within 120 days of contract signing,” or by January 2019. ECF Nos. 21 ¶ 36; 22-2 at 6. Further, the parties agreed to choose a date for the “Project Kick-off,” as well as a mutually agreed upon set of substantive and timing milestones as set forth in a “Project Plan.” ECF No. 22-2 ¶ 4. HealthGrid also agreed to use “commercially reasonable efforts to avoid delays in the Project schedule.” Id. CCI and HealthGrid held the “Project Kick-off” meeting on October 18, 2018. ECF No. 21 ¶ 43. At the meeting and per the terms of the Agreement, HealthGrid presented to CCI its

Project Plan, which defined the project’s scope and timeline. Id. ¶¶ 45–46. The Project Plan specified that the appointment optimization and post-care summary components would be completed in January 2019; the Gap-in-Care campaign and satisfaction surveys by March 2019; and the electronic check-in and patient portal by April 2019. Id. ¶ 46. Immediately after the Project Kick-off, HealthGrid encountered difficulties in implementing the Project Plan. As a result, none of the promised services were delivered within 120 days or within the milestones set forth in the Project Plan. ECF No. 21 ¶¶ 41, 47. Chief among the difficulties was implementing a “bi-directional” PAR system. Id. ¶¶ 49, 67–99. At the time, CCI’s used an electronic records program produced by Virence Health Technologies (“Virence”). Id. ¶¶ 54–55. HealthGrid proposed that it could implement bi-directional functionality in the PAR system by either using the current Virence platform or, if necessary, implementing different administrative and scheduling technology. Id. ¶ 66. Unfortunately, Virence notified HealthGrid and CCI that the current system would not support bi-directionality,

but offered to implement a different Virence system that could achieve CCI’s desired functionality. Id. ¶¶ 66–74. HealthGrid, in response, began exploring other options. Id. ¶¶ 75– 80. HealthGrid Project Manager, Claire Gagarin, stayed in close contact with CCI personnel about the project’s progress generally and with respect to the difficulties in implementing a bi- directional PAR system. See, e.g., ECF No. 21 ¶¶ 48–58, 80, 86.1 Within a month from kickoff, Gagarin informed CCI that although she expected CCI would receive the bi-directional functionality it sought, the project would not be completed by the deadlines originally promised. ECF Nos. 21 ¶¶ 84–98; 23-8; 23-9. Gagarin also represented that HealthGrid continued to make progress on implementing the PAR system but could not give a firm alternative timeline for

completion. ECF No. 21 ¶¶ 84–89. By March 27, 2019, HealthGrid forecasted to CCI that the PAR system would be completed by May 2019. ECF Nos. 21 ¶ 103; 23-9 at 4. The next day, HealthGrid invoiced CCI for $25,000 for work performed on the “Implementation & Setup” phase of the project, and for $83,640 for work on the “Annual Pre Care, Post Care, and Point of Care” phase. ECF No. 21 ¶ 104. Relying on HealthGrid’s representations that HealthGrid was on track to complete the bi- directional PAR system, CCI paid the invoices. Id. ¶ 105.

1 The Court views the email correspondence between Gagarin and CCI as incorporated by reference into the Amended Complaint. See Balt. Scrap Corp. v. Exec. Risk Specialty Ins. Co., 388 F. Supp. 3d 574, 585 (D. Md. 2019) (explaining “a court may consider documents that are “explicitly incorporated into the complaint by reference”). A few weeks later, in mid-April 2019, Gagarin twice telegraphed to CCI that the “technical requirements” for the PAR system were “complete.” ECF No. 21 ¶¶ 106–07.

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

Related

The Bremen v. Zapata Off-Shore Co.
407 U.S. 1 (Supreme Court, 1972)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Ruiz v. Brink's Home Sec., Inc.
777 So. 2d 1062 (District Court of Appeal of Florida, 2001)
Connecticut General Life Ins. Co. v. Jones
764 So. 2d 677 (District Court of Appeal of Florida, 2000)
Residential Warranty Corp. v. Bancroft Homes Greenspring Valley, Inc.
728 A.2d 783 (Court of Special Appeals of Maryland, 1999)
Dixon v. Process Corp.
382 A.2d 893 (Court of Special Appeals of Maryland, 1978)
Bane v. Bane
25 Fla. L. Weekly Fed. S 1070 (Supreme Court of Florida, 2000)
Proctor v. Metropolitan Money Store Corp.
579 F. Supp. 2d 724 (D. Maryland, 2008)
Knowles v. CIT Corporation
346 So. 2d 1042 (District Court of Appeal of Florida, 1977)
Brooks v. Euclid Systems Corp.
827 A.2d 887 (Court of Special Appeals of Maryland, 2003)
Green v. H & R BLOCK, INC.
735 A.2d 1039 (Court of Appeals of Maryland, 1999)
Schaefer v. Aetna Life & Casualty Co.
910 F. Supp. 1095 (D. Maryland, 1996)
Bray & Gillespie Management LLC v. Lexington Insurance
527 F. Supp. 2d 1355 (M.D. Florida, 2007)
Hildreth v. Tidewater Equipment Co.
838 A.2d 1204 (Court of Appeals of Maryland, 2003)
Antonio v. SECURITY SERVICES OF AMERICA, LLC
701 F. Supp. 2d 749 (D. Maryland, 2010)
Acciai Speciali Terni USA, Inc. v. M/V BERANE
181 F. Supp. 2d 458 (D. Maryland, 2002)
Robinson v. Fountainhead Title Group Corp.
447 F. Supp. 2d 478 (D. Maryland, 2006)
Roman Zak v. Chelsea Therapeutics International
780 F.3d 597 (Fourth Circuit, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
The Community Clinic Inc. v. Health Grid, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/the-community-clinic-inc-v-health-grid-llc-mdd-2021.