Karma whoring is the requisite corollary for non-anonymous trolling.
Their flagship app is written in VB6 with Cache and AIX. To say that it isn't as bad as public opinion is a gross misunderstanding of just how bad it is.
That said, there is a dramatically different experience from implementers to support, devs, IT, and the many different roles in the organization. And not all of them suck, but from the dev pool, I know far more former Epic developers than current epic developers.
It's a LANoT.
No, 1:16:9. Our entire solar system moved to high-def monoliths shortly after 2001.
But local reception really degraded...
So I'm not at all surprised to learn that doctors are resorting to faxing records. It's almost certainly easier than trying to exchange them digitally.
I thought all faxes were transmitted and received digitally... for the past 20 years. Are there still people storing them on paper?
Normal Facsimile workflow is like this:
1) person pulls up the records, saves them as PDF
2) Person "prints" PDF to fax
3) PDF is converted to CCITT-compatible TIFF format, which is then
4) transmitted as a high quality fax (we're not talking the old 30dpi ones anymore)
5) Recipient's fax machine gets the fax with header info, saves it as PDF and emails it to the appropriate local recipient
6) PDF is saved from email, possibly printed if needed, and filed via the local EMR.
And this is why the data you're looking for is in the hospital's EMR as a PDF: it was received by fax.
Any solution that's going to change this workflow is going to need to handle TIFF and PDF formats, with ClearText-style OCR. That way, people can still use the fax workflow as an alternative to digital data transmission. The system also has to have the ability to pull up the original PDFs in the cases where the OCR failed.
It'll then take at LEAST 5-10 years for the new digital transmission system to work out the kinks and gain enough momentum to retire the old workflow completely.
Leave it to motherfucking Jeremiah Cornelius, whose opinions are so fucking important that he just has to barge his fat ass to the front of the line to reply to the post which will get him closest to the top, no matter whether that post has anything to do with what he wishes to say.
What an asshole.
Thanks for living in the past.
First he urged their selflessness and humility - then in the second case? He exhibited his own.
You are noble. In the best and most approving sense of the word.
There are people who haven't faced a fraction of your difficulty, who are yet to perform the level of introspection you've mustered to understand how they behave - and to derive from it a mission or a wish.
"but it is possible to be happy and depressed, the thoughts are not mutually exclusive."
Yes. Happiness is a real trip.
I don't know if we'd get along together in "real life" - but around this ASCII-space, I'm one of your real fans and supporters. And I'm glad to be.
"I've learned that people will forget what you said, people will forget what you did, but people will never forget how you made them feel."
-- Maya Angelou
...which means if it "can't be done" then you can sue the healthcare provider AND Epic for failing to comply with HIPAA. Since it's a federal offense, you don't even have to foot the bill yourself.
It must be truly horrendous software if the data store is slaved to the UI.
In a system like this, the interface should be easily rewritten by anyone who wants to, and just talk to the back end using a Standard Query Language.
This is a problem that has been solved many times, and yet you STILL get companies like this who have cornered the market with a solution that's 30 years out of date.
When a replacement system is created, it should at least be backed by a public key infrastructure and use two-factor authentication. It should use a standard back-end database with an open tokenization system, a validation system, and logical data typing.
Otherwise, it's really not much better than digital faxes or email with some analysis software tacked on the front with a pretty UI.
Invoke eminent domain to seize the right to share the data, for the common good of citizens health and safety
Mod parent up. This is actually a good idea -- and it'll scare companies into interoperation like fines will never do.
The other bit of information that's in TFS is that this key-logger is sending the logged information in clear-text to a third party.
Let me repeat that: it's sending keystrokes in the clear to a third party.
At this point, it doesn't really matter who it's aimed at, who is supposed to read the information, etc. If keystrokes are being logged and the data is being sent in the clear, then that pretty much means you've got a major security hole in your network. Even if malware authors don't exploit it, it makes ComputerCOP a juicy target for "hackers" worldwide, and it also places employees of the service under undue responsibility to keep your information safe.
This stuff appears to be more shoddily constructed than the key-loggers dropped by the likes of the Zeus bot-net. Think about that.
"The right of the people to be secure in their persons, houses, papers, and effects, against unreasonable searches and seizures, shall not be violated, and no Warrants shall issue, but upon probable cause, supported by Oath or affirmation, and particularly describing the place to be searched, and the persons or things to be seized."
Note that the feds gave docs/hospitals $24 billion to digitalize, of which over half of went either directly to EPIC or to epic contractors.
And this is the source of success of EPIC. Their software is pretty much crap. They hire fleets of college grads, work them for 60+ hour work weeks, burn them out in under 2 years, and replace them with the next lot of inexperienced automatons. The genius isn't in the code, it's in cornering the market of a federally subsidized effort.