Monthly Archive for December, 2007

BCI: Brain Computer Interface

I ran across Commercial brain computer systems are coming today (original article is here). This is a cool graphic:

BCI

I’ve talked previously about Human-Computer interface (HCI) work.

Invasive BCI technologies have incredible potential. In addition to the unique device-human interface challenges (primarily sensors), it will also require significant advancements in the basic understanding of the underlying electrophysiology (cortical and motor). As reported, EEG-based processing will continue to be a corner-stone for this work, just as it is for non-invasive systems.

This slide from the report (pp. 170) summarizes the uses and importance of this type of work:

Figure C.9. Possible applications of BCIs.

Here’s a shorter overview of BMI: Mind Controlled Bionic Limbs

Randall Munroe at Google

Randall Munroe is the creator of xkcd, a webcomic of romance, sarcasm, math, and language. Munroe on Munroe: “I’m just this guy, you know? I’m a CNU graduate with a degree in physics. Before starting xkcd, I worked on robots at NASA’s Langley Research Center in Virginia. As of June 2007 I live in Massachusetts. In my spare time I climb things, open strange doors, and go to goth clubs dressed as a frat guy so I can stand around and look terribly uncomfortable. At frat parties I do the same thing, but the other way around.”

This Authors@Google event took place December 7, 2007 at Google Headquarters in Mountain View, CA.

Authors@Google: Randall Munroe

This guy is a true nerd.

Note: The embedded tag from YouTube does not behave well in WP.

HL7 Interfacing: The last mile is the longest.

Tim Gee mentions the Mirth Project as a cost effective solution for RHIOs (regional health information organizations). In particular, he notes that the WebReach appliance is “ready to go” hardware and software.

I’ve recently started looking at HL7 interface engines for providing our ICG electronic records to customer EMR systems. I’ve mainly been evaluating Mirth and NeoIntegrate from Neotool.

One of the Neotool bullet points about HL7 V2 states:

Not “Plug and Play” – it provides 80 percent of the interface and a framework to negotiate the remaining 20 percent on an interface-by-interface basis

Since HL7 V2 is the most widely adopted interface in the US, that last 20% can be a significant challenge. This is one of the primary purposes for HL7 integration tools like Mirth and NeoIntegrate — to make it as easy as possible to complete that last mile.

If you look closely at the Mirth appliance literature you’ll see this in the Support section:

For customers requiring assistance with channel development, WebReach consulting and engineering services are available, and any custom work performed by WebReach can be added to your annual support agreement.

They’re providing a turn-key hardware and integration engine system, but you either have to create the custom interfaces yourself or hire them (or someone else) to do it for you.

<AnalogyAlert>
This means that you have bought the hammer and identified the nail(s) to pound in. All you need to do now is find and hire a carpenter to complete the job.
</AnalogyAlert>

This really shouldn’t be that surprising though. Custom engineering and support is the business model for the WebReach Mirth project and I’m sure a large revenue generator for Neotool.

There is certainly great value in being able to purchase a preconfigured and supported HL7 interface appliance. Just be aware that it’s not quite ready to go.

Update 17-Dec-07:

If anyone has experience using HL7 integration engines that they’d like to share, I’d love to here for you (preferably through the comments so they’re shared, but private mail is also fine). In particular, I know there are a number of competing offerings to the ones mentioned in this post, and it would be good to know if they are worth evaluating. Thanks!

Nerds and managing them

If you consider yourself a nerd (or even if you’re not sure) then you and your significant other will want to study this:

The Nerd Handbook

Funny stuff because it hits so close to home. It’s a great read for both of you.

In addition to a lot of other interesting and humorous content on his site Michael Lopp (Rands) also wrote a book. The introductory web site Managing Humans is very clever.

Personal Health Record Challenges

The Journal of the American Medical Informatics Association has an article entitled The Early Experiences with Personal Health Records [Volume 15, Issue 1, January-February 2008, Pages 1-7] (found via Constructive Medicine 2.0).

I’ve discussed PHR a number of times in the past. This article details three PHR implementations and discusses past and future challenges. Many of these are access policy issues — privacy, security, data stewardship, and personal control. There are also many technical challenges. For example:

Thus, we will need to modify our existing PHR systems to support a service oriented architecture that permits multiple applications to retrieve our institutional data with patient control and consent. Providing such an architecture will require the nation to create and adopt national standards for clinical data content transmission, terminology and security to ensure interoperability.

