Cerner FHIR capability statement

[Michael Gleason]

Can you point me to the Cern FHIR Capability Statement?    Need this for Expected data that Cerner will be sending in the FHIR Spec. 

[Benjamin Eichhorn (Cerner)]

Hi Michael,

All of the functionality for our server (including the Conformance [DSTU2] and CapabilityStatement [R4]) are documented on https://fhir.cerner.com/. This includes how to call them.

In general, you should be able to hit the "metadata" endpoint for any FHIR server to pull capabilities. See https://www.hl7.org/fhir/dstu2/http.html#conformance and https://www.hl7.org/fhir/http.html#capabilities

Thanks,

Ben (Cerner)

[john forbes]

i'm trying to learn how to cross reference the  capability statement  from  https://fhir-open.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/metadata back to the supported actions from  http://fhir.cerner.com/millennium/overview/#supported-versions.  it appears that a supported action for observations is update.  I was expecting that the  capability statement ( first link) would show for type Observation  within  interaction a "code":"update" or something similar.  See attached for a visual. Any advice on how to relate these two together would be appreciated - J

[Fenil Desani (Cerner)]

You are using open endpoint of our Public Sandbox which, without Authorization, only has the capability of read.

For Create, Update, etc. you need authorization and hence accessible only on closed endpoint.

Try this:

https://fhir-ehr-code.cerner.com/r4/ec2458f2-1e24-41c8-b71b-0e701af7583d/metadata

[john forbes]

yes that works better and aligns to what i expected - thanks  - im attaching a new image that demonstrates this relationship

[Fenil Desani (Cerner)]

Great!