Compelling CPRS Replacement - Revision history

NeilArmstrong: Added a glossary link to CPRS~

2012-08-09T23:26:31Z

Added a glossary link to CPRS~

NeilArmstrong: Added glossary link to Application~

2012-02-22T14:54:05Z

Added glossary link to Application~

← Older revision		Revision as of 14:54, 22 February 2012
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.

Ftrotter: initial

2007-08-12T15:34:11Z

initial

New page

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 ===

[http://www.medsphere.com Medsphere] has created a potential CPRS replacement using [http://www.mono-project.com/ mono] (apparently we must prefer languages names after diseases) called [http://medsphere.org/openvista_cis.html 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 [http://www.gplmedicine.org/articles_12/ controversy].

← Older revision		Revision as of 23:26, 9 August 2012
Line 1:		Line 1:
	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.		[[CPRS~\|CPRS]] is programmed in Delphi. Since [[CPRS~\|CPRS]] was initially developed other programming languages have become more popular and capable than delphi. As a result some feel that [[CPRS~\|CPRS]] should be re-written in a modern language.

	=== To replace or not to replace... that is the question ===		=== To replace or not to replace... that is the question ===

	Reasons that the current delphi based CPRS is no longer workable		Reasons that the current delphi based [[CPRS~\|CPRS]] is no longer workable

	* 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~\|Application]].		* There only a few people who are trained in modifying the current [[CPRS~\|CPRS]] [[application~\|Application]].
	* Without other considerations programmers are typically unwilling to learn a new language for the sake of a single [[application~\|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.

	Reasons that the current CPRS is workable		Reasons that the current [[CPRS~\|CPRS]] is workable

	* CPRS has an extremely small foot-print, making it easy to distribute automatically.		* [[CPRS~\|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~\|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.		* [[CPRS~\|CPRS]] has a tremendous amount of institutional knowledge embedded in its design, reprogramming [[CPRS~\|CPRS]] is a very difficult task.

	=== Medsphere OpenVistA CIS ===		=== Medsphere OpenVistA CIS ===

	[http://www.medsphere.com Medsphere] has created a potential CPRS replacement using [http://www.mono-project.com/ mono] (apparently we must prefer languages names after diseases) called [http://medsphere.org/openvista_cis.html 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 [http://www.gplmedicine.org/articles_12/ controversy].		[http://www.medsphere.com Medsphere] has created a potential [[CPRS~\|CPRS]] replacement using [http://www.mono-project.com/ mono] (apparently we must prefer languages names after diseases) called [http://medsphere.org/openvista_cis.html 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 [http://www.gplmedicine.org/articles_12/ controversy].