[ARCHIVE] Profile Scope and Data Latency

Archived 2023.08.11. Content moved to Guidance on data latency. 

Questions below relate to Profile scope changes introduced in DP216, Profile scope support, which was accepted and forms part of CDS v1.17.0.

Question

Should Data Holders (DHs) support the email, address and phone scope as per OIDC 5.4? Are only the openID and profile scope mandatory and other scopes optional?

Answer

No. These scopes are not supported in the Consumer Data Standards (CDS).

Question

Are there specific CDR requirements for how up-to-date or current the customer data returned via the profile scope must be? For example, is it acceptable to return customer data that was captured at the time of the consent creation?

Answer

The CDS contains non-functional requirements regarding Data Latency. However, regarding the 'up-to-date' nature of information returned, the customer data should be as current as possible, compliant with the OAIC Australian Privacy Principles and follow existing industry regulatory requirements.