qligier
commented
3 weeks ago Hi @dvribeira!
There is no formal process yet. Ideally, eHealth Suisse would notify Husky when a change in terminology happens so that we can plan for a value set regeneration.
About the subpackages:
- the ones with dates correspond to official release. They should correspond to the version label in ArtDecor (e.g.
202306.0-stable), but when the value set doesn't change, its version isn't updated (so you can have a202212.0-stablein the subpackage202406). stableis the last official release that has already come in force.betais any future version of the value sets. It's useful to support new codes that won't make it quickly in official releases (e.g. for eMedication codes).
It appears we have missed 202306 and 202406, although we have #46 and #105 for that.
About the configuration of the code generator: it uses YAML files to select value sets and their version. I think eHealth Suisse maintains a similar YAML file for each release, it could be useful to avoid checking all value sets by hand.
dvribeira
@ralych @qligier
I was interested in using a more up to date version of this enum, to reflect the current state of https://art-decor.org/decor/services/RetrieveValueSet?prefix=ch-epr-&language=en-US&version=&id=2.16.756.5.30.1.127.3.10.13.2 http://fhir.ch/ig/ch-term/3.0.0/CodeSystem-2.16.756.5.30.1.127.3.10.7.html
I know that these classes are generated by the code-generator but I wanted to know how these updates are managed at a project level and whether there is any kind of formal process involved, since I have also seen that there are several subpackages for these enums (
beta,r202104,r202212andstable), before tampering with any of these files in either husky or the code generator.