This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Versioning"
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
## 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 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 | ## The ability to select a specific version of a terminology and make queries relative to that version | ||
− | # '''Who needs it and why?''' - | + | # '''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 | # '''Why should this be standardized?''' - This needs to be standardized because it is a generic issue that crosses specific terminologies | ||
<br/> | <br/> |
Revision as of 20:05, 23 May 2005
- 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]