3 ms·
The press release is of course nearly devoid of interesting facts The "We will use AI" and that will be great. Is highly annoying. M/UMPS and Visual Basic 6
by ThinkBeat 4y ago
The press release is of course nearly devoid of interesting facts
The "We will use AI" and that will be great.
Is highly annoying.
M/UMPS and Visual Basic 6 running on Google Cloud.
That might be the first time for that stack. Maybe.
They used to run off of a proprietary or at least legacy
database as well. I wonder if they still are.
It will be interesting to integrate that to conform with
BigQuery.
Or perhaps they will export all the data to a sane store first.
Epic is notorious for not integrating with any other system.
Or at least they were a decade ago.
- nradov 4y agoEpic primarily uses the InterSystems Caché database, which is essentially a modernized edition of MUMPS. It is about as "legacy" as any piece of software can be with parts of the code dating back to 1966, but still works well and for certain applications it's still superior to more modern databases. BigQuery is not an appropriate database for an EHR. Epic used to be notorious for lack of interoperability. They now have an extensive set of open APIs and are active participants in industry standards development organizations. https://open.epic.com/ https://open.epic.com/
- kakoni 4y agoI believe technically there is Chronicles, Epics own "database framework/abstraction" that runs on top of Caché. Then about Caches superiority, this is the only public benchmark that I could find (from Intersystems) https://community.intersystems.com/sites/default/files/documentation/Cache_benchmark-1c69bf617b51d5a2dee145442deaa371.pdf https://community.intersystems.com/sites/default/files/docum... Where 8-core server (back in 2009 that is) could do about 2 million database reads per second.