Dealing with concepts in SNOMED, when more than 2 code representations for the same concept are possible
- riki.merrick
Add your comments directly to the page. Include links to any relevant research, data, or feedback.
Status |
|
|---|---|
Impact | High / Medium / Low |
Driver |
|
Approver |
|
Contributors |
|
Informed |
|
Due date |
|
Outcome |
|
Rationale |
|
Background
Have PLR123 AND SNOMED extension concept code - that works as long as we are submitting oursleves now, but for terms that have been submitted before we had the namespace extension, so then we will get a NEW SNOMED concept ID - what should we do?
Relevant data
A single concept could have PLR123, APHL SNOMED extension concept and if submitted to either US or international edition prior to having the APHL namespace, or if submitted by another organization we may end up with a different SNOMED CT concept ID as the replacement code.
Options considered
| Option 1: | Option 2: |
|---|---|---|
Description | Inactive both of the APHL codes in the extensions | Keep the APHL SNOMED extension code active |
Pros and cons | is inline withthe current approach, where we assigned APHL SNOMED extension terms to inactivated concepts, when we switched over - but those are both retired | we would have duplication for those concepts we woudl have to activate all the already replaced codes |
Estimated cost |
|
|
Action items
Outcome
To inactivate both PLR and APHL SNOMED extension terms, when a differnt SNOMED CT concept identifier is assigned by US or SNOMED International