Hi,
If I understand correctly the things you mention, that is ADL 1.5 templates,
opt generation and documentation of these do not yet exist,
Is there a timeplan for when they will be finished?
Regards
Olof Torgersson
24 sep 2010 kl. 12.56 skrev Thomas Beale:
What needs to be considered is,
technical discussions
Subject: RE: openEHR and iPhone/iPad anyone?
No offence but I prefer not to top-post. Specially considering this
thread is moving a bit OT.
Please comment below.
ons 2010-10-06 klockan 11:24 +0200 skrev Mikael Nystr?m:
Hello,
It is correct that we in Link?ping currently
Hi,
That sounds very interesting. I guess the same backend/server-solution could be
used for making a native user interface instead?
Regards
Olof
24 sep 2010 kl. 12.49 skrev Daniel Karlsson:
Dear Everyone,
we here in Link?ping are now running a student project were the EHR is to be
viewed
What needs to be considered is, for each particular app, what data are
being captured and displayed? Usually it is not 'everything' - it will
be a very narrow data set in each case. For each such data set, one or
more openEHR ADL 1.5 templates could be created and converted to XSD
and/or
Hello everyone
Further to Thomas' comment about generating the XSD from a template and
through this, suitable data structures in any language and in relation
to Olof's question, i think that if the focus is the GUI and the
presentation of data and information, then the application can simply
Hi, and thanks to everyone that has replied.
I agree that the best way would be to create a GUI on the iPhone/iPad and let
the actual data be managed
on a server somewhere, thus one should not need to do so much core work in
Objective C.
Personally I would like to create a native GUI and not
6 matches
Mail list logo