How to represent codes from the wrong version of a codeset
8 views
Skip to first unread message
Ruth Berge
Aug 10, 2012, 3:17:23 PM8/10/12
to ihe-pcc-im...@googlegroups.com
Both in the Meaningful Use ONC rules and in the CCDA implementation guide there are specific versions of some value sets that are called out. The example I want to use is that ONCE calls out the January 2012 release of Snomed CT (where I am assuming that I can refer to that release as a version). What if we have a problem that was coded using an older version of Snomed CT (say the July 2011 release)? Would we correctly represent this as an alternate code since it is not the requested release version?
The same is true for other vocabularies I am just using SnomedCT as an example.
Another point is that after the rules are established from the ONC, assuming that they leave Snomed CT at January 2012, then what about updates afterwards? Unless they update the rule to say it is all releases after the one they have called out, then we are forever stuck with an old version of any of these vocabularies. So would we use the required version as the original code and then provide any alternates (either from newer or older versions) as translations or alternate codes?
The same is true for other vocabularies I am just using SnomedCT as an example.
Another point is that after the rules are established from the ONC, assuming that they leave Snomed CT at January 2012, then what about updates afterwards? Unless they update the rule to say it is all releases after the one they have called out, then we are forever stuck with an old version of any of these vocabularies. So would we use the required version as the original code and then provide any alternates (either from newer or older versions) as translations or alternate codes?
Reply all
Reply to author
Forward
0 new messages