AU Base profile is not being validated properly

[rajyraman]

There is an extension called http://hl7.org/fhir/StructureDefinition/individual-genderIdentity which is part of FHIR Core Extensions Registry. This extension is not loaded on the server. However, if I use a mismatched data type for family and given elements, the validation warning regarding the extensions is all I get. There seems to be no error generated for the mismatched datatypes for these two elements. Why is this happening?

Request

{
    "resourceType": "Patient",
    "id": "12345",
    "meta": {
        "profile": [
             "http://hl7.org.au/fhir/StructureDefinition/au-patient"
        ]
    },
    "identifier": [
        {
            "use": "official",
            "system": "http://ns.electronichealth.net.au/id/ihi/1.0",
            "value": "8003608166690503"
        }
    ],
    "name": [
        {
            "use": "official",
            "family": 2,
            "given": false
        }
    ],
    "gender": "male"
}

Response

{
    "resourceType": "OperationOutcome",
    "issue": [
        {
            "severity": "warning",
            "code": "business-rule",
            "details": {
                "coding": [
                    {
                        "system": "http://hl7.org/fhir/dotnet-api-operation-outcome",
                        "code": "2012"
                    }
                ],
                "text": "Cannot walk into unknown StructureDefinition with canonical 'http://hl7.org/fhir/StructureDefinition/individual-genderIdentity' at 'http://hl7.org.au/fhir/StructureDefinition/au-patient#Patient.extension (Patient.extension:genderIdentity)'"
            },
            "location": [
                "Patient // OperationOutcome.Location is deprecated, please use OperationOutcome.Expression"
            ],
            "expression": [
                "Patient"
            ]
        }
    ]
}

Even if I remove the profile in the request, the mismatched datatypes does not seem to trigger any errors.

Using R4 in Health Data Services workspace.

[evachen96]

Hi @rajyraman - the observed behavior aligns with the current, more permissive implementation of the FHIR server. Looking ahead, we intend to adopt validation practices more closely aligned with validator.fhir.org. However, this enhancement is currently in the backlog.