List of open-source health software

Last updated

The following is a list of notable software packages and applications licensed under an open-source license or in the public domain for use in the health care industry.

Contents

Public health and biosurveillance

Electronic records and medical practice management

Name Maintainer License Programming language/
Software stack
Operating System FeaturesTarget setting
EHR/EMR HIS? Practice management?Clinical EngineeringOther
ClearHealth ClearHealth Inc. [4] GNU GPL [4] PHP, JavaScript [5] ?EMR?Scheduling & billing HIPAA security
ERPNext Frappe Technologies GNU GPL [6] Python; JavaScript ?EMRYesYes
GaiaEHR ? GNU GPL [7] PHP & Ext JS ?EHR??
GNUmed GNUmed GNU GPL [8] Python (wxPython); PostgreSQL [8] Cross-platform [8] Yes [8] No?
GNU Health GNU Health (GNU Project) GNU GPL [9] Python; PostgreSQL Cross-platform EMR [9] Yes [9] Yes [9]
Hospital OS ? GNU GPL [10] Java [10] Linux & Windows [10] ?Yes?Small Thai hospitals [10]
HOSxP ? Public domain [11] Delphi/Kylix [11] Windows [11] EHRYes [11] Financial [11] Thai hospitals [11]
MedinTux MedinTux team [12] CeCILL [12] C++ [13] Cross-platform [14] ??Yes Modular design; web [15] & desktop interfaces French hospital emergency departments & smaller practices
OpenEMR ? GNU GPL [16] PHP, JavaScript; MySQL [17] Cross-platform [16] Yes [16] ?Yes [16] Patient portal & prescriptions [16]
Open Dental Open Dental Software [18] GNU GPL [18] ??Dental recordNoYes Dentistry
OpenHospital Informatici Senza Frontiere [19] GNU GPL [19] Java [19] Cross-platform [19] EMRYesYesSmall rural hospitals
OpenMRS OpenMRS Inc. [20] MPL with Healthcare Disclaimer [20] Java, JavaScript Cross-platform EMR??Extensible & scalableClinic, Hospital System, Country Level Health System
OSCAR McMaster ? GNU GPL [21] Java ?EMR [21] ?Billing Web interface; PHR [21] Canadian healthcare providers
Spinnaker Dental IT Ltd [22] GNU GPL [22] ??Dental record?Yes Open Dental fork [23] UK dental practices [23]
THIRRA ? MPL [24] PHP5 (CodeIgniter), JavaScript (jQuery); [24] PostgreSQL ?EHR [24] ?? Disease surveillance; [24] web interface Ambulatory care & public health [24]
VistA US Department of Veterans Affairs Free [25] MUMPS ?EHR?? Veterans Health Administration facilities
ZEPRS Zcore Research Triangle Institute [26] Apache [26] Java [26] ?Yes?? Web interface

Health system management

Disease management

Imaging/visualization

Medical information systems

Research

Mobile devices [58]

Out-of-the-box distributions

Interoperability [62]

Specifications

See also

Related Research Articles

<span class="mw-page-title-main">Free software</span> Software licensed to be freely used, modified and distributed

Free software, libre software, or libreware is computer software distributed under terms that allow users to run the software for any purpose as well as to study, change, and distribute it and any adapted versions. Free software is a matter of liberty, not price; all users are legally free to do what they want with their copies of a free software regardless of how much is paid to obtain the program. Computer programs are deemed "free" if they give end-users ultimate control over the software and, subsequently, over their devices.

The MIT License is a permissive software license originating at the Massachusetts Institute of Technology (MIT) in the late 1980s. As a permissive license, it puts very few restrictions on reuse and therefore has high license compatibility.

<span class="mw-page-title-main">Apache License</span> Free software license

The Apache License is a permissive free software license written by the Apache Software Foundation (ASF). It allows users to use the software for any purpose, to distribute it, to modify it, and to distribute modified versions of the software under the terms of the license, without concern for royalties. The ASF and its projects release their software products under the Apache License. The license is also used by many non-ASF projects.

<span class="mw-page-title-main">OpenSSL</span> Open-source implementation of the SSL and TLS protocols

OpenSSL is a software library for applications that provide secure communications over computer networks against eavesdropping, and identify the party at the other end. It is widely used by Internet servers, including the majority of HTTPS websites.

