The IG publisher is not able to validate the use of Swedish codes / codesystems / valuesets because they are unknown to it. While standing up our own, IG publisher-compatible terminology server is a long-term goal, we can address this need in the short term by creating a supplementary package that will contain all Swedish codesystems in a FHIR format.
This package can then be used as a dependency to all of the IGs in Sweden to provide the codesystems needed for validation to work.
While package will technically be published as an implementation guide as that is the format required by the tooling, but it should not be thought of as a guide at all - instead, it is a collection of Swedish codesystems in a FHIR format with its own lifecycle. This package can be updated as often and as needed.
Additionally, when we do stand up the terminology server, this package can be used as an input it to load all the codesystems up.
TODO:
[ ] create a proof of concept that codesystems from a dependant package can be used to validate valuesets in another IG.
The IG publisher is not able to validate the use of Swedish codes / codesystems / valuesets because they are unknown to it. While standing up our own, IG publisher-compatible terminology server is a long-term goal, we can address this need in the short term by creating a supplementary package that will contain all Swedish codesystems in a FHIR format.
This package can then be used as a dependency to all of the IGs in Sweden to provide the codesystems needed for validation to work.
While package will technically be published as an implementation guide as that is the format required by the tooling, but it should not be thought of as a guide at all - instead, it is a collection of Swedish codesystems in a FHIR format with its own lifecycle. This package can be updated as often and as needed.
Additionally, when we do stand up the terminology server, this package can be used as an input it to load all the codesystems up.
TODO: