AUCDI development approach

The AUCDI is being developed using a community-centric, consensus-driven process.  The AUCDI development process includes engaging clinicians, software vendors, healthcare organisations, and government agencies to co-design and validate health data standards. The process is transparent and open, allowing for wide participation and feedback to ensure that the AUCDI is practical, understandable, and easily adopted. This approach leverages existing frameworks and incorporates continuous input to create robust, standardised data for interoperability.

AUCCDI community development process and the Sparked CDG development process

AUCDI Community Development Process

Stage 1: Use case and requirement gathering

Use case and requirement gathering occurs to understand the priorities of the community and are used to drive the scope of the data groups included in AUCDI.

In this stage, the following activities occur:

  • Requirement gathering to collect and prioritise requirements from the community to guide the development.
  • Development of a set of scope drivers to engage with the CDG and focus discussions and assist the selection of data groups to meet the identified priority use cases.
  • Developing use cases that illustrate how AUCDI will be applied in real-world scenarios.
  • Identification of data groups to support identified high priority use cases
    • High priority data groups are proposed for inclusion in AUCDI
    • Lower priority data groups are placed in the backlog for future development
  • Development of core design principles

Stage 2: Data groups drafted

During this stage the following key activities occur:

  • Drafting of AUCDI data groups and elements in collaboration with the Sparked CDG or relevant Sparked community group and Sparked partnership through outputs of the Requirement Gathering process.
  • Data groups and elements are drafted leveraging existing national and international work and presented.

Stage 3 and 4: Draft data groups are presented to the CDG and Data groups updated and added to the draft

During these stages, the draft data groups are validated with the CDG using the CDG decision making process, as part of the Sparked CDG Development Process through the following activities:

  • Presentation of draft data groups to the Sparked CDG or relevant Sparked community group and Sparked partnership through online and in person workshops and meetings.
  • Additional data groups can be drafted leveraging existing national and international work and presented to the Sparked CDG or relevant community group for discussion. During the discussion, the Sparked CDG decision making process is used.
    • Where necessary, a joint clinical and technical community group meeting can be held to discuss issues requiring both clinical and technical input.
  • Issues with the draft data groups may be raised by the Sparked Technical Design Group for discussion by the CDG or community group directly or through the Harmonisation group process.
  • Changes are made where required and then added to the draft AUCDI.
  • Issues may be escalated to the Harmonisation group for discussion and advice.

Stage 5: Draft completed for internal Sparked partner review and QA

During this stage the following key activities occur:

  • Draft AUCDI release is completed and provided to the Sparked partnership for initial review
  • Draft AUCDI release is updated and draft for public comment prepared for publication.

Stage 6: Draft released for community comment

During this stage the following key activities occur:

  • Share the draft AUCDI release and invite community for review and feedback through publication on the website

Stage 7: Draft published for feedback

The draft AUCDI is published on the Sparked website as a PDF and anyone (regardless of Sparked membership) is able to review the AUCDI. All Sparked members are notified via email and mentioned at Sparked CDGs and relevant TDGs. Social media platforms are also used to promote that community feedback period to as wide an audience as possible.

Feedback reviewed

Once the feedback period is closed, all feedback received is reviewed, documentation is updated and specific responses are developed by the Sparked editing team. In some instances, specific feedback, proposed changes and proposed responses to the feedback provider will need to be escalated to the Editorial Triage or Harmonisation group.

These instances include (but not limited to):

  • A proposed change requiring a material change to AUCDI, where there are concerns around compatibility with current release or related technical documentation (e.g. AU Core).
  • A proposed change requiring a non-material change to AUCDI, however major impact has been identified for implementers.
  • Where there is potentially further community review and feedback that is required.
  • Where there is potentially a need for additional insight/expertise for appropriate editorial review to be completed.

Stage 7A:  Escalation

If an item is escalated to the Sparked Harmonisation group, the group will review the items and provide advice recommendation on how to proceed.

The group may make recommendations such as:

  • The item should be moved to the backlog for additional discussion/further comment by community
  • The item can proceed as proposed
  • The item the proposed change/response is amended before proceeding

Update and provide a response

The editing team will update the AUCDI as required and complete a response for each item of feedback received.

Stage 8:  Partner Review

During this stage the following key activities occur:

  • Final review internal review of AUCDI release by Sparked partnership team.
  • AUCDI release prepared for publication with feedback and responses.

Stage 9:  Publish final

The finalised AUCDI will be published. All items of feedback and responses from the Sparked editing team will also be published on the Sparked website. Feedback is de-identified and replaced with an ID number.  Each responder is contacted to let them know that the feedback responses have been published and their ID number. Email notification of the AUCDI publication is sent to all Sparked members and posted on social media.

Product Maintenance Processes

Rapid product iteration follows the lifecycle outlined above, supported by a robust product pipeline that must be actively managed to ensure a continuous flow of development, testing, and refinement.  By leveraging real-time feedback and employing agile methodologies, multiple releases of AUCDI can be managed in one year with a formal aggregated product release once a year.  This supports rapid adjustments to AUCDI, adapting efficiently to changing demands and regulatory requirements. This comprehensive management of the product pipeline not only accelerates the time to market but also ensures that the products developed are highly relevant and functional across a wide range of user needs.

Backlog Management

Requests are collected and added to the AUCDI backlog. Prioritisation is done by the Sparked CDG in a collaborative consensus process.