TML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101208/10e1b4ce/attachment.html>
Hi Koray,
I agree with Thomas here, Koray, but I take your point about the
separation into a further layer represents added potential development
complexity. I think we should expect tools to handle this in the same
way that a complex development environment like Visual Studio handles
various laye
environment. You should not have to think about these separate layers
> during development.
exactly
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101208/71781480/attachment.html>
ttp://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101208/81e70a7e/attachment.html>
ing.
> *
> *
I would suggest that the GUI templates just reference paths found in the
openEHR template.
- thomas
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attac
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101208/679651d3/attachment.html>
Hi Pablo,
In both ADL1.4 and 1.5 every path is still an archetype-based path.
The proposed schema for an operational template is very similar to the
XML schema of an individual archetype but obviously includes multiple
aggregated archetypes and omits any nodes which are constrained out.
Templates
enEHR Clinical Knowledge Editor www.openehr.org/knowledge
> Honorary Senior Research Associate, CHIME, UCL
> BCS Primary Health Care SG Group www.phcsg.org
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101208/42cd0939/attachment.html>
8 matches
Mail list logo
