throbber
Case 1:19-cv-11278-RGS Document 24 Filed 09/13/19 Page 1 of 4
`
`UNITED STATES DISTRICT COURT
`DISTRICT OF MASSACHUSETTS
`
`
`Plaintiff,
`
`UNILOC 2017 LLC,
`
`
`
`v.
`
`ATHENAHEALTH, INC.,
`
`
`
`Defendant.
`
`Civil Action No. 1:19-cv-11278-RGS
`
`
`
`
`
`AMENDED COMPLAINT
`
`Plaintiff, Uniloc 2017 LLC (“Uniloc), for its Amended Complaint against defendant,
`
`athenahealth, Inc. (“Athenahealth”), alleges:
`
`THE PARTIES
`
`Uniloc is a Delaware limited liability company.
`
`Athenahealth is a Delaware corporation having a principal place of business in
`
`1.
`
`2.
`
`Watertown, Massachusetts.
`
`JURISDICTION
`
`3.
`
`Uniloc brings this action for patent infringement under the patent laws of the
`
`United States, 35 U.S.C. § 271, et seq. This Court has subject matter jurisdiction under 28 U.S.C.
`
`§§ 1331 and 1338(a).
`
`COUNT I
`(INFRINGEMENT OF U.S. PATENT NO. 6,324,578)
`
`Uniloc incorporates paragraphs 1-3 above by reference.
`
`Uniloc is the owner, by assignment, of U.S. Patent No. 6,324,578 (“the ’578
`
`4.
`
`5.
`
`Patent”), entitled METHODS, SYSTEMS AND COMPUTER PROGRAM PRODUCTS FOR
`
`MANAGEMENT OF CONFIGURABLE APPLICATION PROGRAMS ON A NETWORK,
`
`3288456.v1
`
`1
`
`

`

`Case 1:19-cv-11278-RGS Document 24 Filed 09/13/19 Page 2 of 4
`
`which issued on November 27, 2001 on an application filed on December 14, 1998. A copy of
`
`the ’578 Patent was attached as Exhibit A to the Complaint.
`
`6.
`
`Athenahealth operated a centrally hosted Content Distribution Network known as
`
`athenaNet.
`
`7.
`
`Athenahealth infringed claims of the ’578 Patent by making, using, offering for
`
`sale, and selling the athenaNet system, as further detailed in the attached Exhibit C.
`
`8.
`
`Athenahealth also infringed the ’578 Patent by actively inducing the use of the
`
`athenaNet system. Athenahealth’s customers who used the athenaNet system as Athenahealth
`
`instructed infringed at least claims 15, 31, and 46 of the ’578 patent. Athenahealth intentionally
`
`instructed its users to infringe, with knowledge they were infringing, by providing instructions
`
`with its athenaNet system.
`
`9.
`
`Athenahealth also infringed the ’578 patent by offering to sell, selling, or
`
`otherwise commercializing the athenaNet system, which was used to infringe the ’578 Patent,
`
`and constituted a material part of the invention. Athenahealth knew portions of the software in
`
`the athenaNet system that provide the infringing functionality were especially written solely for
`
`use to implement what it knew was infringement of the ’578 Patent, as described above.
`
`Athenahealth also knew those portions had no use, other than for infringement.
`
`10.
`
`Athenahealth has been on notice of the ’578 Patent since, at the latest, the service
`
`of the complaint upon Athenahealth on May 17, 2017, in the previous action between Uniloc and
`
`Athenahealth in the Eastern District of Texas. Athenahealth has known and intended (since
`
`receiving such notice) that its continued actions would actively induce and contribute to
`
`infringement of the ’578 Patent.
`
`3288456.v1
`
`2
`
`

`

`Case 1:19-cv-11278-RGS Document 24 Filed 09/13/19 Page 3 of 4
`
`11.
`
`Athenahealth may have infringed the ’578 Patent through other software and
`
`architecture utilizing the same or reasonably similar functionality, including other versions of the
`
`athenaNet system.
`
`12.
`
`Uniloc has been damaged by Athenahealth’s infringement of the ’578 Patent.
`
`COUNT II
`(INFRINGEMENT OF U.S. PATENT NO. 7,069,293)
`
`Uniloc incorporates by reference paragraphs 1-12 above.
`
`Uniloc is the owner, by assignment, of U.S. Patent No. 7,069,293 (“the ’293
`
`13.
`
`14.
`
`Patent”), entitled METHODS, SYSTEMS AND COMPUTER PROGRAM PRODUCTS FOR
`
`MANAGEMENT OF APPLICATION PROGRAMS TO A TARGET STATION ON A
`
`NETWORK, which issued on June 27, 2006, claiming priority to an application filed on
`
`December 14, 1998. A copy of the ’293 Patent was attached as Exhibit B to the Complaint.
`
`15.
`
`Athenahealth has infringed, and continues to infringe, claims of the ’293 Patent
`
`by making, using, offering for sale, or selling the athenaNet system, as further detailed in the
`
`attached Exhibit D.
`
`16.
`
`Athenahealth has been on notice of the ’293 Patent since, at the latest, the service
`
`of the complaint upon Athenahealth on May 17, 2017 in a previous action between Uniloc and
`
`Athenahealth in the Eastern District of Texas. By the time of trial, Athenahealth will have
`
`known and intended (since receiving such notice) that its continued actions would infringe the
`
`’293 Patent.
`
`17.
`
`Athenahealth may have infringed the ’293 Patent through other software and
`
`architecture utilizing the same or reasonably similar functionality, including other versions of the
`
`athenaNet system.
`
`18.
`
`Uniloc has been damaged by Athenahealth’s infringement of the ’293 Patent.
`
`3288456.v1
`
`3
`
`

`

`Case 1:19-cv-11278-RGS Document 24 Filed 09/13/19 Page 4 of 4
`
`PRAYER FOR RELIEF
`
`Uniloc requests that the Court enter judgment against Athenahealth:
`
`(A)
`
`that Athenahealth has infringed the ’578 Patent and the ’293 Patent;
`
`(B)
`
`awarding Uniloc its damages suffered as a result of Athenahealth’s infringement
`
`of the ’578 Patent and the ’293 Patent;
`
`(C)
`
`awarding Uniloc its costs, attorneys’ fees, expenses, and interest, and
`
`(D)
`
`granting Uniloc such further relief as the Court may deem proper.
`
`
`Date: September 13, 2019
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
`/s/ James J. Foster
`Paul J. Hayes
`James J. Foster
`Kevin Gannon
`PRINCE LOBEL TYE LLP
`One International Place, Suite 3700
`Boston, MA 02110
`Tel: (617) 456-8000
`Fax: (617) 456-8100
`Email: phayes@princelobel.com
`Email: jfoster@princelobel.com
`Email: kgannon@princelobel.com
`
`ATTORNEYS FOR THE PLAINTIFF
`
`
`CERTIFICATE OF SERVICE
`
`I certify that all counsel of record who have consented to electronic service are being
`
`served with a copy of this document via the Court’s CM/ECF system on September 13, 2019.
`
`
`
`
`
`/s/ James J. Foster
`
`
`
`
`
`
`
`
`
`
`
`3288456.v1
`
`4
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket