When resolving fields it would be useful in certain instances to have the option to NOT have the _resolved field set to <null> when the original value can’t be found in the domain. In these instances it would be useful to have the original value put in that field:
- For range domain fields: There is no code-description look up so all values are currently set to <null> in the _resolved field. All data from the original field is lost.
- For coded domain fields: When the coded value isn’t found in the domain the value is set to <null> in the _resolved field but there are instances where it would be good to have the option to not lose the original value (maybe also include a warning in this instance as stated in this other idea).