openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120222/ed849bf9/attachment.html>
> >
>>> > ___
>>> > openEHR-technical mailing list
>>> > openEHR-technical at openehr.org
>>> > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>>>
>>>
>>>
r description of ORM seems to me to mean
something else. If I'm wrong, I certainly apologize.
Thanks,
Randy Neall
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120222/0cb98ad8/attachment.html>
ong thought that OpenEHR was intended to operate in precisely
> the way I have described, as a basis for expressing complex information
> with simple schema and source code, neither of which embody, in hard-wired
> form, particular medical information structures. Your description of ORM
&g
How can anyone say that HL7 is open in any fashion? You are not free
to distribute it outside of your organization except in small parts so
that the specifications cannot reproduced.
See the paragraph immediately preceding the one previously quoted here:
"HL7 CORPORATE/ORGANIZATIONAL MEMBERS are
ist
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
>
> ___ openEHR-technical mailing
> list openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
>
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20120222/b5e5e65d/attachment.html>
6 matches
Mail list logo