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

Reigniting posterous again perhaps

I'm taking another look at Posterous again. I'm not really sure why as I haven't written a proper blog for a while but this seems an easy way to share between all my other tings...

NESTA - Next Gen.

via nesta.org.uk Following on from an article on the BBC about Raspberry Pi, this next gen report has some interesting findings. The scariest stat which I picked out from the BBC website was "out of the 28,767 teachers who were awarded Qualified Teacher Status... in 2010, only three qualified in computing or computing science as their primary qualification" Having worked as a computer science teacher for a year in a school that was a specialist in Computing I can concur that the uptake in Comp Sci was woeful. 2 Students for A2... The other teachers backgrounds in Computer Science was also fairly woeful (most knowing a bit about Office but still a paltry amount even about that). I couldn't speak for my counterpart that I was covering however. I suspect they were fairly up on things. All in all what kills me is that Computer science is not a secondary level subject. Areas are often covered, a little in IT, a little in DT subjects (if kids choose Systems and Contr

Motorola MC65

We have a new PDA in town now. As a replacement for the army of MC9000 and MC70s that are in the field and are being discontinued, we now are moving up to the Motorola MC65. I have had the new handheld for about a week now and have been impressed so far. It's a great improvement over the MC70. I have no idea how the numbering system of the Symbol / Motorola devices works. I assume there must be several ranges such as the 50s 60s and 70s.? Anyway the?PDA?has windows mobile 6.5.3, a better touch screen and is faster. Much faster. The skin that has been put on the OS has also applied to our software and I think it makes it look much cooler. We had several problems in adjusting our software so it would work with the new MC65. First was the change in resolution. The MC70 has a much lower resolution than the MC65s and as some of our screens were not using the auto scale settings in the form and some of the buttons on our forms were created at run time rather than design time, this posed