Database and core proc

[jeremyestein]

Implements #35

Find the location visit from the time and place associated with the waveform data, as this information is not given to us directly.

Pass both original (source) and interpreted (mapped) location strings to the core proc. Mapped location string is used to look up the location visit and ultimately to find out who the patient is.

Pass both original (source) and interpreted (mapped) stream description strings to the core proc, which stores them as an Visit Observation Type.

[github-actions[bot]]

PR checklist

Default guide for a PR (if multiple PRs for the work, only keep one version of it and link to it on the other PRs)

• [ ] From the UCLH data science desktop, a validation run has been set off
• [ ] load times in UCL teams has been populated with the run information
• [ ] During the run, glowroot has been checked for any queries which are taking a substantial proportion of the total processing time. This can be useful to identify indexes that are required.
• [ ] After the run, look for any unexpected errors in the etl_per_message_logging table, the error_search.sql file on the shared drive can be used for this \\sharefs6\UCLH6\EMAP\Shared\EmapSqlScripts\devops\error_search.sql. Create an issue if you find an unexpected exception and is not related to the changes you've made, otherwise fix them!
• [ ] After the run, populate the end time in load times
• [ ] Let Aasiyah know about the completed validation and give her information on the changes and where to start with the validation
• [ ] Check validation report and give any feedback to Aasiyah if there are any changes needed on her side, iterate on getting the validation to match at least 99% (validation and emap code).

[jeremyestein]

Are we actually going to be able to link to a visit?

That's the idea, although the waveform HL7 uses a different location string schema than what we have in Emap from the main HL7 ADT feed, so it would require some (potentially very trivial) mapping. @stefpiatek thinks we should delay that feature in favour of getting this out quicker. Beyond location string mapping, we will only know exactly how well it works when we have real data, because we might find the waveform time+location doesn't correspond with real location visits as neatly as I'd hoped.