- It's direct point to point communication (over a network)
- The transport network is dedicated and not open to anyone and covered by quite strong laws in many countries
- It's easy to see the history of communications
- It's easy to see if the other end successfully received something
- It's relatively standardized and ubiquitous ( in health )
Email would be the closest thing, but it doesn't have all the advantages, and the extra add ons that would make it better (like encryption, delivery receipt, digital signatures) are not standardized and/or ubiquitous ( and often hotly argued about )
So fax is the lowest common denominator, that, if it was proposed today, would not be accepted for many of its disadvantages, but it's now hard to find a way to replace it.
is it? what if the hospital is using a VOIP solution?
I think this is a biggie. It means your workflow doesn't need to include going back later and checking to see if your document was received, and then trying to send it some different way. You don't have to guess which way the recipient is capable of receiving a message.
It's the original e-mail. ;-)
Many fax machine can be programmed over the wire, so maybe you have default pins and now your faxes are being forwarded and you don't know.
This was not the case when I worked in healthcare. It was a constant back and fourth of "did you receive it?" over the phone.
And you basically file a police report, hardly anyone cares, and you are left with a bunch of paperwork to go fix it yourself. You get the money back eventually with plenty of paperwork.
At which point do thieves committing all sorts of punishable crimes actually get punished? In my case, the person signed up for a line of credit at Lowes, purchased 20k of construction goods, presumable all in a videotaped store and got off scott free.
https://research.checkpoint.com/sending-fax-back-to-the-dark...
Also, fax machines are very often just as internet connected as anything else. Email to fax, fax to email, fax-over-IP, it's not just modems dialing each other on copper anymore.
Punishable, sure, but that's CYA thinking. It's less secure, because there's no way to encrypt fax like you can encrypt email. Punishment doesn't help anyone except the CEOs, unless, of course, it was the CEO's information that got leaked.
Also, yes, phone calls are sent over the Internet just like emails. The big difference is, yes, that phone audio isn't encrypted.
People mess around with just about anything they can get their hands on- so what if the nurses send messages to each other and have fun? I'd be willing to give the people who take care of me a ream of paper if it meant they were in a good mood.
Patient privacy monitoring (ensure no one peeks into patient records inappropriately) and medication analytics platform (monitors suspicious and anomalous activity related to drugs and opioids diversion).
This of course deals with multitude of different systems, EMR's, data formats, legacy-everything etc, but the GREAT about this whole thing - is opportunity.
No one really tackled a challenge of visibility across different systems and data formats in Healthcare and it's lots of fun to be part of that.
("Fun" is non-corporate word - but it still fun!)
I prototyped an access logger based on tamper evident logs, which used rolling hash codes. Precursor to this blockchain mania.
re: visibility
I'm still bullish on the Translucent Database thesis. TLDR: Use the password salt + hash technique to encrypt data at rest at the record level.
--
Source: Designed, implemented, supported 5 regional healthcare exchanges. eg Brooklyn Health Information Exchange (BHIX): https://www.itnonline.com/content/medplus-implement-clinical...
VB6/MUMPS stack is... not ergonomic to code in.
Epic is easy to hate (it's everywhere), and for good reason. However, the alternatives are not obviously better unless there's been some radical innovation. There are definitely systems designed for a particular piece of a hospital (ex, ER, or labs, etc) that are probably better than Epic is, but when it comes to having one system for the entire hospital, they're all pretty bad.
The main problem is that the customer is not the nurses, it's the legal/financial/administrative side.
This. The reason my medical staff like me is that I fight for usability for them, and push back against legal when they make requests that aren't backed up by the regulations. Legal hates me for the same reason, I know the regs and I'm willing to fight them on it.
My email is jwconway at protonmail dot com.
Yeah, our org is on Cerner and there's excited talk around going to Epic in the future. People don't seem to understand that it's just going to be more of same in dealing with an old, monolithic system.
So they have quite a lot on their plate when it comes to tooling. When I was there, there was a truly horrible attempt at a DSL for code-generation that would build database querying code, but I found it both unwritable and unreadable.
That sounds like a medical condition.
And after looking into the MUMPS language, I can see why they named it after a disease!
But there are many systems in a hospital. And as EuphoricEmu pointed out within the hospital, admits, discharges and movements throughout the hospital are still done via HL7v2 (a delimited and structured format).
Additionally, I would absolutely NOT build a new system on HL7v2 at this point in time. I would only use it to integrate with existing systems.
Also, I do know of EHR systems that use FHIR for their internal data storage format.
RHIOs building gateways for 3rd party apps is very much the future of FHIR. But they’ll still be interacting with that crufty legacy system.
Just my own two cents.
Are RHIOs using engineers/consultants to wrapped legacy systems then devise methods to make accessing that data easier -- how are RHIOs using FHIR and legacy system to construct the future of medical data interoperability?
The issue is that most EHR/EMR vendors have very limited limited interoperability with FHIR. As a lot of these vendors are struggling with CCD 2.1 implementations. The exciting space is allowing patients through 3rd party apps to request specific information or even send it to the HIE (RHIO in this case) and let there GPs know of certain events.
Which means a lot of work to bend over backwards to get APIs exposed for these 3rd parties.
The only problem is that is such a diverse way the healthcare providers are implementing it. So you end up having provider specific code :)
My ETL work in healthcare finally pushed me to treat the problem as screen scrapping. Bypassing all the attempts at formality, eg XSD.
The next step, which I prototyped but was put into purgatory by being acquired, was to simply capture all the data and use text retrieval tools, eg Lucene. Versus ingesting the data, normalizing it (to some schema) and populating database(s). Basically, postponing the translation/transformation of client data until viewing. Because, as you hinted, everyone does stuff differently, and clients generally have no idea what their data looks like until we showed them.
The proper solution would be to have direct access to source data, versus data feeds, but that ain't gonna happen until we have single payer, because the current incentive structure strongly discourages such simplicity.
I think the EMR industry is driven more by safety, liability, and revenue for hospitals (in that order) than by patient/physician desired features or security.
It's also difficult to build tooling that interconnects across all of the medical specialties - and with the amount of customization that some providers want.
- https://www.gnuhealth.org/#/download/projects
- https://savannah.gnu.org/projects/health
- https://en.wikibooks.org/wiki/GNU_Health
Can't tell if it's any good, though I hear it's been used in some medical facilities around the world.
This strikes me as the SAP problem.
Everybody hated their big company's <foo> system. Until SAP came along and somehow made it orders of magnitude worse.
It's what happens when purchasing decisions are driven from the top. Sadly, in healthcare, given all the regulations, I'm not sure there is another option.
And it's not only an IT systems problem. It's a comprehensive systems problem.
Which includes training, and counterparty expectations, and manual data entry, etc.
E.g. if I update my system, you need to update your system
From what I saw, one of the biggest motivators would be carving out legal protections for trialing some smaller % of total workflow under new systems.
E.g. If you moved < 5% of your claims handling to a new automated system, and it started rejecting claims that there was an informal understanding would be patched up on the insurance side, then nobody could be sued via intra-party contracts (but still beholden to national / federal guidelines, of course)
By decreasing that first burden of migration, you might get more traction in aggressive IT updates.
I see you’ve played InternetExplorer X vs X+1 before.
I have a long history in proper IT, and I'm very legally/regulationally knowledgeable, and in my two healthcare gigs I've made friends of the medical staff for improving responsiveness in IT and making things easier to use, while also reducing security problems by having both of those worlds of knowledge. Usually top IT management isn't technically knowledgeable, and frequently they're not even that good with regulatory knowledge. That makes it hard on the rank and file to be efficient. Not to pay my own back too much, but being well versed in both regs and tech helps a LOT in user satisfaction.
Even off the shelf is no solution really. Everything is proprietary, you get locked in and years later the vendor isn't maintaining shit and moving away becomes an blackhole of a cost sink.
>It's INCREDIBLY common for nurses and doctors to need to have administrator access on their Windows desktops for various apps.
Honestly, needing admin on a "user network" device isn't the worst. You can still run malware that attacks the network via non-admin context :/ The best move is to use AppLocker if it's critical.
This made me smile, because this is exactly what I did when working for a major health insurer...
It’s funny. You got Ruby guys out here who think every problem can be solved with a new DSL, and you guys actually have a DSL and want to get rid of it! Maybe the grass is always greener on the other side?
Nah. C
Also traces its roots to the PDP7 https://en.wikipedia.org/wiki/C_(programming_language)#Early...
Government promises, and thus government kills. A monopoly enforced by guns and prisons.
During the mid aughts, hospitals simply didn't have the experience to defend against predatory consultancies.
Hopefully that situation has improved with the addition of people like you.
Another problem is that EVERYTHING is custom, we use very, very few off the shelf solutions. Need an EMR? Let's build it in MUMPS, a 51 year old language that originated on the PDP7 and call it a state of the art system like Epic or GE Healthcare. Don't like the terminal interface? Let's slap a GUI on the front that still interacts via TTY on the back end. SQL? Nah. C, C++, or any more modern language with more robust features and way more programmers? Nope.
Now, there are some EMRs and other healthcare-centric apps that are better written, but they're also terrible. Healthcare is a relatively small market, you'll never sell a million units of your app, so you charge out the wazoo for it, get a few health systems on it, and allow they to go crazy with customization to help lock them in. And then you try to add on modern security features on to a system that's been growing for 50 years and it's a nightmare. It's INCREDIBLY common for nurses and doctors to need to have administrator access on their Windows desktops for various apps.
I was about to leave IT in general when a healthcare gig landed on me, and I'm glad it did. I find it very refreshing to be in an industry where it's so far behind that there are mountains of problems to tackle, even if half of them are so stupid it makes me want to cry.