uld probably
double. Nearly all so-called imperfections are simply own goals and
self-injury, and I for one don't see that as an acceptable state of affairs.
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101106/7ec012eb/attachment.html>
eing their own set does not solve the problem. If
> any set meets my needs, I don't care what else is in the package.
>
>
> W. Ed Hammond, Ph.D.
> Director, Duke Center for Health Informatics
*
*
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101106/db2056a9/attachment.html>
Interesting comments. It is interesting that the ISO standard was approved
by HL7, CEN and ISO.
As to why we fix the problems of ISO 21090 on HL7, someone else will have
to address. As far as I know, HL7 actually does not even vote on ISO
standards. I must admit that I hoped at times the differe
to be considered...
- thomas *
*
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101106/7ad74c45/attachment.html>
I agree with Dqavid's points.
The world, unfortunately, is not perfect. Understanding how the ISO data
types standard came into being might be useful in understanding why it is
as it is. After more than 5 years in trying to get a g;obal standard for
data type, a group, lead by Graham Grieve, was
Implementing the Guidelines' section)
I would be interested in hearing of other experiences.
- thomas beale
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101106/e650aa4f/attachment.html>
6 matches
Mail list logo
