Performer required for vital sign observation

[Shelby Smith]

I have measurements taken by patients themselves and recorded into another system. I want to create those same values as Observations in the cerner FHIR server, but there is not a practitioner involved in taking the measurement although it is required to specify a practitioner performer on Observation creation.

How is it possible to do?

[Aaron McGinn (Cerner)]

The Observation.performer is not required [1] [2], so you don't have to provide it.

[1] https://fhir.cerner.com/millennium/r4/diagnostic/observation/#create-performer

[2] https://hl7.org/fhir/R4/observation.html#resource

-Aaron (Cerner)

[Shelby Smith]

The first link under the notes says:

• Vital Signs require performer.

I'm trying to add a vital signs Observation performed by a patient.

[Shelby Smith]

The data would be gathered by a device that the patient uses and sent to the EHR.

[Brij Shah]

Hi,

I think you're trying to perform creating vital sign Observations through patients which we currently do not support.

As you can see on our official documentation[1] we currently only support system authorization when creating vital sign observations.

Thanks,

Brij

[1] https://fhir.cerner.com/millennium/r4/diagnostic/observation/#authorization-types-2

[Shelby Smith]

I am not trying to create through patients. I am authenticating with a system account and the following scope: "system/Observation.read system/Patient.read system/Observation.write".

I was going to send the request id and payload, but any time I attempt to post, I receive a 502 Bad Gateway response:

{

    "resourceType": "OperationOutcome",

    "issue": [

        {

            "severity": "fatal",

            "code": "exception",

            "details": {

                "text": "Bad gateway"

            }

        }

    ]

}

X-request-Id: 8efeb8ba-3505-4650-ba7e-ebcf1e7b0b30

[Shelby Smith]

I'm still having this issue. Just wondering if there is anyone looking into it?

[Brij Shah]

Hi,

Can you give it a fresh try and send us x-request id if it does not work? There could be some intermittent issues with the server but everything seems to be up and working currently.

Thanks,

Brij

[Shelby Smith]

It still seems to give the same error. It did work at some point, weeks ago when I started the post. 

I will add that the request is being sent from Denmark.

I've attached the curl request minus the access token.

Here are the response headers:

Content-Type: application/fhir+json; charset=utf-8

Content-Length: 118

Connection: keep-alive

Date: Mon, 15 Feb 2021 20:22:03 GMT

Cache-Control: no-cache

Server-Response-Time: 1828.996275

Vary: Origin

X-Request-Id: 710ad4d9-6ba2-42f3-81cb-803ce27da8ed

X-Runtime: 1.828888

X-Cache: Error from cloudfront

Via: 1.1 1ebf52f5e79648444025879af65610d2.cloudfront.net (CloudFront)

X-Amz-Cf-Pop: CPH50-C1

X-Amz-Cf-Id: c5ZsJ2vdcJx_8LVzwCMDPgFkX02WDOwSdQsAP-Fh3P_ARgU3t56pfw==

And the response body:

{"resourceType":"OperationOutcome","issue":[{"severity":"fatal","code":"exception","details":{"text":"Bad gateway"}}]}

Thanks,

Shelby

[Brij Shah (Cerner)]

Hi,

Apologies for the delay, we have made some enhancement and this issue should be resolved now. Can you give it a try?

Let us know if you're still facing any issues.

Thanks,

Brij

[Shelby Smith]

I get a different error.

Here are the response headers:

Content-Type: application/fhir+json; charset=utf-8

Content-Length: 149

Connection: keep-alive

Date: Thu, 04 Mar 2021 09:51:22 GMT

Cache-Control: no-cache

Server-Response-Time: 572.6020480000001

Vary: Origin

X-Request-Id: c121aa3b-016b-44b0-84fc-f1dec9b1cd62

X-Runtime: 0.572534

X-Cache: Error from cloudfront

Via: 1.1 1ebf52f5e79648444025879af65610d2.cloudfront.net (CloudFront)

X-Amz-Cf-Pop: CPH50-C1

X-Amz-Cf-Id: uldiVkJuBLk1UOmQETFrZ2PeDhuNdrZcLF27oQ4xCw-oGtBvv6UZUQ==

Response body:

{"resourceType":"OperationOutcome","issue":[{"severity":"fatal","code":"exception","details":{"text":"Internal service error from resource store"}}]}

[Aaron McGinn (Cerner)]

Sorry for the missed response. Is this error still occurring for you? If so, can you provide a new X-Request-Id to help us investigate?

-Aaron (Cerner)