Hi Ed,
I didn't say it was bad (it is probably very good) - I said it was
'fixed'. Like CCR - which as far as I understand is very good domain
modelling - but also pretty fixed. The debate here is about 'how' not
'what'. If I was working on the vMR in HL7 right now, the first thing I
would do would be to copy exactly the content you have modelled in the
diagram I referred to - in to archetypes and templates. Then I would get
for free:
* the ability to change it with no changes to any reference model
(information remains valid)
* the ability to add completely new things, also without requiring
any changes in the underlying information model
* the ability to query everything in a generic fashion using queries
based directly on the domain models
This argument is the same as with all the *MIMs in HL7 - as a technology
I don't think they work, but I don't question their content (in most
cases I am not competent to do that). I would really love the
opportunity to show you how nice this model could be if modelled in
archetypes in an openEHR system. You would get just what you want with
much greater flexibility. Please don't think I would seriously question
Duke's clinical work. I just think you are working with the wrong IT;-)
regards
- thomas
On 26/06/2010 19:28, William E Hammond wrote:
> Hi Thomas,
>
> I am now back at Duke in a full time capacity. The work within HL7 is
> being lead by Ken Kawamoto from Duke, a colleague of mine. Duke has one fo
> the best clinical research enterprises in the world - the Duke Clinical
> Research Institute and the new Duke Translational Medical Institute, where
> the Duke Center for Health Informatics is based. We have asignificant
> weffort committed to defining detailed clinical content. I'd say let's
> postpone the decision (as ever) for a couple of years and see if we are as
> bad as you think.
>
> Actullay, we have an effort similar to Evelyn's and look forward to working
> with her.
>
>
*
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20100626/2a8929f5/attachment.html>
