Saturday, October 02, 2004 Karsten Hilbert wrote: > 2: to use HL7 v3 tools to deliver decision support to > prescribing: default dosing, dosing correction for height, weight, and > renal function, dose checks, contraindication checking, allergy > checking, and drug-interaction and food-drug interaction checking. Any particular reason HL7 v3 is being chosen ?
http://ncvhs.hhs.gov/040527p4.htm see Slide 23: http://ncvhs.hhs.gov/040305p1.pdf http://www.hl7.cz/doc/HL7NewsletterApr02.pdf Besides some other possible contract requirements, for benefits I would point you to Gunther's presentation to the GCRC Biomedical Informatics Workshop October 29-30, 2003, Bethesda, MD: http://aurora.regenstrief.org/~schadow/HL7TheDataStandardForBiomedicalInform atics.ppt and other links on any one of his webpages: http://aurora.regenstrief.org/~schadow/ http://aurora.rg.iupui.edu/~gunther/ some more open source and HL7 http://homeusers.brutele.be/ypaindaveine/opensource/inventory.html "[with] Credits ... to Joseph Dal Molin, OpenGALEN web site, ... for the significant contribution." The following excerpt is from: http://ncvhs.hhs.gov/030127tr.htm MR. MARSHALL: I can take a crack at that. It is the position of the personal health record Working Group that personal health record data should adhere to standards where possible and I will pick out a couple of examples. We believe that the data in a personal health record and personal health information data set should be codified in a way that is consistent with existing standards. Those are evolving as you know, but we believe that they should adhere to that. Secondly, when it comes to the format of data exchange, I showed earlier an example of an XML format. XML unto itself, of course, is a growing standard and way for systems to electronically communicate. Having said that, the argument could be made that existing standards, such as HL7 would be a way for systems to communicate. I would submit that that may be true. However, HL7 being a very large and often complicated standard of exchange for health information may be burdensome to organizations who hold this kind of personal health information and would be inclined to participate in secure exchange of that information and they may find that particular standard burdensome. So, I would submit that as one possibility. MS. KEELER: HL7, any standard is a burden. HL7, I think that is probably one of the very few places that health information technology might actually be in front of other industries is in that particular standard and the ability to really tie together disparate systems. We have had it for awhile. We have had it for 10 or 12 years. So, while it is burdensome, it is there. It is defined and pretty much everybody uses it. So, I guess I would submit -- I think it is a good place to start and we can define whatever the next one is once we get started. ...MR. HAMMOND: Our belief is that the HL7 reference information model now has reached the point of stability and acceptance throughout the industry and, in fact, throughout the world, that this is a standard that we recommended. Data tap is another important component of this in which again the way in which we express things in a way and the way in which we share things is common. Again, we think the Version 3 data taps from HL7 have reached degree of maturity and are moving forward. ...One comment I would make as it relates to the personal health record, too, is HL7 has been working on standards of trusted end-to-end information flow, which means you are not only interested in one step of moving this information from A to B, but trying to define the rules that managing control that information for the rest of that time. Sincerely yours, Tim Tim Flewelling Information Architect/Architecte de l'informatique Health and Wellness/Sant� et Mieux-�tre Government of New Brunswick/Gouvernement du Nouveau Brunswick Tel (506) 453-2871 Fax (506) 444-5505 [EMAIL PROTECTED] http://app.infoaa.7700.gnb.ca/gnb/pub/DetailPersonEng1.asp?RecordID=17800 Confidentialit�/Confidentiality: Le contenu de cet envoi, privil�gi� et confidentiel, ne s'adresse qu'au(x) destinataire(s) indiqu�(s) ci-dessus. Il est interdit par toute autre personne, de le divulguer, le communiquer ou le reproduire. Si vous avez re�u cet envoi par erreur, veuillez en aviser l'exp�diteur imm�diatement et supprimer le message de tout ordinateur. / The content of this e-mail is privileged and confidential and intended solely for its designated recipient(s). Any dissemination, distribution or copying of this material, other than by its intended recipient(s), is strictly prohibited. If you have received this message in error, please contact the sender and delete the material from any computer.
