Application Catalog
RPMS is a federated, modular system built over decades.
Each application is identified by a short namespace prefix (e.g. GMRA, BQI) that scopes its globals, routines, and file numbers within the MUMPS/FileMan environment.
Over 50 certified applications span clinical, administrative, and infrastructure domains.
This catalog is an open-source reference derived from public IHS documentation. See Licensing for status of each component.
Clinical Applications
Collect all patient-related information gathered during patient encounters into a comprehensive, centralized data file. Support healthcare planning, delivery, management, and research.
ACHS
ACM
ACPT
ADE
AG
AGMP
AICD
AMH
AMQQ
APCD
APCH
APCL
APCM
APSP
APSS
ATX
AUM
AUPN
AUT
BADE
BCCD
BCDM
BCER
BCH
BCQM
BDM
BEDD
BEPC
BEPR
BEX
BGP
BGU
BHS
BI
BJMD
BJPC
BJPN
BJVN
BKM
BLE
BMC
BOP
BPDM
BPHR
BPM
BQI
BREH
BRN
BSTS
BTPW
BUD
BW
BYIM
CHIT
EHR
GIS
GMRA
GMRC
GMRV
GMTS
LR
MU2
PSJ
PSN
PSO
PXRM
RA
VEN
Administrative Applications
Support the business of providing healthcare — patient registration, scheduling, billing, credentialing, accounts receivable, and compliance reporting.
ABM
ABSP
ACR
APSA
BAR
BMX
BNI
BNP
BPRM
BQRE
BUSA
ECQM
GRU
LEX
PIMS
TIU
Infrastructure Applications
Provide the RPMS environment with management, development, and communication tools. These are the foundation every other application depends on.
ADS
AVA
BCOM
BDW
BFMC
BHL
BMW
BXT
DI
HL
XB
XM
XT
XU
XWB
Pattern: Namespace as Module Boundary
Every RPMS application owns a short uppercase namespace prefix. This prefix scopes all globals, routines, and FileMan file numbers for that module — preventing collisions across the 70+ applications sharing a single MUMPS environment. It is an early, pragmatic implementation of the same isolation that modern systems achieve with packages, services, or namespaces. When building interoperable health systems, explicit module boundaries and stable identifiers are a foundational pattern worth carrying forward.