Skip to main content

Cross-Enterprise Document Sharing

At HC2008 I was introduced to the XDS standard for Cross-Enterprise Document Sharing (not to be confused with several other uses of the XDS acronym). XDS is a profile of the ebXML standards for registries and other related standards to specify a system for sharing medical documents. The important point is that XDS is supported by several major vendors and has been deployed in clinical health systems in several countries. As far as I'm aware, it has not made any impact in the grid world.

The basic XDS standard can be extended to address particular use cases or to add functionality. One popular extension handles DICOM files (a format widely used in medical imaging). Another (XCA) supports federated registries, removing the single point of failure of the basic model.

I think it is worth investigating for other e-Science applications. It may be simpler to leverage this work than to reinvent it. Also, it might be possible to apply our work on e-infrastructure security to the federation scenarios in XCA, which does not have adequate security mechanisms of its own.

Comments

Ren� said…
I agree, IHE XDS is certainly something one should look at - with the caveat that it offers an infrastructure for the exchange of documents.

Not all of the data exchange requirements are covered by documents, some are better covered by messages. See this whitepaper about the distinction between the two - at least how this distincion is understood within the HL7 community.

The documents shared in the context of XDS mostly use HL7's Clinical Document Architecture (CDA) standard. That standard is also worth a look at..

-Rene

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…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

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…