- Continue to develop 2-3 implementation approaches by forming communities of interest around each one (as suggested by Wes Rishel)
- Communities will likely form around SMTP and IHE/SOAP
- SOAP with an e-mail bridge model
- REST with SMTP
I believe in general that the group is moving towards trying to seek common ground, and that sentiment was strongly supported by many EHR vendors.
One of the problems on today's call was that these one line descriptions of the proposals did not present enough information about what was included in them. We did not come to a decision today, but Vassil Peychev proposed that the remaining proposals be written up and a call be held on Friday to review again. David McCallie and others are working on write-ups now. Given that suggestion occured near then end of the NHIN Direct call, Ariensuggested that be the go forward plan.
Let me briefly summarize how I think these proposals work out:
- The "go your own road" proposal around communities of interest seemed to be a non-starter. Two people really supported it, but I heard strong support (including my own) on trying to come to consensus, even though it may be hard.
- There seem to be two "grand unification theories" going around:
- Use the IHE XDR protocol as the backbone and provide a bridge to the SMTP model.
- Use SMTP as a backbone, with REST as an interface layer, and IHE XDM as recommended content. This would enable step up/down to/from current NHIN and IHE protocols (XDR and XDS). [I strongly support this theory].
There was still a great deal of discussion / dissent over the lack of representation from the smaller providers who this is being built for. The next time this process comes around, there ought to be some sort of provision to provide for them to be directly represented (EHR vendors do have these providers as customers, but representation by proxy is not seen as valid representation; at least in some of this group).
There are also a few who have expressed concerns that large vendors are still dominating the process. However, I would also note that it seemed to be those same vendors strongly expressing desire to reach consensus, rather than divide up around preferred approaches.
I also heard some concerns raised that a very small but strong minority opinion was blocking a majority viewpoint, and also that the majority was trying to work with them.
This was another hot-button topic, and I think that the words minority and/or majority, and large/small vendors are keywords that should be used very carefully in any NHIN Direct call that wants to make progress (I'm just sayin').
There were a number of comments about scalabity of solution A vs. solution B. In a community of experts however, an expert opinion carries little weight when two or more the experts disagree. There was one attempt to shift grounds from "technical scalability" to "social scalability" of the two alternatives. It was an interesting discussion, but I didn't quite get it.
All in all, it was a pretty intense and wide ranging (perhaps too wide ranging at some points), discussion.
We are all very frustrated, and that comes from a number of places. The ability of a small group to hold up a larger group, the struggle by under-represented but important stakeholders to have their viewpoints heard, the desire by some (including me) to move things forward. The newness of this process, our lack of experience with it, and our inability to reach some of our timelines contributes to all of this frustration.
Even with all the frustration, we've gone from four possible outsomes to somewhere around two in a matter of a week, and that is indeed progress. I have to give Arien Malec a lot of credit (worry not, I'll give him grief like I did a few weeks ago when it is deserved).