Change of Diagnosis

change-diagnosis

POST

change-diagnosis

Description

Allows software vendors to create a change of diagnosis with ACC. The change of diagnosis is a secondary interaction (linked to a Claim) generated for reasons such as patient revisits with new symptoms or the initial provider has referred the patient to a specialist (e.g. xray, physio, surgeon) who diagnoses a more detailed understanding of the injury. From a software vendor perspective this is a subset of the Medical Certificate. From a Provider perspective, making this a separate identifiable service adds considerable value.

To learn more about the overall API process check out Get ConnectedLearn More and our Release Notes.

Resource Summary

Security

Type

application/json

Category

Change Of Diagnosis

URL

https://provider.api-compliance.acc.co.nz/api/v2/claims/change-diagnosis

Supporting Documentation

Body Parameters


Name Values Description
body
(required)

Request Body

ChangeDiagnosis {

pmsSoftwareName:
pmsSoftwareVersion:
claimNumber:
 string
1-12 alphanumeric characters. Examples: A123456, AA12345, 1234567, 12345678901, A1234567890 where A represents an alphabetic character and each digit represents any digit.
declaration:
Declaration {
providerDeclaration:
 string * (date)
The date the form was submitted.
}
diagnosis:
[
If present, this must contain at least one diagnosis. 20 diagnoses permitted.
Diagnosis {
diagnosisCodeType:
 string *
See the DiagnosisCodingSystem code tables for valid values.
diagnosisCode:
 string *
Alphanumeric, can include '.'
diagnosisDescription:
diagnosisSide:
diagnosisComment:
diagnosisAction:
primaryDiagnosisIndicator:
 string *
Select exactly one diagnosis in a request as primary.
}
]
patient:
Patient {
address:
Address {
type:
line1:
line2:
suburb:
city:
postCode:
country:
}
contact:
Contact {
emailAddress:
mobilePhone:
homePhone:
workPhone:
}
details:
PatientDetails {
accidentDate:
dateOfBirth:
nhi:
firstName:
middleName:
surname:
}
}
provider:
Provider {
address:
Address {
type:
line1:
line2:
suburb:
city:
postCode:
country:
}
contact:
Contact {
emailAddress:
mobilePhone:
homePhone:
workPhone:
}
details:
ProviderDetails {
providerId:
 string *
The provider's ACC or HPI number, 1-8 characters.
providerTypeCode:
 string *
See the ProviderType code tables for valid values.
firstName:
middleName:
surname:
}
}
vendor:
Vendor {
hpiFacilityNumber:
 string
ID of the facility where the service was provided.
hpiOrganisationNumber:
 string *
1-12 alphanumeric characters, can include '\\'
practiceName:
 string *
1-40 characters.
}

}

Operations

When using the API Key custom token in the Operations portion for any selected API below, set NAME to 'apikey', VALUE to My Apps, Consumer Key value, and select the HEADER option before clicking SET.

Basic HTTP authentication

Set

OAuth 2 authentication

Set

API Key custom token

Set

Working...

Response Error Details

  • HTTP Code
    Error Code
    Description
  • 202

    Accepted

  • 400

    Bad Request: invalid data

  • 401

    Unauthorized: authentication error

  • 403

    Forbidden: authorization error

  • 404

    Not Found

  • 500

    Internal Server Error