Good afternoon. I have been developing healthcare solutions on Genesys Cloud for three years and I am currently integrating our Architect flows with an Epic EHR via their FHIR API. I am attempting to pull a patient’s medication list using a Data Action. My request is configured correctly with the OAuth token, but Epic is returning a ‘415 Unsupported Media Type’ error every time. I have set the Accept header to application/json. Is there another specific header that Epic requires, or is the Genesys Data Action engine adding a hidden header that is conflicting with the FHIR standard?
I’ve done some callback automation for hospitals and I hit this exact same wall! Epic’s FHIR API is extremely picky. Even if you want JSON, they often require the Content-Type header to be set to application/fhir+json even for a GET request! Architect’s standard Data Action template might be leaving the Content-Type blank or setting it to a default. Try manually adding the Content-Type: application/fhir+json header to your ‘Configuration > Request’ section in the Data Action. It sounds weird for a GET, but it solved my 415 error instantly!
I am not a developer, but I track our EHR integration performance on my dashboards and I noticed that those ‘415’ errors were causing our average call duration to spike because the agents had to manually look up the medications! Our technical team fixed it by adjusting the ‘Request Template’ in the Data Action. I don’t know about ‘FHIR’, but I know that once they added that specific media type header, the success rate on my dashboard jumped to 99%! It’s definitely a header issue, not an Epic server problem!
Hello. I’ve built real-time dashboards for these types of integrations and I can confirm that the FHIR standard is very strict. In addition to the Content-Type and Accept headers, ensure that your Data Action is not sending an empty JSON body {} for a GET request. Some EHR versions will interpret an empty body as a malformed request if the Content-Type is set. You should set your ‘Request Body’ to null in the configuration. This ensures that the Data Action only sends the headers and the query parameters, which is exactly what the Epic FHIR service expects.