Stream: dotnet
Topic: Validation error
Yunwei Wang (May 11 2018 at 22:13):
I updated my Nuget package to the latest 0.95. When I run my test cases, I got a strange validate error:
Method not found: 'System.String Hl7.Fhir.Model.ModelInfo.CanonicalUriForFhirCoreType(Hl7.Fhir.Model.FHIRAllTypes)'.
Stack Trace:
at Hl7.Fhir.Validation.ProfilePreprocessor..ctor(Func`2 profileResolver, Func`2 snapshotGenerator, IElementNavigator instance, String declaredTypeProfile, IEnumerable`1 additionalProfiles, IEnumerable`1 additionalCanonicals) at Hl7.Fhir.Validation.Validator.Validate(IElementNavigator instance, String declaredTypeProfile, IEnumerable`1 statedCanonicals, IEnumerable`1 statedProfiles) at Hl7.Fhir.Validation.PocoValidationExtensions.Validate(Validator me, Base instance) at IMO.FhirTerminologyService.Business.Tests.CapabilityStatementTests.CapabilityMetadata()
Yunwei Wang (May 11 2018 at 22:18):
Another question about Simplifier, I uploaded my capability json, and the validation failed. It complained about this canonical url:
"profile": "http://hl7.org/fhir/StructureDefinition/OperationDefinition",
Encountered unknown member 'value' while de-serializing (at path 'line 58, pos 82')
And I noticed the FHIR Version shown as STU3 though the capability statement has
"fhirVersion": "3.3.0",
Yunwei Wang (May 11 2018 at 23:40):
Found the cause. Hl7.Fhir.Specification.R4 on Nuget has older version 0.94. Why was 0.95 unlisted from Nuget?
Michel Rutten (May 12 2018 at 07:34):
@Ewout Kramer ?
Brian Postlethwaite (May 12 2018 at 07:43):
I didn't think the R4 Spec project was sent to NuGet yet.
Brian Postlethwaite (May 12 2018 at 08:50):
That questionnaire posts to here ok
sqlonfhir-stu3.azurewebsites.net/fhir/Questionnaire/3507478
Ewout Kramer (May 12 2018 at 13:51):
The problem is that we should have never published a Specification.R4 - So, I should unlist 0.94 too ;-) There is no functional version of the R4 Specification library - it merely compiles.
Yunwei Wang (May 12 2018 at 14:42):
@Ewout Kramer I use Hl7.Fhir.Validation.Validator in my test project to validate that FHIR resources returned are valid. If Specification.R4 should not be used, any other way to validate a resource?
Ewout Kramer (May 12 2018 at 14:43):
I am sorry, but you cannot yet validate in R4, we will work on that over summer....
Brian Postlethwaite (May 12 2018 at 14:43):
On the .net Stack, there is no current R4 validator ;)
Yunwei Wang (May 12 2018 at 14:46):
Ha. That is why that nuget package says "The owner has unlisted this package. This could mean that the package is deprecated or shouldn't be used anymore." :grinning:
Ewout Kramer (May 12 2018 at 14:47):
Yep ;-) Published by accident. Mea culpa ;-)
Yunwei Wang (May 12 2018 at 14:51):
Make Sense. OK. I will remove those validations from my testing project for now.
Last updated: Apr 12 2022 at 19:14 UTC