Versioning

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:

1. 1. Enumeration of the versions supported by the interface
   2. 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.
   3. 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?

Use Case Name: Value Set Versioning

• Description: CTS2 needs to be able to represent multiple versions of a value set. The interface needs to support:

1. 1. Enumeration of the versions of value sets supported by the interface
   2. The ability to query version history of a value set - when it was introduced, when it was changed, when it was withdrawn, what happened to it, etc.
   3. The ability to select a specific version of a value set and make queries relative to that version

• Who needs it and why? - HL7/NCI?
• Why should this be standardized? - This needs to be standardized as value sets are standard HL7 vocabualry objects

• Questions and issues:
  • Are value set versions linked to Vode System versiona?

[BACK]