What this highlights of course is that getting data from a medical device into an EMR is a lot harder than it should be. "It’s not pretty" is an understatement. In the ideal world nobody should have to be connectologist to get medical data where it needs to be. Unfortunately, we have a long way to go before that becomes a reality.
File stream data can be used from the .NET Framework using the traditional SqlParameter, but there is also a specialized class called SqlFileStream which can be used with .NET Framework 3.5 SP1 or later. This class provides mechanisms, for example, for seeking a specific position from the data.
There are pros and cons to this approach. The backup and transactional issues, along with the performance considerations, all have to be evaluated against your specific system requirements. Having the SQL Server engine manage the database relationship to the binary files seems like a big advantage over maintaining flat files yourself.
Jeff Atwood is a great writer. All of his blog posts are informative and interesting.
How to Write Without Writing is a case in point. It starts off with a clever hook ("trick my fellow programmers"), expounds the benefits of writing, particularly answering questions ("fun sized") as a way to improve your communication skills. All of this is true.
The worm in the apple of course is the blatant promotion for the Writers Stack Exchange site. You really can't fault Jeff for doing this though. If you were running a venture funded business that depended on driving traffic, you'd make use of your celebrity in exactly the same way.
This will hopefully not diminish the message that writing can be used as an effective vehicle to gain technical knowledge as well as being a critical professional skill.
That wasn't as insurmountable and impenetrable as I thought it was going to be.
I'm jealous of companies that get to produce diagnostic medical devices without having to go through the FDA 510(k) process. For example, the iHealth BP3 blood pressure monitor is a high-tech looking device with a free Apple application:
The article Is Cloud the tomorrow of Medical Devices Industry? includes some of the challenges -- regulatory, privacy, security etc. -- faced by manufacturers trying to manage medical device data in the cloud. You can't disagree with this statement:
The success of the vision of Smart Connected Health Grid is dependent on wide scale adoption of cloud computing in all areas of healthcare.
There's no doubt that adoption of cloud-based technologies are starting to provide concrete market opportunities in the Healthcare space.
There are also two major market barriers that will have to addressed in order for the cloud's full potential to be realized:
1. Who's going to pay for it?
The Apple/Google/Facebook "created a marketplace around the end consumer" model will not work in the medical industry. Consumers do not manage their own healthcare, and certainly not their medical data.
Glucose monitoring is also not a good model. Strips and meters are reimbursed by Medicare and most private insurers.
The "Service Delivery Platform" may be a great idea, but unless you can prove its effectiveness at saving money in the overall healthcare delivery system it has only limited value.
Proving this effectiveness is difficult to do, and the bar is very high on the expected returns for preventative care. Maybe this is where the vertically integrated Accountable Care Organizations (ACO) could have an impact?
The end consumer (re: their willingness to spend money anyway) is not likely to be part of the revenue generation equation.
2. Interoperability.
You can't overstate connected in "Connected Health Grid." This is where the real value is.
Data collected from a medical device must be put into context with all of the available health data in order to properly access a patient's current state.
This means you have to make the device data that resides in your cloud available to be consumed by others, e.g. payers, PHRs, hospital EMR systems, etc. Each of these interfaces is unique and costly. HIPAA is also key barrier here.
There are many technical issues surrounding medical device connectivity. I've written frequently about these interoperability topics in the past.
The potential is there, but IMO creating a value proposition that will result in a sustainable market based on a technology alone will probably not work. It's the old "hammer looking for a nail" problem.
Medical device data combined with cloud-based technology will be part of many effective healthcare solutions. Some of these may actually make money, someday.
Cardiocam is a low-cost, non-contact technology for measurement of physiological signals using a basic digital imaging device such as a Webcam. The ability to perform remote measurements of vital signs is promising for enhancing the delivery of primary health care.
A link to a PDF (here) has a full description of the research, including their Cardiac pulse recovery methodology:
The method uses Blind Source (Signal) Separation (BSS) by Independent Component Analysis (ICA) of the changes in the video signal:
Volumetric changes in the facial blood vessels during the cardiac cycle modify the path length of the incident ambient light such that the subsequent changes in amount of reflected light indicate the timing of cardiovascular events.
Keely Wray advocates that PCHR data should be "Hackable" (my highlight):
I mean "hackable" in the sense of the word that is quickly growing in popularity: allow owners of a product to manipulate, re-purpose or add to the functionality of a product to serve their own personal needs.
Ms. Wray asks:
Doesn't it make sense to allow patients to put the technologies together in a way that meets their needs?
Their own needs? Maybe yes, but probably not.
The biggest incentive for innovation will be where someone sees an opportunity to meet a lot of other people's needs. This may well be for group that shares a common problem or aliment with the technologist(s). The initial intent may be altruistic, but real growth will only take place when a market emerges. This is the reality that could lead to significant new health data management solutions.
For example, PatientsLikeMe started off this way (from the About Us page):
Our personal experiences with ALS (Lou Gehrig's disease) inspired us to create a community of patients, doctors, and organizations that inspires, informs, and empowers individuals.
Today's New York Times article Making Ads That Whisper to the Brain gives a pretty balanced view of using EEG monitoring for doing market research -- "Neuromarketing."
This is not a mind reader,... We can only measure whether you are paying attention.
I write frequently on EEG related technologies, and often sceptically about some of its applications. The term "pop neurology" seems to apply here, especially when it comes to the ability for this technology to correlate to purchasing behavior. The establishment of NeuroStandards will only ensure that everyone is fooling themselves the same way.
Also, "brain-whispering" makes no sense. Most ads I see are loud and intellectually insulting (TV) or are visually annoying (Web) -- it's more like brain-shouting.
... see what we can do to “agilify” our practices under these standards as we move forward.
It's been three years since I wrote Agile development in a FDA regulated setting. I'll be interested to see if the application of "agile, high assurance activities" in this environment -- and the associated issues -- have changed since then.
I've followed BCI: Brain Computer Interface and EEG work for a long time. There is still a long way to go on the "mind reading" front, but these types of developments are all encouraging.