On a successful POST the and are returned. The ‘IncidentID’ ‘IncidentReferenceNumber’ ‘IncidentID’ must be included for any PUT or GET requests as part of the URL. The incident report can be resubmitted with changes the Incident’ end point if the department ‘PUT – has withdrawn the incident report (DHHS Incident report status = ‘Withdrawn’). The supplied on a successful POST must be supplied in the PUT URL. ‘IncidentID’ The incident report status and withdrawal information can be retrieved using the incident’ end ‘GET – point. This data can be useful to gauge the progress of the incident report in the department. The supplied on a successful POST must be supplied in the GET URL. ‘IncidentID’ Figure - Example of a successful response Figure - Example of an unsuccessful response API entity list (POST/PUT - Incident) The following table lists all of the Data Fields that belong to the CIMS Incident API entity when creating/updating an incident report. The data entity list for the POST/PUT is the same however the URL for the PUT contains the unique so the system which incident report is being updated. ‘IncidentID’ to section 3.5 for a detailed description of the Incident reporting data fields. Data from Service Provider/s externalIncidentId reportedDate referenceVersion Incident Report - organisationName Incident Report - organisationAddressStreetNumberAndName Incident Report - organisationAddressSuburb Incident Report - organisationAddressState Incident Report - organisationAddressPostCode dhhsArea Incident Report - Incident Report - program Incident Report - serviceType Incident Report - incidentDate Incident Report - incidentDateAccuracy Incident Report - incidentTime
On a successful POST the ‘IncidentID’ and ‘IncidentReferenceNumber’ are returned. The ‘IncidentID’ must be included for any PUT or GET requests as part of the URL. The incident report can be resubmitted with changes the ‘PUT – Incident’ end point if the department has withdrawn the incident report (DHHS Incident report status = ‘Withdrawn’). The ‘IncidentID’ supplied on a successful POST must be supplied in the PUT URL. The incident report status and withdrawal information can be retrieved using the ‘GET – incident’ end point. This data can be useful to gauge the progress of the incident report in the department. The ‘IncidentID’ supplied on a successful POST must be supplied in the GET URL. Figure - Example of a successful response Figure - Example of an unsuccessful response API entity list (POST/PUT - Incident) The following table lists all of the Data Fields that belong to the CIMS Incident API entity when creating/updating an incident report. The data entity list for the POST/PUT is the same however the URL for the PUT contains the unique ‘IncidentID’ so the system which incident report is being updated. to section 3.5 for a detailed description of the Incident reporting data fields. Data from Service Provider/s externalIncidentId reportedDate referenceVersion Incident Report - organisationName Incident Report - organisationAddressStreetNumberAndName Incident Report - organisationAddressSuburb Incident Report - organisationAddressState Incident Report - organisationAddressPostCode Incident Report - dhhsArea Incident Report - program Incident Report - serviceType Incident Report - incidentDate Incident Report - incidentDateAccuracy Incident Report - incidentTime
Application%20programming%20interface%20specification%20%28CIMS%29.docx