enehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060919/2204c91f/attachment.html>
Grahame,
One of the theoretical difficulties of the debate that you are contributing
so eloquently to is to separate methods proper to computing from methods
defined by domain specificity.
Object-oriented programming, modular design, abstract data types, etc. are
fundamental principles whose ex
ok, we have real convergence here.
OpenEHR works exactly like HL7 - define a reference model
with all the needed semantics, and then refine things away
in constraint models (and use the refinements as a basis for
composition). So the principle is the same.
We can generate [class models|schemas|wi
>>> this is true. What is there now:
>>> * CEN HISA
>>> * emerging openEHR service models for EHR, demographics, terminology access
>>> and
>>> archetype access
>>> * state-based process management for Instructions, i.e. medications,
>>> orders,
>>> procedures.
>>> * high-level HL7 HSSP specif
- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20060919/6fb3e1b3/attachment.html>
5 matches
Mail list logo
