 |
Page History
...
| Code Block |
|---|
//First create a ConceptReferenceList to describe the Concept to
search for.
//In this example we use the helper class 'ConvenienceMethods'.
ConceptReferenceList crefs =
ConvenienceMethods.createConceptReferenceList(new String[]
{ "C1234567"}, "NCI MetaThesaurus");
//Next, restrice the CodedNodeSet.
cns.restrictToCodes(crefs);
|
Lastly, resolve the match.
...
Use the 'LexBIGService' API method 'getMappings'.
Extract for this the Supported Association Qualifiers using the 'getSupportedSource' method.
| Info | ||
|---|---|---|
|
...
This can be applied to any Coding Scheme, not just the NCI MetaThesaurus. |
getChildren
Use the 'CodedNodeGraph' API.
...
Use the 'LexBIGService' API method 'getMappings'.
Extract for this the Supported Associations using the 'getSupportedAssociation' method. NOTE:
| Info | ||
|---|---|---|
| ||
Different ontologies may describe their 'Synonym' relations differently. |
getAllTermAssociationQualifierTypes
...
| Code Block |
|---|
ResolvedConceptReferenceList matches = cns.resolveToList(null, null,
null, 1);
|
getHistoryRecords
...
| Code Block |
|---|
ResolvedConceptReferenceList matches = cns.resolveToList(null, null,
null, 1);
|
Once the ResolvedConceptReference has been obtained, extract the desired Properties and inspect the Qualifiers for the Semantic Type.
...
Once the ResolvedConceptReference has been obtained, extract the desired Properties and inspect the Qualifiers.NOTE:
| Info | ||
|---|---|---|
| ||
Associations between codes may also have Qualifiers. |
getAtomCollectionbyCui
In LexEVS, a NCI MetaThesaurus CUI is represented by an Entity (with the CUI being the code for that Entity).
Atoms of that CUI are represented by 'Presentation'(s) of the Entity.
...
Next, restrict that to the desired Code Name ('Heart' in this example):
| Info | ||
|---|---|---|
|
...
To match the String 'Heart' exactly, use the search algorithm 'exactMatch'. |
| Code Block |
|---|
//Next, restrice the CodedNodeSet.
cns = cns.restrictToMatchingDesignations("Heart", null, "exactMatch", null);
|
...
To view the Properties, see 'getPropertyValues' above.
For examples, see the LexEVS Example classes
- org.LexGrid.LexBIG.example.FindPropsAndAssocForCode
fetchPropertyCollectionByCodes
...
| Code Block |
|---|
//Restrict the 'relationContainerName' to the desired container.
NOTE: These containers are
//ontology specific--each ontology defines its own relation container names.
CodedNodeGraph cng = lexevsService.getNodeGraph(String codingScheme,
CodingSchemeVersionOrTag versionOrTag, String relationContainerName);
ResolvedConceptReference[] rcr = cng.resolveAsList(ConceptReference
graphFocus, boolean resolveForward, boolean resolveBackward,
int resolveCodedEntryDepth, int
resolveAssociationDepth, LocalNameList propertyNames,
PropertyType[] propertyTypes,
SortOptionList sortOptions, int maxToReturn).getResolvedConceptReference();
|
...
Once focused and resolved, use the 'getSourceOf' or 'getTargetOf' methods on the ResolvedConceptReference to find the Associations of a given Code.
For examples, see the LexEVS Example classes
- org.LexGrid.LexBIG.example.FindRelatedCodes
- org.LexGrid.LexBIG.example.FindPropsAndAssocForCode
getInverseRoleCollectionbyCode
Use the CodedNodeGraph API to find the immediate relations of a Concept.
To find the Inverse Roles, restricting the Relations Container may be necessary (see getRoleCollectionbyCode above).
Depending on how the onotology defines an 'inverse' role or association, these can be restricted as well.
...
Use the 'LexBIGService' API method 'getSupportedCodingSchemes' - and extract the Names (local name, registered name, etc...) as needed.
| Scrollbar | ||
|---|---|---|
|
