|
|
| (6 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | == Use Case Name: Code System Versioning ==
| + | Versioning is an issue which applies to various artefacts, amongst which: |
| − | * '''Description:''' CTS2 needs to be able to represent multiple versions of a coding system. The interface needs to support:
| + | *[[Code System Versioning]] |
| − | ## Enumeration of the versions supported by the interface
| + | *[[Value Set Versioning]] |
| − | ## The ability to query version history by concept code - when it was introduced, when it was changed, when it was withdrawn, what happened to it, etc.
| + | *[[Interaction Versioning]] |
| − | ## The ability to select a specific version of a terminology and make queries relative to that version
| + | *[[Document Versioning]] (CDA) |
| − | * '''Who needs it and why?''' - General requirement for messaging and querying terminology services.
| |
| − | # A message may deliver data in a coded datatype.
| |
| − | ## To support interoperability when receiving messages from multiple different systems. Where only the code and code system/version is supplied then a query on terminology service would return the display name. This would also apply if using a version of the code system to manage different languages
| |
| − | ## Where code, code system/version, and display name is included in the message then a query on the terminology service would check the validity of the code against the version held in the receiving system.
| |
| − | * '''Why should this be standardized?''' - This needs to be standardized as value sets are standard HL7 vocabualry objects. Where code system versioning not standardised then it will not be possible to achieve semantic interoperability for this type of data
| |
| − | <br/>
| |
| − | * '''Questions and issues:'''
| |
| − | ** How do versions fit into the HL7 CD Data types? | |
| − | ** Since HL7 assigns an OID and version number for a code system, does CTS1 allow the version to be queried? Does CTS1 (HL7 uses the OID only, and not the version number.) | |
| − | ** CTS 2 should use the code system OID and Version number when regestering code systems.
| |
| − | <br/>
| |
| − | <p>
| |
| − | | |
| − | == Use Case Name: Value Set Versioning ==
| |
| − | * '''Description:''' Add definition of Value Set - Russ. CTS2 needs to be able to represent multiple versions of a value set. The interface needs to support: | |
| − | ## Enumeration of the versions of value sets supported by the interface
| |
| − | ## 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.
| |
| − | ## The ability to select a specific version of a value set and make queries relative to that version
| |
| − | * '''Who needs it and why?''' Terminology services may need to support the management of value sets within both applications and messages. It is common for codes to be sourced from specific value sets or terminology subsets, rather than from the parent terminology eg. the acceptable codes in a problem field of an EHR may be drawn from the Disease hierarchy of the terminology. Value sets are defined by application or message owners and may draw their content from a specific version of a terminology or coding system. Valuesets are synonymous with a terminology subset. This can be done by selecting specific concepts or a concept and its children. | |
| − | # HL7 has determined that value sets should be registered and allocated an OID. Value sets will change over time and hence will also require version codes.
| |
| − | # Custodians or editors of valuesets will require a capacity to be altered to logical changes in the value set which occur as the result of new versions being created of the value set's parent codeset.
| |
| − | * '''Why should this be standardized?''' - This functions function is required to support terminology subset/valueset management.
| |
| − | <br/>
| |
| − | * '''Questions and issues:'''
| |
| − | ** Are value set versions linked to Code System versions?
| |
| − | <br/>
| |
| − | <p>
| |
| − | | |
| − | [[http://informatics.mayo.edu/wiki/index.php/CTSII_Use_Cases#CTS2_Use_Cases BACK]] | |
