Thinking about this tweetstorm, one of the issues I’ve run into as an engineering leader is what to call the software engineering stuff that’s “agile” given that the Agile Community(tm) has killed the brand.
And by & large, I’ve taken to call it “DevOps”, because the DevOps community have taken up much of the mantle @KentBeck & the XP community started with. & Kent has independently focused on safe small changes deployed to production. Which is DevOps.
3/
Much of the art here is making changes safe enough to deploy to production continuously. And to do that, we need to design incrementally, test obsessively, take architecture seriously so we decompose dependencies. & we need to automate everything & do it all the time.
If I were public health interoperability czar with the power to pull the Levers Of Power
A 🧵
2/
ELR:
- Unify FDA, CLIA & CMS powers to tie payment & lab certification to reporting, work w/ CDC to create a registry of reportable tests & include public health reporting in analyte machine test scenarios
- Require reporting of demographics & contact info as COP
3/
- Create a certification fast lane to the LOI/LRI specifications & create test methods that go all the way to lab reporting
- Create a long-term funding mechanism for public health, create certification criteria & tie grant to certification & prod deployment
NCVHS was created forever ago, but it's mission was updated w/ HIPAA to advise the secretary on, among other things, the administrative transactions created for HIPAA (& as a reminder, the privacy & security stuff in HIPAA was sideline in the day…
3/
b/c HIPAA was about insurance portability & administrative efficiency & health data privacy came along for the ride).
HITAC, defined in Cures was the update to HITSC/HITPC which was created for HITAC. Fhew.
Anyway 2 FACAs advising on standards tells you a lot.
Speakers in the public health community explicitly noting that the Promoting Interoperability (née MU) program established the baseline for syndromic surveillance & dropped many of the feeds in place.
A tweetstorm that will make some people mad. I apologize in advance.
There are two perspectives on the IHE SOAP-based specifications (primarily XDS, XCA and XCPD), not mutually exclusive
2) a) They have worked in practice, so should not be ripped and replaced
b) They are legacy technology and we should work on more modern alternatives.
A 3rd perspective, enshrined in #TEFCA#QTF is:
c) We should continue to make them the core of our health infrastructure
3)
The world "legacy" makes people mad -- my perspective is that technology moves on regardless of whether we like it or not. Some standards, particularly low level networking standards, have stood the test of time, some have... not
To start with, a basic question: are market forces for interoperability good, or nah?
2/
There are three basic positions that I hear articulated
a) "making money on interoperability is immoral"
b) "making 'unreasonable' profit on interoperability is immoral"
c) "extracting monopoly rents as an interoperability gatekeeper is immoral"
3/
These are obviously *very* different stances, and the inability to articulate and distinguish them causes real problems. I often hear a silent assumption that all fees are monopoly rents and ipso facto immoral.