This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Requirements-Code Translations"
Jump to navigation
Jump to search
(New page: {{V3 Methodology Requirements}} Code translations are essentially a collection of assertions about which codes from one code system might reasonably be substituted for codes from another c...) |
|||
Line 11: | Line 11: | ||
| ''MIF'' | | ''MIF'' | ||
| mif-vocabulary-model.xsd/CodeTranslations | | mif-vocabulary-model.xsd/CodeTranslations | ||
+ | |- | ||
+ | | ''OMG Mapping'' | ||
+ | | {{OMG-MIF-HL7 Profile}} Use Stereotyped Package to create groupings | ||
|} | |} | ||
Line 35: | Line 38: | ||
* [[Requirements-Annotations#Change Request|Change Request]] | * [[Requirements-Annotations#Change Request|Change Request]] | ||
* [[Requirements-Annotations#Deprecation Information|Deprecation Information]] | * [[Requirements-Annotations#Deprecation Information|Deprecation Information]] | ||
+ | |- | ||
+ | | ''OMG Mapping'' | ||
+ | | {{OMG-MIF-In UML}} Add stereotype to capture information | ||
|} | |} | ||
Line 54: | Line 60: | ||
| ''MIF'' | | ''MIF'' | ||
| mif-vocabulary-model.xsd/CodeTranslation/@quality | | mif-vocabulary-model.xsd/CodeTranslation/@quality | ||
+ | |- | ||
+ | | ''OMG Mapping'' | ||
+ | | {{OMG-MIF-HL7 Profile}} Use Stereotyped Package to create groupings | ||
|} | |} | ||
Line 83: | Line 92: | ||
* [[Requirements-Annotations#Open Issue|Open Issue]] | * [[Requirements-Annotations#Open Issue|Open Issue]] | ||
* [[Requirements-Annotations#Ballot Comment|Ballot Comment]] | * [[Requirements-Annotations#Ballot Comment|Ballot Comment]] | ||
+ | |- | ||
+ | | ''OMG Mapping'' | ||
+ | | {{OMG-MIF-HL7 Profile}} Use Stereotyped associations | ||
|} | |} |
Latest revision as of 16:26, 9 August 2010
Code translations are essentially a collection of assertions about which codes from one code system might reasonably be substituted for codes from another code system. Translations are essential when working in an environment where data may not be captured in the code system in which it is eventually required for transmission or analysis.
Requirement | Translations need to be able to be maintained and published as collections. |
Rationale | It's pretty unusual for translations to be made individually. Usually all codes or a subset of codes are translated from one code system into a second code system. Grouping translations together allows common use of metadata such as the purpose of the translations, who did them, etc. |
MIF | mif-vocabulary-model.xsd/CodeTranslations |
OMG Mapping | Use Stereotyped Package to create groupings |
Requirement | Code translation collections may have a number of different types of annotations |
Rationale | See rationales for individual annotations types |
Implementation | |
OMG Mapping | Add stereotype to capture information |
Requirement | Each mapping needs to be able to assert the 'quality' of the mapping. |
Rationale | When comparing codes between code systems, it's unusual for two concepts to be exact matches. By examining the quality of a mapping, users of the mapping can be made aware of any issues they're likely to run into. |
Methodology |
|
MIF | mif-vocabulary-model.xsd/CodeTranslation/@quality |
OMG Mapping | Use Stereotyped Package to create groupings |
Requirement | Mappings need to be able to indicate which direction(s) translation is considered appropriate. |
Rationale | When creating a mapping, the intention might be to map from code system A to B, from B to A or map in both directions. If the intention is not clear, then someone might translate using the mapping in the wrong direction which can be semantically inappropriate. |
MIF | mif-vocabulary-model.xsd/CodeTranslation/@translatableDirection |
Requirement | Code translations may have a number of different types of annotations |
Rationale | See rationales for individual annotations types |
Implementation | |
OMG Mapping | Use Stereotyped associations |