Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Incorrect $validate OperationDefinition in generated Conformance resource #379
We have three Providers (ConceptMap, ValueSet, and CodeSystem) that each implement both type and instance $validate with @Validate annotations, however the single OperationDefinition included in the Conformance metadata resource lists the type of the resource parameter as CodeSystem.
It also lists 6 entries for type (two per resource type). It seems that the type/instance distinction is being lost somewhere.
Only in parameters are generated; no out parameter.
Finally, instance is set to true, but the defn seems to cover both type and instance (as per 6 type values); should there be separate OperationDefinitions for each?
This is an interesting issue.
The definition of
This seems worth raising on the FHIR channels for clarification, but based on the current wording I don't think it makes sense to split the instance/type definitions into 2. Thoughts?
Will commit a fix to the first part shortly.
Added discussion here: https://chat.fhir.org/#narrow/stream/implementers/topic/Operations