MUMPS v OmnisSQL and the rest

[Lou Picciano]

Dr., (sorry, couldn't resist the joke) 

Hello, Alan! Long time no talk to!

Used MUMPS _many_ years ago, in the context of MEDLINE and hospital systems data searches. This was, uhhh... back in The Eighties (does anyone remember the eighties?!)  I can't claim much expertise in the current incarnation of the language per se, but:

MUMPs is still very much in use in very large legacy systems - not only in hospitals, but also in banks - lot of it still around. As such, much effort has been put into interfacing it with SQL systems, and other 'NoSQL' and 'Key Store' databases'. There's some very interesting work being done in this area, some of it fronted by NIH. You'll also be aware that Big Pharma is similarly beholden to these legacy stores...

My interest has been in interfacing MUMPs to PostgreSQL (which is at the core of what we do); there has been significant traction in this space. However, none of this helps you much from a browser interface. (Are you limited to the browser interface in your access to the Clinical Systems, or has the hospital deigned to grant you 'full client' access from your offices?)

I'll send you some links off-line; some of these may be palliative, but surely not curative(!). We'll see if there are some steps forward.

Lou Picciano

(Coming to EurOmnis this year?)

     ----- Original Message -----  From: Alan Froehling <alfmd at mvn.net>  To: OmnisDev List - English <omnisdev-en at lists.omnis-dev.com>  Sent: Fri, 05 Jul 2013 20:55:59 -0000 (UTC)  
 Subject: MUMPS v OmnisSQL and the rest

     The hospital that I work at has just started using EPIC for CPOE and EMR databasing.  The user-interface is horrible.  My Mac browser interfaces using a Citrix module.    I understand that EPIC uses the MUMPS database technology which is over 40 years old....