Update to Content-Type header on FHIR responses

4 views
Skip to first unread message

Developer Group for CMS Blue Button API

unread,
Feb 19, 2026, 2:51:05 PM (5 days ago) Feb 19
to Developer Group for CMS Blue Button API

Hello Blue Button Community,

In order to ensure more robust FHIR conformance, in next week’s release, the Blue Button API will default to returning the Content-Type response header with a value of ‘application/fhir+json’. Currently, the default value for the Content-Type response header is ‘application/json’.

This will apply to any FHIR resource calls (Coverage, ExplanationOfBenefit, and Patient). The release with this change is currently scheduled to be deployed to the sandbox environment on Friday, February 27th, and to production on Monday, March 2nd.

Do I need to change anything in my app? 

You will only see a change if your application does not include an Accept header in your FHIR resource requests. If your application doesn’t include Accept headers and your application expects responses that have a Content-Type header equal to application/json, you should either include an Accept header with value application/json in future requests or adjust your application to tolerate responses with a Content-Type of application/json+fhir .

Support

If you need assistance or have any concerns about this timeline, please contact us at BlueButtonAPI @cms.hhs.gov or post your questions here in the Google Group.

-The Blue Button API Team

Reply all
Reply to author
Forward
0 new messages