search

ehealthplatformstandards / BelgianProfileVersioningStrategy

How will we handle the coexistence of different profile versions for the same resource
0 stars 0 forks source link

How to expose StructureDefinitions #6

Closed bdc-ehealth closed 1 year ago

bdc-ehealth commented 1 year ago

from #1 @smals-bvv We can expose StructureDefinitions on the server: but can we say what StructureDefinitions are supported and what not? Or do we only expose the supported StructureDefinitions, like the property in the CapabilityStatement 'supportedProfile'?

bdc-ehealth commented 1 year ago

Like you indicate, I would use: http://hl7.org/fhir/R4/capabilitystatement-definitions.html#CapabilityStatement.rest.resource.supportedProfile . This is a canonical reference, which means that you can include the version. It is not necessary to expose the structuredefinitions of the profiles, as you can refer to the published IG.

bdc-ehealth commented 1 year ago

This is coherent with our decision in #7.