The Blue Button 2.0 Team continues to look at performance improvements for the Blue Button 2.0 API. The ExplanationOfBenefit resource can involve a large amount of data being transferred. To improve performance in this area we are introducing the ability to apply gzip compression.

The following content types can be enabled for compression:

  • text/html
  • text/plain
  • application/json
  • application/fhir+json

The minimum payload size we will gzip is 1 kilobyte.

Compression is switched off by default

In order to see the benefit of gzip compression, the client must send the Accept-Encoding: gzip header as part of their request. Otherwise, the server will respond with the unmodified content type and encoding.

Example Header

The header items to activate gzip compression should include the following:

 Content-Type: application/fhir+json
 Accept-Encoding: gzip

An Opt-in enhancement

The change is an opt-in enhancement and will not create any backward compatibility issues. Developers can choose to implement, or not.

The change has been implemented in Release r17 that went live on 2018-06-05.

Earlier Blog Posts

Blog Index







Back to top Subscribe to RSS Feed Comments via Google Group