-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CX Guidelines | Updates stemming from 2024 Consent Review changes #674
Comments
We’re pleased to share for consultation the following draft guidance:
We invite community feedback via this thread. Your input, questions and comments will help us refine the guidance, allowing us to expedite their release following the finalisation of the rules and standards. Please remember that this guidance is shared in draft state, representing proposed rules and standards that have not been made. This should not be taken as definitive guidance of compliance, and should not be considered as legal or compliance references for the purpose of implementation. The original post has been updated to include these links. |
Following the making of the amended rules and new standards, the DSB has prepared additional draft guidance for community feedback. In response to past requests for more descriptive information on what has changed in each release, we have provided draft Change Log wording below. We have also used symbols and markup in the annotations frame in Figma to help clarify what type of change has been made to the annotation. Please refer to the key at the top of the annotations frame for more details. Note that this format will only be used during this consultation window. Finalised and published guidance on the cx.cds.gov.au website will not include this level of detail. We seek feedback on the Change Log and marked up annotations, and whether participants find these valuable. Consent Management (Data recipient): Collection and use - Default example Updated CX artefacts and requirements relating to Consent Management (Data recipient): Collection and use - Default example. This includes:
We invite community feedback via this thread. Please remember that this guidance is shared in draft state. This should not be taken as definitive guidance of compliance, and should not be considered as legal or compliance references for the purpose of implementation. The original post has been updated to include these links. The CX team are working to finalise additional draft CX guidelines to reflect the published rules. These will be posted here in the coming weeks for community input. |
The DSB has prepared additional draft guidance for community feedback. As outlined in the previous comment, we are providing draft Change Log, as well as using symbols and markup in the annotations frame in Figma to help clarify what type of change has been made to the annotation. We seek feedback on whether participants find these artefacts valuable for consultation. Collection and Use: Default example
Collection and Use: Using outsourced service providers Updated CX artefacts and requirements relating to Collection and Use Consent: Using outsourced service providers. This includes:
We invite community feedback via this thread. Please remember that this guidance is shared in draft state. This should not be taken as definitive guidance of compliance, and should not be considered as legal or compliance references for the purpose of implementation. The original post has been updated to include these links. |
We have made minor amendments to annotations in the following flows, primarily to clarify transitional provisions and effective dates. [NEW] Notifications: CDR Receipts
[NEW] Notifications: 90 day notifications
Collection and Use: Using outsourced service providers
|
Description
In August 2024, the Treasury conducted a consultation on proposed consent and operational enhancement amendments to the CDR Rules. The DSB simultaneously consulted on Decision Proposal 350 to outline the expected changes to the standards to support the proposed rules.
This issue outlines the anticipated updates to the CX Guidelines that will be required to reflect the expected rules and standards changes.
The community are invited to provide feedback on these draft CX guideline changes ahead of any final rules or standards changes to expedite their release. Additional requests for guidance to support the proposed rules and standards can also be made in this thread.
The final CX guidelines will necessarily adjust to the final rules or standards, and as such these draft artefacts are subject to change and should not be interpreted as finalised guidance.
N.B. the draft CX guidelines only outline where a proposed rule and standards change has an associated user interface or consumer experience component. As noted in DP350, CDR agencies will not provide guidance on the proposed nominated representative changes until any relevant rules are made.
Intention and Value of Change
The DSB publishes CX guidelines to assist participants with implementation of the CDR. The publication of draft CX Guidelines will allow the community to provide feedback on proposed changes and seek further clarifications where necessary.
Consulting on these draft guidelines before the associated rules and standards are finalised will allow their release to be expedited to facilitate implementation. The final artefacts will be published on the CX Guidelines website pending this consultation and the making of any final rules and standards.
These draft guidelines will be discussed with CDR agencies in conjunction with this consultation to ensure alignment before publishing.
N.B. The CX guidelines shared in this issue are in draft state and represent proposed rules and standards that have not been made. These wireframes should not be taken as definitive guidance of compliance with the rules and should not be considered as legal or compliance references for the purposes of implementation.
Areas affected
Changes are expected to impact all variants in the following areas of the CX guidelines:
New item or change proposed
Many changes will be mirrored across multiple flows. For example, many of the draft changes to the default data recipient dashboard will be also reflected in the other data recipient dashboard guidance, such as for amended consents, disclosure consents and withdrawals. As such, we intend to consult on the following subset of flows:
Feedback
The DSB invites community feedback on these artefacts and any other CX guidelines seen as necessary to support the proposed August 2024 rules and associated data standards. This issue will be progressed in MI21.
The CX Guidelines provide optional implementation examples for key rules, standards, and best practice recommendations.
They demonstrate key aspects of the consent model, but certain areas may be considered out of scope. This may include, for example, where the rules and/or standards are silent or non-prescriptive to provide CDR participants with flexibility or discretion according to their own systems or protocols.
❗The CX Guidelines span policy, rules, standards, and best practice, so requests will be considered on a case by case basis and timings may not fall within a Maintenance Iteration cycle.
Importantly, the CX Guidelines are optional to follow, but the CDR rules require CDR participants to have regard to them. The CX Standards differ in that they are binding data standards that must be followed.
Edited 17.10.2024 to add consultation links and details for CDR Receipts and 90-day notification guidance
Edited 22.11.2024 to add a consultation link and details for Consent Management (Data recipient): Collection and use - Default example
Edited 10.12.2024 to add consultation links and details for Collection and use consent: Default example and Collection and use consent: Using outsourced service providers
The text was updated successfully, but these errors were encountered: