Details
-
New Feature
-
Status: Closed
-
Could
-
Resolution: Fixed
-
Platform 1.10.0
-
High
-
Soldevelo Sprint 1
Description
Now that we've upgraded Hibernate to a version that supports hibernate search (in OpenMRS 1.9) we should look into removing our own mediocre search index implementation (concept_word) and do something more powerful and faster that relies on hibernate search, or lucene.
A powerful and important feature of concept searching is the inclusion of stop words and equivalent words. Any searching solution should incorporate these features.
- stop word - words that should not be indexed (e.g., a, and, the, ...)
- equivalent words - variations of common terms (e.g., heart, cardiac, myocardial, myocardium). Ideally, these are normalized to a single term in indexing and searching so that, for example, a search for "heart" and "cardiac" would return identical results. This can significantly reduce the need for synonyms containing these equivalent words.
Gliffy Diagrams
Attachments
Issue Links
- depends on
-
ITSM-2894 Deploy hibernate-search feature branch by CI
-
- Closed
-
-
ITSM-2895 Configure CI to test hibernate-search feature branch
-
- Closed
-
- relates to
-
TRUNK-2705 Improve concept searching when a concept contains multiple matched concept names
-
- Closed
-
-
TRUNK-4441 Migrate getDrugs to use LuceneQuery
-
- Closed
-
-
TRUNK-425 Use Hibernate Search with Apache Lucene for Patient Searches
-
- Closed
-
-
TRUNK-3843 Introduce API performance tests
-
- Closed
-
-
TRUNK-4426 Search widget should find concepts by mappings
-
- Closed
-