Added support for hybrid remote terminology #795
Conversation
|
Formatting check succeeded! |
There was a problem hiding this comment.
Pull Request Overview
This pull request introduces support for hybrid remote terminology services by adding new configuration properties, validation tests, and bean registration to integrate remote terminology services. Key changes include updating integration tests to validate remote terminology functionality, adding new YAML configuration entries for SNOMED and LOINC, and registering a new bean in the server configuration that adds remote terminology validation support.
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| src/test/java/ca/uhn/fhir/jpa/starter/ExampleServerR4IT.java | Updated test configuration and added a new test to validate remote terminology services. |
| src/main/resources/application.yaml | Introduced remote terminology service configuration for SNOMED and LOINC. |
| src/main/java/ca/uhn/fhir/jpa/starter/common/validation/OnRemoteTerminologyPresent.java | Added a condition class to check for the presence of remote terminology configurations. |
| src/main/java/ca/uhn/fhir/jpa/starter/common/FhirServerConfigR4.java | Registered a new bean to integrate remote terminology validation support based on configuration. |
| src/main/java/ca/uhn/fhir/jpa/starter/AppProperties.java | Added a new property and nested class to hold remote terminology service details. |
|
Formatting check succeeded! |
…api-fhir-jpaserver-starter into feat/remote-terminology-support
|
I created #810 to be able to see why the smoke test fails |
|
Formatting check succeeded! |
…api-fhir-jpaserver-starter into feat/remote-terminology-support
|
Formatting check succeeded! |
|
Formatting check succeeded! |
|
@patrick-werner I don't got much more insights from the extra logging files you added, I'm afraid |
No description provided.