BUG: Patient phone number isn't converting correctly

[angelathe]

Description

In the example eCR below, the patient's phone number is not converting correctly to FHIR format. Investigate the cause of this issue and implement a fix.

Note: The phone number provided is invalid. Please verify that this is not a data quality issue before addressing the FHIR conversion problem.

Steps to reproduce

TN_sample_eCR3: phone number not being converted successfully

Expected Result

If any patient contact information is available, it should be correctly converted to FHIR and displayed in the eCR Viewer.

Actual result

Example from TN_sample_eCR3: Phone number is not displayed

Priority

Provide an estimate for level of impact the bug has today by placing an X in the applicable bracket

Priority

• Low priority The bug does not have to be fixed immediately. High and medium priority bugs should be addressed first.
• Medium priority Typically, medium-priority bugs do not affect customers directly and therefore can be fixed in the normal course of testing and development.
• High priority High priority bugs must be addressed immediately. They often affect the app’s functionality and impact customers and their user experience. They must take priority.

Notes

FHIR conversion may be required for this ticket.

[mcmcgrath13]

I don't have access to the tennessee data, but based on the screenshot added this telecom node to another patient's eCR and it does convert as I'd expect

{
      "system": "phone",
      "value": "+1-111-111-111",
      "use": "mobile"
}

I believe the telephone formatting service is rejecting this as invalid. @ashton-skylight @emmastephenson in this case do we want to do something else other than null it out? maybe pass it through, but with some sort of invalid caveat?

[ashton-skylight]

Perhaps something like this?