Getting the InternalServerError during Update Appointment API call.

[kaushikprovidertech]

I am getting the Error while doing Appointment Update API call.

My application was working with the version. 22 but we migrated from 22 to 23 and same API call is failing and return me the Internal Server Error.

Here is the details what I am doing,

We are using Hl7.Fhir.DSTU2 Nuget C# library to work with the Athena APIs.

We are able to get the Appointment like

await fhirClient.ReadAsync($"Appointment/{appointmentId}");

We are changing the status of the Appointment to Booked or Cancelled like below

appointment.Status = FhirAppointment.AppointmentStatus.Booked;

When we try to update the Appointment status using API like below.

await fhirClient.UpdateAsync(appointment);

On Above API call we always getting the Below Error. This was working fine with the version 22 but stopped working after version 23

Operation was unsuccessful, and returned status InternalServerError. OperationOutcome:

Outcome null

# Severity Type Detail 1 ERROR PROCESSING

. .

SOME STRANGE - When I checked the same appointment from the Athena Software - then status of the Appointment is changed to Booked, but in API it return false.

[AjeetYadav07]

Please refers to the github issue 165 , having detailed information on creating appointment. I hope you creating appointment with locationId but it should be facilityId as participant. Sample payload is also attached for the same.

[kaushikprovidertech]

Please refers to the github issue 165 , having detailed information on creating appointment. I hope you creating appointment with locationId but it should be facilityId as participant. Sample payload is also attached for the same.

I am not creating the Appointment, I am fetching the appointment, and posted same payload which I received during the get call with just update the status.

[AjeetYadav07]

@kaushikprovidertech,

Please refer to the Github issue 294 and Github issue 295.

[deepaktiwari29]

Hello @kaushikprovidertech, hoping we have answered your question. Marking this issue as closed, if you have any further questions, please open a new ticket.