OpenEMR Product Registration Project

OpenEMR Development
1

matthewvita wrote on Tuesday, September 20, 2016:

Hi all,

Goal of this small project: Allow users to (optionally) one-time register their OpenEMR installation to improve visibility of unique users. After registering, users will receive email updates when OpenEMR is updated (including security updates).

Project page is here: http://open-emr.org/wiki/index.php?title=Product_Registration

Thanks,
Matthew

2

visolveemr wrote on Tuesday, September 20, 2016:

Hi Matthew,

We really appreciate your effort in creating the user registration for OpenEMR.

As a part of initial effort in contributing to OpenEMR with registration , we also came up with the similar idea and started to process in getting OpenEMR User registration done .

Since we see multiple threads from your end, saying most of the items are already under development, we would like to join hands to take part with the development progress if needed.

Thanks,
ViSolve OpenEMR Support Team
ViSolve

3

visolve1995 wrote on Tuesday, September 20, 2016:

Mathew,
Specifically, if you need any help on the back end implementation (NOT the
GUI - since you have already designed it) including testing please let the
team know.

Thanks,
Sena

On Tue, Sep 20, 2016 at 3:42 PM, ViSolve visolveemr@users.sf.net wrote:

Hi Matthew,

We really appreciate your effort in creating the user registration for
OpenEMR.

As a part of initial effort in contributing to OpenEMR with registration ,
we also came up with the similar idea and started to process in getting
OpenEMR User registration done .

Since we see multiple threads from your end, saying most of the items are
already under development, we would like to join hands to take part with
the development progress if needed.

Thanks,
ViSolve OpenEMR Support Team
ViSolve http://hc.visolve.com

OpenEMR Product Registration Project
https://sourceforge.net/p/openemr/discussion/202506/thread/b5901dcf/?limit=25#fea9

Sent from sourceforge.net because you indicated interest in
OpenEMR / Discussion / Developers

To unsubscribe from further messages, please visit
SourceForge.net: Log In to SourceForge.net

4

robertdown wrote on Tuesday, September 20, 2016:

Hi Sena,

I’m actually heading up the backend development aspects. Will reach out to you later today and my implementation plan

5

visolve1995 wrote on Tuesday, September 20, 2016:

Excellent - No issues and if you guys needed any help we are here…
Regards,
Sena

On Tue, Sep 20, 2016 at 5:08 PM, Robert Down robertdown@users.sf.net
wrote:

Hi Sena,

I’m actually heading up the backend development aspects. Will reach out to
you later today and my implementation plan

OpenEMR Product Registration Project
https://sourceforge.net/p/openemr/discussion/202506/thread/b5901dcf/?limit=250#fea9/d2f0/8ec2

Sent from sourceforge.net because you indicated interest in
OpenEMR / Discussion / Developers

To unsubscribe from further messages, please visit
SourceForge.net: Log In to SourceForge.net

6

matthewvita wrote on Tuesday, September 20, 2016:

Wow, thanks to all for quick feedback and offering to help!

@Robert: please update the project page with whatever plan you have for the backend. I wanted to mention that I’ve had luck with https://www.mailgun.com/ for the sending out piece. It’s not totally free though. Else, https://nodemailer.com/ is a pretty plug-and-play solution where you create a “service” gmail account to be the sender. SES is nice as well, but I know we’re trying to move fast with this project.

Thanks,
Matthew

7

mdsupport wrote on Tuesday, September 20, 2016:

Rather than spending your creative energies on a separate mechanism, can we not leverage twitter API?

8

robertdown wrote on Tuesday, September 20, 2016:

We’ve already selected a platform to handle the registration info and will have something in the next couple of days (hopefully)

Not sure the Twitter API would fit this area

On Sep 20, 2016, at 15:22, MD Support <mdsupport@users.sf.netmailto:mdsupport@users.sf.net> wrote:

Rather than spending your creative energies on creating a separate mechanism, can we not leverage twitter API?

OpenEMR Product Registration Project

Sent from sourceforge.nethttp://sourceforge.net because you indicated interest in https://sourceforge.net/p/openemr/discussion/202506/

To unsubscribe from further messages, please visit https://sourceforge.net/auth/subscriptions/

9

matthewvita wrote on Tuesday, September 20, 2016:

Not everyone has Twitter but everyone has email.

Good thought though.

-m

10

matthewvita wrote on Monday, October 17, 2016:

Just an update just in case folks want to collaborate on the remaining work items (mainly dealing with AWS deployment, polishing things, and testing).

The project page is here: http://open-emr.org/wiki/index.php/Product_Registration

The master task list and 1 of 2 PRs is here: https://github.com/openemr/openemr/pull/257#issuecomment-251567550

Thanks,
Matthew Vita

11

bradymiller wrote on Monday, October 17, 2016:

Hi,

Thanks for all of your work on this.

Time to bring the code into the codebase. Is it functional now? Also, what happens if the OpenEMR instance is not connected to the internet (ie. does it time out nicely)?

I’m looking into a wildcard SSL certificate to cover both open-emr.org and reg.open-emr.org.
Any folks know of places to find inexpensive wildcard SSL certificates?

And where should we direct the reg.open-emr.org domain to (after reading up on AWS, looks like will be using CNAME)?

thanks,
-brady
OpenEMR

12

mdsupport wrote on Monday, October 17, 2016:

We do not have first hand experience but Let’s Encrypt seems to be promising since they already have support from one root authority. If this really work, it something all portal servers should incorporate in the standard setup instructions.

13

bradymiller wrote on Tuesday, October 18, 2016:

Hi,

Thanks for pointing out the Let’s Encrypt option. That will be a very nice free way to support https on the main open-emr.org website (after we migrate the website away from sourceforge).

It looks like AWS actually has a service to support this (without cost, I think), so this seems to be the route to go:
https://docs.aws.amazon.com/acm/latest/userguide/acm-overview.html

-brady
OpenEMR

14

bradymiller wrote on Tuesday, October 18, 2016:

And here are certficate create/use instructions specific to AWS EB:
http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/configuring-https.html

15

mdsupport wrote on Tuesday, October 18, 2016:

You will have to try it out to find what this means -

You cannot use Amazon-issued certificates outside of AWS.

I guess that means Amazon CA is not automatically included in most browsers.

If that is a problem, you could also try cacert.org - again with same browser root CA issues.

16

bradymiller wrote on Wednesday, October 19, 2016:

Hi,

Read into this a bit, and appears it means that the certificates can only be used in some of the amazon services (like load balancer and cloudfront). Since the registration project will be using a load balancer, I think this will work for this(and it will hopefully show up on browsers as being “official”).

Looks like we won’t be able to use this mechanism within an EC2 container for the website (we are thinking of migrating the open-emr.org website from sourceforge to an AWS EC2 instance). In this case, though, the Lets Encrypt option you pointed out should work very well (and best of all is free in terms of cost and maintenance).

-brady
OpenEMR

17

bradymiller wrote on Thursday, October 20, 2016:

Hi,

I just committed Matthew’s registration code into the codebase. It’s very cool. Thank you Matthew!
Let us know if any issues.

-brady
OpenEMR

18

matthewvita wrote on Friday, October 21, 2016:

Brady,

Thank you for your tweaks. I have noted the remaining tasks in the top post on this pull request so it is clear: https://github.com/openemr/openemr/pull/257

Thanks,
Matthew