GCP Healthcare Discuss

Thank you, Truc, for your prompt response. I had some bad luck too—the first image I tested happened

Hi Maico, This fix should be rolled out in all regions now. Thanks, Milena On Thu, Jul 24, 2025 at 3:

Hey Esteban! I'd follow this tutorial to run the IG Publisher after your SUSHI build: https://

Thanks a lot for letting us know the bug! We're going to fix the UI. On Tuesday, July 22, 2025 at

Thanks for your response - I have submitted a feature request: https://issuetracker.google.com/issues

That is great news Wel done team Kind regards, Joost Pielage 0645351694 On Wed, 11 Jun 2025, 22:00

Oh, excellent. Thank you! On Monday, May 19, 2025 at 10:29:43 AM UTC-4 Truc Le wrote: Hi Jared Cobb,

We have observed an increase in latency for the 90th percentile of our overall traffic. Please note

No, this is not on our roadmap yet. On Thursday, April 10, 2025 at 7:03:53 PM UTC-4 oscar....@

From the documentation, I see the following rules related to configuring Pub/Sub messages on various

Paul, Thanks very much for the timely reply. Much appreciated. Yes, we would be interested in

Hello, These are the errors that I could see: 1. Carriage return should be \r, not \n 2. The input

Thank you both for the responses. Your explanation about the expression limitations is very clear. I

Hi Vineeth, We do have documentation on setting up a Cloud VPN. Additionally we have documentation

Thank you for your inputs Truc. The best way forward for us seems to be modify the adapter to add

Hi Vineeth, Currently creating a GCS filter file is the easiest way. You could file a feature request

I understand your point and from the PACS perspective, it makes sense. However, as a DICOM API,

Hi Gopal, Please refer to our DICOM conformance statement on returned results. When searching on

Hi Steve, We are confident that our FHIR store is capable of recognizing either the project number or

The first Organization in the bundle has a reference in the "endpoint" field to urn:uuid:

Sorry silly me. 😀. I am not awaiting. It's weird though that to get the text we need to await On

Thnx Paul/Jared I figured it out . This works "request": { "method": "POST

This limitation is the result of licensing terms on our use of SNOMED CT. We are currently unable to

Hi Imran Haider, Thanks for reaching out to us. From the error message you posted, the core error is:

The body of the API response should contain an OperationOutcome resource with those details in it.

Hi Paul, I tried switching the versions and it worked. Thank you so much for your help On Wed, Mar 20

I've directed this to the team and Yatish has replied on the github issue. On Thu, Feb 29, 2024

Thank you for the quick insights! Much appreciated. -Erik On Monday, January 15, 2024 at 11:41:54 AM

Hi Darine, LUT Data could have VR either US or OW. If VR is US, DICOM API should currently have it in

You could use FHIR parser libraries such as HAPI-FHIR or hapi-fhir-converter to parser to XML and/or