Profile Extensions Not Being Validated

[edwinnswift]

I have a profile on Practitioner that includes extension definitions as follows

The profile structure definition has been uploaded to the server, as well as each extension structure definition. I also have a slice on identifier as illustrated above. If I try to create the Practitioner resource without the required identifier I get the expected operation outcome. However, if I make one of the extensions mandatory, I do not get the same result. Furthermore, if I attempt to create the extension with a type other than what is defined (e.g. valueString vs valueReference) I do not receive a negative outcome.

Clearly the profile is defined correctly since the identifier is being validated. Am I missing something with the extensions?

[EXPEkesheth]

@edwinnswift, could you please provide steps to reproduce the issue? We would also like to understand how you are using the $validate operation. For more information on the validation operation, please see the documentation link.

[edwinnswift]

Thanks for the follow up @EXPEkesheth , I actually got this working. One of the extensions tied to the profile had a url change after the extension was applied to the profile. I updated the profile with the proper definition and it started validating. I would have expected an outcome that the structure definition could not be found, but did not get one.

As for how I am using $validate, I am passing the x-ms-profile-validation header on create and update. Seems to be working as expected now. Thank you!

[EXPEkesheth]

Closing issue as it is working as expected