Locus Emergency
The new Locus Emergency integration is not yet deployed. This integration is to be able to test it and to be ready once it goes live.
Locus Emergency Integration is a connection point between EWA and the Norwegian Emergency Medical Communication Centre (AMK). Using the Locus Emergency Integration API, customers can send emergency medical data to EWA, allowing them to monitor and respond to medical emergencies more effectively.
With the integration of the Locus Emergency Integration API, communication between the emergency operations centers (EOC) and the ambulance is automated, allowing the tablet to receive information from the EOCs. This integration enhances the efficiency and accuracy of emergency medical data transmission, enabling faster and more effective response to medical emergencies.
Please note that the Locus Emergency Integration API serves as a connection point between EWA and customers such as AMK. It is designed to receive emergency medical data from customers and store it in EWA's database, but it does not provide access to EWA's functionality directly.
Changelogs
Integration API with new Locus Terminologies
The second version of the Integration API has been introduced to align with Locus Emergency terminologies regarding the variable naming.
Please note the new endpoint for Locus Emergency should be: {your-domain}/integration/api/v2/import.
# Example uri: "https://dev.ewa.bliksund.com/integration/api/v2/import"
Here are the updated terminologies:
| Current | Locus terminology | Example | Norwegian |
|---|---|---|---|
| central-mission-id | incident_id | 240518-598 | Hendelsesnummer |
| emcc_id | eoc_id | AMK1 | AMK |
| resource_id | mission_id | 101 | Oppdragsnummer |
| emergency_code | urgency | Vanlig | Hastegrad |
| dt_place_incident | dt_at_scene | Fremme hendelsessted | |
| dt_left_place_incident | dt_depart_scene | Avreist hentested | |
| dt_at_destination | dt_arrived_destination | Fremme leveringssted |
Handling of the Urgency Code
When an urgency code is sent from the EOC, it should be mapped to predefined values to match the commonly used terminology in EWA and Locus Emergency and enable multi-language support within our application. If no matching value is available, the original text of the urgency code sent from the EOC will be displayed as is. This ensures that the urgency codes are either presented in a familiar format or remain in their original form to avoid any misinterpretation or loss of critical information.
Support of the New EOC-ID Format
The format of the EOC-ID (from Emergency Operations Centers, previously Central-Mission-ID) has been updated to meet the requirements of the Locus Emergency integration, including a change in variable naming. Previously, the ID contained of the EMCC-ID and the Resource-ID, separated by a hyphen ("-"). But since yhe format of the EMCC-ID (for Emergency Medical Communication Centre, mostly used in Norway) has changed to incorporate the date and a sequential number for the day separated by another hyphen, the new integration needed to be adjusted. In this process, the EMCC-ID was also renamed into Incident-ID to reflect that it represents a specific event on that particular day. Additionally, the Resource-ID was renamed into Mission-ID to support one resource (like an ambulance) having multiple missions within a single incident. In conclusion, the format has changed as shown in the picture below.
To be able to parse the new EOC-ID into its segments, the logic in EWA was changed to treat the segment after the last hyphen as the new Mission-ID (previously Resource-ID) and the rest as the Incident-ID (previously EMCC-ID). This was implemented within a separate version of the EOC-Integration-API to support backward compatibility until all customers have transitioned to the new Locus Emergency version.
Distance
Distance (in kilometers) sent from Locus Emergency will be handled and distance tile in EWA will be updated. The data is also saved to the database and will be displayed where applicable.