FHIR patient extensible data portability

Discussions on Fhir DevDays raised this issue in key ways to increase the capacity of the Fhir API, so that patients can handle the limited approval of service provider applications.

When the healthcare provider provides the FHIR API (eg, Argonaut), it meets the requirements of “Usage APIs.” Can you reasonably expect the possibility of a significant “Download” to be offered in Fhir format (view / download / transport)?

Do you suggest quick and dirty solutions?
It may be something like a compressed package that contains $ results for everything in the patient because the patient is using. Susting helps a great potential.

The amount of data is limited to the data available in the provided FHIR API, which is often not all possible data.

Concerns worry when exporting $ each contains other data like documents and photos. The theory is all necessary for export, but the problem is the huge volumes that can be made. (Unfortunately, the compression for documents and images where the slight difference is almost the same, more useful, but they see because Base64 encoding is quite different.)

Should this document be FHIR?
It might be better to have this Fhir document, but it is not clear to me that it brings a great advantage to just that all known data (also known as dollars) are exported.

It would be useful to have a more configurable package that comes from a particular company for a particular purpose at a particular time. It can also be a product source in the package. This may be very important for the recipient at this point so it can be recorded and shown that it is complete (document principles).

Basically, the CCD offers this tag and often has a “downloadable” solution, so it’s just a type of MIME (FHIR).

I think exporting is more important than ensuring that it is a FHIR document.

Why does someone do or want that?
It is useful for patients who want to use applications that have not been approved by the vendor. Waiting for each of your vendors to approve a useful application may be limited to the patient and to the marketplace.

Imagine a potential stupid patient who does not know what he is doing with his affirmations … this will happen, and when this happens, there will be a cry. This cry complains that the service provider does not act as a parent for this child, but this type of anger should not be a reason not to do so. It is better to warn the patient, but not get all the data in a FHIR download.

Who does it?
If so reasonable, who is doing today?

Leave a Reply

Your email address will not be published. Required fields are marked *