When a response is received from the users API the identifiers aren't ordered.

For example our library gates system requests a GET on the user API to retrieve an identifier, in our case <id_type desc="Additional ID 1">OTHERID1</id_type>. it can only read the first hit for this identifier

I would like the response to order the values by status, with Active coming first.

This would allow us to read the active value and ignore any subsequent Inactive values

This is an example what is currently returned
<user_identifiers>
<user_identifier segment_type="Internal">
<id_type desc="Additional ID 1">OTHERID1</id_type>
<value>1234567890</value>
<status>INACTIVE</status>
</user_identifier>
<user_identifier segment_type="External">
<id_type desc="Barcode">BARCODE</id_type>
<value>removed</value>
<status>ACTIVE</status>
</user_identifier>
<user_identifier segment_type="External">
<id_type desc="University ID">UNIVID</idtype>
<value>removed</value>
<status>ACTIVE</status>
</user_identifier>
<user_identifier segment_type="External">
<id_type desc="Additional ID 1">OTHERID1</id_type>
<value>0987654321</value>
<status>ACTIVE</status>
</user_identifier>
</user_identifiers>

This is how I would prefer it to be returned
<user_identifiers>
<user_identifier segment_type="Internal">
<id_type desc="Additional ID 1">OTHERID1</id_type>
<value>0987654321</value>
<status>ACTIVE</status>
</user_identifier>
<user_identifier segment_type="External">
<id_type desc="Barcode">BARCODE</id_type>
<value>removed</value>
<status>ACTIVE</status>
</user_identifier>
<user_identifier segment_type="External">
<id_type desc="University ID">UNIVID</idtype>
<value>removed</value>
<status>ACTIVE</status>
</user_identifier>
<user_identifier segment_type="External">
<id_type desc="Additional ID 1">OTHERID1</id_type>
<value>1234567890</value>
<status>INACTIVE</status>
</user_identifier>
</user_identifiers>