Bulk upload fhir mapping bugfix

[DanielSass]

BACKEND PULL REQUEST

Related Issue

• 7804

Our bulk upload result flow does not correctly add descriptions for SNOMEDs that are not within our (very limited) list of codes used by the frontend. When a bulk upload is submitted with a valid code that isn't in this list we were incorrectly setting the description to "Invalid result".

Changes Proposed

• Stop defaulting the value to "invalid result", leave the description off of the fhir object if we can't correctly populate it.

Additional Information

Testing

• Testing in an env for the specific changes we're making is difficult without grabbing the fhir message off of the queue in Azure. Easier to just debug locally to verify mapping behavior.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
84.6% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud