If we use “issues” as the top level item in the EHR, instead of the “encounter”, it comes naturally to attach confidentiality attributes to the issue instead of the department, doctor, or encounter. That’s a huge improvement. Let’s take an example to show why.
As things are in current systems, confidentiality walls or borders are located [...]

In my last post I described the positioning of the SRR record and I also painted it as a form that can either be predetermined in the form of a clinical guideline record or a free form record to which the doctor can add steps, or a mixture of both. Since we don’t want to [...]

In my last post, I arrived at the conclusion that the main element in the electronic healthcare record should be a list of problems and each of those problems should be an SRR, that is a document that is updated with  the most recent data pertaining to this problem, not a document that gets replaced [...]

In my previous post, I described the two kinds of data that I think I see in most, if not all, applications. The two kinds are the “state reflecting record” (SRR) and the “transformation additive series” (TAS). Cumbersome names, I admit, but if you have a better idea, let’s hear it.
A medical record, be it [...]

In my neverending quest to straighten out the electronic healthcare record, I have to introduce a view on data that is essential if I’ll be able to explain what’s wrong with the current model and how it should be fixed. As always when we’re in a mess with the design of systems, we climb the [...]

As I already bragged about, I got me one of those delicious little OSX Mini Snow Leopard Server boxes. So sweet you could kiss it. I just got everything together to make it run a subversion server through Apache, too, and as a way to document that process, I could just as well make a [...]

A friend of mine just told me about what an MS evangelist said at a symposium on multicore (paraphrased), after getting the question:
“Did MS consider that cache awareness for programmers in multicore development?”
…and he answered:
“The average developer is not capable of handling that kind of level of detail. … Most developers are that ignorant. Welcome [...]

Over the last week or so, I’ve spent a lot of time with the WDC 2009 sessions, and Dashcode, at least in its upcoming 3.0 version, seems to be amazingly capable. The results are almost indistinguishable from SDK apps (for want of a better label). And, they don’t go through the app store. And, they [...]

This morning I started developing for the iPhone (it arrived two days ago, what took me so long?). After watching a load of presentations from WWDC 2009 (you have to pay for that, but boy is it worth it), I got really curious about Dashcode. This environment lets you develop web applications and it looked [...]

So I’ve used a Mac for a while and I’m just starting on iPhone development and a blinding flash of the almost-obvious strikes me. This is not the Blackberry killer or the Palm killer, it’s the long-fuse Microsoft killer.
Remember the monkey dance? Ballmer yelling “Developers, developers, developers!”, while jumping around like a neurally defective and [...]