Skip to main content

Grids & e-Health

This week, I attended Healthcare Computing 2008 to get an update on the current state of e-health in the UK and to explore how grid technology can contribute. Health Informatics is a broad subject and it isn't possible to engage with the whole field, but I see three main areas of potential engagement.

The path is most followed by the academic community to date is that of linking together data used in clinical trials or in health research. This is a natural fit for the e-science community as it extends existing work on secure access to distributed research data. The medical world imposes more security constraints, which adds academic interest, but is otherwise familiar to the e-scientists. It is also of a scale that is manageable in research projects. Successful projects include Psygrid, which is now deployed across the NHS research centres in mental health and in bioinformatics. So this is the first area of engagement.

A natural question is whether this experience with research data grids is also applicable to clinical systems. Clinical practice is a much larger enterprise. Major initiatives exist to share data such as patient records and medical images. These are either provided by small-scale systems implemented by individual health trusts, or by specialist commercial solutions. These systems face the same problems as data grids - single sign-on, access control, metadata management, data vocabularies - but engagement with the grid world seems virtually non-existent. There is probably scope for mutual learning between the two communities, but the healthcare community is understandably focussed on providing solutions now. So I regard the chances of successful engagement here as slight.

A more likely area is the computing aspect of grids. Although this has also made little impression on the clinical community to date, there are successful R&D projects in the areas of data analysis and diagnosis support, including GIMI and Healthcare at Home. These use pattern matching technologies to detect suspicious lumps in medical images or to warn of possible problems in patient monitoring systems. These are rather specialised systems, which would make it easier to arrange pilot deployments to text their clinical effectiveness.

The third area of promise is the most straightforward. The NHS is one of the world's biggest organisations and runs a lot of IT systems. As a result, there are plenty of opportunities for deploying modern IT infrastructure techniques, with virtualisation as an easy quick win. The NHS has yet to consider the effect of CO2 emissions and electricity costs from its myriad systems and it will have to do so soon.

Taking this to a further stage, I believe that the NHS would benefit greatly from adopting service-oriented techniques. There is currently a developing interest in lean management techniques in NHS hospitals, with great opportunities for improving processes for patients and employees while saving money for hard-pressed hospital trusts. Such process optimisations can be delivered more easily if the IT layer is equally flexible. The business management should lead, but the IT infrastructure must be agile to follow the dance.

Comments

Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…