The Mozilla Public License (MPL) is a free and open-source weak copyleft license for most Mozilla Foundation software such as Firefox and Thunderbird. The MPL license is developed and maintained by Mozilla, which seeks to balance the concerns of both open-source and proprietary developers; it is distinguished from others as a middle ground between the permissive software BSD-style licenses and the GNU General Public License. So under the terms of the MPL, it allows the integration of MPL-licensed code into proprietary codebases, but only on condition those components remain accessible.

<span class="mw-page-title-main">GNU Data Language</span>

The GNU Data Language (GDL) is a free alternative to IDL, achieving full compatibility with IDL 7 and partial compatibility with IDL 8. Together with its library routines, GDL is developed to serve as a tool for data analysis and visualization in such disciplines as astronomy, geosciences, and medical imaging. GDL is licensed under the GPL. Other open-source numerical data analysis tools similar to GDL include Julia, Jupyter Notebook, GNU Octave, NCAR Command Language (NCL), Perl Data Language (PDL), R, Scilab, SciPy, and Yorick.

A permissive software license, sometimes also called BSD-like or BSD-style license, is a free-software license which instead of copyleft protections, carries only minimal restrictions on how the software can be used, modified, and redistributed, usually including a warranty disclaimer. Examples include the GNU All-permissive License, MIT License, BSD licenses, Apple Public Source License and Apache license. As of 2016, the most popular free-software license is the permissive MIT license.

ITK is a cross-platform, open-source application development framework widely used for the development of image segmentation and image registration programs. Segmentation is the process of identifying and classifying data found in a digitally sampled representation. Typically the sampled representation is an image acquired from such medical instrumentation as CT or MRI scanners. Registration is the task of aligning or developing correspondences between data. For example, in the medical environment, a CT scan may be aligned with an MRI scan in order to combine the information contained in both.

<span class="mw-page-title-main">WTFPL</span> Permissive free software license

The WTFPL is a permissive free software license. As a public domain like license, the WTFPL is essentially the same as dedication to the public domain. It allows redistribution and modification of the work under any terms. The title is an abbreviation of "Do What The Fuck You Want To Public License".

<span class="mw-page-title-main">Public-domain-equivalent license</span> License that waives all copyright

Public-domain-equivalent license are licenses that grant public-domain-like rights and/or act as waivers. They are used to make copyrighted works usable by anyone without conditions, while avoiding the complexities of attribution or license compatibility that occur with other licenses.

The Ruby License is a Free and Open Source license applied to the Ruby programming language and also available to be used in other projects. It contains an explicit dual licensing clause, stating that software subject to its terms may be distributed under either the terms included the Ruby License itself or under those of either the GNU General Public Licence v2, or the two-clause BSD License.

License proliferation is the phenomenon of an abundance of already existing and the continued creation of new software licenses for software and software packages in the FOSS ecosystem. License proliferation affects the whole FOSS ecosystem negatively by the burden of increasingly complex license selection, license interaction, and license compatibility considerations.

License compatibility is a legal framework that allows for pieces of software with different software licenses to be distributed together. The need for such a framework arises because the different licenses can contain contradictory requirements, rendering it impossible to legally combine source code from separately-licensed software in order to create and publish a new program. Proprietary licenses are generally program-specific and incompatible; authors must negotiate to combine code. Copyleft licenses are commonly deliberately incompatible with proprietary licenses, in order to prevent copyleft software from being re-licensed under a proprietary license, turning it into proprietary software. Many copyleft licenses explicitly allow relicensing under some other copyleft licenses. Permissive licenses are compatible with everything, including proprietary licenses; there is thus no guarantee that all derived works will remain under a permissive license.

<span class="mw-page-title-main">3D Slicer</span> Image analysis and scientific visualization software

3D Slicer (Slicer) is a free and open source software package for image analysis and scientific visualization. Slicer is used in a variety of medical applications, including autism, multiple sclerosis, systemic lupus erythematosus, prostate cancer, lung cancer, breast cancer, schizophrenia, orthopedic biomechanics, COPD, cardiovascular disease and neurosurgery.

Companies whose business centers on the development of open-source software employ a variety of business models to solve the challenge of how to make money providing software that is by definition licensed free of charge. Each of these business strategies rests on the premise that users of open-source technologies are willing to purchase additional software features under proprietary licenses, or purchase other services or elements of value that complement the open-source software that is core to the business. This additional value can be, but not limited to, enterprise-grade features and up-time guarantees to satisfy business or compliance requirements, performance and efficiency gains by features not yet available in the open source version, legal protection, or professional support/training/consulting that are typical of proprietary software applications.

