tag:blogger.com,1999:blog-733074358901582680.post3765880737567351644..comments2024-03-23T05:28:35.472-04:00Comments on Healthcare Standards: Seamless InteroperabilityKeith W. Boonehttp://www.blogger.com/profile/16883038460949909300noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-733074358901582680.post-63713003648522094242011-05-24T20:31:44.560-04:002011-05-24T20:31:44.560-04:00Mutual understanding is not all or nothing: system...Mutual understanding is not all or nothing: system A may get some of what system B can export and vica-versa but, rarely, will two parties understand each other completely. And that's fine, certainly for read-only exchange.<br /><br />To take your labs example - some local codes may have loinc equivalents, some may not. If both systems understand the same local codes, then all is well. Otherwise, they fall back to loinc. Over time, hopefully there's more loinc and more mutual understanding. Perhaps clearer than printer drivers, you have browser behavior. Old browsers don't collapse because they see a new HTML5 "section" tag.<br /><br />Interop, beyond the (trivial) "email or soap" stuff, is not all-or-nothing. If that's what is meant above by seem-less, then seem-less is achievable. If seem-less == exact match then ...conor dowlinghttp://www.caregraf.comnoreply@blogger.com