91–100 of 119 posts
I've been volunteering in hospitals in a developing country for a while now and the information systems they use here are really bad. With an eye on replacing said information systems, I've had a look at the open source medical records / hospital management systems available. When I looked at the details these systems are often not great replacements. So you're replacing aging, poorly written information systems with…
https://en.wikipedia.org/wiki/List_of_open-source_health_sof... Please avoid too much diversification by reinventing wheels, instead please contribute to one of these projects. Mobile first is a basic requirement in developing countries.
When you say "mobile first is a basic requirement" you're thinking about a specific context of software intended for the general population of people in those countries.
However, with projects like HospitalRun, the general population is not the audience, Hospital staff and administrators are, and even in developing countries they still primarily use laptops and tablets at the Hospital.
Looks great. Why such emphasis on "Ember"? Does the target audience really care what front-end framework is used?
I applaud the efforts taken here, more than I've ever done, and it looks good. But wasn't there big talk of Ember's (JavaScript's) poor(er) performance on Android devices recently? It seems like this tech would be prime for Android users. I don't know if the performance is bad from a usability standpoint or just a pure numbers via specs point of view.
They're currently working on a way to get past this, by actually enabling server-rendering (much like react):
Earlier quoted context omitted.
We know how to do this. Plenty of other industries have solved this problem. It takes organizational will to make it a priority.
That's not the point, the point is that the effort required makes it harder to innovate and that not only does that limit competition but it also enable proprietarism. In a perfect world you could just e-mail the data without any concerns of authenticity, privacy, robustness etc. But you can't, so you would have to bring in a huge firm that is going to spend a lot of money and effort getting everything right or at le…
My only issue is that there needs to be a requirement of inter-operate with each other. Sure take a copyright and a patent pending BUT make it so that other company systems can speak to each other. The parent shouldn't have to have the burden of "Holy Crap I am the only person in the world to know everything about my child." Doctors and nurses shouldn't have to have me retell everything a hundred times when 90% of that should be available.
Innovate PLEASE but play nice with other systems.
Earlier quoted context omitted.
Responsive work is on the roadmap and coming soon. However, the current intent is for the project to be fully usable on tablets, but not necessarily on phones. The hospital staff in our use cases will all be using the software from either a laptop or tablet.
Understood. I'm on a laptop, and unless the window is full screen the UI isn't great.
Sorry another story about my journey with my son while he battled cancer. Closed Proprietary image formats and systems HURTS patients. We used the local hospital for Chemo and everything else at the Children's Hospital 1.5 hours away for his legs and lungs. I would always have to wait 20-30 minutes to get a DVD of the studies (PET, CT Scan or MRI even ultrasound, but those are worthless) and then bring them to the do…
Wow. Thanks for sharing this, I know it can't be easy talking about it. It's things like this where people who can solve the problem just aren't aware of the problem. Connecting the two is the hardest thing in innovation. It is painful to know how many developers can solve this yet they spend their days on improving their laundry for your cat delivered to your door app. Nobody is at fault or to blame, I'm not saying…
If anyone is intrested here is a few links.
He had a bucket list and one of them was to write a comic book. When he passed the Comic Book Blogs honored him by sharing his story. http://www.unleashthefanboy.com/comics/inspirational-comic-w...
NPR made his obituary the obituary of the day. It actually wasn't something I knew about till weeks later and really made me glad to listen to.
While I don't agree with many of the specifics of the HL7 spec[1], I guess the community behind this project should decide if this system will conform or not. [1] http://www.hl7.org/implement/standards/
The thing is, every client implements a different subset of the spec, and nonconformance is widespread.
There is no "conforming" to a spec which is a spec in name only.
http://webcache.googleusercontent.com/search?q=cache:3ygj10u...
https://en.wikipedia.org/wiki/List_of_open-source_health_sof... Please avoid too much diversification by reinventing wheels, instead please contribute to one of these projects. Mobile first is a basic requirement in developing countries.
Smart-phone may not be the mobile target you're thinking of here.