Hi All and thanks Ed and Thomas, This sort of discussion has been going on for some time. Describing what happened with ENV13606 (pre-standard) trials which did not have archetypes and the problems with HL7 this and that is helpful to a point - we need reality checks. This standards domain is difficult and highly complex. HL7 CDA provides for a document which has more than a Word file but does struggle with structured content. openEHR struggles to get the engineering solutions, which are still complex and debated, into production.
What I do believe is that openEHR has the best way to model content at the moment. It is not perfect, particularly as the tools are designed for clinicians. Further, we have a Web 2.0 enabled process to create content and I think we all know that we cannot proceed on content specification using traditional meeting or government sponsored approaches. We also have a growing set of tools, some open source, some not, and an agreement with IHTSDO to work together on this front. Deciding to model information as it is to be used WITHIN systems is new and not without dissent. This approach is a threat to some in the terminology industry (because it reduces the requirements substantially) and to large system providers who, on the whole, dictate the environment at the moment. It is not realistic to expect to get everyone on board. When HL7 move to version 4 it will probably be a lot more like openEHR than version 3, but that remains to be seen. I would love version 4 and openEHR to be the same or at least a united front. I am not sure if that is possible within the standards funding structures that exist at the moment. Let's think about it anyway. Cheers, Sam > -----Original Message----- > From: openehr-technical-bounces at chime.ucl.ac.uk [mailto:openehr- > technical-bounces at chime.ucl.ac.uk] On Behalf Of William E Hammond > Sent: Tuesday, 2 February 2010 3:49 AM > To: For openEHR technical discussions > Cc: openehr-technical at openehr.org > Subject: Re: Interoperability with HL7 > > I agree that ISO is not the place to develop standards, but it is a > body > recognized by all the world. The concept of the JIC appears to be > functional - not smooth and not easy, but progress is being made. It > is > not so much that one organization is better than another or that one > standard is better, but there are good and bad with some of what we do. > I > think the good outweighs the bad, and we can fix some problems. > > Why don't we go off line, and try to come up with a plan, then bring > back > to the larger community. > > Ed > > W. Ed Hammond, Ph.D. > Director, Duke Center for Health Informatics > > > > Thomas Beale > <thomas.beale at oce > aninformatics.com > To > > openehr-technical at openehr.org > Sent by: > cc > openehr-technical > -bounces at chime.uc > Subject > l.ac.uk Re: Interoperability with HL7 > > > 02/01/2010 01:01 > PM > > > Please respond to > For openEHR > technical > discussions > <openehr-technica > l at chime.ucl.ac.uk > > > > > > > > > On 01/02/2010 17:07, William E Hammond wrote: > I like your reply. I am willing to commit to putting energy > behind > merging > al standards groups, probably under ISO. > > > > Not wanting to be more of a trouble-maker than usual, but I would have > to > say - if we could work this out together, let's do it, but I don' t > think > ISO is the place to do it, only to a) have wide-ranging background > discussions and b) to rubber stamp the result. ISO might be the > appropriate > background community, but it can't come up with the framework or > standards > - it is in fact quite bad at that. My more detailed opinions on this > are > here: http://wolandscat.net/2009/09/17/the-crisis-in-e-health- > standards/ > > I know (once again) that what is stated there won't be popular with > some > people, but the feedback has been very interesting indeed. > > - thomas > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
