[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ohf-dev] CTS Client infrastructure

hi Dan

well, I can't get the LSI demo to run - need a user name and password which aren't provided that I can find. But
casual inspection suggests that the LSI is not enough.


it seems to me that you need not only to query for a single
code system, but for at least pairs, and more than code systems,
for valuesets as well (at least)

Perhaps this is something that should be part of CTS II?

irrespective, what about the plug-in ideas?

Grahame


Dan Armbrust wrote:
Grahame Grieve wrote:
Ok, we have overcome the administrative hurdles to getting
CTS into the CVS - I think.
Now we need to consider how much and how to integrate CTS
with Eclipse. There's 2 parts to this, server side and client
side. For now, let's concentrate on the client side.
So, CTS client infrastructure. Though really, in the long term,
it's not *client* infrastructure it's *consumer* infrastructure.

As a developer, and CTS consumer, I think I know what I want. I
imagine the CTS providers are plug-ins, using a generic CTS
interface. Multiple different CTS plug-ins provide different CTS services, and the user/administrator/whatever decides which CTS they want to use and how to configure it. I simply ask
if a CTS is available, and create it, and then use it. As an alternative, I know which CTS I want and how to configure it, so
I ask for that CTS with those parameters to be created.
This requires a double plug-in structure - a host CTS manager which provides CTS management - registration, arbitration, creation, configuration, and a CTS provider plug-in which registers with the CTS manager.


I suspect it makes sense for there to be more than CTS active,
but if there was, I'm not sure how I decide which one to use?
Maybe there's some sort of meta-query interface where you ask
the manager for a list of active CTS's that recognise a given
(domain/value set/something)?

What do you think? is any of this making sense?

Grahame


------------------------------------------------------------------------

_______________________________________________
ohf-dev mailing list
ohf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ohf-dev


We have rough / beta service that does some of what you are looking for as a meta-query interface - while its probably to limited and customized to be useful in the more general case - you may find it useful to look at...

http://informatics.mayo.edu/LexGrid/index.php?page=lsiw

We refer to it as the LexGrid Service Index (lsi)

There is also a SOAP interface to this which has a simple query API - the SOAP interface is used by our CTS Demo client for finding and connecting to a CTS Server (or data source)

http://informatics.mayo.edu/LexGrid/index.php?page=ctsdemo

(take a look at the LexGrid Services Index tab on the connection dialog)

It only distinguishes down to the terminology level now, however.

Dan


--
Grahame Grieve
CTO, Jiva Medical Software Integration Tools
CTO, Kestral Computing Healthcare Applications