Stream: fhir/infrastructure-wg
Topic: Agenda item for when Grahame's back
Josh Mandel (Aug 09 2021 at 18:38):
CapabilityStatement2 -- we've consistently said we need community feedback on the proposed "features" data model + APIs, but it hasn't risen high enough on anybody's TODO to actually run a connectathon track or otherwise drive feedback.
1) In the absence of testing or feedback, do we default to "yes, upgrade to CapabilityStatement2 in R5" or do we default to "stick with the current CapabilityStatement in R5"?
2) Assuming testing and feedback are important here, should we make some concrete plans?
Lloyd McKenzie (Aug 09 2021 at 21:02):
I think bringing CapabilityStatement2 in un-tested would be a bad idea. But not sure how to increase it on enough folks' priority lists to get testing done.
Last updated: Apr 12 2022 at 19:14 UTC
