Release 8 (R8) - STARS go-live release notes

Page contents:

Release 8 (R8), the STARS go-live release, introduces the final core capabilities required to support the five business outcomes SMS suppliers need to enable:

• Submit valid data

• Reconcile previously submitted data

• Remove data submitted in error

• Check data quality

• Make a declaration

R8 is both a Production and Client Integration Environment release. It enables SMS suppliers to progress through the production readiness self-assessment and continue integrating their solutions with STARS.

Once an SMS supplier has demonstrated readiness, its RTO clients can progress through the onboarding checklist.

Additional capabilities being released include the Classification API, replacing downloadable classification CSV files, validation and reporting period enhancements, and the introduction of jurisdiction in API routes.

Preparation to support Stage 2 development (STA system integration) has commenced. Jurisdiction is now required for transaction batch uploads and some related operations.

Some developer portal content has changed in line with the Release 8 build and will continue to evolve during Stage 2. SMS suppliers should account for additional functionality that will be introduced in future releases, particularly jurisdiction-specific validation and data quality behaviour.

Breaking changes

Release 8 contains several changes that require SMS supplier system updates. Refer to the New and enhanced capabilities section for full details of these changes.

Jurisdiction in APIs

Jurisdiction is now mandatory in many API routes, parameters or request and responses bodies. SMS suppliers may need to update their integrations to supply the NAT jurisdiction (national) and allow for other jurisdictions in stage 2.

Reporting period model

The reporting period data model has changed. SMS suppliers should update affected integrations to use the new structure.

Submitted-in-error processing

Submitted-in-error requests must now include a reason when records are marked as voided. SMS suppliers should review and update affected workflows to meet the requirements.

New and enhanced capabilities

Jurisdictions are included in APIs

Jurisdiction is now mandatory in many API routes, parameters or request and responses bodies.

Key capabilities available in this release:

API routes now include jurisdiction. STARS stores jurisdiction against each transaction batch. The jurisdiction supplied in the route is checked against the transaction batch to help identify mismatches. Reporting periods now take the jurisdiction into account, establishing the foundation for future jurisdiction specific validation and reporting requirements.

Key supporting material:

• Reporting Pathways guidance

• Jurisdictions guidance

• Updated OpenAPI Specifications

Submitted in error enhancements

Release 8 introduces updated submitted-in-error terminology and functionality.

Key capabilities available in this release:

Submitted-in-error processing now uses IsVoided and VoidedReason. Validation outcomes more clearly distinguish active records, previously voided records and records that cannot be found in the submission, while enhanced reconciliation support helps suppliers understand and manage the resulting record state.

Key supporting material:

• Submitted in Error guidance

• Updated Rules Catalogue

Introduction of data quality checks

Release 8 introduces the first implementation of data quality assessment capabilities.

Note: only the optional contributing resources data quality result endpoint is available in this release. The summary endpoint will be provided in the next release.

Key capabilities available in this release:

SMS suppliers can use the new data quality assessment APIs to initiate and monitor organisation-wide data quality checks. Release 8 supports Validation and retrieval of failed validation results for 15 initial data quality rules.

Key supporting material:

• Data quality guidance

• Data quality API documentation

• STARS Rules Catalogue

Classification API

A Classification Data API has been introduced. This capability replaces the previously available downloadable classification CSV files.

Key capabilities available in this release:

SMS suppliers can retrieve authoritative classification data through the Classification Data API. The API supports incremental synchronisation, timestamp based retrieval and pagination, enabling systems to identify and retrieve classification changes efficiently.

Key supporting material:

• Reference and Classification Data API Usage Guide

• Updated Data and Rules guidance

• Updated Open API specifications

Validation enhancements

Several validation framework enhancements have been introduced.

Key capabilities available in this release:

Release 8 also introduces an initial business validation phase, a data quality phase, and improves the overall validation performance.

STARS Rules Catalogue

The STARS Rules Catalogue has been significantly.

Key capabilities available in this release:

• includes all data quality rules and identifies the 15 rules currently implemented

• adds a Validation Results column to improve visibility of rule outcomes

• clarifies that the Date of Birth Accuracy Code is not used when implementing the age-based rules BRDG00220, BRDG00176, BRDG00037 and BRDE00003

• updates BRDG00147, BRDG00049 and BRDG00112 to use AUS Eastern Standard Time rather than UTC

• updates the applicability requirements for BRTS90330

• adds the new business rule BRTS90370.

Key supporting material:

• Validation framework guidance

• Updated STARS Rules Catalogue

Reporting Period enhancements

Release 8 introduces a redesigned reporting period model to support future jurisdiction specific requirements.

Key capabilities available in this release:

Reporting periods now use ReportingPeriodNumber and take the jurisdiction into account. The updated reporting period APIs also support enhanced declaration and reconciliation processing and provide the foundation for future jurisdiction specific requirements.