LexGrid is the model used to store terminologies. The LexGrid Model is Mayo Clinic's proposal for standard storage of controlled vocabularies and ontologies. The LexGrid Model defines how vocabularies should be formatted and represented programmatically, and is intended to be flexible enough to accurately represent a wide variety of vocabularies and other lexically-based resources. The model also defines several different server storage mechanisms (e.g., relational database, LDAP) and a an XML format. This model provides the core representation for all data managed and retrieved through the LexBIG system, and is now rich enough to represent vocabularies provided in numerous source formats including:
LexBIGServiceManager - The service manager provides a centralized access point for administrative functions, including write and update access for a service's content. For example, the service manager allows new coding schemes to be validated and loaded, existing coding schemes to be retired and removed, and the status of various coding schemes to be updated and changed.
Service Management Subsystem
Lexical Set Operations provides methods to return a lists or iterators of coded entries. Supported query criteria include the application of match/filter algorithms, sorting algorithms, and property restrictions. Support is also provided to resolve the union, intersection or difference of two node sets.
Graph Operations support the subsetting of concepts according to relationship and distance, identification of relation related source and target concepts, and graph traversal. Additional operations include enumeration and traversal of concepts by relation, walking of directed acyclic graphs (DAGs), enumeration of source and target concepts for a relation, and enumeration of relations for a concept.
History provides vocabulary-specific information about concept insertions, modifications, splits, merges, and retirements when supplied by the content provider.
LexEVS CTS 2 Services
Key is that implementations can be shared – No one organization has to offer all services
- used for REST, SOAP and JSON formatting
- Includes item / directory / list
- Import and Export content
- Code System
- Code System Version
- Entity Description
- Value Set
- Value Set Definition
- Resolved Value Set
- Map Version
- Map Entry
- Concept Domain
- Concept Domain Binding
- Each component can be implemented by itself or in conjunction with other components
- Components reference other components via:
- URI’s – if the referenced component is not known to the service
- HREF’s (optional) – if the referenced component IS known to the service
LexEVS CTS2 Documentation