Appointment Status Update

[Shilpa sunil kumar]

Hi,

I am trying to update Appointment status using Hl7.Fhir.Rest Update API.

I am setting versionaware to true and also the passing the Etag header.

I get a response : 

Operation was unsuccessful because of a client error (NotFound). OperationOutcome: Overall result: FAILURE (1 errors and 0 warnings)

[ERROR] Not Found.

can someone please help me identify the issue here.

[Cerner FHIR Developers]

Hi, 

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

Thank you.

[Shilpa sunil kumar]

 

Hi,

I am unable to get the response headers as I am trying to update the patient name using Fhir.Rest API Update and I get an exception as`

Hl7.Fhir.Rest.FhirOperationException: Operation was unsuccessful because of a client error (NotFound). OperationOutcome: Overall result: FAILURE (1 errors and 0 warnings)

[ERROR] Not Found.

at Hl7.Fhir.Rest.TaskExtensions.WaitResult[T](Task`1 task)

I get the same exception for Appointment Update as well.

  

The code which i  do for patient update is similar to the below code.

var client = new FhirClient(new Uri("<cerner sandboxurl>/patient/"));//create client with Patient.read token

var patEntry = client.Read<Patient>("1");

var pat = patEntry.Resource;

pat.Name.Add(HumanName.ForFamily("Kramer").WithGiven("Ewout"));

client = new FhirClient(new Uri("<cerner sandboxurl>/patient/"));//create client with Patient.write token

client.Update<Patient>(patEntry); 

Need help on the same. None of the updates are working when I try using the REST API Update.

 

I am able to perform Search and Read  API operations but Update does not work for me. Please help me identify If I am missing something here.

Note: I do pass seperate bearer token for read(Patient.read)  and update(Patient.write)

          

[Benjamin Eichhorn (Cerner)]

Hi,

You should be able to pull the X-Request-Id header either through debugging or by using Chrome Developer Tools or other browser equivelents (if your app and calls are made client side) and go to the "Network" tab and locate the specific request made and identify the X-Request-Id header. Unfortunately we won't be able to assist in regards to your request unless with have this header.

Thank you,

Ben (Cerner)

[Michele Mottini]

Does the Read<Patient>() even succeeds? Because this:

    new FhirClient(new Uri("<cerner sandboxurl>/patient/"));  

appears to be wrong, you should specify the FHIR base URL, not the Patient resource one

  - Michele

  CareEvolution Inc

--
You received this message because you are subscribed to the Google Groups "Cerner FHIR Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cerner-fhir-devel...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cerner-fhir-developers/906c303a-b0ed-4554-98be-c56cee3bad09%40googlegroups.com.

[Shilpa sunil kumar]

Hi Michele,

Yes. Read succeeds and I get the Patient resource as well.

new FhirClient(new Uri("https://fhir-ehr.sandboxcerner.com/r4/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/patient/"));  is the Url i use.

client.Read<FhirModel.Patient>("Patient/" + PatientId);

returns the patient resource as response for the above Read API Call.

Only the Update and ValidateUpdate API Calls, I am unable to get proper response and get the FhirOperationException.

[Shilpa sunil kumar]

Hi Ben,

I am trying to do a Patient resource update using ValidateUpdate API Call (FHIR REST API Call), I get the below error

Hl7.Fhir.Rest.FhirOperationException: Operation was unsuccessful because of a client error (NotFound). OperationOutcome: Overall result: FAILURE (1 errors and 0 warnings)

[ERROR] Not Found.

with, X-Request-Id for the Patient Update API Call : "ea5fd5a9581769129d866b7533ee8252" 

Note: Read, Search API Calls(Fhir Rest API Calls) get through for the Patient resource.

Thank you,

Shilpa

[Benjamin Eichhorn (Cerner)]

Hi,

It looks like you making a POST to https://fhir-ehr.sandboxcerner.com/r4/0b8a0111-e8e6-4c26-a91c-5069cbc6b1ca/Patient/4342009/$validate.

We do not support this operation currently which is why you received a 404.

Thank you,

Ben (Cerner)

[Shilpa sunil kumar]

Hi Ben,

Yes. I am trying to make an Update API call to update patient details.

I assume, U mean to say REST FHIR Api Update/ValidateUpdate is not supported by Cerner. 

When you say currently not supported, by when will it be available or can i expect it any time soon since, the Rest API Update is far more simpler to use for me.

Thanks,

Shilpa

[Benjamin Eichhorn (Cerner)]

Hi Shilpa,

We do support updating Patient's via the Patient PATCH operation, but we don't support the validate operation for any resource. You can read more about our documentation on Patient PATCH on fhir.cerner.com[1] as well as our other support operations. We do not comment on timelines in this group.

[1] https://fhir.cerner.com/millennium/r4/individuals/patient/#patch

Thanks,

Ben (Cerner)

[Shilpa sunil kumar]

Hi Ben,

Thank you for the response.

I am able to do the PATCH operation for patient as mentioned in the link above. I am unable to do the same via Update Rest API.

As you said Validate is not supported, I tried with just Update, but get a 404- Not found. I would like to know if the Update Rest API is supported by Cerner.

This is the X-Request-Id : "1471bc50c18504b38bb837eba6363491"  for updating Patient resource via Update REST API.

Reason why I am asking is I am able to do Read, Search REST API Calls and get the response, only for the Update I am facing the issue for other resources also like Appointment.

Thanks,

Shilpa

[Benjamin Eichhorn (Cerner)]

Hi Shilpa,

As previously mentioned, we support updating Patient (as well as several other resources in R4) through the use of a PATCH operation. This is the only supported method of updating a Patient. Your call resulted in a 404 because you attempted a PUT rather than a PATCH. Please read through our documentation previously linked.

Thank you,

Ben (Cerner)

[Shilpa sunil kumar]

Hi Ben,

Thank you, I tried changing the MethodType to PATCH and also am sending the If-Match headers.

I am getting Bad Request Error.

The X-Request-Id is "1ef77965b96b22780c7f0b04e2e2b62f".

Or 

Is it because I am sending the entire patient resource in the request body instead of the way it is mentioned in the link (with only the required parts that needs to added/replaced), that it fails?

Can you please help me out with this.

Thanks,

Shilpa

[Benjamin Eichhorn (Cerner)]

Hi Shilpa,

Yes, that is the issue. The OperationOutcome (error message) you received should generally help indicate where/what you need to alter your request to resolve issues you may be having. You will need to follow the RFC specification as we have linked on that documentation.

Thanks,

Ben (Cerner)