I scraped together the following from a number of sources and got it to work fine and without compiler warnings. Interesting links are, among others: http://cocoawithlove.com/2008/03/construct-nsinvocation-for-any-message.html http://macdevelopertips.com/objective-c/objective-c-categories.html But, I get ahead of myself. The idea here is to have one object forward method invocations to another. Typically, you have a class responding to method A, [...]

Now we’ve arrived at the last of the solutions in my list, namely “Opening the market for smaller entrepreneurs”. There are a number of reasons we have to do this, and I’ve touched on most of them before in other contexts. The advantages of having a large all-in-one vendor to deliver a single system doing [...]

Around 1996 I was part of the CEN TC251 crowd for a while, not as a member but as an observer. CEN is the European standards organization, and TC251 is “Technical Committee 251″, which is the committee that does all the medical IT standardization. The reason I was involved is that I was then working [...]

The quality of our IT systems for health-care is pretty darn poor, and I think most people agree on that. There have been calls for oversight and certification of applications to lessen the risk of failures and errors. In Europe there is a drive to have health-care IT solutions go through a CE process, which [...]

Forcing a large application into small independent parts that have to communicate with each other using minimal interfaces is always a good thing. Large monolithic applications go “fat and lazy” when there is no requirement to keep them split up. Also, the effort to expand and maintain the applications go through the roof. We know [...]

Ah, finally we arrive at solutions. The first in the series is the elephant in the room: issues. Why do I say “elephant in the room”? Because when a doctor examines and treats a patient, he thinks in “issues”, and the result of that thinking manifests itself in planning, tests, therapies, and follow-up. When he [...]

This post is part of a series detailing the problems of current electronic healthcare records. To orient yourself, you can start at the index page on “presentation” on the iota wiki. You will find this and other pages on that wiki as well. The wiki pages will be continuously updated. Since current electronic health care [...]

Electronic health care record systems are widely and frequently claimed to reduce injury and death due to prescription errors, since they are able to detect and warn for interactions between products. This claim is largely nonsense, because of the following: Interactions between products are not the only dangerous effects we have from bad prescriptions Interactions [...]

Prescriptions made in classic EHR systems have no context of “why” and “for what”. The only information about the reason for the prescription is an entirely optional field on the physical label informing the patient about the purpose of the medication. That is far from sufficient. The drawbacks due to the lack of a structured [...]

I’m at point 2 in the list of problems we need to solve. You can also find this text, possibly improved, on the iotaMed wiki. As new discoveries are made in medicine, we need to get these out to “the factory floor”, so they are applied in practice. If there’s a new more efficient diagnostic [...]