FHIR Chat · New error about contained resources

Stream: IG creation

Topic: New error about contained resources

Jean Duteau (Oct 01 2021 at 14:56):

I just updated my IG publisher from 1.1.73 to 1.1.81 and I'm getting a new error around contained resources and I'm pretty sure that the error is incorrect, but I'll welcome a change in my understanding. In a repository that ran clean before (
https://github.com/hl7/fhir-spl), the new error I'm getting is:

ref-1: 'SHALL have a contained resource if a local reference is provided' 'SHALL have a contained resource if a local reference is provided' ( (url: usagent; ids: ))

The resource in question has three contained resources. One OrganizationAffilation references the containing resource and references another contained resource:

{
      "resourceType" : "OrganizationAffiliation",
      "id" : "SampleLabelerUSAgentAffiliation",
      "meta" : {
        "profile" : [
          "http://hl7.org/fhir/us/spl/StructureDefinition/USAgentAffiliation"
        ]
      },
      "organization" : {
        "reference" : "#"
      },
      "participatingOrganization" : {
        "reference" : "#usagent"
      },
      "code" : [
        {
          "coding" : [
            {
              "system" : "http://ncicb.nci.nih.gov/xml/owl/EVS/Thesaurus.owl",
              "code" : "C73330",
              "display" : "Foreign Facility's United States Agent"
            }
          ]
        }
      ]
    },

This is the resource that is getting the error and from the error message, I'm assuming that it's taking the #usagent and expecting that to be in a contained resource within the resource itself. But a) contained resources can't contain resources and b) the relative link is intended to be to other contained resources.

Lloyd McKenzie (Oct 01 2021 at 16:38):

And #usagent exists as a resource in a sibling contained resource?

Jean Duteau (Oct 01 2021 at 17:57):

Yep, it's in the same array of contained resources. Organization-SampleLabelerOrganization.json

Lloyd McKenzie (Oct 02 2021 at 01:30):

@Grahame Grieve

Grahame Grieve (Oct 04 2021 at 03:31):

well this one is weird. Certainly nothing has changed in the validation layer that has anything to do with this

Jean Duteau (Oct 04 2021 at 03:48):

like I said, it wasn't an error in 1.1.73 but it is in 1.1.81

Grahame Grieve (Oct 04 2021 at 04:10):

oh this might be Lloyd's changes around invariant validation

Lloyd McKenzie (Oct 04 2021 at 04:12):

Did I mess up, or is it just now checking something it wasn't before?

Grahame Grieve (Oct 04 2021 at 04:15):

well, the error actually happens when it's checking slicing. So it shouldn't be recorded (as well as it shouldn't happen)

Grahame Grieve (Oct 04 2021 at 04:19):

the underlying issue is that conformsTo() jumps into the bundle in the contained resource, without the context, so the contained references can't be resolved.

Grahame Grieve (Oct 04 2021 at 05:23):

fixed next release. Seems like some sort of discovered check, because the issue has always been there

Ramandeep Dhanoa (Nov 29 2021 at 20:10):

I feel like I have similar scenario here. I have QuestionnaireResponse who has 2 contained resources - Questionnaire and ValueSet. Questionnaire contained resource is referencing ValueSet as #VSPHQ9 (where VSPHQ9 is the id of the contained ValueSet). In QA - I am getting this warning message "ValueSet #VSPHQ9 not found by validator" - Any insights on why this might be happening?