Coverage Order

[Hieu Trung Tran]

Hi Supporters,

When adding coverage as the following order:

#1 - create a new private patient level

#2 - create a new public patient level

#3 - create a new private patient level

After get back data, Cerner API returns a new order that doesn't match with creation, as following:

#1

#3

#2

I mean the public coverage is always put down. Do we have any way to keep the original order the same with creation?

Thanks!

[Hieu Trung Tran]

Hi Supporters,

Could you please review this question and let me know the rule of Coverage ordering?

Thanks!

[Thanh Xuan Nguyen]

Hi Cerner team,
Do you have any updates for the rule of Coverage ordering?
What is the primary indicator for the order of the insurance records that we send to Cerner?

Thanks,
Thanh

[Nishanth Namana (Cerner)]

Hello thanhxnguyen and hieuttran,

This is Nishanth from Cerner Support. I'm currently checking this with our team. I'll post you a response once I have an update on your question.

Thank you,

Nishanth Namana (Cerner).

[Long Thanh Do]

Hi Cerner team,

Do you have any updates on this issue so far?

We are looking forward to your response.

Thanks,

Do Thanh Long

[Long Thanh Do]

Dear Nishanth,

We really look forward to your feedback on this question.

Please let us know if there is any update.

Thanks a lot,

Do Thanh Long

[Nishanth Namana (Cerner)]

Hello Do Thanh Long,

I checked with our team and this is what I found. FHIR Coverage API always return Private Coverages first followed by Public Coverages. This is because, in Millennium both are stored in separate tables. So, FHIR first retrieves the private coverages and then retrieves the public coverages.

Does this answer your question? Please let me know if you any other questions.

Thank you,

Nishanth Namana (Cerner).

 

[Thanh Xuan Nguyen]

Your information is very helpful.

We still have one question. What is the primary indicator for the order of the insurance records that we send to Cerner?

In our system, a patient can have a list of coverages and each coverage of this patient has a field called "Order Number". When integrating with other system, we can use the order number to identify a coverage and then check if this coverage is modified or not.

Let say an example:

A patient "XYZ" has 3 new private coverages: A, B, and C.

Our system will call Cerner API 3 times - https://fhir.cerner.com/millennium/r4/financial/support/coverage/#example---patient-level-private-coverage-1

• Step 1: Call Create API to create coverage A
• Step 2: Call Create API to create coverage B
• Step 3: Call Create API to create coverage C

Then, I want to get a list of coverages of patient "XYZ". I will call this API to search coverage https://fhir.cerner.com/millennium/r4/financial/support/coverage/#example---patient-level-private-coverage

Does Cerner support to store the order number of patient's coverage? Is there any way to have an indicator for the order of the insurance records?

Is the order of coverage records from Search API the same as the order of coverage records that I called Create API?

Thanks,

Thanh Nguyen

[Long Thanh Do]

Dear Cerner team,

We still have one question that Mr. Thanh has replied to above and we are really looking forward to your answer.

Please, let us know if there is any update.

Thanks,

Do Thanh Long

[Nishanth Namana (Cerner)]

Hello Thanh Nguyen and Do Thanh Long,

No, unfortunately Cerner doesn't not support storing the order number of patient's coverage. Also the ordering of coverage records is not guaranteed in Search API.

Thank you,

Nishanth Namana(Cerner).

[Long Thanh Do]

Hi Nishanth,

Thank you for your feedback. We really appreciate that.

Have a great day!

Thanks,

Do Thanh Long