I’ve also previously discussed interoperability in some detail. A SOA is a great idea, but with so many standards and proprietary implementations out there, it seems like the only way a national standard will ever be adopted is if the federal government steps in. This would require not only the definition of what the standards are, but what types of PHR/EMR systems are affected, along with a time-line for mandatory implementation.

All of that seems like a tall order. The technical aspects alone would be tough, but getting it done would also require a political process that would likely drag on for years. You really have to wonder if a national standard for interoperability is even possible?

Their conclusion regarding the importance of the P in PHR is a good one:

By placing the patient at the center of healthcare data exchange and empowering the patient to become the steward of their own data, protecting patient confidentiality becomes the personal responsibility of every participating patient.


On a semi-related note (i.e. isn’t worth a separate post, so I’ll park it here), I finally saw Michael Moore’s movie SiCKO the other day. It achieved a certain level of shock value regarding how people in the US are treated by insurance companies and HMOs, but it was a disappointment overall. It made no effort to further the understanding of why the health care system in this country is so messed up in the first place or to try to suggest ways to improve it. Instead it just showed the US problems and quickly turned to how great the UK, France, and Cuba socialized systems are (gosh, you mean you don’t have to pay any money at all!). Oh well, that’s Hollywood for you.

Stereotyping Programmers

Let’s start with a definition of Stereotype:

Stereotypes are generalizations about groups and their individual members, based primarily on membership in that group. They may be positive or negative, they may be accurate or inaccurate regarding average characteristics of a group, and may be used to justify certain discriminatory behaviors. Some people consider all stereotypes to be negative because they are unjust to individuals who vary from group characteristics.

Over the last week Jeff Atwood had a couple of posts on this subject: The Two Types of Programmers and Mort, Elvis, Einstein, and You.

If you dig into some of the links from these posts you’ll find that the Microsoft persona classifications have been the source of heated debate for a long time. There is no fine line here, in this context personas and stereotyping are the same thing.

The first time I heard the terms ‘Mort’ and ‘Elvis’ was when I read ALT.NET Recap: Front and center, let’s talk constructively about Mort. As you can tell from my comment to that post, I was greatly offended. I probably over-reacted. I just reread the post though, and I still feel the same way. Here’s an example of why:

Back to the question about whether or not Mort can get the stuff we’re talking about like separation of concerns and TDD. The typical Mort has managed to acquire a working knowledge of…

And the “Mort related quotes” didn’t help either.

Even though Jeremy’s intent was to explore how to improve the ALT.NET community, the use of stereotypes in this manner seriously distracts from that purpose. As I commented, if I came away feeling that way, I’m sure that others will too.

I don’t mean to single out Jeremy in this regard (even though I did) — his blog is consistently high quality, and inoffensive. The use of Mort-Elvis-Einstein is ubiquitous in the Microsoft blogosphere.

On the other hand, when I read the posts by Jeff and others that debate this issue I take no offense at all. I can even thoughtfully try to place myself into the different personas like many of the commenter’s did. This just shows how important context and intent are. As Jeff found out, this is a touchy issue — nobody likes to be pigeonholed.

Grouping based on stereotypes is inherently non-inclusive (there’s always someone not in a group, or in the wrong group). Even after you’ve figured out how to reach the unreachable, make sure that your message is made in an inclusive way.

UPDATE: (5-Dec-07)

This is sort of related: Call to Action : People Are Not Resources (via D’Arcy). Related in that calling people resources is also stereotyping, at least by the strictest definition. The more common form of stereotyping in exclusive, whereas being a pork-belly is all-inclusive. For some reason, I’m not as offended by being considered a resource as I am being called a Mort. But that’s just me.

What I don’t get is that if calling individual humans “resources” is bad, how come “Human Resources”, as a department name, is fine? If you want to get rid of labels, you really need to start at the top. How about “Human Assets” or the “Recruitment, Retainment, and Severance” department?

UPDATE: (12-Dec-07)

Jay Kimble has another take on this issue in his Is it 80% and 20% or is 20% too high… post.

…it seems to me that there are 2 kinds of people.

Those that think hard on an issue and those that don’t.

I would further generalize and say that laziness is one of the root causes of stereotyping. Stereotyping is the easy way out (“buzz words”) and is done by people that don’t want to take the time to understand another persons point-of-view or the complexity of an issue.

Subscribe

Categories

Twitter Updates