Yes any initiative that relies on the patient to move data around is doomed to failure. Patients need to be able to get access to their data, but to deliver effective care the data has to flow between provider (and payer) organizations.
In terms of exporting data from one HIS system and into another, it's not clear to me that this will every work without more infrastructure. The exported HL7 data from one organization is going to be of little use to another, they would need some very specialized software to mediate between the data in the exported HL7 file and their own systems. Importing it directly into their hospital information systems is simply not going to be possible; their systems won't understand the myriad of idiosyncratic decisions that the other organization has made, often in response to the specific systems they have purchased (scheduling, laboratory, scheduling, etc.)
Other types of data are still problematic.
Even Epic doesn't have the ability to consolidate multiple CDA documents, or even write information directly to the chart. Each one requires manual review. Standards for exchange are not really the problem.
It’s all edges. It’s really grim. And once you have it sorted out, another variation pops up and fails in some new and awful way. Trying to maintain charts with columns and rows for example, basic stuff, in is near impossible. Just when you crack it you find some down stream system you have no control over is transposing rows and messing up records. It’s critical stuff and it’s a mess.
Putting the responsibility on the patients to transfer data strikes me as backwards. The vast majority of patients whose lives depend on the easy transfer of records from one organization to another are incapacitated. They have been hit by a car, suffered a stroke, or are moving from one facility to another.