can solve one problem at a time, instead of
having a messy one-fits-all solution.
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110325/c8089def/attachment.html>
Maybe we could use as inspiration all the available XML to GUI efforts
that already exist. Mostly to avoid reinventing the wheel
2011/3/25 pablo pazos :
> Hi Koray,
>
> I think we are the core group, and if we can agree some basic notation of
> some basic GUI directives (there are some thoughts of
etting us all on the same page with
respect to lessons being learned.
- thomas beale*
*
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110325/3ae62633/attachment.html>
; concerns of our artifacts. If we have a solid base to our complete clinical
> > data structures like Archetypes, we can define other "upper layer" artifacts
> > to model rules, conditions, gui directives, etc.
> >
> > I like this approach because we can solve on
-- next part --
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20110325/af79ad43/attachment.html>
5 matches
Mail list logo