The CDR now encompasses all Australian ADIs as data holders and an increasing number of data recipients are enabling services for consumers to use. The number of API calls and active consents is now rapidly increasing. This is very exciting for those of us that have been working on the CDR but it now introduces the new challenge of ensuring that the levels of service offered to Australian consumers is good and improving over time.
The management of technical platforms often rely on non-functional requirements to define the baseline of what good service looks like and, in this regard, the CDR is no exception. The CDR data standards include a set of non-functional requirements that were published in 2019. These requirements were not made binding, however, as there was no real world traffic that could be used to check if they were appropriate. To support the expanding regime the DSB is now consulting on making the existing non-functional requirements binding and whether they should be altered in response to practical experience.
You can view and contribute to the Decision Proposal 208 - Binding NFRs here on our GitHub Repository: https://github.com/ConsumerDataStandardsAustralia/standards/issues/208
Photo by Scott Graham on Unsplash