Verify in the HL7-> FHIR mappings that we are not creating unnecessary empty elements

[mkalish]

User Story

As a FHIR receiver, I do not want to receive resources with empty data

Description/Use Case

It's possible to accidentally create a mapping that will generate an empty FHIR resource. As an example of this is where the FHIR inventory states that a field on the mapped FHIR resource has a constant value; without a correct mapping, if the HL7 value is missing the result can be a FHIR resource without data in it except the constant value

Risks/Impacts/Considerations

Dev Notes

This likely should be implemented in the converter library rather than trying to handle this case by case by changing the logic to not create a resource at all when spec value is not populated.

Acceptance Criteria

• [ ] Empty FHIR resources do not get created when mapping HL7

[Andrey-Glazkv]

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jack-h-wang @jalbinson @JessicaWNava @JFU-NAVA-PBC @jimmyfagan @mkalish @thetaurean

[Andrey-Glazkv]

Please add your planning poker estimate with Zenhub @brick-green