I also found that people don't trust paid services either, when it comes to their health (at least when provided by companies other than their health provider)
I like the idea behind Zenobase. Aurametrix explored relationships between many different sources of data that could be related to health. It is not public now, but would be happy to share the insights.
I dropped out, after implementing five exchanges, because it became obvious to all of us doing the work that single payer was the only correct answer. All of our customers and partners were competitors and had no incentive to share data.
I didn't anticipate consolidation of providers, perhaps accelerated by the passage of ACA. Babysteps, eventually leading to single payer? I don't know.
Maybe I should have stuck it out.
For the moment we're focused on folks with serious illnesses, but we've got plans down the road for pricing and a product geared more toward the casual user. Thanks again!
So it's kind of hard to fit everything in one basket. There is HL7 that should a sort of golden standard but many programmers on the field totally ignore it.
Some people criticize HL7 for being overly complex. And there is some truth to that due to legacy issues. But the reality is that healthcare is tremendously complex and so that drives a certain level of unavoidable complexity in the standards.
As for docs, the main problem is that they've spent the last century or two training snowflake workflows and vocabularies. :(
That said, PicnicHealth looks nice, and I wish them best luck! The pricing seems a bit high for someone who doesn't have health issues and just wants to keep track of regular tests, but I find it easier to trust a paid service than a company with a surprise business model.