V4 Change Log

2021-11-17

2023-11-15

2023-10-11

2023-10-09

2023-08-04

2023-07-26

2023-07-12

2023-05-31

When introducing the preferred_pharmacies field while retaining the default_pharmacy field, we need to ensure backward compatibility. The following behavior will be implemented:

  1. Existing Default Pharmacy:

    • If a patient already has a value set for the default_pharmacy field and the NCPDP ID of the default pharmacy exists in the preferred_pharmacies list, it will be automatically added to the preferred_pharmacies list.  
    • If the NCPDP ID of the default pharmacy does not exist in the preferred_pharmacies list or is an invalid value, the default pharmacy will be set to an empty string in the patient's data.
    • Users will not be able to exclude the default pharmacy directly. They can remove the default pharmacy by either using the UI or removing all pharmacies from the preferred_pharmacies list.
  2. Default Pharmacy Updates:

    • If the default pharmacy is updated, the new value will be automatically added to the preferred_pharmacies list if it is not already present. 
    • If the new default pharmacy is already present in the preferred_pharmacies list, there will be no duplication.

Note: The default_pharmacy field will be deprecated in a future version. It is recommended to use the preferred_pharmacies field to manage the patient's pharmacies. Please ensure that the NCPDP ID of the default pharmacy is valid and exists to avoid the default pharmacy being set to an empty string in the patient's data.

This backward compatibility ensures that the existing functionality of the default_pharmacy field is maintained while allowing users to manage their preferred pharmacies through the preferred_pharmacies list.

2023-05-31

2023-05-12

2022-06-23

2021-10-01

2021-07-08

2020-02-24

2020-02-05

2019-12-13

2019-12-12

2019-12-02

2019-11-15

2019-10-01

2019-09-18

2019-09-17

2019-09-02

2019-08-28

2019-08-09

2019-07-25

2019-07-16

2019-04-04

2019-01-04

2018-10-16

2018-10-15

2018-09-25 From V3

2018-09-18

Starting this day, we will be using a new version naming mechanism. Instead of calling the versions by dates, we will be using numerical versions. Please checkout our version map here for more information.

2019-10-01