FHIR patient extensible data portability
Discussions at FHIR DevDays raised this question of a basic way to leverage FHIR API capability to enable the Patient beyond the limited Apps their provider has approved. If a healthcare provider offers a FHIR API (e.g. argonaut) -- meeting the Meaningful Use "API" requirement. Would it be reasonable to expect that the Meaningful Use "Download" (from View/Download/Transfer) capability would be offered in FHIR format? Proposed quick-and-dirty solution? This could be something like a zipped Bundle containing the results of $everything for that Patient, given that patient as the user. The zipping would help with the potential huge size. The amount of data would be limited to that which is available on the FHIR API offered, which is often not all possible data. Concern would come up when this export of $everything includes other data such as documents and images. The theory is that they are all necessary to export, but the problem is the overwhelming size that might re...