This value set is an absolute mess and doesn't come anywhere close to meeting MnM requirements for an extensible terminology. Codes overlap - or are fully duplicated, there are no clear boundaries between concepts, the value set is huge, making ongoing maintenance difficult. The value set is also intensional, meaning it can change at any time, forcing continuous remapping in order to remain conformant. There is no way that there is agreement throughout the world that all implementers must map their codes to this value set. This needs to be replaced with an example binding to a small value set with an enumerated set of codes that shows the range of possible codes.

(Comment 13 - imported by: Ron G. Parker)