Invalid code in the formatCode

[jkiddo]

As can be seen in the QA of CH Term - https://fhir.ch/ig/ch-term/qa.html#_home_runner_work_hl7ch.github.io_hl7ch.github.io_buildtmp_ig-builds_ch.fhir.ig.ch-term_3.3.0-milestone_input_resources_valueset_DocumentEntry.formatCode contains a code that does not exist. Also reported on IHE/FormatCode#33.

This means the code urn:ihe:pcc:ic:2009 is not valid to be used.

[pjolo]

Annex 3 of the EPDV-EDI Regulation currently defines the following:

As I understand it, the code urn:ihe:pcc:ic:2008 should be used for Immunization Content (IC), as described in document [IHE PCC TF Rev 9.0]

For Immunization Registry Content (IRC), the code urn:ihe:pcc:irc:2008 would be correct, as listed in [IHE PCC TF Rev 8.0]

This means that Annex 3 must be updated to correspond.

[jkiddo]

@pjolo here you are: #147 . The code no longer exists in the backing IHE Code System. Either you need to reintroduce it there (and probably mark it as deprecated)- or remove it from here - or both.

[pjolo]

@jkiddo The code cannot simply be deleted from the ValueSet because it is explicitly referenced in the EPDV-EDI regulation and the ValueSet must comply with this regulation. Since the ValueSet comes from ArtDecor, the correction would have to be made directly there. Deleting the code from the ValueSet would also not make sense because it is currently in active use.

I would find it better to mark the existing code as “deprecated,” as you already mentioned, instead of deleting it and to add the correct code to the ValueSet and also adjust it accordingly in the EPDV-EDI regulation.

[jkiddo]

well ... as long as the code does not exist in its backing Code system from IHE, then its not technically valid - regardless of what the regulation says. To mark it deprecated you will still have to correct it in the backing Code system

[oliveregger]

@pjolo will discuss with pero from ehs to find a solution

[oliveregger]

see also related https://art-decor.org/art-decor/decor-issues--ch-epr-?id=2.16.756.5.30.1.127.77.10.6.26

[ralych]

@pjolo i suppose it's used in the EPD context. so a removal will have some consequences to the running EPR system.

[jkiddo]

instead of removing it, then do IHE/FormatCode#34 as suggested by @qligier

[oliveregger]

@pjolo will have a look at the issue

[pjolo]

@oliveregger @jkiddo
Unfortunately, this code cannot simply be removed from the Value Set, as it is anchored in Annex 3 and is actively used in production in the context of the EPR. Deleting it directly would therefore result in problems in existing implementations.

With the planned national Terminology Server, it should be possible in the future to resolve such issues more easily and handle such requirements more flexibly.

We propose two options:

1. Close the issue and reopen it once the Terminology Server is up and running.
2. Mark as a feature request and keep the issue open for further work once the Terminology Server goes live.

[jkiddo]

Then you need to get this strongarmed in: IHE/FormatCode#34 - that is the only way forward as I see it. The code is invalid in its current form, and waiting for a national Terminology server wont fix this - only the addition in IHE FormatCode will fix this. That is independent of what the regulation says.