FHIR Chat · IG Publisher adding CodeSystem 'contact' and 'jurisdiction'? · IG creation

Stream: IG creation

Topic: IG Publisher adding CodeSystem 'contact' and 'jurisdiction'?

Rob Hausam (Dec 10 2020 at 23:48):

I'm working on updates for the LIVD IG and ran into something today that seems a bit concerning and problematic. The IG has a profile on CodeSystem for the specific LOINC fragment that is used for the LIVD catalog instance. The profile was constraining out (0..0) the 'contact' and 'jurisdiction' elements (you can question if that's a good idea, but that's another discussion - and for the moment those two constraints have been temporarily removed). With those two constraints in place I was getting two build errors for the CodeSystem instance which said that the element was a max of '0' but '1' was present. And it turns out that apparently IG Publisher (1.1.51) is altering what is in the source file for the resource instance and adding elements for 'date', 'contact' and 'jurisdiction', and it even overrides the existing 'publisher' information in the source and replaces it with the HL7 Work Group. That doesn't seem like very desirable behavior generally, or at least it would be something that should be possible to disable (maybe there is a way to do that?). The relevant content in the source file (input/vocabulary/codesystem-loinc-fragment-livd.json) is:

    "status": "active",
    "publisher": "Regenstrief Institute, Inc.",
    "copyright": "This content from LOINC® is copyright © 1995 Regenstrief Institute, Inc. and the LOINC Committee, and available at no cost under the license at http://loinc.org/terms-of-use",

And the content in the generated output file (output/CodeSystem-loinc-fragment-livd.json) is:

  "status": "active",
  "date": "2020-12-10T14:09:35-06:00",
  "publisher": "HL7 International - Orders and Observations Work Group",
  "contact": [
    {
      "telecom": [
        {
          "system": "url",
          "value": "http://hl7.org/Special/committees/orders/index.cfm"
        }
      ]
    }
  ],
  "jurisdiction": [
    {
      "coding": [
        {
          "system": "http://unstats.un.org/unsd/methods/m49/m49.htm",
          "code": "001"
        }
      ]
    }
  ],
  "copyright": "This content from LOINC® is copyright © 1995 Regenstrief Institute, Inc. and the LOINC Committee, and available at no cost under the license at http://loinc.org/terms-of-use",

As I said, for now to avoid the build errors I've (at least temporarily) relaxed the constraints on 'contact' and 'jurisdiction'. But the correct publisher should remain as it was originally specified as "Regenstrief Institute, Inc." - and I don't know how to fix that at the moment. Does anyone know if it is possible to disable this unrequested and unwanted overriding and adding behavior? Or get this fixed in the publisher?

Elliot Silver (Dec 10 2020 at 23:50):

I believe this is coming from your IG resource.

Rob Hausam (Dec 10 2020 at 23:54):

I agree that's where the data comes from. But I don't think this is something that you can control anywhere in the IG resource (if that's not the case I would be happy to hear that)? And I'm certain that I can't leave out the contact and jurisdiction data from the IG (nor would I want to). I just don't want it to be automatically propagated where it isn't wanted and appropriate.

Grahame Grieve (Dec 11 2020 at 00:18):

it only happens if the IG asks for it to happen

Grahame Grieve (Dec 11 2020 at 00:19):

see apply-* in https://confluence.hl7.org/display/FHIR/Implementation+Guide+Parameters

Sarah Gaunt (Dec 11 2020 at 00:47):

@Rob Hausam think this might be the same issue: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/IG.20Publisher.20stripping.20extensions.3F

Rob Hausam (Dec 11 2020 at 00:56):

@Grahame Grieve That's more parameters that I hadn't paid attention to or had any need to before - so that's good to know. But I can't quite resist saying that it doesn't seem to apply in this case. :) Because there isn't a single instance of and 'apply-*' parameter in our IG resource, yet we're seeing this behavior. But I will try and see what happens when I set the parameter(s) to false.

Rob Hausam (Dec 11 2020 at 00:58):

@Sarah Gaunt Yes, it seems to be the same issue. Thanks.

Sarah Gaunt (Dec 11 2020 at 01:00):

Problem is - once I set that parameter in the IG, I then had to go and manually add the jurisdiction to every profile in the IG. Well, not a problem really, just a pain.

Rob Hausam (Dec 11 2020 at 02:51):

Yes, I had to add it to some of the profiles, too. But setting the 'apply-*' parameters to 'false' (I did that for all of them) did solve the issue that I was having.

Last updated: Apr 12 2022 at 19:14 UTC