tag:blogger.com,1999:blog-6010387589635528818.post4918435630207175488..comments2024-03-17T12:30:37.450-04:00Comments on The KHIT Blog: If you were in Washington in 2008 and somebody gave you $30 billion to spend on health IT...BobbyGhttp://www.blogger.com/profile/03807934795994985233noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-6010387589635528818.post-72558292292828632252015-02-24T11:37:28.025-05:002015-02-24T11:37:28.025-05:00I am so sorry that this has happened to your famil...I am so sorry that this has happened to your family -- and I am shocked that you answered at all. <br /><br />Thank you.<br /><br />I suspect we are maybe looking at FHIR from different angles, and I would love to talk more when you have dealt with life. Just reply to this when you become more free/open and we can pick up from there?<br /><br />William A.noreply@blogger.comtag:blogger.com,1999:blog-6010387589635528818.post-55568541579983293622015-02-24T11:29:34.092-05:002015-02-24T11:29:34.092-05:00Thanks for your thoughtful comment. Don't have...Thanks for your thoughtful comment. Don't have time to fully respond at the moment. My Mother in Law died Saturday night. We're scrambling. All I can say right now is that, absent a std data dictionary, you will be essentially left with point-to-point interfacing. "API" MEANS "Interface," after all. Someone will have to do all of this cross-data mapping if data are to be assimilated into a recipient's EHR RDBMS -- rather than residing separately in some xml document-level inbox items. Recall the IEEE definition of "interoperability." -- usage without additional steps.<br /><br />All I'm implying is some skepticism toward FHIR. Maybe it'll suffice as a partial fix. We'll see. And I'm fully aware that my std data dictionary proffer, whatever its theoretical architectural merits, is unlikely to happen.BobbyGhttps://www.blogger.com/profile/03807934795994985233noreply@blogger.comtag:blogger.com,1999:blog-6010387589635528818.post-79990227449027961192015-02-24T11:00:45.294-05:002015-02-24T11:00:45.294-05:00Let me first say that I am not from this industry....Let me first say that I am not from this industry...<br /><br />You say:<br />> There are, after all, only three fundamental data types at issue: text (structured, e.g., ICD9, those within other normative vocabulary code sets, and unstructured, e.g., open-ended free-form SOAP note narratives), numbers (integer and floating-point decimal), and images. <br /><br />You point to a post, with an exemplary screen shot of an OpenEMR data-dictionary (schema) subset:<br />http://regionalextensioncenter.blogspot.com/2014/02/we-should-not-prescribe-specific.html<br /><br />And you imply (again, after implying it elsewhere often) that FHIR ain't going to save us.<br /><br />Looking at FHIR's data structures, it certainly seems to contain all the scaffolding to incorporate everything that you are talking about in that exerpted quote above. The extension mechanism seem raw/rough/immature, but my question is this: Is there any reason not to use FHIR as an encoding and interchange vehicle for transferring files based on said standard data dictionary? If so, can you suggest another better place to start?<br /><br />Best Regards,<br />W. Archibald<br />=Unknownhttps://www.blogger.com/profile/13516553208356739832noreply@blogger.com