In CARES, when importing NEMSIS 3.5.0 files, ICD-10-CM codes in eScene.09 are mapped to CARES Location Types. If you want to document something more specific, LocationTypeOther can be used to manually document free text in the custom element LocationTypeOther. This is rare and unneeded in most cases, it is just there so that an agency can fill in the free text field if they wanted to for a location that one could argue doesn't have a code. We definitely do not want the word Other/Not in List other generic type answers in the custom element LocationTypeOther.

Basically any scene has a valid ICD-10-CM location code, and that's what should be used.

To illustrate when an agency might want to use the custom element, here is a hypothetical scenario: Imagine the patient was found on the walkway of this STL Airport equipment that provides runway lights for the airport but is in the median of I-170 in St. Louis.

If they did truly want to document a super unique location like this that someone might argue wouldn't fit in any other ICD-10-CM code, they can send LocationTypeOther and Y92.8 together. The incident XML should look like this:

<eScene.09>Y92.8</eScene.09>

…

<eCustomResults.ResultsGroup>

<eCustomResults.01>Walkway on airport runway light tower over the median of the Interstate</eCustomResults.01>

<eCustomResults.02>LocationTypeOther</eCustomResults.02>

</eCustomResults.ResultsGroup>

CARES does not require this level of detail. Interstate, Airport, or Other Industrial Place would all be reasonable eScene.09 codes for this. But sometimes an agency wants to be able to document unique places (especially if they have recurring cardiac arrests there and this impacts patient survival/arrival time/etc). So the option exists for this reason.