Data Holder cache update periods

Question

The Consumer Data Standards (CDS) outline metadata cache update periods in the section Participant Statuses,  Metadata Cache Management,  Cache Update Periods.

SoftwareProduct and DataRecipient statuses can be retrieved through respective APIs GetSoftwareProductsStatus and GetDataRecipientsStatus. Given this:

• If a Data Holder (DH) has scheduled status retrieval through these APIs between 2-5 minute intervals, then is it necessary to poll GetDataRecipients every 2-5 minutes too? Or can GetDataRecipients be scheduled to be polled every 6 hours to retrieve all other information on the Accredited Data Recipient (ADR)?
• If the status of an ADR Brand does not impact DH responsibilities due to the cascade rules, then is it true that the DH does not require to retrieve the ADR brand status in 2-5 minutes intervals, as this will be covered by polling GetDataRecipientsStatus and GetSoftwareProductsStatus APIs?

Answer

GetDataRecipients is optimised for the presentation of ADR and its associated information on the Data Holder dashboard. This API should be called on a periodic basis to keep the dashboard up-to-date. This data changes infrequently, so the DSB recommends a 6-hour poll interval for this API.

Any changes in ADR statuses warrant a quick reaction. DH responsibilities are tied to the status APIs, such as GetSoftwareProductsStatus. The status APIs need to be called frequently to allow for the DH platform to react within 2-5 minutes. This is why the DSB recommends a polling interval from 2-5 minutes.

The DH is not required to retrieve brand status in 2-5 minutes intervals.