RE: [Draft] expected FAQ on my draft

["V. Juggy Jagannathan" <juggy@careflow.com>]

Carol et. al:

looks like you have been busy :-). i have not assimilated all of the info
flying around - but
would like folks to show me how this will work with the evolving COAS specs.
Here is one
of the most basic access that COAS has:

interface PatientAccess : AccessComponent {

		BaseItem get_clinical_item (
			in ClinicalData::OID oid
		) raises (
			InvalidOid,
			UnknownOid
		);

......

}

where OID is observation ID of somekind - could be a blob or anything for
that matter.
Would "intent" be "get_clinical_item" ? How will the policy be specified?
Enforced?
Will the interceptor model - that I am hoping will work - will it work here?


The above is the simplest form of access and the
ONLY one which does not return a set of observations in ALL of the current
COAS specifications.

At the opposite end of the spectrum, an example access is:

		BaseItemSeq get_clinical_item_by_policy (
			in PersonIdService::PersonIdSeq who,
			in TerminologyServices::QualifiedCodeSeq what,
			in TimeDefs::TimeSpan when,
			in ContextSeq the_context,
			in QueryPolicySeq policy,
			in unsigned long max_sequence,
			out BaseItemIterator the_rest
		) raises (
			PersonIdService::InvalidIds,
			PersonIdService::DuplicateIds,
			InvalidCodes,
			DuplicateCodes,
			InvalidTimeSpan,
			InvalidContext,
			DuplicateContextName,
			InvalidPolicy,
			DuplicatePolicyName
		);

in the above, the observations being accessed are keyed in by who, what,
when, additional
contextual information (name-value pairs), filtering policies, how many
observations are they
prepared to handle etc.

Now what is "intent" here? How would one enforce access policy decisions?

clueless in morgantown,

- regards
- juggy

----------------
Broadcast message to hrac-rfp from "V. Juggy Jagannathan" <juggy@careflow.com>.
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.