EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
healthcareitnews.com
EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
1–10 of 21 posts
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#220% payout to the whistleblower. That's pretty hefty!
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#3Interestingly, this lawsuit was filed in my home state of Vermont -- because Vermont is "sympathetic" to fraud charges.
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#4> Navani, along with CMO Rajesh Dharampuriya and COO Mahesh Navani are liable for the payment of $154,920,000, while developer Jagan Vaithilingam is on the hook for $50,000 and two project managers, Bryan Sequeira and Robert Lynes, each owe $15,000, the Vermont DOJ said.
Pretty interesting to see a Developer and PM have to pay out as well. I wonder how the judge reached that conclusion.
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#5It looks like they fined officers of the company, as well as a developer and 2 PMs. Is this standard practice for False Claims Act suits? How much should I worry about this as a developer?
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#6It looks like they fined officers of the company, as well as a developer and 2 PMs. Is this standard practice for False Claims Act suits? How much should I worry about this as a developer?
IANAL and I can't find the court documents, but probably not much. Not unless you are offering up solutions to intentionally bypass the requirements.
Having worked at an EHR, PMs routinely instructed us to build things specifically. I could suggest cosmetic stuff, but couldn't really suggest changes to the underlying business logic of the requirements because it had usually been hammered out by PMs/Nurses/Doctors/Maybe-legal. These requirements formed the basis of test cases for QA to run though.
ECW was not the vendor I worked for, so it's possible the developer had more influence over business logic or its implementation.
These things sound like time or cost-cutting measures:
>opted to added the 16 drug codes necessary for certification into its software rather than enable the product to access those from a complete database
Sounds like they didn't buy the database.
>eClinicalWorks did not satisfy data portability requirements designed to enable doctors to transfer patient data to over vendor’s EHRs
This sounds like they didn't want to build something to export to CCDA?
These sound like negligence / not enough testing:
>failed to accurately record user actions with audit log functionality
>did not always accurately record diagnostic imaging orders or conduct drug-drug interaction checks
For drug-drug interaction, that is probably another drug database to purchase, so it's possible they simply hadn't bought it. Building your own is obviously out of the question.
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#7It looks like they fined officers of the company, as well as a developer and 2 PMs. Is this standard practice for False Claims Act suits? How much should I worry about this as a developer?
IANAL and I can't find the court documents, but probably not much. Not unless you are offering up solutions to intentionally bypass the requirements. Having worked at an EHR, PMs routinely instructed us to build things specifically. I could suggest cosmetic stuff, but couldn't really suggest changes to the underlying business logic of the requirements because it had usually been hammered out by PMs/Nurses/Doctors/May…
Yeah DDI check are tricky, and you basically have to buy a solution.
As for the CCDA piece, that's interesting. It should be pretty easy to build that, it's a pretty simple standard and I think there are C# and Java libs that basically just do it.
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#8Earlier quoted context omitted.
IANAL and I can't find the court documents, but probably not much. Not unless you are offering up solutions to intentionally bypass the requirements. Having worked at an EHR, PMs routinely instructed us to build things specifically. I could suggest cosmetic stuff, but couldn't really suggest changes to the underlying business logic of the requirements because it had usually been hammered out by PMs/Nurses/Doctors/May…
Yeah DDI check are tricky, and you basically have to buy a solution. As for the CCDA piece, that's interesting. It should be pretty easy to build that, it's a pretty simple standard and I think there are C# and Java libs that basically just do it.
> It should be pretty easy to build that
lol. It's not the standard that's hard, it's how every EHR vendor has implemented it.
*ehr employee who's worked with CCDA and FHIR
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#9Earlier quoted context omitted.
Yeah DDI check are tricky, and you basically have to buy a solution. As for the CCDA piece, that's interesting. It should be pretty easy to build that, it's a pretty simple standard and I think there are C# and Java libs that basically just do it.
> It should be pretty easy to build that lol. It's not the standard that's hard, it's how every EHR vendor has implemented it. *ehr employee who's worked with CCDA and FHIR
Yeah, the implementation vary quite a bit. FHIR seems like it might actually be nice.
Re: EHR vendor eClinicalWorks to pay $155M to settle whistleblower suit
#10Earlier quoted context omitted.
Yeah DDI check are tricky, and you basically have to buy a solution. As for the CCDA piece, that's interesting. It should be pretty easy to build that, it's a pretty simple standard and I think there are C# and Java libs that basically just do it.
> It should be pretty easy to build that lol. It's not the standard that's hard, it's how every EHR vendor has implemented it. *ehr employee who's worked with CCDA and FHIR
[deleted]