Stream: IG creation
Topic: CapabilityStatement, SearchParameter and OAS Validation
Kevin Mayfield (Feb 26 2022 at 07:09):
I'm exploring FHIR Validation of these.
So for token and date I have this:
Screenshot-2022-02-26-at-07.08.00.png
Kevin Mayfield (Feb 26 2022 at 07:14):
Which as OAS looks like :
Screenshot-2022-02-26-at-07.09.56.png
I have both date and token coming up as arraystring
Where token and date refer to an OAS format type (which doesn't exist) of token and date.
Does this sound correct? Or does a better way exist.
It's showing some gaps in CapabilityStatement, using the above examples. I think I may want to apply a max to CapabilityStatement.rest.resource.searchParam.
So if max is 1 then it is not an array of string.
Kevin Mayfield (Feb 26 2022 at 07:17):
For some FHIR search params in CapabilityStatement I think I may need to specify a ValueSet. So I populate an OAS enum, like I've done automatically for _include or _revinclude.
Screenshot-2022-02-26-at-07.16.31.png
Kevin Mayfield (Feb 26 2022 at 07:21):
The main reason for doing this is to get new to FHIR developers on the right track.
We've had some issues around API definitions being non FHIR conformant, developers building profile specific schemas, etc. Ideally I want to do a validate OAS against FHIR (and probably extend FHIR Validation to do the same around CapabilityStatement, OperationDefinition and SearchParameter resources)
Kevin Mayfield (Feb 26 2022 at 07:24):
p.s. have also started extending OAS info to include FHIR NpmPackage information.
See x-HL7-FHIR-Packages below
Screenshot-2022-02-26-at-07.24.19.png
Last updated: Apr 12 2022 at 19:14 UTC
