Invalid HTTP response 503 from https://tx.dev.hl7.org.au

[dattachandan]

Hi team

When I ran the container locally(can't see on the remote sever on Cloudwatch), I see exceptions during validation , are these intermittent and is there a way to run the TX server locally?

Attaching a sample log below

httpResultException-503-fhir-TX.log

[projkov]

Hello Chandan @dattachandan

It looks like there was a temporary problem with the accessibility of the terminology server. Now it should work without any issues.

Unfortunately, we don't have the option to run the TX server locally.

I appreciate your interest in our test kit!

[projkov]

@dattachandan Users can set any TX server URL using a variable called TX_SERVER_URL. By default value is https://tx.dev.hl7.org.au/fhir

[projkov]

@mjosborne1

Hello Michael. Is there any way to run the ontoserver locally?

[dattachandan]

@projkov thanks for the update, will be good to know if a AU based terminologies server can be set locally especially when we do internal CI builds for any integration testing

[lawley]

I don't know that running a local Ontoserver will help with the above. The request with the error is to a non-FHIR, Grahame-specific endpoint (.../tx-reg/...). This looks more like a bug in the validator

[lawley]

Looking at the code in org.hl7. fhir.r5. terminologies .client. TerminologyClientManager it seems that setting IGNORE_TX_REGISTRY=true should avoid any attempt to use the tx registry

[ir4y]

@projkov please have a look and test ☝️

[projkov]

Looking at the code in org.hl7. fhir.r5. terminologies .client. TerminologyClientManager it seems that setting IGNORE_TX_REGISTRY=true should avoid any attempt to use the tx registry

@lawley Hello Michael. Thank you for the advice.

Did you know something about how to change the value of this variable through cliContext? I can't find any information in the docs, or code samples.

[ir4y]

It looks like a constant that could not be changes dynamically: https://github.com/hapifhir/org.hl7.fhir.core/blob/dd01e008ca6fdc4742293f38a9c99d77c7e33d74/org.hl7.fhir.r5/src/main/java/org/hl7/fhir/r5/terminologies/client/TerminologyClientManager.java#L89

[jwjahns]

Hello, I also ran into this when attempting to deploy locally, and found that setting noEcosystem true in the cli_context blocks (here and here) seems to resolve this. In the Java validator code, noEcosystem eventually sets useEcosystem, which is checked in the same places that IGNORE_TX_REGISTRY is checked. However, I couldn't find documentation on this noEcosystem parameter, so I'm not entirely sure if this is the intended usage.

(note that this requires a Java validator version of at least 6.3.6 - see "Dont use tx-registry when manual terminology server is set")

[ir4y]

@projkov Could you please check?