Resolves Default Reason for Visit (RFV) and Note Type Issue on the FHIR Update Payload

Last updated: 19 Apr 2024

We have resolved an issue in our logic that would update appointmentType and RFV to the associated instance’s default values if these values were omitted from the FHIR update payload. Now, if appointmentType or RFV is omitted from the FHIR Update payload, they are ignored in the message consumer to keep the appointment values as is.