A heads up, the ‘Maps to’ relationship for ICD10PCS codes include concepts where the concept class is ‘ICD10PCS Hierarchy’. The hierarchy codes can be 3 or 4 characters in length. This can result in incorrect mappings when looking up ICD procedure codes, where you are depending on the look-up to determine if the code is ICD9 or 10 and if the source data, like Truven, the leaves out the period in the procedure code.
The concept class is ‘ICD10PCS Hierarchy’ for ICD10PCS hierarchy codes and
‘ICD10PCS’ for concept with the full 7 character code. Since we only
expect to see the complete 7 character ICD10 codes in the source data we
will limit our lookup to where CONCEPT_CLASS = ‘ICD10PCS’.
I equate the ‘Maps to’ relationship with the CDMv4 source to concept map
table. And in that case, I would suggest that the ‘Maps to’ relationship
for ICD10PCS codes only include a mapping for the 7 character codes i.e.
where concept class = ‘ICD10PCS’.
@Christian_Reich @Dymshyts @DTorok
Just following up on this old thread: Does it make sense to change STANDARD_CONCEPT value from ‘S’ to ‘C’ in case of ‘ICD10PCS Hierarchy’ concepts to not worry about mismapping? These codes are not actually being used for billing, so they are not actual “standard” concepts.
Hamed
2 Likes
Yes, this is a good point. We’ll change that in the next ICD10PCS update
Great, thanks!