 |
Page History
...
Two separate source files exist with the file extension coremif in the RIM distribution package, "DEF=UV=RIM=<version>" and "DEF=UV=VO=<version>." The first defines a kind of super hierarchy to the RIM and the second defines the values and relationships that are consistent with the current load of the HL7 RIM to LexEVS. Opportunities for expressing entities and assertions that define entity relationships exist for the RIM core MIF that should be outlined here. Also connections from this MIF file to the DEF=UV=VO, or vocabulary, file can further define relationships to the values that are currently expressed in the old LexEVS mapping.
The RIM core MIF expresses a number of tags under the root static model that are defined as subject area packages. We know from the defining xsd that these are sub-packages and we can see that one sub-package can be nested within another, implying that one package is a subclass of another. Furthermore some sub-packages define contained class tags implying yet another area of classification. We can deduce relationships from these that will allow us to map to LexEVS target and source entities. When the contained classes are elsewhere defined in the RIM core MIF attributes and annotations are declared which normally might map to Entity Properties in LexEVS. However, the attribute tagged values will some times bear references to a data type tag or a concept domain tag, both of which are defined in the vocabulary core MIF and correlate to the the code systems also defined there. We could pre-corrolate this relationship by persisting this as a LexEVS association, or we could leave it as a property and post correlate the relationship for interested users through a series of LexEVS calls.
