Hi William I didn't see anyone say that the hl7 models have been developed without clinical input. I am certain this isn't true.
I don't completely agree with you about the ease of accessibility for clinicians of UML models and MIF models - it's not our experience. Regards Hugh Sent from my iPhone On 09/11/2010, at 15:54, Williamtfgoossen at cs.com wrote: > They (the clinical models in HL7 v3 R-MIM format) are all part of extensive > clinician input and review, sorry clinicians do understand the modeling in > HL7 space, but indeed like any other modeling effort, need some education > first. > Statements that this HL7 clinical content modeling is done without clinicians > input is simply a lie. > Comments that clinicians are unable to read and understand and critique UML > and/or HL7 RIM based class models is not consistent with my 8 year + > experience with a dozen of national projects in the Netherlands. > > > > There are several papers out there explaining how clinicians where involved > and reviewing content and leading the input. > > Bridging the HL7 template - 13606 archetype gap with detailed clinical > models.Goossen WT, Goossen-Baremans A.Stud Health Technol Inform. 2010;160(Pt > 2):932-6.PMID: 20841821 [PubMed - in process]Related citations > > 2. > Sending electronic nursing discharge messages using the HL7 v3 Care Provision > standard.Goossen W.Stud Health Technol Inform. 2009;146:269-75.PMID: 19592847 > [PubMed - indexed for MEDLINE]Related citations > > 3. > Using detailed clinical models to bridge the gap between clinicians and > HIT.Goossen WT.Stud Health Technol Inform. 2008;141:3-10. > > Using SNOMED CT codes for coding information in electronic health records for > stroke patients.van der Kooij J, Goossen WT, Goossen-Baremans AT, de > Jong-Fintelman M, van Beek L.Stud Health Technol Inform. > 2006;124:815-23.PMID: 17108614 [PubMed - indexed for MEDLINE]Related citations > > 8. > Evaluation of documents that integrate knowledge, terminology and information > models.van der Kooij J, Goossen WT, Goossen-Baremans AT, Plaisier N.Stud > Health Technol Inform. 2006;122:519-22.PMID: 17102312 [PubMed - indexed for > MEDLINE]Related citations > > 9. > Intelligent semantic interoperability: Integrating knowledge, terminology and > information models to support stroke care.Goossen WT.Stud Health Technol > Inform. 2006;122:435-9. > > 18. > Development of a provisional domain model for the nursing process for use > within the Health Level 7 reference information model.Goossen WT, Ozbolt JG, > Coenen A, Park HA, Mead C, Ehnfors M, Marin HF.J Am Med Inform Assoc. 2004 > May-Jun;11(3):186-94. Epub 2004 Feb 5.PMID: 14764610 [PubMed - indexed for > MEDLINE]Free PMC ArticleFree textRelated citations > > 19. > Electronic patient records: domain message information model > perinatology.Goossen WT, Jonker MJ, Heitmann KU, Jongeneel-de Haas IC, de > Jong T, van der Slikke JW, Kabbes BL.Int J Med Inform. 2003 > Jul;70(2-3):265-76. > > 21. > Modeling nursing care in health level 7 reference information model.Helleman > J, Goossen WT.Comput Inform Nurs. 2003 Jan-Feb;21(1):37-45. > > > Electronic patient records: Dutch domain information model > perinatology.Goossen WT, Jonker M, Kabbes BL.Stud Health Technol Inform. > 2002;90:366-70. > > Model once, use multiple times: reusing HL7 domain models from one domain to > the other.Goossen W.Stud Health Technol Inform. 2004;107(Pt 1):366-70. > Met vriendelijke groet, > > Results 4 Care b.v. > > dr. William TF Goossen > directeur > > De Stinse 15 > 3823 VM Amersfoort > email: wgoossen at results4care.nl > telefoon +31 (0)654614458 > > fax +31 (0)33 2570169 > Kamer van Koophandel nummer: 32133713 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > openEHR-technical mailing list > openEHR-technical at openehr.org > http://lists.chime.ucl.ac.uk/mailman/listinfo/openehr-technical -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openehr.org/mailman/private/openehr-technical_lists.openehr.org/attachments/20101110/4ae8ac6b/attachment.html>
