Issues with new R4 FinancialTransaction resource.

[Sam Kim]

I am trying to make a Postman request to POST a FinancialTransaction using the example request body found in the documentations, but I am getting this response back:

{

    "resourceType": "OperationOutcome",

    "issue": [

        {

            "severity": "error",

            "code": "not-found",

            "details": {

                "text": "Resource not found"

            }

        }

    ]

}

I made sure to include system/FinancialTransaction.write and system/Basic.write in the scope when retrieving the bearer token prior to the POST call to "https://fhir-ehr.sandboxcerner.com/r4/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/Basic".

Any ideas on what else I could be doing wrong?

Thanks,

Sung Kim

[Benjamin Eichhorn (Cerner)]

Hi Sam,

Per our group guidelines, could you please post the X-Request-Id associated with your request? This is returned in the headers of the response. 

Thanks,

Ben (Cerner)

[Sam Kim]

Hi Benjamin,

Here's my X-Request-Id associated with my request: 143eb137b7bac020c9436c0b041b4c52.

Thanks!

[Keifer Laverty (Cerner)]

Hey Sam,

It looks like the Encounter ID being used in the 'Target' extension field in the request body is invalid. The requests we use in our fhir.cerner.com documentation are non-normative so this encounter id will need to be changed. Currently there is no good way to get valid financial encounter ids, but we are working on publishing a list of financial encounter ids that will work for Financial Transaction. In the mean time here are a few Encounters that should work:

• 4721908
• 4703907
• 4723906
• 4723905
• 4715906

Hope this helps!

[Sam Kim]

Hi Keifer,

This information was very helpful; however, I'm getting a 422 Unprocessable Entity error now with the request-id: ca961f8b0dec778ac7f9e9a18c962a14. Is there anything else I need to fix?

[Keifer Laverty (Cerner)]

Hi Sam,

This looks to be a problem with the location field. The location for Financial Transactions are client configured locations that identify the place that the bill was posted from. However, currently there are no location IDs in this domain. The location field is also optional, so for now I would omit the location field all together, and that should allow you to continue testing.

We will work on making sure there are locations in this domain soon so you are able to test with the location present as well.

[Sam Kim]

Keifer,

Thanks for the prompt response, using your advice I was finally able to get a 201 response.