Add a "here's all the codes of interest across resources" table for easy investigation

[mikix]

Problem Statement
Sometimes you have a problem like "OK I know which asthma LOINC codes I'm interested in, but I don't know where they would exactly be coded in my EHR" - and you have to do a bunch of searching around, in observation components, observation toplevels, procedures, conditions, etc.

Desired behavior
It might be nice if there was one table that just had a simple schema like this and was the UNION of all those places you might manually search:

resource_type, resource_id, code, system, display

This would help with quick "do we have this data coded at all in the EHR?" searches.

[comorbidity]

+1 UPVOTE on this ticket!

[mikix]

Matt says this is already mostly available in the discovery study:

SELECT * FROM "cumulus_cerner_db"."discovery__code_sources" limit 10;

But it does not include the resource ID for going back to the source.

[dogversioning]

i'm happy to do this/approve a PR that does this, but a note of caution - this table is going to be very large due to all the observations (potentially repeated), and so it may have performance issues that we don't normally see in some of the smaller resources.

[mikix]

Hmm, is it better or worse if it groups the IDs into a list? Or maybe just has a representative ID (aribtrary(id))?