tag:blogger.com,1999:blog-8556327481922524425.post8372360010996844409..comments2019-01-19T02:32:35.693-06:00Comments on Business Intelligence and Other Oxymorons: Jon Stewart Don't Know Squat About DataMikehttp://www.blogger.com/profile/04016378069185334533noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8556327481922524425.post-5115821859347776342013-05-02T20:59:25.883-05:002013-05-02T20:59:25.883-05:00The document you refer to is something of a market...The document you refer to is something of a marketing publications. You no doubt noticed that the business model of the two databases is different (first question and answer).<br /><br />The second answer is the one you point to and I will say only that this looks very similar to other marketing brochures you may have seen. Such documents never (NEVER) state a negative and like this one, usually "answer" a question without ever taking a stand. The actual text is pasted below.<br />===================================================== <br />๔ Can AHLTA and VISTA โtalkโ to each other?<br />Yes, AHLTA and VistA do share significant EHR information. The Bidirectional Health Information Exchange (BHIE) allows for information sharing of lab/radiology results, medications, allergies, procedures, problems, encounter notes, other clinical notes, vital signs, drug allergies and anatomic pathology/microbiology lab results.<br />=====================================================<br />The types of information specifically called out as being part of the interface (BHIE) are, in fact, significant but are by no means complete and depending on the actual usage (for example of encounter notes) may or may not be common coin. Note particularly that AHLTA is used for dependents as well as active duty service members. VISTA deals only with the service member. AHLTA uses social security number internally to tag information but an internally generated identifier to make sense of a family's information. That AHLTA specific identifier is meaningless to VISTA and this alone could render the transfer of data extremely difficult if not impossible.Mikehttps://www.blogger.com/profile/04016378069185334533noreply@blogger.comtag:blogger.com,1999:blog-8556327481922524425.post-56724544557116482612013-04-24T23:26:40.261-05:002013-04-24T23:26:40.261-05:00Maybe I'm wrong here, but I searched google an...Maybe I'm wrong here, but I searched google and found this http://www.health.mil/content/docs/pdfs/categorized_ahlta_webhall_responses.pdf<br /><br />It states very clearly that they both use the same records format....so what's the problem? Couldn't they update them both to include a bulk import/export feature? I'm no software engineer, but this sure sounds like it can be done because:<br /><br />"AHLTA and VistA do share significant EHR information"Anonymousnoreply@blogger.com