ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 27th of April 2023

CDR Implementation Call Banner

Agenda & Meeting Notes

When: Weekly every Thursday at 3pm-4:30pm AEST
Location: Microsoft Teams
Meeting Details: Join on your computer, mobile app or room device Click here to join the meeting
Meeting ID: 446 019 435 001
Passcode: BU6uFg
Download Teams | Join on the web
Join with a video conferencing device
[email protected]
Video Conference ID: 133 133 341 4
Alternate VTC instructions Or call in (audio only)
+61 2 9161 1229,,715805177# Australia, Sydney Phone Conference ID: 715 805 177# Find a local number | Reset PIN
Learn More | Meeting options

Agenda

Introductions
Actions
CDR Stream updates
Presentation
Q&A
Any other business

Introductions

5 min will be allowed for participants to join the call.

Acknowledgement of Country

We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.
We pay our respects to Elders past, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.

House Keeping

Recording

The Consumer Data Right Implementation Calls are recorded for note taking purposes. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material shall be provided without the participant's consent. Participants may [email protected] should they have any further questions or wish to have any material redacted from the record.

Community Guidelines

By participating in the Consumer Data Right Implementation Call you agree to the Community Guidelines. These guidelines intend to provide a safe and constructive space for members to discuss implementation topics with other participants and members of the ACCC and Data Standards Body.

Updates

Type	Topic	Update
Standards	Version 1.23.0 published 14th of April 2023	Version 1.23.0 Change Log
Standards	Proposed next version(s) of the Consumer Data Standards: 1.24.0	Version 1.24.0 is planned to contain changes from Maintenance Iteration 14
Maintenance	Iteration 14 is complete!	All the Meetings notes
Maintenance	Iteration 14 retrospective survey issued	If you were an attendee please take the time to provide feedback
Maintenance	Iteration 15 commences 3rd of May 2023 Invitations sent out	Agenda is being prepared
TSY Newsletter	To subscribe to TSY Newsletter	Link here
DSB Newsletter	To subscribe to DSB Newsletter	Link here
TSY Newsletter	24th of April 2023	View in browser here
DSB Newsletter	21st of April 2023	View in browser here
Consultation	Decision Proposal 229 - CDR Participant Representation	Placeholder: no close date Link to consultation
Consultation	Decision Proposal 267- CX Standards Telco Data Language	Feedback extended with an end date to be determined pending the making of the telco rules. Link to consultation
Consultation	Decision Proposal 275 - Holistic Feedback on Telco Standards	No Close Date Link to consultation
Consultation	Noting Paper 276 - Proposed v5 Rules & Standards Impacts	No Close Date Link to consultation
Consultation	Noting Paper 279 - Accessibility Improvement Plan	No Close Date Link to consultation
Consultation	Noting Paper 280: The CX of Authentication Uplift	UPDATE: See NP296 for continuation of consultation
Consultation	Noting Paper 296 - Offline Customer Authentication	Feedback 1st of May 2023 Link to consultation Video 55 of NP296
Consultation	Noting Paper 289 - Register Standards Revision	Feedback 5th of May 2023 Link to consultation Video 56 of NP289
Consultation	Decision Proposal 302 - Telco Draft Feedback Cycle 2	No Close Date Link to consultation

CDR Stream Updates

Provides a weekly update on the activities of each of the CDR streams and their stream of work

Organisation	Stream	Member
DSB	CX Standards	Amy
DSB	Technical Standards - Energy	Hemang
DSB	Technical Standards - Telecommunications	Brian

Presentation

None this week.

Q&A

Questions on Notice

Questions will be received by the community via Microsoft Teams chat before the questions are opened to the floor. Participants can submit questions outside of the CDR Implementation Call to the CDR Support Portal.

In regards to topics for questions, we ask the participants on the call to consider the Community Guidelines when posing questions to the subject matter experts.

Answer provided

Ticket #	Question	Answer
1951	CDR Data payloads - lastUpdateTime where some fields captured and others are not In data payloads where a "lastUpdateTime" field is included (such as Get Customer Detail) and our source systems only track updates for some of the source data and not others, how should lastUpdateTime be populated? Thus far our suspected options are: 1. Best effort - Use the most recent time available (This will result in some fields being updated without a change to the lastUpdateTime) 2. Do not include - If we cannot reliably provide an accurate lastUpdateTime then do not provide it as it may impact implied functionality for recipients (i.e. if lastUpdateTime is the same as the last time the API was called, do nothing)	The lastUpdateTime field was included as a signal to the recipient that the data has, in some way, been updated or corrected and therefore is much less likely to be stale. In this context the best option is what you have described as the "Best effort" option. The field is only optional because some organisations have zero ability to track the date of change in which case they do not hold this data. As you do hold the data (at least in part) it would be better to populate the field as well as you can.
1952	Data Holder Development Inquiry - Date Format Could you please let us know the format for data values e.g. dd/mm/yyyy or mm/dd/yyyy?	In the Standards under High Level Standards -> Common Field Types: https://consumerdatastandardsaustralia.github.io/standards/#common-field-types You can find we [reference] use RFC3339.