FileMan vs. Competitors VA FileMan remains one of the most uniquely resilient database management systems (DBMS) in existence, serving as the core engine behind the U.S. Department of Veterans Affairs VistA Hospital Information System. Originally developed in the late 1970s by George Timson using the MUMPS (M) language, FileMan handles data structures, screen-oriented data entry, security, and report generation simultaneously.
Unlike modern databases that separate storage from the application tier, FileMan embeds an active data dictionary and a text-based user interface directly into the database engine. However, when stacked against modern relational and non-relational database management systems, FileMan occupies a highly specialized niche.
Here is how FileMan compares to its prominent modern competitors. The Competitors at a Glance Database System Paradigm Type Primary Strengths Ideal Use Case VA FileMan Polymorphic / NoSQL (MUMPS)
Active data dictionary, integrated text UI, embedded business logic. Enterprise Healthcare (VistA, RPMS). PostgreSQL Relational (RDBMS) Extensibility, strict ACID compliance, SQL standardization. General enterprise apps, financial systems. MongoDB Document (NoSQL)
JSON schema flexibility, horizontal scaling, modern developer ecosystem. Content management, real-time analytics. InterSystems IRIS Multi-Model (Modern M)
High-speed transactional processing, native SQL-to-MUMPS mapping. Modernized healthcare tech, global finance. Key Comparison Arenas 1. Architectural Design and Data Flexibility
FileMan: Operates as a “polymorphic” database. It relies on a deeply integrated, active data dictionary. Fields are not just static placeholders; they can invoke full, interpretive MUMPS code at runtime. For example, a calculated field like a patient’s “Length of Stay” dynamically executes background routines to compute the value seamlessly upon request.
Competitors: Relational databases like PostgreSQL demand predefined schemas, foreign keys, and structured tables. Changes to data models require migration scripts. NoSQL databases like MongoDB offer total schema flexibility via JSON documents but push the calculation logic completely onto the external application layer rather than executing it natively inside the field definitions. 2. Built-in User Interfaces and Tools
FileMan: Provides a complete, out-of-the-box text-based user interface. A developer or administrator can define a file and immediately utilize pre-built utilities to search, edit, and print reports directly through a terminal. It also manages internal security mechanics natively, such as Learn-As-You-Go (LAYGO) access controls.
Competitors: Modern database servers act strictly as silent data engines. To search, edit, or enter data in PostgreSQL or MongoDB, developers must build a custom frontend application (using tools like React or Python) or rely on standalone administrative GUIs like pgAdmin or MongoDB Compass. 3. Query Language and Ecosystem Integration
FileMan: Lacks native SQL support. Querying data requires standard FileMan APIs, the built-in text search tools, or direct MUMPS global lookups. While modern variants support Database Server (DBS) calls to separate data access from user I/O, integration with external tech stacks remains a complex hurdle.
Competitors: SQL is the universal standard for data manipulation across relational platforms. For non-relational storage, MongoDB uses an intuitive, programmatically friendly JSON query language. Both paradigms enjoy extensive native library support across every modern programming language imaginable. 4. Scalability, Maintenance, and Modern Support
FileMan: Highly efficient on minimal resources, footprinting roughly 3.5 MB of disk space for core routines and globals. However, finding developers proficient in standard MUMPS and historical FileMan infrastructure is incredibly difficult, restricting its maintenance mostly to government healthcare systems like the VA and Indian Health Service (IHS).
Competitors: Modern systems excel in automated horizontal scaling, cloud-native deployments (AWS, Azure), and massive community support. If a system requires high throughput and web-scale replication, enterprise options like InterSystems IRIS (the commercial evolution of MUMPS foundations) or MongoDB vastly outclass legacy FileMan setups. Summary: When to Use What?
VA FileMan is not a general-purpose database for modern web applications. It remains relevant because it is the foundational pillar of VistA, one of the largest electronic health record systems in the world. Its ability to seamlessly blend data storage with execution logic keeps legacy medical operations performing reliably.
For any greenfield software project, modern web applications, or scalable enterprise platforms, standard engines like PostgreSQL or MongoDB are the correct choice due to their vast developer ecosystems, modern tooling, and flexible integration paths. If you are evaluating software platforms, let me know:
Are you maintaining an existing legacy healthcare system or building something entirely new?
What programming languages (e.g., Python, M, JavaScript) does your current development team use?
I can provide technical documentation or architectural paths tailored exactly to your environment.
VA FileMan Programmer Manual: Database Server (DBS) Introduction
Leave a Reply