Skip to main content

RFID tracking for mapping people moving around a hospital

Last week I was talking to an very interesting individual regarding mapping how people move around in hospitals for the purpose of understanding how infections spread through a?hospital. Although it was just a general conversation, if I remember correctly they wanted to map out the movement into a diagram of nodes and edges. For example the wards could be nodes and the people could be the edges between the wards.?

I haven't really thought on the theory of it very much yet but I think it would be a brilliant piece of research to flesh out (I hope they are able to carry on with it).?

It just got me thinking about how you would effectively track patients movement through a hospital. Ideally the movement would have to be monitored anonymously so people didn't feel they were being tracked. I wonder if one technique would be to give all people coming into the hospital an RFID tag (perhaps a card) that they can carry around with them. At each entrance to a room / ward / area the RFID scanners (similar to those used at the entrance to shops but hopefully less intrusive) would pick up the tags and the individual ids and track them.?

With the ids and the rooms they went to you can build up a list of edges to the nodes and see which areas are hubs for movement. Using that you could map it against the data of infection outbreaks and try and look for patterns.?

Obviously this is a very simplistic view of the problem. For a start the cost could be astronomical. Would people need to give the tags back? How could you control that? There are plenty of questions but it's worth thinking about.?

Comments

Dom Finn said…
Yes looking into it, this sort of technology would be excellent. The actual data is anonymous which is good. As long as that can be proved without a doubt and the cost was right this would be an excellent idea. http://www.pathintelligence.com/en/products/footpath/footpath-technology

Popular posts from this blog

Creating star ratings in HTML and Javascript

I'd searched around a little for some shortcuts to help in doing this but I couldn't find anything satisfactory that included the ability to pull the rating off again for saving. I'd ended up coming up with this rather cheeky solution. Hopefully it helps you too! This is my first post in a while (I stopped blogging properly about 8 years ago!) It's strange coming back to it. Blogger feels very crusty and old by todays standards too.

Make your objects immutable by default

More about the Good Dojo In my post last week , I discussed creating objects that are instantiated safely. Please go back and read if you are interested. At the end of the post, I mentioned that I'd also written the class so it was immutable when instantiated. This is important!!! I feel like a broken record in repeating this but I am sure at the time of writing your code, you aren't modifying your object all over the place and so are safe in the belief that protecting against mutability is overkill. Please remember though, your code could be around for a hell of a long time. You aren't writing your code for now... you are writing for the next fool that comes along (including you) . Nothing is more upsetting that coming back to fix a bug on some wonderfully crafted code to say "Who has butchered my code?!", but often you were involved at the start of the process. You made the code easy to modify, allowing objects to be used / reused / modified without thi

An instantiated object should be "ok"

I've been QA'ing quite a bit of work recently and one common theme I've noticed across both Java and C# projects I have been looking at is that we occasionally open ourselves up unessacarily to Exceptions by the way objects are being created. My general rule of thumb (which I have seen mentioned in a Pluralsight video recently but also always re-iterate in various Robust Software talks I have done) is that you shouldn't be able to create an object and then call a method or access a property that then throws an exception. At worst, it should return null (I'm not going to moan about that now). I've created an example below. We have two Dojos, one is good and one is bad. The bad dojo looks very familiar though. It's a little class written in the style that seems often encouraged. In fact, many classes start life as something like this. Then as years go on, you and other colleagues add more features to the class and it's instantiation becomes a second