Waveform extension: additional concepts needed for `metadata_concept_id`

[briangow]

In the waveform_channel_metadata table from the OMOP waveform extension, we use the concept_name + concept_id matches from WAVEFORM/Ontology/concept_delta.csv. There are entries in this table for SAMPLERATE and RESOLUTION metadata parameters.

We need to extend this to capture additional metadata parameters. In my current ETL, I also need:

• AMPLITUDE (to be used to capture the concept and units for the sample amplitude)
• SEGMENTLENGTH (to be used to capture the length of a given segment in WFDB)

It would be great if these parameters could be added to the vocabulary sooner than later, so I can generate a clean build prior to creating a poster about the waveform extension, for presentation next month.

Eventually, we should come up with a more comprehensive list of metadata parameters. From WFDB these are some other Record parameters that we may need mappings for at some point:

• n_sig - Total number of signals
• counter_freq - The frequency used to start counting
• base_counter - The counter used at the start of the file
• sig_len - The total length of the signal
• fmt - A list of strings giving the WFDB format of each file used to store each channel
• samps_per_frame - The total number of samples per frame
• skew - The offset used to allign signals
• byte_offset - The byte offset used to allign signals
• baseline - A list of integers specifying the digital baseline
• adc_res - The value produced by the ADC given a given Volt input. Note that adc_gain from WFDB corresponds to the RESOLUTION concept_name in WAVEFORM/Ontology/concept_delta.csv. For adc_res we could name the concept something like ADC_RANGE or simply RANGE.
• adc_zero - The value produced by the ADC given a 0 Volt input
• init_value - The initial value of the signal
• checksum - The checksum of the signal
• block_size - The dimensions of the field data