Stream: fhir/infrastructure-wg
Topic: Rework of CapabilityStatement
Grahame Grieve (May 28 2019 at 01:31):
I have started the process of reworking CapabilityStatement by publishing http://build.fhir.org/capabilitystatement2.html#resource, which is the current CapablityStatement with most non-normative content removed
Grahame Grieve (Sep 22 2020 at 17:30):
I have got the updated CapabilityStatement2 publishing now - see http://build.fhir.org/capabilitystatement2.html
This contains an early and rough draft of what a reworked CapabilityStatement would look like, orientated towards feature negotiation rather than adding more and more flags around system behavior.
Grahame Grieve (Sep 22 2020 at 17:31):
FHIR-I discussed this in committee yesterday, and agreed to follow up discussion here, along with a connectathon around this in January.
Grahame Grieve (Sep 22 2020 at 17:31):
this is the place for the discussion.
Vassil Peytchev (Sep 22 2020 at 17:40):
The current proposal is focused on the REST API - are other APIs in scope? Since OperationDefinition covers operations, would features be appropriate there as well?
Grahame Grieve (Sep 22 2020 at 17:45):
yes, I think features are appropriate in OperationDefinition and SearchParameter too.
Grahame Grieve (Sep 22 2020 at 17:46):
I'm not sure about other APIs. What other API are you interested in? As far as I know, all the potential APIs we could talk about fall under CS+OD+SP?
Bryn Rhodes (Sep 22 2020 at 19:59):
I can see a use for it in Library, we are currently exposing similar functionality for CQL (what features of the language are required to run this expression, and what capabilities does this engine support).
Last updated: Apr 12 2022 at 19:14 UTC
