At 04:13 PM 5/8/00 -0400, you wrote:
>Thank you for a comprehensive reply! One quick question.
>"standardization of correlation manager interfaces" and "information
>required for Healthcare transactions" are not semantically that
>different, particularly when one adds in the additional wording having
>to do with "all operating systems", "all platforms", etc. How would you
>differentiate between HL7 messaging and CorbaMed interfacing? Are they,
>in reality, two different ways of doing the same thing, though one uses
>common objects and the other uses messages?
CORBAmed is the functional or computational specification. HL7 is the data
representation.
These are different things and one needs the other. Correlation Manager
has a very specific
meaning with respect to PIDS. CORBA already takes care of the all
operating systems, all
platforms, and all languages, so this has nothing to do with the rest.
CORBA provides a robust underlying "messaging" interface. HL7 describes
the character of a message, but really by specifying the data to be sent in
the message. CORBAmed just takes the data to be sent in an HL7 message
and makes it accessible through some functional interfaces (such as
find_candidates, get_profile, etc.).
This questions seems to keep recurring so I guess I've not yet done a good
enough job describing what
CORBA is. There are a ton of books at the local bookstore that describe
all of this much better than I can, so it would be really nice if people
could get one of these and read it. A good one is "Enterprise Application
Integration" by Ron Zehavi just published this year.
Dave
>John
>
>Mary Kratz wrote:
> >
> > Clearly, HL7 is not in the business to standardization of
> > correlation manager interfaces, but rather in the information required for
> > Healthcare transactions.
