Stream: implementers
Topic: FHIR Conformant
Bapi Behera (Apr 16 2021 at 00:50):
To be “FHIR Conformant”, a system MUST publish Capability Statement. What you will answer : True or False
Shamil Nizamov (Apr 16 2021 at 01:02):
Applications SHALL return a resource that describes the functionality of the server end-point.
John Moehrke (Apr 16 2021 at 12:49):
servers, yes... clients, maybe.
Lloyd McKenzie (Apr 16 2021 at 16:23):
Servers must publish one and make it available at the metadata endpoint. Clients and non-RESTful systems don't have to have one, but asserting that your system is FHIR conformant without having a CapabilityStatement that supports that declaration isn't terribly meaningful.
Amit Cudykier (Apr 16 2021 at 19:35):
I would say NO based on the reference below. If I am reading it correctly it says "May be used" meaning you do not necessarily need to have a capability statement. Would you agree?
"A Capability Statement documents a set of capabilities (behaviors) of a FHIR Server for a particular version of FHIR that may be used as a statement of actual server functionality or a statement of required or desired server implementation."
https://www.hl7.org/fhir/capabilitystatement.html#5.2
John Moehrke (Apr 16 2021 at 19:37):
that "may" is a statement that the client may use the servers capabiltiy statement for purpose
John Moehrke (Apr 16 2021 at 19:40):
a server that is supporting REST clearly must support the metadata endpoint (using GET or OPTIONS) and return a conformance resource. This is stated on the http page, not the capabilityStatement page
Amit Cudykier (Apr 16 2021 at 20:21):
Thank you! that makes sense from the client's perspective. From the server (system) perspective the Conformance reference does imply you need CapabilityStatement: "Systems can only claim FHIR Conformance for functionality described in the applicable CapabilityStatement."
http://hl7.org/fhir/conformance-rules.html#2.1.0
Last updated: Apr 12 2022 at 19:14 UTC
