Stream: IG creation
Topic: CapabilityStatement and fhir packages
Kevin Mayfield (Jul 30 2021 at 14:46):
We are looking at listing IG packages being used by a server in a CapabilityStatement.
I know we have this CapabilityStatement.implementationGuide
Kevin Mayfield (Jul 30 2021 at 14:47):
but that list is for the IG webpages. I think what we want is something that contains this type of information:
[
{
"packageName": "uk.nhsdigital.medicines.r4",
"version": "2.1.14-alpha"
},
{
"packageName": "uk.nhsdigital.r4",
"version": "2.1.34-discovery"
},
{
"packageName": "UK.Core.r4.v2",
"version": "2.0.8"
}
]
David Pyke (Jul 30 2021 at 14:52):
Are these IGs not published as web pages?
Kevin Mayfield (Jul 30 2021 at 14:53):
Yes but we don't expect users to use the CapabilityStatement for the web pages but it is likely we and users will want to know which IG version they have used (and tested against)
David Pyke (Jul 30 2021 at 15:10):
That would need to be an extension on CapabilityStatement. It may be possible to have the version as part of the canonical (e.g., www.example.org/fhir/IG/2.1.14-alpha) if your and connecting systems can handle that. People would have to then know that the final part matters.
In general, that's not an easy lift
Lloyd McKenzie (Jul 30 2021 at 19:20):
CapabilityStatement.implementationGuide isn't for web pages - it's for the canonical URL of the ImplementationGuide - which can be a versioned or non-versioned reference. It does not depend on any particular package server - or a package server at all.
Kevin Mayfield (Aug 01 2021 at 04:50):
I'm looking at using an extension. Initial mock is here https://simplifier.net/guide/nhsdigital/NHSDigital-CapabilityStatement#apiDefinition
From an apiManangement point of view we are after details of the openApi and IG packges in addition to profiles and messageDefinition's used.
David deRoode (Aug 02 2021 at 14:10):
(deleted)
Last updated: Apr 12 2022 at 19:14 UTC
