Alvin Marcelo writes:
> Brian said:
>
> > In any event, there is a huge advantage to selecting a
> standard model
> > for everyone to work with. The way this model gets specified in UML,
> > however, must allow for additional data elements without requiring
> > changes to the interface. The PIDS spec shows one way to do this -- all
> > of the identifying data elements of HL7 are accessibible without
> > restricting an implementation to just those elements.
>
>
> You have to help me here then Brian.
>
> 1. Can we then include PIDS/CORBAmed as a model alongside HL7 3, GEHR, and
> CEN?
PIDS provides a computational view point on an information model such as
HL7 and CEN (for patient identifying information). It works well with
these other systems.
>
> 2. My point of view is severely limited because it seems I have decided to
> implement my project in SQL (forgive me). In any case, I would be
> interested in bridging the PIDS spec to my actual SQL tables.
> Can you share with us how that can be done?
>
Specifying the model in SQL mixes the computational model with the
information model which can lead to a "brittle" system. The value of
separating these viewpoints is described in the ISO Reference Model for
Open Distributed Processing (which can be found at
http://www.iso.ch/ittf).
I believe the understanding of this approach is critically important for
developing interoperable, extensible systems.
Dave
>
> Thanks a lot.
>
> Alvin
>
>
>
