Stream: Da Vinci
Topic: API Versioning
Mark Neumuth (Nov 17 2021 at 20:03):
We recently worked with a 3rd Party Application that was not able to handle APIs with different versions. Our solution was to change all APIs using the Patient Access base URL to v2. Going forward anytime we move to a new version with one API we will ensure all other APIs using that same base URL are also moved to that version. However, this should only occur when there is a breaking change within an IG. When discussing with this particular 3rd Party Developer they stated there shouldn't be any versioning since there shouldn't be any changes. We decided to keep versioning of APIs to allow developers the time to adjust to the changes. How are other payers and 3rd party applications handling API versioning?
Josh Mandel (Nov 17 2021 at 20:06):
When you say "v2", do you mean FHIR DSTU2, or v2 of a specific Da Vinci IG, or v2 of your own implementation, or something else?
Mark Neumuth (Nov 17 2021 at 23:58):
I'm referring to the versions of the APIs third party applications call to pull our member data. For example: apif1.aetna.com/fhir/v2/patientaccess/ExplanationOfBenefit
Josh Mandel (Nov 18 2021 at 02:53):
But what does "2" reflect in this example?
Last updated: Apr 12 2022 at 19:14 UTC
