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

Support for importing an example bundle by reference to another IG, or directly #1043

Closed
saulakravitz opened this issue Mar 9, 2022 · 3 comments

Comments

@saulakravitz
Copy link

Sushi current supports neither of these:

  1. importing an example bundle from an IG that is listed as a dependency. I wanted to import the example death certificate bundle defined in VRDR into the Vital Records FHIR Messaging IG.
  2. importing an example JSON bundle by including it in the input/resources folder and referencing it by ID.

In the end I needed to include the FSH for the complete example in the Vital Records FHIR Messaging IG....

@cmoesel
Copy link
Member

cmoesel commented Mar 10, 2022

The primary issue here is that when SUSHI loads dependencies, it only holds onto structure definitions, code systems, value sets, and implementation guides. Everything else (including Bundles) gets dropped. The same behavior applies to predefined resources in input/resources (or elsewhere).

SUSHI should probably load and keep the entire package, but we'll need to determine how the other resource types are stored, how they should be fished for, and if this causes any issues (using extra memory, fishing up things it didn't used to fish up, etc).

@cmoesel
Copy link
Member

cmoesel commented Dec 23, 2024

#1548 addresses point 2 above. It does not address point 1 above, but the IG Publisher doesn't load example resources from dependencies, so I don't think you can reference an example across IGs anyway.

@cmoesel
Copy link
Member

cmoesel commented Jan 6, 2025

Closing this as I believe SUSHI now supports all it can/should support based on current IG Publisher behavior (see comment above).

@cmoesel cmoesel closed this as completed Jan 6, 2025
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

3 participants