This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Authoring/Maintenance"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
<br/> | <br/> | ||
<p> | <p> | ||
| + | |||
| + | |||
| + | # '''Description:''' There should be means to support collaborative development and user feedback/change requests at the vocabulary level. | ||
| + | ## (details as needed) | ||
| + | |||
| + | # '''Who needs it and why?''' - | ||
| + | # '''Why should this be standardized?''' - There is a need to give vendors guidance regarding how they connect their implementations and channel user requests. | ||
| + | <br/> | ||
| + | # '''Questions and issues:''' | ||
| + | ## | ||
| + | <br/> | ||
| + | <p> | ||
| + | |||
[[http://informatics.mayo.edu/wiki/index.php/CTSII_Use_Cases#CTS2_Use_Cases BACK]] | [[http://informatics.mayo.edu/wiki/index.php/CTSII_Use_Cases#CTS2_Use_Cases BACK]] | ||
Revision as of 20:28, 23 May 2005
- Description: Ability to request incremental updates, or change sets (based on versioning) of a code set.
- (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:
- Description: There should be means to support collaborative development and user feedback/change requests at the vocabulary level.
- (details as needed)
- Who needs it and why? -
- Why should this be standardized? - There is a need to give vendors guidance regarding how they connect their implementations and channel user requests.
- Questions and issues:
[BACK]
