Re: [COAS-List] COAS - Access Contol

[Konstantin Beznosov <beznosov@baptisthealth.net>]

> Kent,
> Thanks I knew the RFP had been issued I was looking for submitters and
> where they were in regards to a submission (the web site doesn't have anyone
listed as submitters) Tom

Tom and other COAS submitters:

As I presented during the Orlando plenary session of CORBAmed on Thursday,
there are 6 official submitters to the RFP. As far as I know, there are two
submitting teams: HBOC and Data Access + supporters; and 2AB, BHSSF,
CareFlow|Net and IBM + supporters.

You can find what's going on in the second submitting team if you look at 
http://cadse.cs.fiu.edu/omg/hrac-rfp/

currently the our team is in the stage of defining design goals, terminology,
healthcare secure resource (a key concept in the RFP) space.

It would be an invaluable contribution from the COAS team and, hopefully, it
can help to the COAS team too, if the COAS team can come up with some
COAS-related scenarios on controlling access to the observation data accessed
via interfaces defined by your response.

Konstantin

> 
> >>> Kent Wreder <KENTW@BHSSF.ORG> 07/16 2:10 PM >>>
> Tom,
> 
> Here's the pointer to the CORBAmed RFP:
> http://www.omg.org/library/schedule/Healthcare_Resource_AC_RFP.htm 
> 
> Konstantin:
> Can you pls give Tom and the COAS group an update?
> 
> Kent.
> 
> 
> >>> "Tom Culpepper" <tcculpepper@wpmail.code3.com> 07/16/98
> 02:01pm >>>
> Kent,
> Please point me to HRAC so I can get educated.
> Tom
> 
> >>> Kent Wreder <KENTW@bhssf.org> 07/16 1:36 PM >>>
> I'd like to propose that the Access Control aspects of COAS tracks with
> HRAC.  I copied this email to the one submission team that I am aware of
> (hrac-rfp@cs.fiu.edu).
> 
> Kent.
> 
> [snip]--
> > Certianly COAS must take careful note of access controls.  The
> Information
> > may well have access rights attached to them which may prevent
> queriers from
> > returning the full information, as well as rights which may have been
> > imposed at the system, place or country level.
> 
> Yep.  We crossed this issue in the development of PIDS too.  The nice
> thing is that by specifying the interface in COAS as an object the true
> implementation is encapsulated.  The implementation can filter the
> contents before it returns it.
> [end snip] --
> 
> 
>