Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>A handful of large healthcare software vendors use some version of MUMPS, definitely a non-SQL database. Epic, Meditech, GE, and the VA's VistA all use some implementation of MUMPS. MUMPS lends itself well to healthcare solutions in part because of its performance and scalability. </p> <p>I know that some MUMPS implementations (I'm thinking specifically of <a href="http://www.intersystems.com/cache/" rel="noreferrer">Intersystems Caché</a>) allow you to query the database with SQL, but that requires some in depth technical knowledge to map your non-relational data model to relational tables. </p> <p>I work for a large EMR vendor that uses MUMPS and I can tell you it's not a "fun" experience. By that I mean that there aren't great tools that allow me to whip up awesome features in a few lines of code (there's no LINQ-To-M in .NET). But I recognize that the price I pay in writing more code to query data is worth the marketshare. </p> <p>If you're starting an EMR business and designing your architecture, you need to think of your ultimate goals. If you're looking to create a full-fledged EMR that can span multiple areas and specialties, you'll need a LOT of features while still keeping an eye on performance, reliability, and scalability. You'll also need a few thousand developers to get your product to market ASAP because with the new Healthcare stimulus, the hospitals are buying <em>now</em>. </p> <p>If you're looking at a specialty niche application, where your user base will be small and focused, you can take your pick of any database technology, looking more for tooling and rapid development.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload