tag:blogger.com,1999:blog-733074358901582680.post6787208008092994187..comments2024-03-23T05:28:35.472-04:00Comments on Healthcare Standards: An Informatics Model for HealthIT StandardsKeith W. Boonehttp://www.blogger.com/profile/16883038460949909300noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-733074358901582680.post-9314434415284163002012-03-26T20:46:49.080-04:002012-03-26T20:46:49.080-04:00More could be done to assist both healthcare provi...More could be done to assist both healthcare provider organizations and vendors in navigating this labyrinth. The discussion should start with characterizing the types of "conversations" that an various kinds of organization engage in, and then explaining how those conversations can be conducted on a standards-based substrate.<br /><br />Of course, the discussion would eventually bleed back into internal operations, and in particular, the way clinical and other data is structured and stored. For example, SNOMED CT can't be used in data exchange if it has no place in the data that was stored prior a decision to exchange it with someone. There is a whole raft of questions about the current scope of the preferred coding standards, i.e., what clinical conversations they can and cannot facilitate. More to the point, HL7's clinical statement model imposes a set of (at least) implicit requirements on EMRs. A standards-compliant clinical statement can't be formulated if the data required to construct it hasn't been stored appropriately.<br /><br />So far, in most of the discussions around standards, the requirements of a true problem-oriented medical record are mostly left out in the cold. That's a bit ironic given the POMR's considerable (albeit largely unacknowledged) relevance to Meaningful Use Stage 2, not to mention Stage 3.Chris W.noreply@blogger.com