exception_e

Awesome! I have a million things on my plate with the project so if you want, you can reach out to me at matthewvita48 (at) gmail (dot) com so we can discuss what may interest you!

Great idea!

I'm going to show this to a few of the folks on our non-profit board. From first glance, it looks like a great fit.

Thanks, Matthew

Hi everyone. Happy to see my posting caught some attention (nice start to my lunch break!).

Obviously, our team is asking for badly needed donations to support our work (primarily for poor locale users), but we're always looking for volunteers, as Brady pointed out. I am a serial HN reader and have learned that folks love React (and Vue) here. If there are any React (or Vue) gurus interested in volunteering, we'd love to get our UI at parity with modern web standards. I can definitely say that volunteering on this project is great for technical reasons as well as getting to meet grateful users from all over the world.

I noticed there's some healthy discussion here around US healthcare/open source usage and I ask you to consider that very modern and developed countries such as the US, UK, etc, etc have the money for EMRs and a more-or-less reasonable gov't that offers up regulations and incentives to get rid of paper. This is simply _not_ the case in many parts of the world. Therefore, I ask you to consider that without medical open source solutions (not just limited to OpenEMR), most are stuck on paper!

NOTE/UPDATE: John, our data scientist on the project, posted on here about his AWS efforts (seen below). He's never used HN and is having a hard time editing his post. `:%s/Trial/Tier` is what he's getting at... we have put together a very low cost (AWS free tier) solution for folks in low resource areas as well universities looking to teach with a modern EMR without the big price tag!

-Matthew

Most of our users are outside of the US where nonfree solutions are simply not in the cards financially.

In the US, we are seeing adoption in practices that can't afford expensive EMRs and in those that want to truly customize their system.

Also, Meaningful Use/HITECH is not ACA.

Oh, come on. Don't downvote this. Had a big chuckle xD

Please see: https://news.ycombinator.com/item?id=15121351 - I am still looking for a person to fit this role. I can also have this person fill many QA needs on the project in general.

My email is matthewvita48 at gmail dot com

Thanks!

Thank you, TLDR authors for this tool. It solves a real problem and can coexist with traditional man pages.

I may have missed it in the discussion already, but would it be possible for TLDR to favor editable online sources for its content (e.g.: WordPress/Mediawiki with Markdown)? This Wikipedia style of editing may be a big game changer.

Caveat: Of course, content would have to be packaged locally for offline use.

To be fair, most people use IDEs that generate them based on the fields so this would be unlikely.

This is AMAZING. I am going to use this for its intended purpose because I love passive learning. I also intend on using it as a tool to keep me in check with nags with things that don't end up on my immediate schedule: "Have you written the unit tests for that open source project yet?". Having that show up a few times in random days or months would be great.

All I can think about is how I wouldn't be able to do this because I love my cats and rabbit too much. Wouldn't be possible.

Very cool though!

Brilliant. I am looking to redo my portfolio site and this will help with wording examples

My thoughts exactly. This is very important.

I was very skeptical about this early on. IMO, documentation is best left close to the code. Collaboratively editing is what git and project wikis are for (esp in open source).

Looks very nice and concise. A few suggestions:

- You should make those endpoints restful with resources rather than using action verbs (just a best practice so that APIs are consistent and readable)

- Maybe this is a nitpick, but ctx/context is a term that appears across many Java frameworks. When I think of context, it has to do with global framework full (Spring Context, base framework classes, etc) rather than request/response objects.

- Can you provide a snippet of unit test code for the class?

- Any advice on advanced input validation?

Very good work.

Oops! This has been posted here: https://news.ycombinator.com/item?id=14828772

Sorry about the dupe. Hiding the post.

I understand the cell carrier proximity issues, but I'm very interested to see if there's any follow up the server side of things. Perhaps there are some Kubernetes lessons to be learned.

I love seeing the updates. It is also a great way to get feedback and answer questions about your open source software. Because of this, I plan on posting the next OpenEMR project update here, even though it is mainly bug fixes and UI tweaks.

A lot of good feedback and questions were posted last time the update was posted here.

EDIT: I re-read your post a few times and understand what you mean (originally thought you were directing name calling to _me_). Yes, it is important to be flexible with these things and not operate in absolutes. It is very important to be kind and human to others in open source.

Also, I learned what "help vampires" are. Neat.

I agree that "Pull Requests for Everything" is actually a good idea to encourage programmers to be practical and provide value (I have a pretty strong opinion here... fork, work, pull is always better than passively entering in an issue).

However, this approach is not good for non-technical end users. Remember that there is a lot of end-user facing open source out there and those folks aren't programmers!

> I also would like to contribute to open source software projects

If you'd like, I'm looking for help on https://github.com/GoTeamEpsilon/OpenEMR-AWS-Guide

Send me an email at matthewvita48@gmail.com

...this applies to anyone in this thread as well :)

Archive folder works. Disc space is cheap and plentiful!

This is great for Docker base images.

Unless it's different with Chromebooks, it's free up to 15 GB.

The Pragmatic Programmer. I'm on mobile, so just Google for it.

This book is amazing and still holds up today, for the most part.

touché

Without wine, you can't.

Just sent both an issue and a PR. Great idea!

Hospitals in America aren't the main consumers of OpenEMR. Think smaller facilities, and hospitals and facilities outside of the US.

It's just for our website and wiki. We've moved to Github for the most part.

There is talk between myself and a couple of other contributors to move the site and wiki to AWS :).

Feel free to volunteer to speed this up, of course.

EDIT: Misread your comment. We are hosting downloads on the SF site. Really need to move to AWS...

Not sure what you mean... can you please be more specific?

OpenEMR is 100% open source. It's GPL'ed :).

As far as compliance, we are happy to inform you that OpenEMR is now 2014 ONC Ambulatory EHR Certification complete.

EDIT: If you're asking about support, there are over 30 professional vendors. Community support​ is also available.

If you have further questions, feel free to reach out to my email (in my profile).