MUMPS/docs/First_MUMPS_Standard_Article.md at main · rochus-keller/MUMPS · GitHub
//blob/show" data-turbo-transient="true" />
Skip to content
Search or jump to...
Search code, repositories, users, issues, pull requests...
-->
Search
Clear
Search syntax tips
Provide feedback
--><br>We read every piece of feedback, and take your input very seriously.
Include my email address so I can be contacted
Cancel
Submit feedback
Saved searches
Use saved searches to filter your results more quickly
-->
Name
Query
To see all available qualifiers, see our documentation.
Cancel
Create saved search
Sign in
//blob/show;ref_cta:Sign up;ref_loc:header logged out"}"<br>Sign up
Appearance settings
Resetting focus
You signed in with another tab or window. Reload to refresh your session.<br>You signed out in another tab or window. Reload to refresh your session.<br>You switched accounts on another tab or window. Reload to refresh your session.
Dismiss alert
{{ message }}
rochus-keller
MUMPS
Public
Notifications<br>You must be signed in to change notification settings
Fork
Star<br>25
FilesExpand file tree
main
/First_MUMPS_Standard_Article.md
Copy path
Blame<br>More file actions
Blame<br>More file actions
Latest commit
History<br>History<br>History
97 lines (51 loc) · 12 KB
main
/First_MUMPS_Standard_Article.md
Copy path
Top
File metadata and controls<br>Preview
Code
Blame
97 lines (51 loc) · 12 KB
Raw<br>Copy raw file<br>Download raw file
OutlineEdit and raw actions
How MUMPS Got Its first Standard a Year Before ANSI
by Rochus Keller
July 7, 2026
Ask almost anyone when the MUMPS programming language was first standardized and you will hear the same answer: 1977, as ANSI X11.1-1977. It is the date in the Wikipedia infobox, in countless retrospectives, and in the bibliographies of papers that ought to know better. It is also wrong, or at least incomplete. The first formal MUMPS standard was an U.S. government publication issued in January 1976 : the NBS Handbook 118, MUMPS Language Standard.
I recently completed and published an implementation of the MUMPS 1976 standard, and received many surprised reactions from people who had never heard of it before. So it makes sense to take a closer look at this standard and its history here.
The problem: one language, seven dialects
MUMPS (Massachusetts General Hospital Utility Multi-Programming System) was born in 1966 in the Laboratory of Computer Science at Massachusetts General Hospital, where a team needed a time-sharing system on a minicomputer that no commercial vendor could then provide [^1]. The design was a striking success: up to twenty simultaneous users could share a database on a PDP-9 with just 32K words of memory [^2].
Success bred imitation, and imitation bred fragmentation. As different groups ported and enhanced MUMPS independently, the language splintered. By 1972, at least seven distinct dialects could be identified across the growing user community [^2]. This was more than an academic annoyance. The National Center for Health Services Research (NCHSR), part of the Department of Health, Education and Welfare (HEW), had hoped that MUMPS application packages written at one hospital could be freely shared with every other institution running MUMPS — avoiding wasteful duplication across a large base of federally funded medical systems. The proliferation of incompatible dialects made that portability increasingly impossible [^2].
The response: NBS, a field study, and the birth of the MDC
To halt the divergence, the National Bureau of Standards (NBS), the Department of Commerce agency that would be renamed to "NIST" in 1988, was given a contract in 1972 to study the MUMPS dialects and make recommendations [^2]. The study's central recommendation was structural: create a body to steward the language. "As a result of this study, NBS recommended the formation of the MUMPS Development Committee (MDC)" [^2].
In the fall of 1972, the chief implementors and users of the competing dialects gathered at a conference in Boston, forming both the MUMPS Users' Group (MUG) and its sibling, the MUMPS Development Committee (MDC) [^3]. The MDC was funded with support from NCHSR and from NBS [^4].
Crucially, the MDC was not an internal government committee. Its constitution was explicitly modeled after the ANSI X3 language standards committees , and it drew members from both the vendors marketing MUMPS and the institutions using it [^2]. It was a genuine public, cross-industry body. Its constitution described it this way:
"The MDC is an informal and voluntary organization of interested individuals, supported by their institutions, who contribute their efforts and resources to the end of developing a computer programming language, which meets the requirements of a wide range of applications. The results of MDC activities will be in the public domain with the intent of promoting MUMPS language commonality and compatibility among computers." [^2]
And its stated technical...