Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GNU Health

gnuhealth.org

Post reply on HN
Print view View original

121–130 of 138 posts

Re: GNU Health

#121

Post by bonsai_spool »

leakycap wrote: post #87
bonsai_spool wrote: post #77

Earlier quoted context omitted.

> EHR is being used because it's required - both by payors and regulation/law. I can think of zero instances where an organization switched to EHR without being forced by a deadline from an outside source. Your argument fails in cases where hospitals switch from bespoke EHRs to use one large EHR that has better revenue features. This is quite trivially discovered if one follows the news of large hospital chains who h…

> This is quite trivially discovered if one follows the news of large hospital chains who have moved to Epic recently. Epic is one of the few providers who can meet a larger organization's overall needs The competitors, like eClinicalWorks, are a shadow in comparison No doubt companies increase revenue with more efficient capture of services, costs, labor factors, etc, but I've actually been in the room with people f…

> but I've actually been in the room with people from Epic and have heard the sales presentation. I'm betting I have a decent grasp on both what they're selling and what the buyers are asking for.

This may be true but it is different from your earlier claim about an upcoming deadline forcing any change in EHR, which was clearly false.

Re: GNU Health

#122

Post by cameron_b »

nradov wrote: post #55
john61 wrote: post #24

Earlier quoted context omitted.

This is meant to be used in hospitals. Where I live no hospital personal uses phones to manage healthcare data. They have PCs.

You seem to be living in the past. While EHRs are still primarily used from desktop PCs, all of the major ones have native mobile apps now. Clinicians appreciate being able to review patient charts and action alerts while away from a PC cart.

And this would be a white-label Epic MyChart for the particular system with embedding for the inpatient or customer facing connections that should be used

It seems like that could be done with a system shipping their own white-labeled GNU Health app through the App Store

Re: GNU Health

#123

Post by righthand »

IshKebab wrote: post #110
righthand wrote: post #91

Earlier quoted context omitted.

No offence but IshKebab is not a person I would associate with someone who knows anything about health, useable and practical software. No matter how noble their intentions are about criticizing software they’ve never used nor never attempt to use because of unfounded stigmas. Misguided indeed. Automake, bash, emacs, gnucash, gnuhealth, coreutils, gnupg, gimp, grep, make, etc. are all great pieces of GNU software. Do…

> Automake, bash, emacs, gnucash, gnuhealth, coreutils, gnupg, gimp, grep, make, etc. are all great pieces of GNU software. Come on now. Gnucash is actually decent and I guess I can't complain about grep or coreutils but are you seriously claiming automake is great? The biggest mess I've even seen. Make fundamentally can't handle spaces in paths, nor is there a sane way to split a project into multiple Makefiles. GIM…

So you admit that all this software we’ve used for decades and still use. That’s pretty great, practical and useable software to me. Is it perfect software and future proof? No but you’re just looking for ways to support your wild opinion that Gnu software is some how bad or not useful.

Re: GNU Health

#124

Post by nylonstrung »

ivanjermakov wrote: post #82
bjoli wrote: post #74

Earlier quoted context omitted.

I wonder what would happen if EU harmonized the legislation so that the EU states could go together and develop an OSS journaling system. The amount of money saved would be astronomical.

Spending money is what drives the economy. No diverse expensive healthcare software means thousands of employees don't get paid and don't spend earned money within the economy.

So hospitals in Copenhagen buy Epic EHR to stimulate the economy of Wisconsin?

Re: GNU Health

#125

Post by IshKebab »

righthand wrote: post #123
IshKebab wrote: post #110

Earlier quoted context omitted.

> Automake, bash, emacs, gnucash, gnuhealth, coreutils, gnupg, gimp, grep, make, etc. are all great pieces of GNU software. Come on now. Gnucash is actually decent and I guess I can't complain about grep or coreutils but are you seriously claiming automake is great? The biggest mess I've even seen. Make fundamentally can't handle spaces in paths, nor is there a sane way to split a project into multiple Makefiles. GIM…

