MUMPS

MUMPS

MUMPS — the Massachusetts General Hospital Utility Multi-Programming System — is the language most Americans' medical records run on and almost nobody's heard of. It began in 1966–67 as an internal skunkworks at MGH: Neil Pappalardo, Robert Greenes, and Curt Marble, working in Dr. Octo Barnett's lab, were frustrated watching their NIH hospital-systems project get built in assembly on a BBN time-shared PDP-1 — so they built an alternative development environment of their own. When Dr. Barnett's 1967 NIH renewal proposed to build the hospital system in MUMPS instead, the gamble got funded.^[1]

The design answers a specific pain — hospital data — with unusual economy. Its defining feature is the integrated database: globals, persistent sparse arrays that live on disk and are addressed with ordinary variable syntax (^PATIENT(1234,"MEDS")) — one of the first high-speed transactional key-value stores, a quarter-century before "NoSQL" had a name. Its syntax is legendarily terse: single-letter commands (S X=5, W "HELLO"), implicit everything, a language engineered for speed on tiny machines rather than readability. Ancestors reach back through BBN's TELCOMP and STRINGCOMP to RAND's JOSS — and it first ran on a PDP-7, moving to the PDP-9.^[2]

Sixty years of invisible infrastructure

MUMPS was ahead of its era in a way that's easy to miss: it implemented multitasking on machines without threading or memory protection — and because MUMPS programs had no way to reference raw memory, process isolation was enforced by the language itself, not by hardware. It was standardized by ANSI as X11.1 — officially just "M" — and its descendants are not legacy; they're the plumbing: Epic's system (the dominant US electronic health record, covering well over three-quarters of American patients) and the VA's VistA both run on M. If you've been treated in a US hospital, MUMPS handled your data.^[3]

Where it sits

MUMPS is the survival case of this catalogue: JOSS-era roots, PDP-7-era implementation, and a domain — medicine — where reliability outranks fashion. It proves a language can be ugly, sixty years old, and load-bearing — the health data of a nation is running on it right now.

Check your understanding

• What does MUMPS stand for — and why was it built?
• What are "globals," and why are they historically important?
• How did MUMPS achieve multitasking on machines without threading?
• What modern systems still run on M?