Custom OpenEMR code modules page in the wiki

Hi Folks-

There’s a new page in the OpenEMR wiki that showcases code modules that have been written for OpenEMR. These modules have not yet been approved for inclusion in the codebase, but the dev thinks they’re mature enough to be installed in a production instance.

In this page you can review the dev’s summary writeup of the module, maybe see some screenshots, and contact the dev for more information.

Please note that even though Brady did approve of the page itself, these modules have not been vetted by the usual OpenEMR selection process so any use of them is strictly ‘cave installer’, so to speak.

If you’re a dev who wants to post there you’ll need to be familair enough with mediawiki markup to hack together a simple little chunk of text describing your module. But it’s pretty simple stuff and links to instructions on that are included. After all, if you can develop in php how hard can mediawiki be?

Check out and put your module up there-- you could get famous, and revolutionize health care at the same time!

  • Harley
1 Like

@htuck Are these open-source modules / paid for modules? Are they available to be installed via composer like what @sjpadgett and I did with the SMS Fax Module? I love the idea, and for developers or consumers to be able to do a simple composer require like the example below would be awesome

composer require "module-provider/module-name:module-version"

That’s how we do it with the fax module:
composer require "openemr/oe-module-faxsms:2.2.0"

Hi @adunsulag -
The page is simply a place for devs to display their wares, so to speak. But you bring up an interesting point. In keeping with the FOSS nature of OpenEMR, I would hope that devs would restrict their offerings to FOSS modules but how can one prevent them from making whatever arrangements they want with a prospective customer?

It is reasonable to me that an IT professional would charge for the installation of the module and training in its use. But I can’t think of any way to dictate that the code be FOSS without requiring that it’s hosted on github or somesuch place, and I’m not going to be the Enforcer about this. Of course, if the module gets included into the OpenEMR codebase it will be free AND open source, but until then, I guess whatever the dev offers is what it is.

As far as using composer, I’ve played with it a little and it does seem like a really good way of doing things. However, for the purposes of that wiki page, it’s up to the dev to decide how to make their module available. If they want to log into the user’s OpenEMR server, fire up nano and manually type the code in… well, ok fine!

1 Like