Discover Functional Profile
A key function desired by virtually all stakeholders is the ability to query by example using an item from a model or vocabulary (e.g., data element, property, data type, constraint, relation, concept, etc.) to find equivalent and related elements defined anywhere in the knowledge repository. The response should provide an easily understood description of the degree and nature of the semantic convergence between the example item and responsive items.
Discovery has architectural implications on the Semantic Infrastructure:
Service Descriptions include reference to policies defining conditions of use and optionally contracts representing agreement on policies and other conditions. This requires the following capabilities (as also enumerated under governance):
- descriptions to enable the service modules to be visible, where the description includes a unique identifier for the service and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the service, its functions, and its effects;
- one or more discovery mechanisms that enable searching for services that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual service descriptions, possibly through some repository mechanism;
- accessible storage of services and service descriptions, so service participants can access, examine, and use the services as defined.
Descriptions include references to metrics which describe the operational characteristics of the subjects being described. This requires the following capabilities (as partially enumerated under governance):
- the infrastructure monitoring and reporting information on SOA resources;
- possible interface requirements to make accessible metrics information generated or most easily accessed by the service itself;
- mechanisms to catalog and enable discovery of which metrics are available for a described resources and information on how these metrics can be accessed;
- mechanisms to catalog and enable discovery of compliance records associated with policies and contracts that are based on these metrics.
Descriptions provide up-to-date information on what a resource is, the conditions for interacting with the resource, and the results of such interactions. As such, the description is the source of vital information in establishing willingness to interact with a resource, reachability to make interaction possible, and compliance with relevant conditions of use. This requires the existence of:
- one or more discovery mechanisms that enable searching for described resources that best meet the criteria specified by a service participant, where the discovery mechanism will have access to individual descriptions, possibly through some repository mechanism;
- tools to appropriately track users of the descriptions and notify them when a new version of the description is available.
This Functional Profile includes, but is not limited to, the following capability elaborations:
- queryModelTouchpoints
- 026.3
- 029
- publishedLiteratureIndex
- queryUnstructuredSources
- queryEvsAndModels
- saveQueryResults
Derived From Requirements
- Gap Analysis::Discover::007 - System allows for discovery of touch points to other models System allows for discovery of touch points to other models
- *Gap Analysis::Discover::026.3 - Provide a mechanism to assist the user in choosing the right data element * Provide a mechanism to assist the user in choosing the right data element
- Gap Analysis::Discover::029 - Support search like 'x' for concepts in the EVS using natural language processing to identify possible matches Support search like 'x' for concepts in the EVS using natural language processing to identify possible matches
- Gap Analysis::Discover::033 - Concept based search Provide a discovery service/tool which exposes data elements not based on the Names stored in the KR but by using a concept from the EVS search and pulling associated Administered Components from the KR to match.
- Gap Analysis::Discover::148 - Index published literature Create indexes of published literature using natural language processing and ontologies to index the content
- Gap Analysis::Discover::159 - Unstructured Document Search Automatically extract information for reuse from unstructured sources, programmatic access to the 'materials and methods section of a paper' so the same experiments can be performed using your own data
- Gap Analysis::HL7 CIC::CIC-16 - Retain query results in different representation and storage formats There is a need to provide retention of query results in different formats
- Gap Analysis::EVS::EVS-5 - Unified UI for Model and EVS Search End-users need the ability to perform a search for models and to search EVS through a single user interface
queryModelTouchpoints
System allows for discovery of touch points to other models
026.3
Provide a mechanism to assist the user in choosing the right data element
029
Support search like 'x' for concepts in the EVS using natural language processing to identify possible matches
publishedLiteratureIndex
Create indexes of published literature using natural language processing and ontologies to index the content
queryUnstructuredSources
Automatically extract information for reuse from unstructured sources, programmatic access to the 'materials and methods section of a paper' so the same experiments can be performed using your own data
queryEvsAndModels
Support search for models and the EVS through a single User Interface
Provide a discovery service/tool which exposes data elements not based on the Names stored in the KR but by using a concept from the EVS search and pulling associated Administered Components from the KR to match.
saveQueryResults
There is a need to provide retention of query results in different formats
