This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Authoring/Maintenance"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
− | # '''Description:''' Ability to request incremental updates (based on versioning) of a codeset. | + | # '''Description:''' Ability to request incremental updates, or change sets (based on versioning) of a codeset. |
## (details as needed) | ## (details as needed) | ||
# '''Who needs it and why?''' - | # '''Who needs it and why?''' - | ||
− | # '''Why should this be standardized?''' - As new versions of code sets are released, updating to the newest version of that codeset should be consistent. | + | # '''Why should this be standardized?''' - As new versions of code sets are released, updating to the newest version of that codeset should be consistent between CTS service providers. This will help to ensure predictable terminology content. |
<br/> | <br/> | ||
# '''Questions and issues:''' | # '''Questions and issues:''' |
Revision as of 20:04, 23 May 2005
- Description: Ability to request incremental updates, or change sets (based on versioning) of a codeset.
- (details as needed)
- Who needs it and why? -
- Why should this be standardized? - As new versions of code sets are released, updating to the newest version of that codeset should be consistent between CTS service providers. This will help to ensure predictable terminology content.
- Questions and issues:
[BACK]