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

Double entries in IG when providing FHIR resources as binaries #910

Open
oliveregger opened this issue Jun 18, 2024 · 0 comments
Open

Double entries in IG when providing FHIR resources as binaries #910

oliveregger opened this issue Jun 18, 2024 · 0 comments
Labels
Approved Change has been reviewed and accepted and can now be applied to the templates bug Something isn't working

Comments

@oliveregger
Copy link
Contributor

For testing we would like to provide non conformant FHIR resources within an IG. We wan't to add them as Binary resource, so that the validator / IG Publisher does not create errors or warnings for it and that it can be also processed.

This works fine and is no problem if we provide the FHIR resource base64 encoded directly in the binary.

However if use the nice FHIR IG Publisher shortcut and use the automatic Binary Conversion (like for logical models) we get two entries, one for the binary (which what we wanted) but also one for the resource itself, see for example:

https://build.fhir.org/ig/ahdis/ch-ig/branches/oe_binary/qa.html

we have there now two entries:

image

but we would only like to have one, when we would create it manually.

source of branch/repo reproducing it is here: https://github.com/ahdis/ch-ig/tree/oe_binary

zulip background discussion is here: https://chat.fhir.org/#narrow/stream/274423-TestScript-Resource/topic/How.20to.20test.20invalid.20data

will provide a PR.

oliveregger added a commit to ahdis/fhir-ig-publisher that referenced this issue Jun 18, 2024
@lmckenzi lmckenzi added bug Something isn't working Approved Change has been reviewed and accepted and can now be applied to the templates labels Jun 18, 2024
grahamegrieve added a commit that referenced this issue Jul 4, 2024
do not add Binary resources which are not really Binary #910
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Approved Change has been reviewed and accepted and can now be applied to the templates bug Something isn't working
Projects
Development

No branches or pull requests

2 participants