Massachusetts General Hospital Utility Multi‐Programming System Gt‐M - sgml/signature GitHub Wiki
Relational Diagram
+---------------------------+
| ROGUELIKES |
| 1. Anti‑mainstream |
| 2. Randomness as meaning |
| 3. Player interpretation |
| 4. High barrier to entry |
| 5. Experimental community |
+-------------+-------------+
\
\
\
+--------------------+--------------------+
| ROGUELIKE + POEM | ROGUELIKE + UA |
| - Emergent meaning | - DIY structure |
| - Nonlinear form | - Anti‑institution |
| - Personal story | - Fluid outcomes |
+--------------------+--------------------+
/ \
/ \
/ \
+-------------+-------------+
| POEMS |
| 1. Anti‑mainstream |
| 2. Ambiguity as meaning |
| 3. Reader interpretation |
| 4. High barrier to entry |
| 5. Experimental community |
+-------------+-------------+
\
\
\
+--------------------+--------------------+
| POEM + UA | ALL THREE (R/P/UA)|
| - Meaning emerges | - Countercultural |
| - Nonlinear norms | - Structure rigid |
| - Interpretation | - Meaning fluid |
+--------------------+--------------------+
/ \
/ \
/ \
+-------------+-------------+
| UNINCORPORATED ASSOCIATIONS |
| 1. Anti‑institutional |
| 2. Fluidity as meaning |
| 3. Member interpretation |
| 4. High barrier to stability|
| 5. Experimental community |
+-------------+-------------+
\
\
\
+--------------------+--------------------+
| MUMPS + R | MUMPS + P |
| - Integrated rules | - Structured form |
| - Emergent usage | - Compressed meaning|
+--------------------+--------------------+
/ \
/ \
/ \
+-----------------------------+
| MUMPS PROGRAMMING |
| 1. Data‑centric structure |
| 2. Integrated database |
| 3. Emergent system behavior |
| 4. High barrier to entry |
| 5. Niche, mission‑critical |
+-----------------------------+
Comparison
| Language | Ordered List of Shared Characteristics | Unordered Sublists (Details) |
|---|---|---|
| MUMPS | 1. Enterprise origins and longevity | - Built for institutional computing in the 1960s- Still used in health systems and transactional workloads |
| 2. Structured, high‑volume data processing | - Hierarchical global storage- Real‑time updates- Predictable data access patterns | |
| 3. Mainframe‑class reliability | - Long‑running processes- Stable runtime environments- Deterministic concurrency | |
| 4. Database‑centric operational model | - Native hierarchical database- Integrated language+database design | |
| 5. Reliability emphasis | - Deterministic behavior- Predictable memory usage- Long‑term maintainability | |
| 6. Hard to replace | - Mission‑critical workloads- Decades of accumulated logic | |
| COBOL | 1. Enterprise origins and longevity | - Built for business data processing- Still used in finance and government |
| 2. Structured, high‑volume data processing | - Record‑oriented layouts- Fixed‑format data- Batch workflows | |
| 3. Mainframe‑class reliability | - Stable batch systems- Predictable I/O- Strict concurrency | |
| 4. Database‑centric operational model | - External bindings to IMS, VSAM, DB2 | |
| 5. Reliability emphasis | - Deterministic pipelines- Clear data structures | |
| 6. Hard to replace | - Large legacy systems- High migration cost | |
| PL/I | 1. Enterprise origins and longevity | - Built for scientific and business workloads- Still used in mainframe environments |
| 2. Structured, high‑volume data processing | - Strong typing- Structured data types- Mixed scientific/business workloads | |
| 3. Mainframe‑class reliability | - Stable runtime- Predictable execution- Long‑term deployment | |
| 4. Database‑centric operational model | - External bindings to IMS, VSAM, DB2 | |
| 5. Reliability emphasis | - Deterministic behavior- Maintainable codebases | |
| 6. Hard to replace | - Deep integration with mainframe systems |
Downloadables
sudo apt install -y fis-gtm
Compilers
| Compiler | Open‑source | MIT or GPL License | Downloadable URL | Learning / Training / Doc URL | Date Created | Most Recent Release |
|---|---|---|---|---|---|---|
| GT.M | true | true | https://sourceforge.net/projects/fis-gtm/files/latest/download | https://sourceforge.net/p/fis-gtm/wiki/Home | 1995 | 2024 |
| FIS GT.M | true | true | https://sourceforge.net/projects/fis-gtm/files/latest/download | https://sourceforge.net/p/fis-gtm/wiki/Home | 1995 | 2024 |
| InterSystems Compiler | false | false | n/a | https://docs.intersystems.com | 1978 | 2024 |
References
https://sourceforge.net/projects/fis-gtm/
https://learning.intersystems.com/
mumps gtm site:youtube.com program
https://www.ihs.gov/rpms/Downloads/RPMS_ProgrammingSAC_2009.pdf
https://www.hhs.gov/sites/default/files/ihs-ht-mod-legacy-assessment.pdf
https://github.com/sweattep/VistA-M
https://metacpan.org/release/SZECK/Db-GTM-1.27/source/GTM.pm
Greystone Technology M
https://www.oit.va.gov/services/trm/ToolPage.aspx?tid=6632
https://pmc.ncbi.nlm.nih.gov/articles/PMC150357/
Certification Path
https://www.dice.com/jobs/q-epic+cache+ehr
https://www.intersystems.com/knowledge-hub/certification-program/
Historical Comparison
Chronicles
- chronicles stores records in master files
- master files contain items, values, contacts, and time slices
- chronicles flow is shown through item definitions and rule driven workflows
- chronicles is used for clinical, billing, and operational data
Iris
- iris uses globals for persistent storage
- iris uses objects for structured storage
- both globals and objects store hierarchical data
- iris logic runs through routines and class methods
- iris is used in health, finance, and logistics
S-Expressions
- s expressions use nested lists
- parentheses show structural relationships
- s expressions can be treated as plain data
- s expressions can be evaluated as code
- s expressions are used in symbolic and functional systems
GTM
- gtm uses globals as storage
- gtm uses routines for logic
- gtm adds triggers, processes, and modern tooling
- gtm is used in health and finance
Chronicles VS S-Expressions
- chronicles uses master files with defined structure
- s expressions use nested lists with structural relationships
- chronicles separates data and logic
- s expressions can serve as data or code
- chronicles flow is determined by rules
- s expression flow depends on evaluation
- chronicles is used for clinical and operational data
- s expressions are used for symbolic and functional logic
IRIS VS Chronicles
- iris uses globals and objects for hierarchical storage
- chronicles uses master files with defined schema
- iris uses routines and class methods for logic
- chronicles uses workflows and rule engines
- iris is a database and application engine
- chronicles is a domain specific data model
IRIS VS S-Expressions
- iris stores hierarchical data
- s expressions represent hierarchical lists
- iris separates data and logic
- s expressions unify data and logic when evaluated
- iris flow is determined by routines or rules
- s expression flow is determined by evaluation
- iris is used for enterprise applications
- s expressions are used for symbolic computation
GTM VS Chronicles
- gtm uses globals without defined schema
- chronicles uses master files with defined schema
- gtm flow depends on routine execution
- chronicles flow depends on rule engines
- gtm is a language and storage system
- chronicles is a structured domain model
GTM VS Iris
- gtm uses globals without defined structure
- iris uses globals and objects with defined structure
- gtm mixes code and data
- iris separates code and data through classes
- gtm flow depends on routines
- iris flow is defined through routines and rules
- gtm is used for data logic
- iris is used for full applications
GTM VS S-Expressions
- gtm uses globals without schema
- s expressions use nested lists with structural relationships
- gtm flow depends on routines
- s expression flow depends on evaluation
- gtm runs server logic
- s expressions run symbolic or functional logic
SUMMARY
- chronicles structures meaning through master files and workflows
- iris structures meaning through hierarchical storage and routines
- s expressions structure meaning through nested lists
- gtm stores data in globals without predefined structure and relies on routine driven flow
- chronicles and iris are the most structured
- s expressions are simple and uniform
- gtm is the most opaque because its data layout is not externally defined
Architecture
- https://www.intersystems.com/news/intersystems-iris-data-platform-adopted-by-epic-for-its-new-generation-of-high-performance-scalability-and-architecture-flexibility/
- https://joshuamandel.com/ehi-living-manual/00-04-epic-data-architecture/
- https://www.suretysystems.com/insights/the-backbone-of-epic-understanding-the-role-of-epic-chronicles/
- https://docs.netapp.com/us-en/ontap-apps-dbs/epic/epic-arch-overview.html