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

Resolving FHIR Core package 4.0.0 should always be substituted with 4.0.1 #144

Open
alexzautke opened this issue Jan 13, 2025 · 2 comments

Comments

@alexzautke
Copy link
Member

In https://chat.fhir.org/#narrow/channel/179166-implementers/topic/FHIR.20Core.20Dependency.20hl7.2Efhir.2Euv.2Esubscriptions-backport.2Er4/near/491315689 we discovered that the hl7.fhir.uv.subscriptions-backport.r4 v1.1.0 package is using FHIR Core 4.0.0 instead of FHIR Core 4.0.1. The 4.0.0 package should not be used. It was suggested by Grahame that we upgrade the package and use the correct one.

The next version of hl7.fhir.uv.subscriptions-backport.r4 will have this fixed, but we don't know when it will be released.

This is currently blocking a support ticket by gematik for Firely Terminal.

@mmsmits
Copy link
Member

mmsmits commented Jan 15, 2025

We have code to detect which FHIR release corresponds to a specific version, e.g. R4 -> 4.0.0 and 4.0.1
and also have to know which package belongs to a FHIR release. So we can use that to solve this.

Options:

  • Make it a general rule to always use the current FHIR package of a specific version
  • Only resolve 4.0.1 when encountering 4.0.0.
  • Only resolve 4.0.1 when encountering 4.0.0. in hl7.fhir.uv.subscriptions-backport.r4 version 1.1.0

@mmsmits
Copy link
Member

mmsmits commented Jan 15, 2025

We go for "Only resolve 4.0.1 when encountering 4.0.0." because package 4.0.0. doesn't exist anymore.

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

2 participants