While this problem is being tackled, I looked at some other entries which use ellipses in the data dictionary (which I am guessing has some close similarities to the SEER API, seeing as the presence of ellipses correlates so closely with slight OMOP concept mistakes).
35918591 is similarly missing a response for values
35918412 does have a value corresponding to the range from
03-59, but the concept code is incorrectly set as
35918783 seems to have entirely incorrect responses, as none have the correct name, the ‘Unknown age’ option is missing, and the final bucket is incorrectly from
Lastly, are concept codes supposed to be zero padded in suffix length to ensure proper sorting? E.g.
123@456, instead of
I have seen other concepts with single digit suffixes set to invalid and replaced by valid concepts that are identical in all fields except for the addition of proper zero padding, but I wasn’t sure if this is intended to be practiced throughout the concept table as a whole. If this is the practice, then all three of the above concepts (35918591, 35918412, 35918783) and the original problem concept (35918370) are all incorrectly zero padded among their responses.