Profit in Health Care
I am on the DrWeil.com newsletter list—and it isn't because he looks like me. It actually has some useful information. But, like most newsletters, it has ads.
Sometimes the ads are useful as well. Today's ad was for a non-medical device that will lower blood pressure. I have friends with high blood pressure so I decided it was worth a look. It was as it convinced me that a Linux geek needs to build an Open Source product for those that don't have expensive medical insurance that will pay for overpriced gadgets.
The product is a little box with a few buttons, a small LCD, an embedded processor, a respiration sensor and a set of headphones. Oh, and "patented technology". What the unit does is teaches you to slow down your breathing which should lower your blood pressure. Well, those of us that grew up in the 1960s had a similar method called "chilling out". Less stress and your blood pressure goes down.
This particular box seems to be able to learn about what it did with you last time (gee, it has some flash) and uses two tones to program you—one to tell you to breath in, the other to tell you to breath out. Thinking about the hardware and the technology involved, it it was mass produced in China I feel like it would cost less than $20. It isn't (well, I don't know where it is made but I expect the market is relatively small right now) so I figured $50.
Then I remembered the "patented technology". I have no idea what that is and didn't bother looking it up but figured I needed to double the price to cover it. Well, I was way off. It isn't $20, $50 or even $100. It costs $300. That price alone will likely raise your blood pressure.
At first I started thinking about how you would do something like this with a PDA such as a Palm Z22. The problem is how you would input the breathing sensor. But, a Z22 retails for $100 so it already sounded too expensive if that is all you were going to do with it. Why not just a program that you could run on your desktop or laptop? Being "a real computer" you could probably offer fancier things such as background music.
Could someone profit from this idea implemented as Open Source software? I don't see why not. Certainly not at the same profit per unit but at $30 instead of $300 you could probably sell a lot more. Here is what I think would make sense.
Find or make a breathing sensor. As it probably won't plug into your computer— think USB, serial or parallel port—some additional hardware is needed. Build it. Write the software to talk to the unit. Sell it at a fair price to reflect the cost of the hardware. Make the software Open Source.
What about getting health insurance companies to pay for them? I don't think it is worth it. The $300 product does imply it is FDA approved but I am reasonably sure it just means the FDA doesn't care. It isn't something you ingest or even connect to your body. But, actually getting insurance companies to pay for something is likely to cost a lot more than it is worth. Let someone else do that—you just sell them the breathing sensors with the computer interface and give them the software.
Ok, I feel better. Writing this seems to have lowered my blood pressure.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Paranoid Penguin - Building a Secure Squid Web Proxy, Part IV
- SUSE LLC's SUSE Manager
- Google's SwiftShader Released
- Managing Linux Using Puppet
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- SuperTuxKart 0.9.2 Released
- Parsing an RSS News Feed with a Bash Script
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide