oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

On Thu, 2009-03-26 at 08:50 -0300, Sergio Miranda Freire wrote:

> Although a standardized API for dealing with this full range of services may
> be not possible, there are some things in common with terminologies that
> could be the subject of a standardization: how to get subsets of terms, get
> a code, etc. ISO-HL7 are working in one such standard, also there is a
> Terminology Subset Syntax specification in the openEHR roadmap. 
> 
> All these things may not be of immediate concern for the present OSHIP
> implementation and may look like a red herring, but I prefer to be open to
> other possibilities.

Hi Sergio,

Thanks for your expanded thoughts on this.  

We are remaining open to other "future" APIs by doing two things:
a) what is best for OSHIP applications right now
b) including a Mirth interface so that in that "future" channels can be
created that will do those transformations.  Not just with Terminology
servers but with any data format.  An AQL parser to Zope Catalog
indexes?  I/O with all HL7 messages, etc.  I have even discussed with
Jon Teichrow of WebReach, Inc. regarding creating a channel for TISS so
that we can archetype it inbound to OSHIP.  Very doable he says after
looking at the TISS package.  

Cheers,
Tim




-- 
Timothy Cook, MSc
Health Informatics Research & Development Services
LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == timothy.cook 
**************************************************************
*You may get my Public GPG key from  popular keyservers or   *
*from this link http://timothywayne.cook.googlepages.com/home*
**************************************************************

Attachment: signature.asc
Description: This is a digitally signed message part