Stream: hapi
Topic: StructureDefinition and OperationDefinition
Michael Lawley (Jun 28 2016 at 04:58):
In our auto-generated Conformance statement /metadata, we are seeing entries for StructureDefinition and OperationDefinition. The latter only supports read and has entries for each of the contained OperationDefinitions in the Conformance resource itself (which is strange, because they could be referenced/linked, and not contained).
The former indicates both read and search-type support. Search returns a single entry for [base]/StructureDefinition/operationoutcome but this doesn't resolve.
We're wondering how/why this is happening and what we can do to fix things
Michael Lawley (Jun 28 2016 at 05:01):
[deleted]
James Agnew (Jun 28 2016 at 13:56):
Ah yeah, the conformance generation post-DSTU1 still has some quirks to it. We put a lot of work getting it perfect for DSTU1 but conformance has been a bit of a moving target ever since so we haven't ever quite nailed it.
If you wanted to file a bug about this in our tracker, great. If you want to know where to look to try and correct it, the conformance statement is generated in a class called ServerConformanceProvider (note that there are 3 versions of this class, one for each FHIR version)
Michael Lawley (Jun 28 2016 at 23:13):
Ah, thanks for that background. We already massage some things via a ServerConformanceProvider subclass, so we'll beef that up as the short-term and raise some issues for the long term
Michael Lawley (Jun 29 2016 at 01:33):
#395 raised becuase we can't see (and remove) the generated OperationDefinitions when overriding ServerConformanceProvider
Last updated: Apr 12 2022 at 19:14 UTC
