You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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:
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.
The text was updated successfully, but these errors were encountered: