Page History

...

Introduction

LexEVS CTS2 Usage Context Query API provides capability to query Usage Context available in the system and also to query the binding between Value Set and Concept Domain in conjunction with Usage Context. In LexEVS, the Usage Context is essentially an entity of type 'usageContext' in a code system version. Using LexEVS CTS 2 Authoring or Loader interfaces, you could create a Code System specially for Usage Context entities, but this is not necessary, but will be convenient to have Usage Context entries in specific code system(s).

Interface

org.lexevs.cts2.query.UsageContextQueryOperation is the main interface for all the queries against Usage Context. This interface can be accessed using main LexEVSCTS2 interface, like:

<source>
org.lexevs.cts2.query.UsageContextQueryOperation cdQueryOp = new org.lexevs.cts2.LexEvsCTS2Impl().getQueryOperation().getUsageContextQueryOperation();
</source>

Query Functions

Here are the major query functions available using UsageContextQueryOperation interface:

getUsageContextCodingScheme

This function returns detailed usage context code system.

...

getUsageContextEntity

This function returns detailed Usage Context entity.

...

getUsageContextEntitisWithName

This function returns all the Usage Context entities that matches the name supplied.

...

getUsageContextCodedNodeSet

This is a helper function that returns Coded Node Set(CNS) for Usage Context entities. Further restrictions like, matchingDesignation, Status, Properties, etc., can be applied on this CNS and than resolved.

...

 _usageContextCNS.restrictToMatchingProperties(null, new PropertyType[] { PropertyType.PRESENTATION }, "Auto", "startsWith", null);_
 _org.LexGrid.LexBIG.DataModel.Core.ResolvedConceptReference[] rcr = usageContextCNS.resolveToList(null, null, null, 1).getResolvedConceptReference();_ |

listAllUsageContextEntities

This function returns all the Usage Context entities found in supplied code system version.

...

listAllUsageContextIds

This function is similar to previous one, but instead of returning detailed Usage Context entities, it just returns identifiers of the Usage Context.

...

...