Fix standardization issues in the eCR Viewer

[angelathe]

What needs to be done

Fix formatting and standardizing issues in the eCR Viewer (see list below).

Why it needs to be done

We want consistent formatting throughout the eCR Viewer on many fields. Having the same data in different formats across the Viewer increases cognitive load at best, and at worst, could lead to data being misinterpreted.

For reference, here is the diff between sentence case and title case:

Acceptance criteria

• [ ] Patient Name should always be in title case in the following sections:
  • [ ] eCR Summary
  • [ ] Patient Info → Demographics
• [ ] Demographics info should be in title case for the following fields:
  • [ ] Demographics → Sex
  • [ ] Demographics → Emergency Contact name
• [ ] Addresses should be in title case in the following sections/fields:
  • [ ] eCR summary
  • [ ] Patient Info → Demographics → Patient Address
  • [ ] Patient Info → Demographics → Emergency Contact
• [ ] Dates everywhere should be mm/dd/yyyy, specifically to be fixed in this section:
  • [ ] DOB in Patient Info → Demographics
• [ ] Phone Number changes:
  • [ ] There should be a colon after Home or Mobile or Work → for ex: Home: 111-111-1111
  • [ ] Phone numbers should have dashes (to break them up) → for ex: +1-615-999-9999. to be fixed in the following fields:
  • [ ] Patient Contact
  • [ ] Patient Info → Demographics → Contact AND Emergency Contact

Open questions

• Should we be standardizing these individually or modifying the standardization service?
• What do we do for names like McSomething? is our standardization service smart for those kinds of names?
• Does geocoding help with standardizing addresses?

Additional context

• Examples for these issues: (Link to eCR Viewer)

[emmastephenson]

@sarahtress to review this ticket before Monday

[emmastephenson]

Scope of this work:

• The actual standardization building block should be updated, vs putting these changes directly within the eCR Viewer
• We should create a new endpoint within standardization to "standardize bundle" instead of calling different endpoints for each field (DOB, name, etc)
• Also want to add documentation for what is covered in the new endpoint
• For now, should not be configurable (start with a "dumb" but opinionated endpoint)

[emmastephenson]

@emmastephenson and @gordonfarrell to chat with impl team to see their thoughts on this.