Page History

...

We will otherwise map the definition tag to a definition type property in the LexGrid and concept property tag attributes will define the numerical portion of the unique identifier where the concept property name is "internalId."  The code tag will define the other portion of the unique identifier using the code attribute to concatenate to the end of the numerical identifier preceded by a colon.  These should complete conformance, to a certain extent, with with old LexEVS load of the RIM from the MSAccess database.

To Be Determined:

1. How value sets are defined in the vocabulary core MIF and how and whether they will be mapped to LexEVS.
2. How much of the RIM core MIF should be mapped to LexEVS, if any, and whether relationships implied in the defininigCodeSystem, dataType and conceptDomain tags should be expressed in LexEVS.
3. whether attributes in the RIM core MIF under contained classes be first class entities.
4. whether endPoint designations should somehow be expressed in LexEVS.

Implementation Design

The loading application will parse the xml and stream elements to be marshaled into coding scheme, entity and association elements where they can be tied together as a coding scheme object and loaded to the LexGrid data base.