Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FHIR resource validation breaks when server have multiple versions of same profile #6463

Open
MangalaEkanayake opened this issue Nov 13, 2024 · 2 comments

Comments

@MangalaEkanayake
Copy link
Contributor

Describe the bug
Server have supported 2 versions of a profile.
https://fhir.abc.com/StructureDefinition/ConsentTest|1.0.0
https://fhir.abc.com/StructureDefinition/ConsentTest|1.2.0

following function is called by the library. Always the 'theUrl' is parsing without the version. so the IValidationSupport implementation can't be separate the profiles.
IValidationSupport.fetchStructureDefinition(theUrl: String?): StructureDefinition?

Bug: When validate a Consent resource with value 'https://fhir.abc.com/StructureDefinition/ConsentTest|1.2.0' in element meta.profile : IValidationSupport.fetchStructureDefinition receives 'https://fhir.abc.com/StructureDefinition/ConsentTest'. It should be received 'https://fhir.abc.com/StructureDefinition/ConsentTest|1.2.0'

Expected behavior
Resource should be validated against the profiles in meta.profile

**Environment **

  • HAPI FHIR Version: 7.4.5
  • OS: Windows

Additional context
This works properly on 7.2.1

@MangalaEkanayake
Copy link
Contributor Author

Probably this has introduced by #6040

@MangalaEkanayake
Copy link
Contributor Author

PR: #6534

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant