View in #ohif on Slack
@Christopher_Skene: Has anyone successfully used Google Healthcare transcoding? The transcoded imaging is showing a black in OHIF, and when I look at the Tags view its showing the original TransferSyntax, not the transcoded syntax. This data is also in the metadata response, which is expected as that request doesn’t control for transcoding, but I’m not sure how thats interacting with the renderer or the tag browser.
I guess my question is, does OHIF select the renderer based on the metadata response or the headers in the image?
@Alireza_Sedghi: Our QA server is Google Healthcare
I’m surprised it does not work for you
which modality?
@Christopher_Skene: Alll of them. Do you use GCP transcoding?
@Alireza_Sedghi: Is that a separate api?
@Christopher_Skene: You have to send a different Accept header to get it to transcode, however that only works for Studies/Series/Instances and Frames, not Metadata
I dont think this is strictly an OHIF problem, Im just trying to work out how to get around it. If OHIF is using the Transfer Syntax in the metadata request to select the renderer, then we can intercept the JSON and fix that, as we run a proxy in the middle.
@Alireza_Sedghi: I think they have beta api
You can try that
@Christopher_Skene: I don’t think there’s anything different in the beta api for the ‘metadata’ endpoint. It’s a json endpoint, not a DICOM one.
We’ll try altering the response.