PAS is a hybrid client-server application built on an open source stack. This structure ensures the best compliance with industry standards while providing scalability and high performance. Additionally, all other benefits of open source software, including a lower total cost of ownership, are passed onto our customers.

The PAS application uses legacy technology developed in Delphi, for the Win32 platform.

Problem reporting is built into the system and automatically sends the mumms® technical support team the data necessary to solve the problem. Support requests can also be submitted via phone, fax, or email. All support requests are entered into our help desk database and are tracked to resolution.

 

The PAS system employs a combination of redundant, fail-over Dell PowerEdge and HP Proliant servers using quad core Intel® Xeon® processors, and running Red Hat Enterprise Linux, Apache, and Postgres. The servers are monitored 24 hours a day by a team of UNIX specialists. Servers are hosted in multiple data centers across the country utilizing:

Power: Diesel generator in combination with a next-generation UPS and automatic transfer switch system to provide steady, clean, hospital grade, uninterruptible electricity to the servers

Environment: Raised floor with neutral, grounded, anti-static tiles

mumms® follows the life-cycle strategy of releasing updates early and often. As such, updates releases are put out approximately every three months. All program changes are added to our code repositories and updated to the development servers for internal testing. From there, updates are moved to a staging server to begin extensive testing by mumms® staff technicians, as well as hospice and palliative care client beta testers. (We encourage key personnel at each organization to join our Beta Testing Team.) Prior to every update or installation on the production servers, an advanced notice of the installation date and complete release notes are provided to all users. Additional training (if applicable) is provided. Updates are made directly to the server without any additional actions needed by the program user.

Data on the production servers is mirrored each night to backup production servers. The data is also stored on data-specific backup servers for five days. It is then copied to a tape and transported to a secure offsite facility. In the event of a production server failure, the backup data would be re-synched to a backup server and clients would be automatically updated to use that server. For example, mumms® is headquartered in New Orleans and Hurricane Katrina provided the opportunity to carry out our contingency plans well beyond planning or testing phases. mumms® successfully confirmed that its system contingency plans will support the mumms® system and data links to hospices and palliative care facilities throughout the country. The results of Katrina on the mumms® system were that no mumms® user lost or compromised data or ever lost access to the program.