Trying to understand the openEHR Information Model

2013-04-16 Thread Thomas Beale
us numerous technical people, debates, conferences etc have led to the specifications <http://www.openehr.org/programs/specification/releases/currentbaseline> you see today. Have a look at the revision histories, particularly on the EHR IM and Data types - you'll see a lot of names. - thomas -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130416/c6b27f52/attachment-0001.html>

Trying to understand the openEHR Information Model

2013-04-16 Thread Randolph Neall
developing these > requirements and the understanding they have given to the domain have > greatly affected the quality of the development. This plus numerous > technical people, debates, conferences etc have led to the > specifications<http://www.openehr.org/programs/specification/releases/currentbaseline>you > see today. Have a look at the revision histories, particularly on the > EHR IM and Data types - you'll see a lot of names. > > - thomas > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130416/04ffeaeb/attachment.html>

Trying to understand the openEHR Information Model

2013-04-16 Thread Randolph Neall
5 nodes of data > in some very specific tree structure - the database and query service just > keep working. Referencing, larger logical structures like 'episodes', and > the update semantics don't come for free, and require careful design. So I > think we have bought into a new area of difficulty, as the price of quite a > significant gain over 'single level' systems where the class model or ER > model encode all the information semantics. > > We need something to keep us off the streets... > > - thomas > > > > ___ > openEHR-technical mailing list > openEHR-technical at lists.openehr.org > > http://lists.openehr.org/mailman/listinfo/openehr-technical_lists.openehr.org > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130416/e14f1c0b/attachment.html>

Trying to understand the openEHR Information Model

2013-04-16 Thread Erik Sundvall
> WebSockets for accessing shared contribution builds is anticipated. When > explored properly, specific OT application recommendations should be added > to the architecture. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130416/08fb3a55/attachment.html>

Mimetype ADL

2013-04-16 Thread Bert Verhees
Hi, Is there a mimetype defined for ADL-files? And if not, what is advised to use? Thanks Bert

Trying to understand the openEHR Information Model

2013-04-16 Thread Grahame Grieve
well, yes, there'd be nothing lost, and everything would be in the database. But if the users can only see the last update, then prior stuff is lost anyway. If, on the other hand, users can see the older updates, then they'd simply have no idea what information was current. I think of that las

Trying to understand the openEHR Information Model

2013-04-16 Thread Grahame Grieve
lists.openehr.org> > -- - http://www.healthintersections.com.au / grahame at healthintersections.com.au/ +61 411 867 065 -- next part -- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/pipermail/openehr-technical_lists.openehr.org/attachments/20130416/a8f13ae9/attachment.html>

Trying to understand the openEHR Information Model

2013-04-16 Thread Thomas Beale
lt;http://www.oceaninformatics.com/>* Chair Architectural Review Board, /open/EHR Foundation <http://www.openehr.org/> Honorary Research Fellow, University College London <http://www.chime.ucl.ac.uk/> Chartered IT Professional Fellow, BCS, British Computer Society <http://w