Re: Can Argonaut Project Make Exchanging Health Data Easier?
I'm with Peter. It's about time for healthcare to catch up to other industries when it comes to customer (patient) expectations, and it sounds like Argonaut fills in important niche in pushing the standards and technologies that are developed to actually be adopted by healthcare orgs - that's an important in-between step. I was pleased to hear Mr. Halamka's sobering perspective - his key points seemed to sound an awful lot like 'patients are displeased with the inefficiency of healthcare' and 'why can't we do what's working for other industries?'. Those two points alone will carry Argonaut a long way, I think. It's a complicated web of companies and jargon to a non-healthcare pro, even as a programmer, and combined with government influence there's a high signal-to-noise ratio. We need people who will stay focused on end results.
I suppose there's some consideration for how those convoluted healthcare formats got that way in the first place - security comes to mind first and formost. It makes sense that you would want to make absolutely sure that only the intended receiver could read the document, and that only another healthcare org would even have the right tools or systems to handle it. In hindsight, though, it makes a lot more sense to focus your security on actually making your networks secure, your privacy on holding healthcare professionals responsible for what they do with the data, and freeing your programs and programmers up to make innovations faster and better. Other industries are realizing that the rule is 'get with the times or go extinct' with trends like DevOps and consumerization - glad to see some people in healthcare realize this, too.