Re: [COAS-List] Blob related scenarios for COAS

[Tim Brinson <tim@protocol.com>]

Bob Glicksman wrote:
> 
> Fellow COAS Submitters,
> 
> Karen here raises a bunch of largely client side issues, but one theme
> comes up which is recurrent in lots of like messages that we get.  Most
> people, both inside and outside of CORBAmed, seem to think that COAS is
> going to solve all problems for all healthcare clinical data domains.  I
> think that we realize that this is not possible.  The aim is to define the
> COMMON services that create a FRAMEWORK under which deparmental data types
> can be added under separate RFPs (e.g. CIAS).  If you agree (I think we all
> agreed -- at one time, at least) then we need to re-educate the world about
> this, somehow.  Any ideas?

I think fewer people will be added to the list and most people already
know this.  Chuck, Larry and I were talking this AM and realized that we
could use more query scenerios that will help us craft the IDL (or
validate our solutions against).  Maybe query scenerios are one of the
issues we need to tackle in Denver.

In this case I know Karen already understands what you say.  She
attended the sessions at Orlando and has been on the mail list for some
time.  She asked me if they would still be useful even though COAS might
not address them explicitly.  I told her it could help us understand
what people might want to do with COAS in the future.  In particular I
know she is working strongly with XML but did not know the specific
scenerios (problems) being addressed.  

Karen's first scenerio does not distinguish between client and server
side for some of the functionality.  Where it does it helps to
understand the client responsibilities just as we need to understand the
server responsibilites.  Many people have suggested that things like
"current medication, allergies, chronic problems, lab tests" should be
considered for COAS.  Well at least lab tests fall under the current
definition and the rest could be expanded on in the future.  Karen is
the first person that has written it down and sent to us.  I think this
scenerio is important to know that COAS needs to be able to work with
these things even if we do not explicitly address them now (in this
submission).

The second scenerio seems to be covered by the work being done on the
Report Management RFP and the scenerios that Tad submitted.


Cheers,

Tim
begin:          vcard
fn:             Tim Brinson
n:              Brinson;Tim
org:            Protocol Systems, Inc.
adr:            8500 SW Creekside Place;;;Beaverton;Oregon;97008-7107;USA
email;internet: tim@protocol.com
title:          Systems Software Lead
tel;work:       503 526 4392
tel;fax:        503 526 4200
note:           <img src=http://aco.protocol.com/pids/tbrinson.jpg>
x-mozilla-cpt:  ;0
x-mozilla-html: TRUE
version:        2.1
end:            vcard