Communication of Changes in Data Access API, Data Share, and Analytics

Revenera is committed to addressing customer requests and enhancement suggestions by expanding the existing Data Access API, the Data Share, and Analytics functionality. To keep customers informed, any modifications resulting from these requests are managed and communicated as follows.

Refer to the following sections for details:

•

Addition of Fields and Columns

•

Modification or Removal of Fields and Columns

•

Consumer Implementation Requirements

Addition of Fields and Columns

Any additional fields or columns required for enhancing data accessibility or extending functionality are incorporated directly into the existing version of the Data Access API and Data Share views.

There is no impact on the Analytics functionality, as any newly added fields will not appear in reports by default. Customers can choose to include them as needed.

These changes will not be announced prior to implementation; however, any schema modifications will be documented and communicated through release notes.

Modification or Removal of Fields and Columns

If any fields or columns need to be modified or deprecated due to architectural changes, compliance updates, or optimization efforts, a structured communication approach is followed:

•

Stakeholders will be informed well in advance through official communication channels (release notes, documentation updates).

•

Depending on the nature of the update, a new API version will be introduced.

•

Legacy versions will be maintained for a defined period to facilitate migration.

Consumer Implementation Requirements

To avoid any integration breakage, customers are required to implement their consumers as follows:

•

Ensure consumers ignore unknown fields or column in the Data Access API and Data Share.

•

Adopt robust parsing logic to improve data integrity, such as using keys and names instead of relying on indexes or hard-coded structures.