Stream: shorthand
Topic: reusing existing terminology
Jens Villadsen (Jun 17 2021 at 21:36):
Hi FSH-people. Is there an easy way to reuse the terminology already stated in existing CodeSystem/ValueSet files in Json/xml, in FHS? The case is that the terminology is already maintained in a running system and upon IG updates I am looking into doing an export of the CodeSystem/ValueSets and I need to know if I need to convert them to FSH before they can be used in the FSH files
Jean Duteau (Jun 17 2021 at 21:49):
you have CodeSystem/ValueSet files that you want to import into your guide? If so, just put them in input/resources and then you can refer to them by their ID in your FSH files.
Chris Moesel (Jun 18 2021 at 13:08):
What @Jean Duteau said -- you can put FHIR JSON/XML in input/resources (or a few other input/* variants) and SUSHI will recognize their existence so that your FSH code can reference them. If SUSHI is building your IG JSON for you, then it will also include them in that so that they are published w/ the IG.
But if you just want to reference them without them being a part of the IG, then ideally they would be published as a separate package in the registry; and then you would just declare them as a dependency.
May Terry (Jun 18 2021 at 13:09):
FWIW, this is the approach we took when migrating the Clinical Genomics Reporting IG to FSH last November. :-)
Chris Moesel said:
What Jean Duteau said -- you can put FHIR JSON/XML in
input/resources(or a few otherinput/*variants) and SUSHI will recognize their existence so that your FSH code can reference them. If SUSHI is building your IG JSON for you, then it will also include them in that so that they are published w/ the IG.But if you just want to reference them without them being a part of the IG, then ideally they would be published as a separate package in the registry; and then you would just declare them as a dependency.
Jens Villadsen (Jun 18 2021 at 15:36):
I considered option with separate IG but just using them as sounds easier ;)
Last updated: Apr 12 2022 at 19:14 UTC
