Skip to main content

Virtual autopsies

One of the best talks at AHM2007 was on medical imaging, by Prof. Anders Ynnerman of Linkoping University in Sweden. Imaging researchers always have an advantage when giving talks because they can show much of their work in pictures; Anders took full advantage. The immediacy of visualisation in communicating information meant that some viewers found his medical pictures a little too gruesome.

The computer science aspect of his talk was about techniques for 3-D reconstruction of body images from the 2-D “slices” taken by medical CAT and MRI scanners. As these scanning devices increase in resolution, so the size of data to be processed increases. In order to process the data, ZZX is using intelligent compression techniques, based on whether a voxel represents bone, blood or tissue.

Aside from the technical content, I was very interested in the uses XXX has found for this work in addition to the usual pre-operative medical briefing. His team are now able to help the police by performing virtual autopsies. They can receive a corpse in a body bag, scan it, analyses the results on a computational cluster and give the resulting images to the pathologies a few hours later.

This technique is particular useful for spotting broken bones, for example, or detecting the path of a bullet through a body. This latter example was used to clear a police officer of misconduct charges after a fatal shooting – the team were able to show that the office had aimed at the target’s legs as per orders but the bullet had ricocheted upwards off a railing, killing the victim. So the death was an accident rather than murder.

At present, this system requires careful tuning by the expert team for each case, but it seem eminently suitable to develop further into production use.


Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.

This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…