Page History

...

1 - Translate local codes to standard code systems

A user has a local proprietary code system that the user would like translated to standard code systems data base that uses a combination of enumerated values (e.g. 0: Male, 1: Female, 9: Unknown) and codes drawn from outside code systems such as HICDA or MedDRA.  The user needs to translate these codes into the codes that are adopted by the vocabulary and common data elements workspace. The user would like to be able to capture these local concepts in an Excel spreadsheet and submit them in a simple electronic way (such as an attachment to an email). The user would like to have the concepts returned with the original concepts, the new standard coded concepts with the quality of the mapping, and the definitions associated with the coded concepts. Furthermore the user would like the concepts returned as a CSV file  The user needs to first determine whether there are existing value sets that already represent the same or a broader conceptual space represented in his data base. If one exists, the user then needs to determine whether a mapping exists to the corresponding HICDA or MedDRA codes.  If a value set does not already exist, the user needs access to a set of tools that will (a) allow him to upload his code list along with any corresponding descriptive information, (b) determine which code system(s) are appropriate targets, (c) perform the actual mapping, which is described in a separate use case.  Note that the user may need to record local mappings (enumerated values that are of no interest to the larger community) locally while recording mappings between external code systems in a fashion that is accessible by the whole community.  Once recorded, the user needs access the SI2 framework to locate a service that will allow him to automate the transformations in the target workflow environment, localizing the service if needed to meet performance or confidentiality requirements and connecting the service to the appropriate mapping(s).  The user may also need to embed links to this code in his local software as needed.

2 - Create nested value sets

...

A user has a group of caDSR common data elements which have been used in form construction in the past. Now the user would like to move these forms to the HL7 CDA structure. The user finds it possible to represent a portion but not all of the contextual meaning of the data elements in 11179. The user would like to transform the CDEs to HL7 V3 class structures in order to get the full contextual meaning as used in the CDA document. The user would like to submit the list of CDEs to the ECCF registry transformer and have a set of V3 object classes returned.

6 - Creation of Value Sets and Value Set Mappings

A user has identified one or more sets of permissible values that need to be mapped to standard codes used by the vocabulary and common data elements workspace.  These values need to be assembled in a format such as Excel, XML or simple tab separated values and then be uploaded to a service that will allow them to be mapped to the codes that are endorsed for interchange on the grid.  The user must be able to locate existing value sets and to construct new ones where appropriate targets do not exist.  The user needs to be able to instruct the service to do automatic first approximation at a mapping, and then needs to be able to search, refine and validate mapping, the ability to record a "quality" metric that states how closely the mapping actually approximates the intent of the original value.  The user may encounter potential problems and omissions during this process and will need to submit suggested changes and enhancements to the appropriate oversight body for potential enhancement.  Once created, the user needs to be able to download the resulting mappings in an electronic format such as Excel, XML, etc. as well as to submit the mappings to a service, either local or centralized, that will represent the mappings via a standardized API.