FHIR Chat · CapabilityStatement with $operations · conformance

Stream: conformance

Topic: CapabilityStatement with $operations


view this post on Zulip John Moehrke (Jul 08 2019 at 13:11):

When writing a CapabilityStatement (e.g. for a server) to indicate that there is support/use of an operation (e.g. $docref), should the CapabilityStatement also indicate support for the resources that operation includes (e.g. DocumentReference, Patient, Practitioner, etc..)? Or is just the CapabilitySttement of the operation sufficient? This is especially interesting to me for CapabilityStatement as a 'requirements' .kind

view this post on Zulip Eric Haas (Jul 08 2019 at 15:06):

The operationdefinition defines the requirements so i have always treated it as transitive statement of conformance.

view this post on Zulip John Moehrke (Jul 08 2019 at 15:42):

that was my thinking... Others?

view this post on Zulip Bryn Rhodes (Jul 27 2019 at 20:45):

My thoughts are that it should declare conformance for the resources it supports, independent of the operation, for two reasons. 1) The capabilities you can declare for the resource are broader than what could be inferred from the requirements of the operation, and 2) It may well be the case that you can accept a resource as a paramter to an operation, but not support anything else about it.

view this post on Zulip John Moehrke (Jul 30 2019 at 19:06):

hmmm. so we have a stalemate... need more people to weigh in


Last updated: Apr 12 2022 at 19:14 UTC