 |
Page History
| Scrollbar | ||
|---|---|---|
|
| Page info | ||||
|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
...
Introduction
This document is a section of the Design and Architecture Guide.
Information models overview
The information below is provided for introductory purposes. A full description of all available model components is also available in the javadoc distributed with the LexEVS installation package (see file breakdown in the Installation Guide). Since the javadoc is automatically generated and synchronized during the build process, it is recommended as the primary reference for use by LexEVS developers.
LexGrid model
The LexGrid model is mastered in XML schema. The LexBIG project currently builds on the 2009 version of the LexGrid schema. A formal representation, showing portions of this structure that are of primary interest to the LexEVS project, is presented below. A complete version of the model is available at http://informatics.mayo.edu?page=lgm
.
CodingSchemes
The CodingSchemes branch of the model defines high level containers for concepts and relations. Each CodingScheme represents a unique code system or version in the LexBIG service. Components of interest include:
...
A collection of properties.
codingSchemes
Concepts
Each concept represents a unique entity within the code system, which can be further described by properties and related to other concepts through relations.
conceptsAndInstances
<u>codingScheme</u>
A resource that makes assertions about a collection of terminological entities.
...
A binary relation from a set of entities to a set of entities and/or data. The entityType for the class concept must be "association".
conceptsAndInstances
entities
<u>codingScheme</u>
A resource that makes assertions about a collection of terminological entities.
...
A binary relation from a set of entities to a set of entities and/or data. The entityType for the class concept must be "association".
entities
entity
<u>entity</u>
A set of lexical assertions about the intended meaning of a particular entity code.
...
A link between two properties for an entity.. Examples include acronymFor, abbreviationOf, spellingVariantOf, etc. Must be in supportedPropertyLink.
entity
Relations
Relations are used to define and qualify associations between concepts.
association
<u>codingScheme</u>
A resource that makes assertions about a collection of terminological entities.
...
An entity that occurs in one or more instances of a relation on the "from" (or left hand) side of a particular relation.
association
associationInstance
<u>association</u>
A binary relation from a set of entities to a set of entities and/or data. The entityType for the class concept must be "association".
...
A modifier that further qualifies the particular association instance.
associationInstance
Naming
These elements are primarily used to define metadata for a coding scheme, mapping locally used names to global references.
...
A source role and athe URI of the defining resource
naming
Value Domain Definition
The Value Domain Definition branch of the LexGrid model defines the contents of a value domain.
...
Here is a UML representation of Value Domain Definition in LexGrid 200901 model:
Model components
<u>valueDomains</u>
A collection of value domain definitions.
...
AND: Only include the entity codes that are both in the value domain and the definition entry; logical AND.
Value Domain services
This feature is new in LexEVS 5.1. For details on using value domain services, see the Programmer's Guide, Value Domain Services section.
Pick List Definition
Pick List Definition branch of LexGrid model definies the contents of a pick list.
...
Here is a UML representation of Pick List in LexGrid 200901 model:
Model components
<u>pickLists</u>
A collection of pick list definitions.
...
entityCodeNamespace: Local identifier of the namespace of the entity code if different than the pickListDefinition defaultEntityCodeNamespace. entityCodeNamespace must match a local ID of a supportedNamespace in the mappings section.
Pick List services
This feature is new in LexEVS 5.1. For details on using pick list services, see the Programmer's Guide, Pick List Services section.
LexBIG
...
Model
The following extensions to the LexGrid model were introduced in support of caBIG® requirements. As with the LexGrid model, this document provides a summary of the most significant elements for consideration by LexBIG programmers. The complete and current version of the model is available online at http://informatics.mayo.edu?page=lexex .
Core
LexBIG core elements provide enhanced referencing and controlled resolution of LexGrid model objects.
...
References a service in the Globus environment, this will be a global service handle (GSH).
InterfaceElements
Defines metadata related to model objects required by the runtime.
...
The combination of a system release and all of the entityVersions
that accompanied that release.
NCIHistory
Maintains a record of modifications made to a code system.
...
A change event as documented in ftp://ftp1.nci.nih.gov/pub/cacore/EVS/ReadMe_history.txt. Note that date and time of the change event is recorded in the containing version. All change events for the same/date and time a recorded in the same version.</html>
| Scrollbar | ||
|---|---|---|
|