<span class="mw-page-title-main">Free-software license</span> License allowing software modification and redistribution

A free-software license is a notice that grants the recipient of a piece of software extensive rights to modify and redistribute that software. These actions are usually prohibited by copyright law, but the rights-holder of a piece of software can remove these restrictions by accompanying the software with a software license which grants the recipient these rights. Software using such a license is free software as conferred by the copyright holder. Free-software licenses are applied to software in source code and also binary object-code form, as the copyright law recognizes both forms.

BSD licenses are a family of permissive free software licenses, imposing minimal restrictions on the use and distribution of covered software. This is in contrast to copyleft licenses, which have share-alike requirements. The original BSD license was used for its namesake, the Berkeley Software Distribution (BSD), a Unix-like operating system. The original version has since been revised, and its descendants are referred to as modified BSD licenses.

<span class="mw-page-title-main">GNU General Public License</span> Series of free software licenses

The GNU General Public License is a series of widely used free software licenses or copyleft that guarantee end users the four freedoms to run, study, share, and modify the software. The license was the first copyleft for general use and was originally written by Richard Stallman, the founder of the Free Software Foundation (FSF), for the GNU Project. The license grants the recipients of a computer program the rights of the Free Software Definition. These GPL series are all copyleft licenses, which means that any derivative work must be distributed under the same or equivalent license terms. It is more restrictive than the Lesser General Public License and even further distinct from the more widely used permissive software licenses BSD, MIT, and Apache.

<span class="mw-page-title-main">Open-core model</span> Business model monetizing commercial open-source software

The open-core model is a business model for the monetization of commercially produced open-source software. The open-core model primarily involves offering a "core" or feature-limited version of a software product as free and open-source software, while offering "commercial" versions or add-ons as proprietary software. The term was coined by Andrew Lampitt in 2008.

Software relicensing is applied in open-source software development when software licenses of software modules are incompatible and are required to be compatible for a greater combined work. Licenses applied to software as copyrightable works, in source code as binary form, can contain contradictory clauses. These requirements can make it impossible to combine source code or content of several software works to create a new combined one.

