Issue 2981: how to use HL7 data types                                                                                                                                                                               (coas-ftf)
Source: 2AB (Mr. Tim Brinson, tbrinson@2ab.com)
Nature: Uncategorized Issue
Severity: 
Summary: This is an issue for both the PIDS2 RTF and the COAS FTF.

The PIDS and COAS specifications both indicate how to use HL7 data types
with those services but neither have specified a way for an
implementation to claim conformance to using them.  A conformance point
should be added to both specifications.  This will enhance the
expectations of interoperability for using those services since a user
and of the servcie and the servcie have to be compatible on the
information type specification as well as the service specification.

Resolution: resolved in COAS FTF
Revised Text: 
Actions taken:
November 8, 1999: received issue
November 7, 2000: closed issue
Discussion: 

End of Annotations:=====
Reply-To: "Jon Farmer" <jfarmer@ic.net>
From: "Jon Farmer" <jfarmer@ic.net>
To: <coas-ftf@omg.org>
Subject: alternative verbs for Federated access and put_obsevations
Date: Mon, 27 Sep 1999 15:58:52 -0400
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Content-Type: text/plain;
	charset="iso-8859-1"
X-UIDL: 6!,!!#0G!!/]B!!F;Ge9

here are our desired positions in dimensions of connotation:
- multiple instance vs. one instance vs. one atribute of an instance -
we
want to connote multiple instances
- does a the requestor get any info back - no.

======== options, their thesaurus equivalents, and assessment for
suitability ===================
place - connotes location to explicitly

put or put-in (insert, place, store, publish) - reasonable but can we
do
better?

write (communicate, mark, record) - implies recording on a persistence
medium - too underlying technology-connotative

load - has precedent in pids; implies multiple, and already understood
in IS
as "batch" and one-way-transfer with no significant return info.  I
also lke
the "ammo" connotation.  We are "charging" a sevice with useful info
or
potential energy - ready to be put to useful work.

add - in o-o circles, this connotes adding an (singleton) entry to a
dictionary or to a container.

set - connotes setting a property or a primitive value.  no batch
semantics
permitted.

======================= my recommendation

interface: ObservationLoader             (a utility with a manifest
puprose)

operation: load_observations

Jon