Gerard Freriks wrote:
> Thomas,
>
> I agree with you that in the case CEN (13606) adopts the OpenEHR data
> types they know that it is proven technology.
> Just now, when any moment CEN/tc251 EN13606 will get published, we
> dearly need proven data types to implement it.
>
> In the case that CEN
hey Sam
I'll bite ;-)
> but the openEHR data types are ready for
> archetypes and the cluster element (leaf node) architecture.
it you want, we can go round and round on semantic issues. Always
a pleasure ;-). But is there anything specific that makes
you think that it would be inappropriate o
a types?
>
> - thomas beale
>
>
>
> ___
> openEHR-technical mailing list
> openEHR-technical at openehr.org
> http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
-- next part --
An HTML attach
__
>openEHR-clinical mailing list
>openEHR-clinical at openehr.org
>http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
>
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.ope
Grahame Grieve wrote:
> hey Sam
>
> I'll bite ;-)
>
> > but the openEHR data types are ready for
> > archetypes and the cluster element (leaf node) architecture.
>
> it you want, we can go round and round on semantic issues. Always
> a pleasure ;-). But is there anything specific that makes
> you
ext part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20070222/d3ef26c7/attachment.html>
-- next part --
___
openEHR-clinical mailing list
openEHR-clinical at openehr.org
http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-clinical
See the Release 1.0.1 specification page, look for Status = FINAL DRAFT.
The remainder of the specifications will be appearing in final draft
over the next few weeks before we announce the release.
- thomas beale
___
openEHR-technical mailing list
o
7 matches
Mail list logo