So you admit that all this software we’ve used for decades and still use. That’s pretty great, practical and useable software to me. Is it perfect software and future proof? No but you’re just looking for ways to support your wild opinion that Gnu software is some how bad or not useful.

Ask me how long I've used Jira...

Re: GNU Health

#126

Post by bonsai_spool »

nradov wrote: post #79
bonsai_spool wrote: post #77

Earlier quoted context omitted.

> EHR is being used because it's required - both by payors and regulation/law. I can think of zero instances where an organization switched to EHR without being forced by a deadline from an outside source. Your argument fails in cases where hospitals switch from bespoke EHRs to use one large EHR that has better revenue features. This is quite trivially discovered if one follows the news of large hospital chains who h…

Revenue cycle issues are important but not the only factor. It's simply no longer economically feasible for provider organizations to maintain bespoke EHRs. The costs have gone up too much. They can't afford to pay developers to build and maintain all of the functionality now required due to federal interoperability rules compliance and escalating user expectations.

I'm not talking about bespoke EHRs - the GP made the claim that only governmental insistence compels EHR decisions. If that were true, there wouldn't ever be a change from one EHR system to another.

But these get announced all the time, so the premise is false.

Re: GNU Health

#127

Post by AlotOfReading »

cyberax wrote: post #116
lottin wrote: post #115

Earlier quoted context omitted.

How does exactly "breaking windows" improve the lives of people?

By creating work that needs to be done, and thus forcing people to start spending.

To bring things back to the original point, there's always a way for health centers to spend money improving patient care. They could hire more nurses and give the existing ones more sleep, for example. In the context of the analogy, a broken window is diverting resources from the broken plumbing and refrigerator motor instead of creating an incentive to spend where none existed.

Re: GNU Health

#128

Post by PhilippGille »

EasyMark wrote: post #109
cseleborg wrote: post #22

> The easiest way to get MyGNUHealth is by installing the package from your favorite operating system / distribution. Many operating system distributions already ship MyGNUHealth. I was actually curious to try this out on my phone, since they claim to support mobile devices. If running a command-line package manager is the easiest way to install this on Android, I don't want to know what harder ways exist. I find thi…

why would you run a set of software meant for medical providers (hospitals, clinics, etc) on your phone?

Did you read the article?

> MyGNUHealth is the GNUHealth Personal Health Record application for desktop and mobile devices

Re: GNU Health

#129

Post by scott_w »

rcxdude wrote: post #100
scott_w wrote: post #6

Earlier quoted context omitted.

The person implementing the system for the hospital is accountable. I don’t see why this is difficult because it would be the same if that person built their own product from scratch. There’s no vendor here that they can sue if they were paying for a product and deploying that, but that’s a different situation and the hospital, frankly, won’t care about that. Who their supplier subsequently sues isn’t their problem.

Also, quite frankly, whatever fancy contract you have and whatever legal system is backing it up, if the system you're using fails, it's your problem . You can't actually shuffle around all consequences freely. I see this so often where people pay huge amounts of money (either buying a more expensive system or buying vs building) because 'we need the support!' and then still wind up with a bad system because the qual…

> And even in cases where the problem is 'we might get sued', the fact that you have someone else to sue is to a large extent multiplying problems because you now have two lawsuits.

To be fair, I’m not sure if this is a huge issue. It seems a pretty standard part of business. Like, if I’m a store and I sell a product that’s faulty, the customer would file their case against my business and it’s up to me to decide how to resolve that with my supplier.

Re: GNU Health

#130

Post by righthand »

IshKebab wrote: post #125
righthand wrote: post #123

Earlier quoted context omitted.

So you admit that all this software we’ve used for decades and still use. That’s pretty great, practical and useable software to me. Is it perfect software and future proof? No but you’re just looking for ways to support your wild opinion that Gnu software is some how bad or not useful.

Ask me how long I've used Jira...

Because you had the choice to not use Jira?
Post reply on HN