Difference between revisions of "Compelling CPRS Replacement"
(initial) |
(Added glossary link to Application~) |
||
| Line 6: | Line 6: | ||
* Delphi is not a popular language, modern programmers are not trained in it. | * Delphi is not a popular language, modern programmers are not trained in it. | ||
| − | * There only a few people who are trained in modifying the current CPRS application. | + | * There only a few people who are trained in modifying the current CPRS [[application~|Application]]. |
| − | * Without other considerations programmers are typically unwilling to learn a new language for the sake of a single application. | + | * Without other considerations programmers are typically unwilling to learn a new language for the sake of a single [[application~|Application]]. |
* Unlike MUMPS Delphi offers so special benefits over modern languages. | * Unlike MUMPS Delphi offers so special benefits over modern languages. | ||
Revision as of 14:54, 22 February 2012
CPRS is programmed in Delphi. Since CPRS was initially developed other programming languages have become more popular and capable than delphi. As a result some feel that CPRS should be re-written in a modern language.
To replace or not to replace... that is the question
Reasons that the current delphi based CPRS is no longer workable
- Delphi is not a popular language, modern programmers are not trained in it.
- There only a few people who are trained in modifying the current CPRS Application.
- Without other considerations programmers are typically unwilling to learn a new language for the sake of a single Application.
- Unlike MUMPS Delphi offers so special benefits over modern languages.
Reasons that the current CPRS is workable
- CPRS has an extremely small foot-print, making it easy to distribute automatically.
- CPRS works well on older hardware, which might have difficulty supporting a hardware "heavy" language like Java.
- CPRS has a tremendous amount of institutional knowledge embedded in its design, reprogramming CPRS is a very difficult task.
Medsphere OpenVistA CIS
Medsphere has created a potential CPRS replacement using mono (apparently we must prefer languages names after diseases) called OpenVistA CIS. It works against a modified version of the VistA server which is unfortunately not compatible with FOIA VistA. Currently, it also uses a badgeware license that requires the display of a Medsphere logo if the client is used. Medsphere's reputation within the community is the subject of some controversy.
