-
Notifications
You must be signed in to change notification settings - Fork 8
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
FhirValueSetEnumInterface and system OIDs #153
Labels
bug
Something isn't working
Comments
Also, in |
This was referenced Jul 17, 2024
qligier
added a commit
that referenced
this issue
Jul 18, 2024
qligier
added a commit
that referenced
this issue
Jul 18, 2024
qligier
added a commit
that referenced
this issue
Jul 18, 2024
qligier
added a commit
to project-husky/code-generator
that referenced
this issue
Jul 18, 2024
qligier
added a commit
to project-husky/code-generator
that referenced
this issue
Jul 18, 2024
qligier
added a commit
that referenced
this issue
Jul 18, 2024
qligier
added a commit
to project-husky/code-generator
that referenced
this issue
Jul 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When value sets are generated, the system may be an OID. In that case, it is not URN-encoded. I removed the URN-encoding in eMed value sets in c029d01 (RouteOfAdministrationEdqm was the last one), the EPR value sets were never affected by the URN-encoding.
The issue is that the implementation of
Coding getCoding()
andboolean isEqualTo(Coding)
(fromFhirValueSetEnumInterface
) do not add or remove the URN-encoding, as required by the FHIR specification.The text was updated successfully, but these errors were encountered: