1755
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080625/f86e61db/attachment.html
Georg Duftschmid wrote:
So I have the impression that an EHR reference model helps to achieve
some kind of advanced functional interoperability, but I would not
say that it is REQUIRED to achieve functional interoperability
(refering to the PDF-exchange as a counter-example).
*
no
-- next part --
An HTML attachment was scrubbed...
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080625/ea545a7a/attachment.html
Hi all,
I've just started browsing and investigating two existing archetype
editors,
hardly could I find a step by step tutorial for creating Archetypes
(and then Templates)
Is there any recommended resource?
Regards
paria
PhD Student
IDC | Interaction Design Collegium
Department of
: This is a digitally signed message part
URL:
http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20080625/8172ae38/attachment.asc
I agree with Thomas and Graham that the initial argument really hinges
on whether the most minimum communication of an email with attached
clinical pdf, by being human interpretible meets the definition of
'functional interoperabilliy.
I would say no, simply because it then makes no distinction
Hi Paria,
The Ocean archetype editor help files are not too bad as a 'technical'
guide and these other pages might be helpful
openEHR Entry Types FAQs
http://www.openehr.org/shared-resources/faqs/entrytypes.html
What reference model class to use when?
7 matches
Mail list logo