This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "Authoring/Maintenance"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
# '''Description:''' Ability to request incremental updates, or change sets (based on versioning) of a code set.
+
* '''Description:''' Ability to request incremental updates, or change sets (based on versioning) of a code set.
 
## (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 between CTS service providers.  This will help to ensure predictable terminology content.
 
# '''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:'''
 
##
 
##
 
<br/>
 
<br/>
Line 11: Line 11:
  
  
# '''Description:''' There should be means to support collaborative development and user feedback/change requests at the vocabulary level.
+
* '''Description:''' There should be means to support collaborative development and user feedback/change requests at the vocabulary level.
 
## (details as needed)
 
## (details as needed)
  
# '''Who needs it and why?''' -  
+
* '''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.
+
* '''Why should this be standardized?''' - There is a need to give vendors guidance regarding how they connect their implementations and channel user requests.
 
<br/>
 
<br/>
# '''Questions and issues:'''
+
* '''Questions and issues:'''
 
##
 
##
 
<br/>
 
<br/>

Revision as of 20:31, 23 May 2005

  • Description: Ability to request incremental updates, or change sets (based on versioning) of a code set.
    1. (details as needed)
  • Who needs it and why? -
  1. 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.
    1. (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]