References

  1. "Epi Info". CDC. 13 September 2016.
  2. "Download STEM". Eclipse. 22 June 2017.
  3. "Eclipse Foundation Software User Agreement". Eclipse. 9 April 2014.
  4. 1 2 "clearhealth/LICENSE". GitHub. 30 January 2013.
  5. "clearhealth/clearhealth". GitHub. Retrieved 30 June 2017.
  6. "ERPNext Healthcare/LICENSE". GitHub. 29 January 2016.
  7. "gaiaehr/LICENSE". GitHub. 29 January 2016.
  8. 1 2 3 4 "Gnumed FAQs". Gnumed. 10 October 2011.
  9. 1 2 3 4 "GNU Health - Summary". Savannah. Retrieved 29 June 2017.
  10. 1 2 3 4 "Hospital OS". SourceForge. 10 April 2013.
  11. 1 2 3 4 5 6 "HOSxP". SourceForge. 17 April 2013.
  12. 1 2 "À propos" [About]. Medintux (in French). Retrieved 30 June 2017.
  13. "dev". Medintux (in French). 29 June 2012.
  14. "Installation". Medintux (in French). Retrieved 10 July 2017.
  15. "MedWebTux". Medintux (in French). 13 July 2013.
  16. 1 2 3 4 5 "OpenEMR Features". OpenEMR. 6 May 2017.
  17. "Development Policies". OpenEMR Project Wiki. 17 April 2017.
  18. 1 2 "Open Source License". Open Dental. Retrieved 29 June 2017.
  19. 1 2 3 4 "Open Hospital". SourceForge. 4 June 2017.
  20. 1 2 "OpenMRS License Information". OpenMRS. Retrieved 29 June 2017.
  21. 1 2 3 "Welcome". OSCAR User's Manual. Retrieved 29 June 2017.
  22. 1 2 "Welcome to Spinnaker". Spinnaker. Dental IT Ltd. Retrieved 30 June 2017.
  23. 1 2 "Spinnaker". Dental IT Ltd. Retrieved 30 June 2017.
  24. 1 2 3 4 5 "THIRRA Electronic Health Records Systems". SourceForge. 31 January 2017.
  25. "Distributions of VistA". WorldVistA. Retrieved 1 November 2021.
  26. 1 2 3 "Licensing". ICTedge. Archived from the original on 10 September 2014.
  27. "About iHRIS". iHRIS. Retrieved 3 July 2017.
  28. "Frequently Asked Questions". iHRIS. Retrieved 30 June 2017.
  29. "DHIS 2 Overview". DHIS2. Retrieved 30 June 2017.
  30. "Get Involved". Breathing Games. 17 December 2016.
  31. "The Nightscout Project" . Retrieved 3 July 2017.
  32. "android-uploader/LICENSE". GitHub. 27 September 2014.
    "lasso/LICENSE". GitHub. 2 July 2015.
    "chrome-uploader/LICENSE.md". GitHub. 24 November 2014.
    "windows-phone-app/LICENSE". GitHub. 29 November 2014.
  33. "cgm-remote-monitor/LICENSE". GitHub. 25 September 2014.
    "process-controls/LICENSE". GitHub. 11 January 2015.
  34. "nightscout-apple-watch/LICENSE". GitHub. 23 June 2015.
  35. "fda-presubmission/LICENSE". GitHub. 24 June 2014.
    "cgm-pebble/LICENSE". GitHub. 22 February 2014.
  36. "tidepool-org/Loop: An automated insulin delivery app template for iOS, built on LoopKit". GitHub. 8 December 2023.
  37. "Tidepool Loop has received FDA Clearance!". Tidepool. 4 January 2023.
  38. "CamBA: Tool/Resource Info". NITRC. Neuroimaging Informatics Tools and Resources Clearinghouse . Retrieved 3 July 2017.
  39. "drishti/license.md". GitHub. 1 February 2016.
  40. "Endrov". SourceForge. 3 January 2016.
  41. "License". GIMIAS. Retrieved 30 June 2017.
  42. "Ginkgo CADx" . Retrieved 30 June 2017.
  43. "Copyright and License". ITK. Kitware.
  44. "invesalius3/LICENSE.txt". GitHub. 10 June 2009.
  45. "ITK-SNAP". NITRC. Neuroimaging Informatics Tools and Resources Clearinghouse . Retrieved 30 June 2017.
  46. "License". MITK. 1 December 2014.
  47. "Download". Orthanc. Retrieved 30 June 2017.
  48. "ParaView License". ParaView. Retrieved 30 June 2017.
  49. "License". SlicerWiki. 24 November 2016.
  50. "About Voreen". Voreen. Retrieved 30 June 2017.
  51. "License". VTK. Retrieved 30 June 2017.
  52. "License". StudierFenster. Retrieved 5 October 2020.
  53. Cardoso, M. Jorge; Li, Wenqi; Brown, Richard (2022-10-04). "MONAI: An open-source framework for deep learning in healthcare". pp. 1–25. arXiv: 2211.02701 [cs.LG].
  54. "Frequently Asked Questions". Caisis. BioDigital. Retrieved 30 June 2017.
  55. "History". cTAKES. Apache Software Foundation. Retrieved 30 June 2017.
  56. "Copyrights and Licenses". Galaxy Wiki. 14 May 2015.
  57. "FAQ - Frequently Asked Questions". LabKey Support. Retrieved 30 June 2017.
  58. "glucosio-android/LICENSE". GitHub. 19 August 2015.
    "glucosio-ios/LICENSE". GitHub. 19 August 2015.
  59. "LICENSE.txt". GitHub. 26 August 2017.
  60. "platform/LICENSE.md". GitHub. 18 November 2014.
  61. "Debian Med". Debian. Software in the Public Interest, Inc. 5 July 2016.
  62. "LAIKA: EHR Testing Framework". SourceForge. 19 April 2013.
  63. Brauer, Jacob (14 August 2013). "Source Code Contribution Guidelines". Mirth Connect.
  64. "FHIR Foundation" . Retrieved 3 July 2017.
  65. "Foundation Module". FHIR. HL7. 19 April 2017.
  66. "License and Legal Terms". FHIR. HL7. 19 April 2017.
  67. "specifications-BASE/LICENSE". GitHub. 29 July 2015.

Further reading