Events Calendar

Mon
Tue
Wed
Thu
Fri
Sat
Sun
M
T
W
T
F
S
S
26
27
28
29
30
31
2
3
4
5
6
7
8
9
10
8:30 AM - HIMSS Europe
11
12
13
14
15
16
17
18
19
20
21
22
26
27
28
29
1
2
3
4
5
6
e-Health 2025 Conference and Tradeshow
2025-06-01 - 2025-06-03    
10:00 am - 5:00 pm
The 2025 e-Health Conference provides an exciting opportunity to hear from your peers and engage with MEDITECH.
HIMSS Europe
2025-06-10 - 2025-06-12    
8:30 am - 5:00 pm
Transforming Healthcare in Paris From June 10-12, 2025, the HIMSS European Health Conference & Exhibition will convene in Paris to bring together Europe’s foremost health [...]
38th World Congress on  Pharmacology
2025-06-23 - 2025-06-24    
11:00 am - 4:00 pm
About the Conference Conference Series cordially invites participants from around the world to attend the 38th World Congress on Pharmacology, scheduled for June 23-24, 2025 [...]
2025 Clinical Informatics Symposium
2025-06-24 - 2025-06-25    
11:00 am - 4:00 pm
Virtual Event June 24th - 25th Explore the agenda for MEDITECH's 2025 Clinical Informatics Symposium. Embrace the future of healthcare at MEDITECH’s 2025 Clinical Informatics [...]
International Healthcare Medical Device Exhibition
2025-06-25 - 2025-06-27    
8:30 am - 5:00 pm
Japan Health will gather over 400 innovative healthcare companies from Japan and overseas, offering a unique opportunity to experience cutting-edge solutions and connect directly with [...]
Electronic Medical Records Boot Camp
2025-06-30 - 2025-07-01    
10:30 am - 5:30 pm
The Electronic Medical Records Boot Camp is a two-day intensive boot camp of seminars and hands-on analytical sessions to provide an overview of electronic health [...]
Events on 2025-06-01
Events on 2025-06-10
HIMSS Europe
10 Jun 25
France
Events on 2025-06-23
38th World Congress on  Pharmacology
23 Jun 25
Paris, France
Events on 2025-06-24
Events on 2025-06-25
International Healthcare Medical Device Exhibition
25 Jun 25
Suminoe-Ku, Osaka 559-0034
Events on 2025-06-30

Events

Latest News

TCS to appeal $940 million Epic EHR infringement fines

TCS

The two fines on seven claims, including breach of contract, unfair competition and enrichment, and misappropriation of trade secrets, were for $240 million in compensatory and $700 million in punitive damages, according to The Indian Express.
The Mumbai-based Tata companies slammed with the penalties, Tata Consultancy Services (TCS) and Tata America International, claimed that they “did not misuse or derive any benefit from downloaded documents from Epic System’s user-web portal,” in a statement emphasizing that, in addition, no use was made “of said information for development of its own hospital management system ‘Med Mantra’, which was implemented for a large hospital chain in India in 2009.”

“TCS plans to defend its position vigorously in appeals to higher courts. TCS appreciates the trial judge’s announcement from the bench that he is almost certain he will reduce the damages award,” according to India Today.

The huge award was in question even before the federal jury determined it, however. The District Judge William M. Conley had already raised doubts, according to Reuters, noting that the Indian firm had stated that it “appreciates the trial judge’s announcement from the bench that he is almost certain he will reduce the damages award.”

The lawsuit was filed in 2014. At the heart of the case is that Epic software was being used by Kaiser Permanente, and that institution had hired TCS to help implement the EHR system. A TCS employee then “fraudulently accessed” and downloaded 6,477 documents to which TCS was not entitled, according to court documents.

“Rather than compete lawfully with Epic, TCS has engaged in an apparently elaborate campaign of deception to steal documents, confidential information, trade secrets, and other information and data from Epic, for the purpose of realising technical expertise developed by Epic over years of hard work and investment,” the lawsuit stated according to India Today.

There are a number of issues that complicate the seemingly straightforward case of a TCS worker wrongly accessing Epic information, according to The Wire.

Kaiser licensed Epic’s software in 2003, then brought in TCS in 2005, at which point Epic and TCS signed a consulting agreement in which TCS agreed that Epic’s program held trade secrets that were protected. Then in 2011 Kaiser had TCS test Epic software, giving support for Epic releases, upgrades and maintenance, which it was agreed would happen at offshore sites in India.

These sites were “required” to have data confidentiality protection like disabled USB ports, no email and no Internet access — but there were several machines at these sites, in fact, that did have enabled ports and email, called “kiosk machines”.

TCS claimed these machines were disabled, but a TCS employee testimony revealed that they had both Internet access and working ports. This meant that TCS employees could “download release notes,” which they used to make tests for Kaiser. This was, in effect, a workaround that violated the data security protocol that requires that information be gotten from Epic’s web portal by its own employees or Kaiser personnel and then they would respond to TCS workers’ requests.

In addition, one TCS employee had earlier legitimately had and used prior access rights to the Epic portal, gotten through his work on a previous project, and proceeded to use for the Kaiser project his old credentials to access the Epic site, download information onto a kiosk hard drive, and email it to himself, a violation of the user agreement with Epic. He then shared this information with other TCS workers.

The Epic claim is that the thousands of documents thus obtained, “contain detailed information on the features and functionalities of Epic’s software and database systems developed over thirty years.” In addition, because some of the TCS employees who had access to these documents used them for a comparison study between Epic’s software and TCS’s Med Mantra. This was given to the Med Mantra developers.

TCS responded that these “were of the type necessary for work of the TCS testing team.”

Source