From the release notes: Version 2.76 includes updates to 196 concepts. The ChangeSnapshot file has the list of deprecated concepts. Five concepts were deprecated as they became duplicates once the aforementioned changes were made.
However, the 2.76 MapTo file has 4,000 lines, I understand that there are a lot of duplicates in the MapTo file, but that is more than 5 deprecated codes.
What does the MapTo file represent on this version?
Hello, Kimberly. This is a good question. The ChangeSnapshot is always for this particular release. The MapTo contains the entire history of code alternatives for deprecated/discouraged codes, not just for the current version.
Does this help answer your question? If not, please clarify and we’ll happy to help.
Thank you . I was thinking (and hoping ) that was the case. This helps !
If we had not taken 2.75 yet, can we just take 2.76 and move forward with things or do we need to implement 2.75 prior to 2.76?
Hi Derek, you can skip version 2.75 and move forward with version 2.76 since the files encompass the entire terminology rather than just incremental changes. However, you may want to review the Updates files, DifferenceReport, and ChangeSnapshot files in both the 2.75 and 2.76 releases to see all the changes from 2.74 to 2.76.