- Learn More
- Inbound Data APIs
- Release Notes
Release Notes
Support
- FAQs
- Ask the Forum
- Having trouble? Get in touch
July 2024 API release notes
Type |
Summary |
---|---|
Claim Query API |
We have made a number of minor changes to our Claim Query API product. The following describes the changed behaviour:
|
April 2024 API release notes
Type |
Summary |
---|---|
Medical Certificate API |
Non-breaking change providing the following enhancement: Allow the additional diagnosis side location ‘Bilateral’ to be used for an Injury diagnosis (in addition to Left, Right and Not Applicable) |
Change of Diagnosis API |
Non-breaking change providing the following enhancement: Allow the additional diagnosis side location ‘Bilateral’ to be used for an Injury diagnosis (in addition to Left, Right and Not Applicable) |
February 2024 API release notes
Type |
Summary |
Inbound Documents API: (Version 2.2) |
Enhancements to support an additional set of documents to be processed automatically downstream from the Inbound Documents API, supporting the Integrated Care Pathway Musculoskeletal contract go live. Additional validations added to trim uneccssary spaces provided as part of the submission, improving ACCs ability to process the document.
For all documents please see Developer Resource Centre | Sample Inbound Documents for details. |
November 2023 API release notes
Type |
Summary |
Inbound Documents API: (Version 2.1) |
Minor extension to the number of documents able to be submitted to ACC via the Inbound Documents API, primarily to support Integrated Care Pathway Musculoskeletal go live in early 2024. Additional validations added restricting the use of special characters within metadata, improving ACCs ability to process the submission.
For all documents please see Developer Resource Centre | Sample Inbound Documents for details. |
September 2023 API release notes
Type |
Summary |
Claim API |
Non-breaking change to Claim v2 providing the following enhancements:
|
June 2023 API release notes
Type |
Summary |
Inbound Documents API: (Version 2.0) |
Extended the number of documents able to be submitted to ACC via the Inbound Documents API, to now support most of the regularly used document types (near on 500 now available). Additional validations to the metadata also included to improve ACCs ability to process the submission. For all documents now available, please see Developer Resource Centre | Sample Inbound Documents for details.
For all documents please see Developer Resource Centre | Sample Inbound Documents for details. |
May 2023 API release notes
Type |
Summary |
Inbound Documents API: (Version 1.2) |
Extended documents able to be submitted to ACC via the inbound documents API to include documents relating to acquired brain injury, dental and hearing loss.
For all documents please see Developer Resource Centre | Sample Inbound Documents for details. |
February 2022 API release notes
Type |
Summary |
Claim API |
Non-breaking change to Claim v2 to make the claim number an optional field. If claim number is not specificed upon submission, then the API will generate the claim number and it will appear in the API response message. |
Claim API |
New endpoint added for Claim API auto-numbering. This is to allow a GET request to retrieve a claim number which can then be used to submit a claim. |
Claim API |
The "referralReason" field is made optional. |
Claim API |
Claim API specification updated to reflect changes. |
June 2021 API release notes
Type |
Summary |
All APIs |
Response timeout increased from 30 seconds to 3 minutes. This is to accomodate large invoice payment queries which can take a while to respond. |
Claim Query API |
Updated the Claim Query by NHI + DOB (claims/status/filter) to now by default return 75 results instead of 25. This is to accomodate searching for client records, which may have more than 25 claims within a 5 year period. |
Medical Certificate API |
Introduced an optional field called "returnToNormalWorkDate" within the "workCapacity" section of the medical certificate. 1. If an Incapacity is specified, the returnToNormalWorkDate (currently <input date>) must be after the last end date of the latest incapacity period (currently <lastToDate>). 2. The returnToNormalWorkDate cannot be before the accident date. |
All APIs |
During scheduled maintenance outages, APIs will now return a specific error message to notify users when they call the API {"errors": [{ |
May 2021 API release notes
Type |
Summary |
Inbound Documents API |
Release of a new service providing the initial ability to send the following seven (7) documents types in PDF format:
Only one (1) document, up to a maximum size of 20 Mb, can be submitted per request. |
November 2020 API release notes
Type |
Summary |
Invoice API |
Changed the purchaseOrderNumber field max character length from '7' to '10'. This is to accomodate the change to purchase order numbers which will start to be issued with 8 digits. |
Claim status query API |
Resolved a defect where the claim status query API was incorrectly translating READ diagnosis codes to SNOMED, when in fact the diagnosis type was ICD10. Now, the API does not translate the diagnosis into SNOMED if the code is registered as ICD10. |
June 2019 API release notes
Type |
Summary |
Claim API |
Resolve a defect causing injury comments to sometimes be dropped |
Invoicing query API |
Resolve a defect causing an internal server error response when querying failed invoice submissions with invoice lines > 4 |
Claim API |
Change the max value for restricted hours from '8' to '24' |
Claim status query API |
Resolve an issue where an error is returned when querying a claim that has a value for injuryResolvedFromDate |
Claim status query spec |
Minor spec change to show it's a list of key-value pairs when using POST claims/status query |
Claim spec |
Claim spec section 7.2.1 incorrectly states the employer name requirement. - this is a work accident, or - the claimant can't continue normal work; otherwise, it's optional. |
Claim spec |
Section 9 of the Claim spec has a diagram for Fitness for work. It needs an extra decision row for the employment status code. |
Invoice spec |
The Invoice API spec section 5.1 refers 'invoice/invoiceNumber', but the JSON name implemented is 'invoice/invoiceID'. |
Claim swagger doc |
The swagger has the NHI number as required, swagger update to make it optional to match the API. |
Invoice/Claim query |
Users that are tied to an organisation name that has special characters in the database are unable to use queries as it results in error 'must only contain alphanumeric characters (incl. blank)'. |
Claim Spec |
Update the spec to include an error condition for workInjury field 'Work accident may not be true when inPaidEmployment is false.' |
Claim API |
Remove the error condition for return to work date "returnToNormalWorkDate is later than the first or only toDate + 1 day, and not later than the first or only fromDate + 15 days" |
February 2019 API release notes
Type |
Summary |
Invoice |
‘invoiceId’ optional field to allow PMS vendors to use their own invoice numbers. |
Invoice |
API to automatically make alphabetic characters in the schedule number uppercase, preventing duplicates. |
Invoice |
New business rule: The invoice number must still start with a digit or letter (not 'W'); each remaining character can be a letter, digit, space, hyphen, or underscore. |
Invoice |
A 'success' response to a submitted invoice now uses 'invoiceId' consistently for the invoice number. |
Claim |
Make the validation on employer's name and address match the legacy system, that is:
|
Claim |
Make the date range for a full incapacity period inclusive, as in the legacy system. So 'fully unfit for work' from 10 Apr to 20 Apr: 11 days. |
Claim spec |
Allow a maximum combined period of 14 days. As implemented—this is a specification change only. |
Claim |
Make the employer's postcode and country optional. |