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

Difference between revisions of "Versioning"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
# '''Description:''' CTS2 needs to be able to represent multiple versions of a coding system.  The interface needs to support:
+
== Use Case Name: Code System Versioning ==
## Enumeration of the versions supported by the interface
+
* '''Description:''' CTS2 needs to be able to represent multiple versions of a coding system.  The interface needs to support:
## The ability to query version history concept code - when it was introduced, when it was changed, when it was withdrawn, what happened to it, etc.
+
** Enumeration of the versions supported by the interface
## The ability to select a specific version of a terminology and make queries relative to that version
+
** The ability to query version history concept code - when it was introduced, when it was changed, when it was withdrawn, what happened to it, etc.
# '''Who needs it and why?''' - VHA
+
** The ability to select a specific version of a terminology and make queries relative to that version
# '''Why should this be standardized?''' - This needs to be standardized because it is a generic issue that crosses specific terminologies
+
* '''Who needs it and why?''' - VHA
 +
* '''Why should this be standardized?''' - This needs to be standardized because it is a generic issue that crosses specific terminologies
 
<br/>
 
<br/>
# '''Questions and issues:'''
+
* '''Questions and issues:'''
## How do versions fit into the HL7 CD Data types?
+
** How do versions fit into the HL7 CD Data types?
 
<br/>
 
<br/>
 
<p>
 
<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:44, 23 May 2005

Use Case Name: Code System Versioning

  • Description: CTS2 needs to be able to represent multiple versions of a coding system. The interface needs to support:
    • Enumeration of the versions supported by the interface
    • The ability to query version history concept code - when it was introduced, when it was changed, when it was withdrawn, what happened to it, etc.
    • The ability to select a specific version of a terminology and make queries relative to that version
  • Who needs it and why? - VHA
  • Why should this be standardized? - This needs to be standardized because it is a generic issue that crosses specific terminologies


  • Questions and issues:
    • How do versions fit into the HL7 CD Data types?


[BACK]