Allow the FhirClient to connect to other FhirVersions servers #2142
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ewoutkramer
approved these changes
Jul 6, 2022
marcovisserFurore
deleted the
feature/allow-fhirclient-connect-other-versions
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When the
FhirClientSettings.VerifyFhirVersion=false(which is the default), theFhirClientis now able to connect to another FHIR server with another FHIR version. It is now possible that a R4 FhirClient can connect to a R4B server. When there are errors, we provide additional information that the client and server may not be compatible.Related issues
Resolves #2131
Testing
See the
FhirClientMockTestFirelyTeam Checklist