I was having an issue where the latest version of this SDK was throwing an error when trying to parse Patient ML model run objects after fetching them from the server. The SDK is outdated and doesn't include new fields that have been added to the Patient ML API. The SDK should just ignore those unsupported fields when parsing, instead of throwing an error.
This PR fixes the "not forwards compatible" bug in the Patient ML client. In a follow-up PR I'll regenerate the Patient ML client to match the latest Patient ML service schema.
I was having an issue where the latest version of this SDK was throwing an error when trying to parse Patient ML model run objects after fetching them from the server. The SDK is outdated and doesn't include new fields that have been added to the Patient ML API. The SDK should just ignore those unsupported fields when parsing, instead of throwing an error.
This PR fixes the "not forwards compatible" bug in the Patient ML client. In a follow-up PR I'll regenerate the Patient ML client to match the latest Patient ML service schema.