What needs to be done

Upgrade our saving flow to save to the extended DB schema if so configured.

Why it needs to be done

This ticket puts all the pieces together from previous tickets to allow saving to a DB using the extended schema. We have the extra data from the message parser, an extended schema for setting up the DB, and env vars that should let us tell the system what kind of world it lives in. Lets put it all together and get savin'!

Acceptance Criteria

Given the env vars DATABASE_SCHEMA='extended', DATABASE_TYPE='sqlserver' and using the orchestration config philadelphia-ecr-viewer :

• Write out the full eCR data json object returned from the parser into the extended schema tables. Important notes below!!!!!
• Tests/Test updates for new and updated functions

Technical Notes

This is a write change only, we don't need to read the full extended schema

Extended Schema details in file: containers/ecr-viewer/sql/extended.sql

!!IMPORTANT!! Some of the SQL dialects we need to interact with can't handle datetime data types, so in the extended schema these have been split into two columns DATE and TIME.

Example: An eCR's encounter_start_date and encounter_start_time are two separate columns in the DB despite coming from the same string in the eCR