METHOD AND SYSTEM FOR INTERFACING WITH A MULTI-LEVEL DATA STRUCTURE
The present invention provides a method and system for interfacing with a multi-level data structure by selecting a concept object stored in the multi-level data structure, displaying a first image representing the selected concept object, displaying one or more second images generally above the first image, and displaying a first connector connecting each second image to the first image. Whenever the selected concept object has one or more child concept objects, one or more third images are displayed generally below the first image, and a second connector is displayed connecting each third image to the first image. Whenever the selected concept object has one or more lateral concept objects, one or more fourth images are displayed generally on one or both sides of the first image, and a third connector is displayed connecting each fourth image to the first image.
This application is a continuation of U.S. application Ser. No. 10/660,934, filed on Sep. 12, 2003, entitled, “METHOD AND SYSTEM FOR INTERFACING WITH A MULTI-LEVEL DATA STRUCTURE”, the entire contents of which are hereby incorporated by reference.
FIELD OF THE INVENTIONThe present invention relates generally to the field of computer systems and, in particular, to a method and system for interfacing with a multi-level data structure.
BACKGROUND OF THE INVENTIONAs demonstrated by the Unified Medical Language System (“UMLS”), merging multiple incompatible terminology “ideas” into one imposes a unity upon concepts that are not equivalent. This unification results in ambiguity of interpretation and a loss of structural integrity of the original coding system. While the UMLS has achieved the goal of imposing order upon unrelated data sets, it results in inappropriate representation of all the coding systems involved and, worse, true errors in the stated congruence of conceptual models.
Accordingly, there is a need for a multi-level data structure that provides a wide breadth of standardized knowledge, representing the concepts of every aspect of an enterprise. In addition, there is a need for a method and system that interfaces with the multi-level data structure and that enables easy access, use and maintenance of standardized knowledge relating to an enterprise.
SUMMARY OF THE INVENTIONThe present invention provides a method and system for interfacing with a multi-level data structure that encompasses a wide breadth of standardized knowledge representing the concepts of every aspect of an enterprise. The multi-level data structure of the present invention provides concepts and relationships that provide controlled terminology completely capturing the language of an enterprise. Moreover, the multi-level data structure or knowledge model of the present invention provides for the accurate and complete representation of all terminology systems thereby maintaining the truth and integrity of each of those terminology systems.
In one representative embodiment of the present invention, an interface provides access to a multi-level data structure that has concepts and relationships that provide controlled medical terminology that completely captures the language of healthcare. The present invention also includes a multidimensional semantic content network. The interface of the present invention provides a language-modeling environment enabling the user to maintain and enhance the semantic content. A graphical user interface (“GUI”) is also provided with which a user can easily navigate in order to use and maintain the terminology content.
The present invention provides a method for interfacing with a multi-level data structure by selecting a concept object stored in the multi-level data structure, displaying a first image representing the selected concept object, displaying one or more second images generally above the first image, and displaying a first connector connecting each second image to the first image. Each second image represents a parent concept object of the selected concept object. Whenever the selected concept object has one or more child concept objects, one or more third images are displayed generally below the first image, and a second connector is displayed connecting each third image to the first image. Each third image represents a child concept object of the selected concept object. Whenever the selected concept object has one or more lateral concept objects, one or more fourth images are displayed generally on one or both sides of the first image, and a third connector is displayed connecting each fourth image to the first image. Each fourth image represents a lateral concept object of the selected concept object.
The present invention also provides a computer program embodied on a computer readable medium for interfacing with a multi-level data structure. The computer program includes code segments for selecting a concept object stored in the multi-level data structure, displaying a first image representing the selected concept object, displaying one or more second images generally above the first image, and displaying a first connector connecting each second image to the first image. Each second image represents a parent concept object of the selected concept object. Whenever the selected concept object has one or more child concept objects, one or more third images are displayed generally below the first image, and a second connector is displayed connecting each third image to the first image. Each third image represents a child concept object of the selected concept object. Whenever the selected concept object has one or more lateral concept objects, one or more fourth images are displayed generally on one or both sides of the first image, and a third connector is displayed connecting each forth image to the first image. Each fourth image represents a lateral concept object of the selected concept object.
In addition, the present invention provides a system for interfacing with a multi-level data structure that includes a computer, a display communicably connected to the computer, a memory communicably connected to the computer for storing the multi-level data structure, and a computer program resident on the computer. The computer program selects a concept object stored in the multi-level data structure, displays a first image representing the selected concept object, displays one or more second images generally above the first image, and displays a first connector connecting each second image to the first image. Each second image represents a parent concept object of the selected concept object. Whenever the selected concept object has one or more child concept objects, one or more third images are displayed generally below the first image, and a second connector is displayed connecting each third image to the first image. Each third image represents a child concept object of the selected concept object. Whenever the selected concept object has one or more lateral concept objects, one or more fourth images are displayed generally on one or both sides of the first image, ard a third connector is displayed connecting each fourth image to the first image. Each fourth image represents a lateral concept object of the selected concept object.
The above and further advantages of the present invention may be understood by referring to the following description in conjunction with the accompanying drawings in which corresponding numerals in the different figures refer to the corresponding parts in which:
While the making and using of various embodiments of the present invention are discussed herein in terms of a controlled medical vocabulary engine, it should be appreciated that the present invention provides many applicable inventive concepts that can be embodied in a wide variety of specific contexts. The specific embodiments discussed herein are merely illustrative of specific ways to make and use the invention and are not meant to limit its scope in any way.
The present invention provides a method and system for interfacing with a multi level data structure that encompasses a wide breadth of standardized knowledge representing the concepts of every aspect of an enterprise. The multi-level data structure of the present invention provides concepts and relationships that provide controlled terminology completely capturing the language of an enterprise. Moreover, the multi-level data structure or knowledge model of the present invention provider for the accurate and complete representation of all terminology systems thereby maintaining the truth and integrity of each of those terminology systems.
In one representative embodiment of the present invention, an interface provides access to a multi-level data structure that has concepts and relationships that provide controlled medical terminology that completely captures the language of healthcare. The present invention also includes a multidimensional semantic content network. The interface of the present invention provides a language-modeling environment enabling the user to maintain and enhance the semantic content. A graphical user interface (“GUI”) is also provided with which a user can easily navigate in order to use and maintain the terminology content.
The controlled vocabulary engine and GUI of the present invention are centered around the Systematized Nomenclature of Medicine Reference Terminology (“SNOMED RT”) of the College of American Pathologists. Added to this core are concepts and relationships that completely capture the language of healthcare. Additional terminology sets can be added to supplement the clinical foundation supplied by SNOMED RT. These terminology sets may include administrative terminologies, such as ICD and CPT, pharmacy terminologies, MeSH, UMLS CUI codes, and others that are necessary for the management of clinical healthcare.
Referring to
The Lexicon content provided by the present invention is unique in the industry in its breadth of coverage for Healthcare industry standards. In addition to providing SNOMED/RT as the clinical foundation, the Lexicon contains the administrative terminologies needed in today's healthcare environment: The diagnosis and procedure codes (e.g. ICD 9 CM, ICD10, ICD 10AM) needed by billing applications; drug codes needed by pharmacy applications (e.g., MB and Multum), MeSH codes needed by literature search engines and more. While SNOMED RT provides a clinical foundation, administrative terminologies are logically mapped to their SNOMED RT counterparts and to each other, as appropriate.
The main service mechanism is delivered using a three-tier deployment architecture with access provided through Enterprise JavaBeans (“EJB”) and Common Object Request Broker Architecture (“CORBA”). The present invention facilitates local, enterprise-specific modifications and additions to the terminology content. New concepts can be added and linked to the reference standards. Unique concepts, such as charges, can be added. Microglossaries (term lists) can be managed for specific applications.
The front tier 102 client applications include various applications that provide access to the middle tier 104 application services and thus control of the language model and its content. The front tier 102 client applications may include LExScape 108, Vendor applications 110, LExIndex 112 and Web Browser 114. LExScape 108 is a graphical user interface (“GUI”) for browsing and manipulating the Lexicon. A screen shot of LExScape 108 is depicted in
The middle tier 104 application services include an Application Server 116 and a Web Server 118. The Application Server 116, such as BEA's WebLogic, provides the Enterprise Java Bean (“EJB”) server and container that provide access to the exposed object model via standard remote and serialized objects. The object model includes core objects, such as Relation 120, Concept 122, Term 124, Microglossary 126 and Facet 128, that will be discussed in more detail in reference to
The Web Server 118 hosts servlets 130 that provides access to the Lexicon via an HTML/XML data stream over HTTP. The Web Server 118 provides servlet-based functionality, such as indexing and searching, when the full power of LExScape 108 is not needed. For example, LExIndex 112 uses the servlet 130 to perform the indexing operation and retrieve the index results. When accessed by LExIndex 112 using an HTTP GET operation, the servlet 130 returns a simple web form that can be used to access the indexing services. When a URL or text buffer is submitted, an HTTP POST operation is sent back to the same servlet 130. In response to the POST operation, LExIndex 112 retrieves the contents of the indicated URL (or text buffer) and then indexes the document using the requested query set. The results of the index operation are returned to the client in an XML document.
The database tier 106 handles the relational database that holds the Lexicon, mapped into relational form. The middle tier 104 provides the necessary relational-to-object mapping for the database. Access to the database is made through JDBC from within the Application Server 116. Preferably, application programmers are not provided direct access to the back tier 106. The Lexicon utilizes a highly optimized, simple dB schema to hold the relational form of the Lexicon. The present invention supports the use of MS SQL Server 7.0 and Oracle 8i running on a Windows NT or Windows 2000 Server platform, and Oracle 8i running on AIX.
The present invention provides an application programming interface (“API”) having three major functional categories: (1) Direct and Related Object Access; (2) Searching; and (3) Exporting. Each of the objects in the model has a unique identifier. This identifier can be used to directly access the object on the server. For example, an application may store the Concept ID during data entry and then later access that Concept 122 via the stored ID. Each object API provides methods for accessing the related objects. For example, from a Concept 122, you can obtain all the associated Terms 124. From a Term 124, you can access the associated Concept 122. Navigation between objects is simple and intuitive.
The API includes a wide variety of search capabilities. Client applications can search for Concepts 122 by any of the following attributes: (1) by a specified Term type's text (the text of a Synonym, for example); by the text of any related Term 124; or by the value of a specified Facet 128, such as SNOMED code. On any of these searches, wildcards may be used. For example, one could search for Concepts 122 that have an ICD-9 code starting with “207.” Further, the search may be constrained to locating Concepts 122 in a specified Taxonomy 202 (
The present invention can be used to provide data to applications that will not be continually connected to the Lexicon server by exporting data to external files. Exports can be made of specified Concepts 122, entire sub-hierarchies, and Microglossaries 126. The client has control over exactly what data are exported and the format of the export, such as XML, Comma-separated Values (CSV), or Query Set (intended for use in generating query sets to be used by the LExIndex tools).
The system can be accessed by logging-on through the use of a user ID and password. Security permissions are assigned on an individual or group basis, through the user ID. Security permissions determine the types of modeling activities that a user can perform. Some users may be limited to merely viewing, while others may be given full access to the entire range of functions available in the system. A “content administrator” has the highest access. Only content administrators may make changes that can potentially alter SNOMED RT or other coding systems.
Now referring to
The present invention provides an “aligned model” for representing terminology standards. This means that each standard is uniquely represented and then alignments (relationships) are created between the concepts in each standard. The power of this object model 200 lies in the understanding that the relationships between terminology systems must be represented independently of the conceptual ideas within the individual terminologies. This approach to terminology modeling provides unparalleled ability to represent and access the multitude of terminology standards in a specified field while remaining open to extension and enhancement by the end-user.
The object model 200 is preferably a meta-model, which means that the customer can define entirely new model component types. The use of a meta-model enables the present invention to accurately and completely represent nearly any terminology standard. Instead of trying to force each standard into a rigid, pre-defined structure, the object model 200 can be adapted to represent the standard in its true form.
The meta-model components define the attributes, or properties, for instances of each model type. For example, ConceptType 222 defines instances of Concept objects 122, RelationDefinition 220 defines instances of a Relation 120, and FacetDefinition 228 defines instances of a Facet 128. This defining relationship is comparable to the relationship between a Class definition and a Class instance in object oriented programming languages.
Each of the major terminology systems, such as SNOMED RT, ICD-9 and MeSH, are defined as unique Concept types 222. This allows the present invention system to recognize that the “ideas” represented in the terminology are defined within different logical realms. Even though Concepts 122 from different types can be related, they are not the exact same idea. For example, the concept of “Diabetes Mellitus” in SNOMED RT is related to the concept of “Diabetes Mellitus” in ICD-9, but they are fundamentally different ideas.
A RelationDefinition 220 essentially defines a unique way in which one or more Concepts 122 may be related. The present invention comes pre-configured with several useful RelationDefinitions 220. For example, the IS-A RelationDefinition 220 defines a hierarchical relationship between two Concepts 122 where one concept is the “parent” and one is the “child”. Further, the parent is more general than the child and the child is more specific than the parent. Another example is “SNOMED-ICD—9”, a relation that provides a correspondence between a SNOMED concept and it's closest (semantically similar) concept within ICD-9.
As mentioned above, Facets 128 are the mechanism used to store attributional data on an object within the Lexicon content. All of the core model components can have attributes, including Concept 122, Term 124, Relation 120, Microglossary 126, and MicroglossaryEntry objects 226. The FacetDefinition 228 specifies the properties of a type of Facet 128, including the restrictions on which types of object Facet 128 instances may be applied (e.g., a modeler may wish to restrict the use of a Facet 128 to only Term objects 124), and constraints on the values the Facet 128 instances may hold (such as restricting values to integers or floating point numbers).
All of the meta-model components share a set of common properties: (1) a Globally Unique ID (“GUID”); (2) a localized display name; (3) a localized description; and (4) a nickname. The GUID is a unique ID of the object that is a large string of meaningless numbers used to uniquely identify all the major objects in the system. Preferably, the algorithm used to generate a GUID ensures the no two systems can generate the same QUID. The localized display name is specific to a given language locale, such as “en_US” for US English. Each component can have multiple display names associated with it so that multiple languages can be supported. Likewise, the localized description allows multiple descriptions to be associated with each meta-model component. The Nickname eases access from within customer written applications, meta-model components each have a text nickname. This nickname must be unique among all the objects of a given type. Finder methods allow an application to locate a component by nickname. Thus, an application can locate the ConceptType 222 for SNOMED RT by doing a lookup on the nickname “SNOMED RT” instead of embedding the GUID (a string of 32 hex digits) constant within their application. This increases readability and maintainability of the customer written code.
Each major terminology system (such as SNOMED, ICD-9, or MeSH) is defined as a unique ConceptType 222. This allows the present invention to recognize that the “ideas” represented in the terminology are defined within different logical realms. Even though Concepts 122 from different types can be related, they are not the exact same idea. For example, the concept of “Diabetes Mellitus” in SNOMED is related to the Concept 122 of “Diabetes Mellitus” in ICD-9, but they are fundamentally different ideas.
The use of ConceptTypes 222 is not limited to representing medical terminologies. For example, assume that an enterprise wants to store within the lexicon supplies that can be consumed during various procedures. They can create a new ConceptType 222 to contain the supply objects and then relate each procedure to the supplies that are, or can be, used during that procedure. There is no limit to the types of data that can be modeled and correlated within the lexicon.
A RelationDefinition 220 essentially defines a unique way in which one or more Concepts 122 may be related. Each Relation 120 has a single “source” Concept 122 and the instance relates that source to one or more “target” Concepts 122. Since most terminology standards utilize a hierarchical, or taxonomic structure, the present invention comes with a parent/child relation already defined. The parent/child relation (also called an IS-A relation) defines a hierarchical relationship between two Concepts 122 where one concept is the “parent” and one is the “child”, the parent being a more general idea than the child. The parent/child relation also defines a classification system wherein the child is classified as a “kind of” the parent. For example, the Concept 122 of “Peptic Ulcer” is a child of “GI Ulcer” which is a child of “Disease of GI tract” which is (skipping some intermediate concepts) a child of “Disease”. Thus, “Peptic Ulcer” is a more specific form of “GI Ulcer” and it is classified as a “Disease”. Further, the Concept 122 of “Peptic Ulcer” has a relationship (of type “Associated Topography”, as defined by SNOMED) to the “Upper GI tract”, meaning that this disease affects the upper GI tract.
SNOMED RT, for example, defines numerous “role” relationships. These roles provide additional semantic definition to the medical concepts that are being related. The present invention represents each of these role types using a RelationDefinition 220. Then, instances of the Relation 120 embody the specific relationships defined by SNOMED RT. A few of the roles are explained below for clarity.
- Associated Topography For disorders, names the site affected by a condition, or the affected site resulting in a condition. For procedures, names the anatomical site affected by a procedure.
- Associated Function Relates a finding or disorder to its associated biologic function. Whereas lung cancer has topography of “Lung”, a voice disorder has functional feature “voice”. There is no topographical location for voice since it really has no one single site that creates it. A sexual disorder would have functional feature “sex” or “sexual behavior.”
- Branch Of Names the relationship of arteries, veins, nerves, lymphatics, and other similar structures to their branches.
- Procedure Approach Names the directional, spatial, or relational access to the topographic site of a procedure. An “excision of the leg by cutaneous approach” has a procedural approach of “cutaneous approach”
Relations 120 allow one to richly articulate the complex interactions of medical information. In its simplest form a “relation” allows us to say that the clinical disease, “Diabetes Mellitus” is equivalent to the billing code ICD-9 “250”. Equivalent relations are often referred to as “crosswalks” or “crossmaps” and the present invention comes with a rich assortment of these crosswalks. Even simple relations such as these can be made more complex in the medical realm when one considers the reciprocity of relations. If we assert that “A” is related to “B”, it may also be true that “B” has some relation to “A”. The knowledge model supports the definition of such reciprocal relations, with the full understanding that they are not always true and must be carefully articulated. Further, relations between billing codes and clinical notions may not be one-to-one. That is to say that a given ICD-9 code may be more specific than, equal to, or more general than its related clinical Concept 122. The knowledge model allows such clarifications to be expressed with the “Relationship” property, see below for details.
But Relations 120 are useful for more than just saying that two things are equivalent. They provide a robust mechanism for specifying arbitrary types of relationship between objects. It is these complex relations that allow us to represent the information needed by medical logic modules, billing modules, rules engines, and more.
For example, a medical logic module might depend upon relations in the lexicon to support the following alerts: (1) alert the clinician to do an eye exam whenever the diagnosis of diabetes is made; and (2) if the diagnosis of meningitis is made, make sure the patient has neck stiffness and fever. In another example, a billing logic module might depend upon relations in the Lexicon to send an ICD-9 code (“250”) to a billing application each time a clinician enters a diagnosis of “Diabetes Mellitus.” In yet another example, a business logic module might depend upon relations in the lexicon to assert enterprise policy: (1) if an upper GI series is ordered, a GI consult is required; and (2) if a 5th generation antibiotic is ordered, an Infectious Disease consult is required.
Each RelationDefinition 220 holds the properties that define characteristics of the instances of the relation type. The salient properties are listed below.
A FacetDefinition 228 defines the properties of facet values that can be applied to many of the core model objects. Facets 128 can be applied to Concepts 122, Relations 120, Terms 124, Microglossaries 126, and MicroglossaryEntries 226. Facets 128 are attributional data, often application-specific, associated with a model object.
Facet values are used to represent the “code” values that most terminology standards associate with a conceptual object within the terminology. For example, the SNOMED Code associated with a specific concept is stored in a facet value on that Concept 122 object, and the SNOMED Description Id associated with a term is stored in a facet value on the Term 124 object. Similarly, the ICD-9 code is associated with an ICD-9 concept using a facet value.
Facets 128 are the typical place that an application would store information regarding a model object, such as a cost code, or ancillary ordering code for a Concept 122 that represents an orderable test. Another example, applicable to an e-commerce setting, would be to store identifiers indicating items for sale that are related to a specific symptom or diagnosis, such as syringes or blood test kits for Diabetes.
Each FacetDefinition 228 holds the properties that define characteristics of the instances of that Facet type. The salient properties are listed below.
Note that the Inheritability and Cardinality attributes of a FacetDefinition 228 interact as defined in the table below.
The core, or central object within the Lexicon is the Concept 122. As described above, it represents a “unique entity of medical domain knowledge.” Its defining ConceptType 222 categorizes each Concept 122. Every Concept 122 has at least one parent Concept 122 and zero or more child Concepts 122 (determined by instances of the CHILD relation type). Concepts 122 that have no children are referred to as leaf Concepts 122.
A Concept 122 may represent something as broad as “Diagnosis” (i.e., the class of all diagnoses), to extremely granular entities necessary for clinical documentation, such as “Biliary Calculus (or Gallstone).” Concepts 122 are organized into a multi-axial hierarchy. This means that a Concept 122 can have multiple parents, i.e., it can reside in multiple classifications. For example, the Concept 122 representing “Bacterial Pneumonia” is classified within “Infection of Trunk” as well as within “Bacterial Infectious Disease.” Each Concept 122 should be unique and distinct from all other concepts.
Much of a Concept's 122 meaning stems from its relations to other concepts. Its parentage determines the classification of the Concept 122, while the Concept 122 itself determines one level of classification for all its descendents. Its non-hierarchical relations can specify additional semantic context. For example, the SNOMED Roles associate a Concept 122 with affected topographic location, morphologies, etc. Concept 122 objects may have an arbitrary number of Facets 128. However, essentially all the interesting data regarding a Concept 122 resides in other objects associated with the Concept 122 object. These objects are discussed below.
Terms 124 hold the words used to verbalize a Concept 122. Terms 124 are organized within language locales (such as “en_US”) to support international usage. Terms 124 are also the words used to document an encounter with a patient. When a physician documents that a patient has a broken leg, the phrase used to do so comes from the Term 124 associated with the Concept 122 of “Broken Leg”. Each Concept 122 can have numerous Terms 124 associated with it, but each Term 124 object is associated with exactly one Concept 122 object. Each Term 124 has a number of attributes that further define its applicability for different uses. The attributes are: (1) the language locale in which this Term 124 is used, “en_US” for example; (2) the text string, as in “Broken Leg”, (3) Display Term, which marks the Term 124 that should be used by default to display the associated Concept 122 (This term is the one LExScape uses to render the nodes in the Concept Display); and (4) the Term Type 224, which indicates the primary use of the Term 124. Term objects 124 may have an arbitrary number of Facets 128.
The various TermTypes 224 are listed below:
Each Concept 122 object may have an arbitrary number of Relation 120 instances associated with it. A Relation 120 is a connection between one or more Concepts 122. A relation 120 provides an explanation for the way in which two concepts interact with one another. IS-A (parent-child or hierarchical) relations suggest a relation in which the parent concept is larger/broader and the child concept is more granular. Each Relation 120 instance holds the Concept Id (GUID) of the source Concept 122 and the target Concept(s) 122. All the pertinent information regarding the usage of the Relation 120 is specified in the RelationDefinition 220. Each instance of a Relation 120 is either mentioned or inherited. When a Relation 120 is created on a given source Concept 122, the Relation 120 is mentioned on that Concept 122. If the RelationDefinition 220 indicates that the Relation 120 is inheritable, then inherited instances of the Relation 120 will be added to all the descendents of the original source Concept 122. Note that in each inherited Relation 120, the source Concept 122 is the current descendent, not the original source Concept 122. Inherited Relation 120 instances cannot be modified. Relation 120 objects may have an arbitrary number of Facets 128.
A role relation is a special type of relation strictly defined by SNOMED to suggest horizontal relations that are definitional and not assertional. Example: “Asthma” has topography “tracheobronchial tree” is a SNOMED role relation. It relates two distinct concepts (a diagnosis and a body part, in this example) in a defining way.
Arbitrary Relations can be used in many ways to associate concepts of interest. For example, a SNOMED clinical diagnosis can be related to its ICD billing code. This would permit an interaction between a clinical documentation system and a billing application. Or an agency might wish to link a clinical diagnosis with its common symptoms to fuel a decision support system.
A FacetDefinition 228 defines each Facet 128 instance. The core model objects can have Facets 128 that hold attributional information about the object. Facets 128 are the typical place that an application would store information regarding an object, such as a cost code, or ancillary ordering codes. Facets 128 are also used to hold the “code” values defined by most terminology standards. Facets 128 can be applied to the following object types: (1) Concept 122; (2) Term 124; (3) Relation 120; (4) Microglossary 126; and (5) MicroglossaryEntry 226.
When applied to Concept 122 objects, each instance of a Facet 128 is additionally defined as mentioned or inherited. When a Facet 128 is created on a given Concept 122, the Facet 128 is mentioned on that Concept 122. If the FacetDefinition 228 indicates that the Facet 128 is inheritable, then inherited instances of the Facet 128 will be added to all the descendents of the original Concept 122. Inherited Facet 128 instances cannot be modified, but they can be overridden by mentioning an instance of the Facet 128 on a descendent of the original Concept 122. The cardinality of the Facet 128 determines how inherited and mentioned Facets 128 interact.
Each Concept 122 is uniquely categorized by its defining ConceptType 222. Concepts 122 may be additionally categorized into Taxonomies 202. A Taxonomy 202 object is applied to a single Concept 122 object and defines a named sub-hierarchy of the Lexicon content. All the descendents of the target Concept 122 are part of the Taxonomy 202. The taxonomy name can then be used to constrain certain operations, such as searching, to Concepts 122 that reside within the sub-hierarchy. For example, the “Disease” taxonomy refers to the entire sub-hierarchy containing the Concept “Disease” and all of its descendants. Enterprises may specify their own names for identified sub-hierarchies and use them to bound searches or control exports.
As the name implies, a Microglossary 126 is a subset list (micro) of Terms 124 (glossary) from the Lexicon allowing users to view a custom subset of the Lexicon content rather than viewing the entirety of the Lexicon content. These Term 124 lists can be used for any purpose, at the discretion of the application designers. Typical uses are for creating “pick” lists for use within an application to speed structured data entry during an encounter. For example, a Microglossary 126 could be created that contains the top 25 chief complaints that a GP sees every day. Another example would be a list of medications that the Pharmacy has decided to carry for specific treatments, such as Beta-blockers. Microglossaries 126 are provided primarily for application use.
A Microglossary 126 contains an ordered list of MicroglossaryEntry 226 objects, described below, and an associated ExportContext. A Microglossary 126 can be exported to an external file. At the time of the export, the application (or user via LexScape 108) can select which attributes are to be exported. For example, an application may export the Term text, the related Concept ID, and the Concept's SNOMED ID. The ExportContext saves the settings from the last export performed on a Microglossary 126. This allows for an automated re-export using the same settings. Microglossary 126 objects may have an arbitrary number of Facets 128.
Facets 128 can be applied to entire Microglossaries 126 to provide application-level information about an entire list. For example, a Microglossary 126 containing blood tests required for management of pregnant patients may have a Facet 128 that contains an instruction to display this list only for Obstetric encounters. Similarly a Microglossary 126 containing drugs to treat asthma in children might have a Facet 128 to constrain display of the list to encounters with pediatric patients.
Each entry in a Microglossary 126 contains the following: (1) the TermPhrase 204, which is an object holding one or more Term 124 references; and (2) a set of Facets 128. Facet values placed on a MicroglossaryEntry 226 provide a mechanism to associate data with a Term 124 “in context” of the MicroglossaryEntry 226. Facet values associated with a MicroglossaryEntry 226 are intended to provide a simple storage area for use by the application developer. With proper application support, this allows individual caregivers to manage their own term lists.
As another example, a Pharmacy could provide a Microglossary 226 of drugs orderable for certain conditions, in this case Beta-blockers. Based upon negotiated contracts, supply, or other factors, the Pharmacy manager will determine the “Beta-blocker of choice” on a semi-regular basis. Instead of having to notify every prescribing physician, the Pharmacy manager could simply assign a DRUG_CHOICE of “BETA1” to the drug of choice. Now, the physician that wants to prescribe a Beta-blocker and doesn't need a specific drug (based on other findings) can simply order “BETA1”. This provides the Pharmacy with the control they need to manage costs in a manner that is extremely simple to administer.
The use of Facet values on MicroglossaryEntry 226 objects provides for “in context” information, i.e., the facet value is unique to the combination of Microglossary 126 and Term 124. It is often inappropriate to place a Facet value on the Term 124 object, since there is no “context” for the Term 124 object. In the example above, it might not be appropriate to place the “BETA1” facet value on the Term “Atenolol”, so the value is placed on the MicroglossaryEntry 226 in the specific formulary (Microglossary 126) in which it is located. In another formulary, possibly for use at a different clinic, Atenolol may not be the preferred beta-blocker, and in that MicroglossaryEntry 226 it would not have the “BETA1” facet value.
A TermPhrase 204 is an ordered set of one or more Terms 124 that represent a collection of Concepts 122, such as “Dialysis without complications”. TermPhrase 204 objects live strictly within a given MicroglossaryEntry 226 object. They have no life beyond their use in a Microglossary 126. Each TermPhrase 204 holds either a single term, or multiple, ordered Terms 124. If the TermPhrase 204 holds multiple Terms 124, it is said to be compound. Compound TermPhrase 204 objects are primarily used for rapid documentation and to handle combinatorial coding sets required by applications. A new Concept 122 could be created to represent the combination of Terms 124, but that could lead to combinatoric explosion and general, non-useful clutter within the Lexicon. The TermPhrase 204 object should address existing incompatibilities between coding schemes of vastly different granularities that could not otherwise co-exist in the same data source.
Referring now to
Attribute panel 320 lists the lateral relations and facets of focus concept 310. Concept details 325 contain details relating to focus concept 310 such as its unique identifier, type, and taxonomy. Term panel 340 lists names for focus concept 310. Term panel 340 also indicates such information as the display name, a retired term, text and type for focus concept 310. Workbench 345 is the work area where the user can temporarily store terms and term phrases while modifying them. Microglossaries tab 350 displays the microglossaries panel. This panel will be blank until a microglossary has been created. Term facets tab 355 displays the term facets panel. Relation facets tab 360 displays the relation facets panel. Relation facets provide arbitrary data that may be stored in relations. Term phrase editor tab 365 displays the term phrase editor that is used to build phrases that can be stored as microglossary entries. Status bar 370 displays informational messages about system status and activities.
Before the user can create and modify such object values as concepts, facets, relations and microglossaries, the user must first define the objects. The present invention provides many predefined objects such as concept type, relation definition, facet definition and microglossary definition. When the user begins adding objects and values by adding new concepts and facets, the first step is to decide the type of object or value to be added. To view a list of predefined object types, the user selects the appropriate “Edit [object type] Definitions” in the “Edit” selection from the menu bar at the top of the main GUI display as shown in
In addition, a user can open multiple main windows at one time. A new window is opened by selecting the “New Window” entry from the File menu, or by pressing a button on the toolbar. The new window is initially focused on the concept that was the focus concept of the window from which the “new window” operation was performed. Each window may be navigated independently. Drag and drop operations work between main windows. Using “side by side” windows dramatically simplifies the creation of lateral maps between concept types.
There are several navigation methods that may be employed: the concept display, the GO menu, bookmarking or by term. Each of these methods can be easily accessed through the main GUI display as exemplified by
Navigation through the concept display is accomplished by clicking on the concept as shown in the main GUI display as shown in
Navigation through the use of the GO menu is accomplished by selecting “GO” from the menu bar at the top of the main GUI display as shown in
Navigation through the use of bookmarks is a two-step process. First, the bookmark must be set. This can be accomplished in a variety of ways. The first way is by right-clicking the desired concept and then selecting “Bookmark this Concept” from the menu that is displayed. The second way is by navigating to the concept and then selecting “Bookmark” from the “Bookmarks” menu item on the main GUI screen as displayed in
Searches can be performed in a variety of ways, such as exact match, contains and fuzzy search. Searches can be restricted by taxonomy or concept type. There are two (2) ways to access the search function. First, the user can select “Search” from the “File” menu item as shown in the GUI display of
The search dialog box allows the user to conduct a full text search or a search by term or by facet. Drop down selection boxes display lists of available terms or facets, depending on the type of search selected. The user can also select whether to restrict either the taxonomy or the concept type. Additionally, the user can choose the type of search methods from such options as: exact match; contains; starts with; and fuzzy. A text box enables the user to conduct searches on keywords not specifically found in either the term or facet drop down selection boxes. A full text type search is also available; this option implicitly inserts the “and/or” operators between all terms entered in the text box. Search results are returned in groups of 25 in alphabetical order by default. Other types of sorts and groupings may alternatively be used. A user can also navigate by using the search results. For example, by double-clicking on a returned result, the user can display the concept. Right-clicking on a returned result can display a menu containing options such as activiate (navigate to the concept), show properties, add to exports or export now.
Search results are displayed in box 670. Each result 672 is displayed on a separate line. A result 672 can be used to navigate as previously described. The user can jump forward in the search result list by pressing next 674 and can jump backward in the search result list by pressing back 676. Line 678 displays the location of the user in the results list. The screen is closed by pressing close 680.
A taxonomy is a division of items in to ordered groups, categories, or hierarchies. Medical information, for example, can best be present within hierarchies. In the present invention, a taxonomy is a hierarchy of concepts. For example, “procedure” is a taxonomy. All the children of “procedure” are a part of that taxonomy. The top level of a taxonomy is the root concept. The root concepts of the present invention are defined by the enterprise in which it is used. For example, the root concepts for the healthcare industry are: SNOMED RT; HCPCS 2000 (HCFA Common Procedure Coding System); ICD-10 (International Statistical Classification of Disease and Related Health Problems, Tenth Revision); ICD-10 AM (International Statistical Classification of Disease and Related Health Problems, Tenth Revision Australian Modification); CPT (Physicians' Current Procedural Terminology); and ICD-9 CM (The International Classification of Diseases: 9th Revision-Clinical Modification). Users can define new taxonomies at any level below the root level. When a user defines a new taxonomy, the user does not create a new hierarchy by giving a name to a portion of an existing hierarchy. Identifying new taxonomies can optimize searching. For example, a cardiologist doing modeling solely in the area of cardiac disease could create a taxonomy with the concept “myocardial disease” as its top-level concept. This would enable searches that are restricted to this taxonomy.
A user can create new taxonomies and delete those taxonomies that the user has created. To create a new taxonomy, the user navigates to the root-level concept under which the new taxonomy will be placed. Then, the user selects “Create Taxonomy” from the “Edit” menu item on the GUI display as shown in
To remove a taxonomy, the user navigates to the root-level concept of the custom taxonomy. Then, the user selects “Remove Taxonomy” from the “Edit” menu item as shown on the GUI display of
The present invention enables the user to manage, export and retire concepts. Concepts can be shown or hidden. The user can clone concepts, add or remove facet values, add or remove terms, change term text, drag concepts to the workbench, include concepts on term phrases, include concepts in term lists (microglossaries), add or remove concepts, add or remove taxonomies.
Hiding or displaying concepts is accomplished by first choosing “Select Concept Type Displayability” from the “Edit” menu of the GUI display as shown in
To create a new concept, the user navigates to the concept under which the new concept will be placed. The user then selects “Create Child Concept” from the “Edit” menu of the GUI display as shown in
An alternative method for creating concepts is by cloning. This is accomplished by navigating to the concept to be cloned and making it the focus concept. The user then selects “Clone Concept” from the “Edit” menu of the GUI display as shown in
New concept types can also be created. This is accomplished by selecting “Edit Concept Types” from the “Edit” menu of the GUI display as shown in
A concept's properties can also be viewed and added. This can be accomplished by right-clicking the desired concept. The resultant menu displays such options as: show concept properties and add concept properties.
Concepts and their associated facets can also be exported into such formats as XML (extensible Markup Language), a query set and CSV (comma-separated values). This is accomplished by navigating to the concept, right-clicking on it and selecting either “Mark for Export” or “Export Now” from the resultant menu. The first selection adds the concept to a list of concepts to be exported. This list can be accessed by selecting “Concept Export Manager” from the “File” menu of the GUI display as shown in
In this dialog box, the user has the option of deselecting the concept(s) and/or their relations and/or descendents. The user can further refine the export by selecting the “Enable Export Filters” option. This allows the user to include or exclude concepts based on facets. Any number of filters can be used. After making selections, the user clicks “Next.” The procedure then differs based on whether or not filters have been enabled.
If filters have been enabled, a dialog box is displayed allowing the user to define and add filters based on facets. Various types of filters can be used, such as “include-if-present” and “exclude-if-present.” Selecting “Next” resumes the basic export procedure.
At this point, the user is allowed to select the format into which the concepts will be exported. Again, the user selects “Next” to continue the export procedure. A dialog box is then displayed allowing the user to perform a variety of export-related functions such as specifying the export destination (for example, exporting to a new file or appending to an existing file) and testing the export. It is also possible to test the export and then save it to a file. Clicking “Finish” completes the export. The export may also be halted by selecting “Stop the Export.” If the user selects CSV format, they may then select specific facets to be included as columns in the export. This option is not available for XML format since XML format contains all information on the concept being exported.
A concept that has been retired, has been removed from use but is still in the system. Retired concepts can be cloned, displayed or hidden. They may also be “unretired.” However, terms, facets or relations cannot be added to retired concepts. All of the descendents of a concept selected to be retired must also be retired or moved to become the children of other concepts before a concept can be retired. Additionally, when a concept is retired, its terms are also retired.
To retire a concept, the user navigates to the concept and right-clicks on it. Then, the user selects “Retire Concept” from the resultant menu. A confirmation box is then displayed. The user clicks “OK” to retired the concept. When displayed, retired concepts can be visually designated by such means as a special symbol.
Terms give names to concepts. When creating a concept, the user must assign it at least one term so that the concept can have a display term. After a concept has been created, the user can add new terms to it, retire outdated terms, change a term's type and reassign the display term. As with retired concepts, retired terms can also be shown or hidden. Terms can be used to build term lists, also known as microglossaries. Terms have facets and types. Term facets enable the user to link codes or other data to terms in the same manner that concept facets link associated data with concepts.
There are a variety of term types, such as: synonym (for example, asthma), misspelling (for example, azma for asthma), abbreviation (for example MI for myocardial infarction), grammatical variant (for example reddish as a variant of red), consumer term (for example, heart attack for myocardial infarction), short (for example, exploratory heart surgery), medium (for example, cardiotomy, exploratory w/removal, FB; w/o bypass), long (exploratory heart surgery with removal of foreign body; without bypass), coding modifier (external upper lip). Coding modifiers represent a portion of a diagnosis, procedure, or other entity. They are used in a coding system to reduce text by omitting the common part of a statement that would be repeated for a series of codes. For example, one group of coding modifiers from the ICD-10 series lists various areas of a lip (C00.0-0.9). Use of one of these coding modifiers also assumes the inclusion of the text from code COO which is “malignant neoplasm of lip.”
The present invention allows the user to import lists of words that can be used as terms. By creating a plain text file of these words and importing the file into the present invention through the “Import Term Candidates” option on the “File” menu of the GUI display as shown in
To add a new term to a concept, the user navigates to the concept and right-clicks on it. From the resultant menu, the user then selects “Add Term.” A dialog box is then displayed enabling the user to enter the new term and select its type. The present invention checks to ensure that no identical active term exists for this concept in the current locale. If the term is unique, it is assigned and appears in the term panel for that concept.
To change a term type, the user right-clicks on the term and selects “Change Term Type” from the resultant menu (Terms may also be added, replaced and retired from the same menu). A type list dialog box appears from which the user can select the new type. The change is completed when the user selects “Change” from the dialog box.
The display term for a concept can be changed if the concept has more than one term assigned to it. This is accomplished by right-clicking the term that will become the new display term and selecting “Make Display Term” from the resultant menu (This menu also allows the user to add terms, retire and replace terms, retire terms, change term type and access properties). The present invention requests confirmation of the desired action. Selecting “Yes” completes the action.
Facets store values associated with concepts, terms, relations, microglossaries and microglossary entries. Facets have a variety of attributes, among them mentioned versus inherited, cardinality and inheritability. Facet values are “mentioned” only once. This is as related to the first concept to which it is added. Facet values can be inherited many times. If the facet is defined as inheritable, changes made to facet values on the concept where the facet value is mentioned affect not only the mentioned facet values, but also their descendents. Cardinality determines whether a facet can have only one, or multiple values of a particular facet on any given concept or term. Inheritability determines whether facet values are inherited by the concept's descendents.
Some facets store coding systems such as MeSH and LOINC. Others store information that will be used by external applications. For the healthcare industry, coding systems such as LOINC, MedicineNet, MeSH and UMLS, are stored in facets. Facets can be created, changed and deleted. Concept facets, term facets and relation facets are accessible from the GUI display as shown in
To manage facet definitions, the user selects “Edit Facet Definitions” from the “Edit” menu of the GUI display as shown in
To modify an existing facet definition, the user would highlight the desired facet definition and select “Edit” on the facet management dialog box. This displays the facet definition dialog box with the data related to the selected facet definition displayed. The user can then make modifications to the facet definitions in the areas as described in relation to creating new facet definitions.
To delete an existing facet definition, the user highlights the desired facet definition and selects “Delete” on the facet management dialog box. The system then requests confirmation prior to performing the deletion.
The procedures for adding facet values to concepts, terms and relations are similar. In each case, the user must navigate to the concept, term or relation to which the facet value will be added. To add a facet value to a concept, the user right-clicks within the body of the attribute panel on the GUI display as shown in
Facet values can also be modified and/or deleted. To modify a facet value, the user right-clicks the facet value in the attribute or term panel of the GUI display as shown in
A concept is defined by its relations, which link two concepts. The present invention provides two (2) predefined relation types: hierarchical (parent-child) and lateral. New relations types can be created. Parent-child relations are created when new concepts are added. Existing concepts can be linked by adding new parent-child relations. This can be accomplished by adding a new parent to a child concept, or by adding a new child to a parent concept.
The new parent cannot already exist within the child's hierarchy, either as an ancestor or a descendent. If it does, the present invention will generate a message. The message may be simply an error message or may offer an alternative action such as replacing the parent. If such an alternative is selected, inheritable properties of the new parent are added to the child concept, retaining its inheritability.
To add a parent, the user drags the concept to which the parent is to be added to the workbench on the GUI display as shown in
Lateral relations are not hierarchical. They may or may not define the focus concept. The present invention represents all SNOMED RT roles as lateral relations that define the source concept. Another type of lateral relation is a code set mapping, such as that which links SNOMED RT to ICD or CPT codes, but does not define either SNOMED RT or the coding concept. Code set mappings link a concept to another concept that represents a code in a set such as CPT or ICD-10. It is useful, for example, to link a clinical concept with an administrative coding concept.
To add a lateral relation, the user navigates to the concept that will be the target of the new relation and drags the concept to the workbench on the GUI display as shown in
To create a new relation definition, the user selects “Edit Relation Definitions” from the “Edit” menu of the GUI display as shown in
Microglossaries are custom lists made up of terms from the present invention and may also contain user-entered values. Microglossaries are built from terms, term phrases and facets. A microglossary might contain a list of commonly used drugs, major diagnosis areas, common procedures, or even a listing of ICD concepts. Microglossaries can be used as input to other applications to create, for example, a pick list. The following actions can be performed on microglossaries: add and delete terms; add, modify and delete term phrases; copy terms among open microglossaries; associate facets with the entire microglossary; build microglossary entries (one per row) by adding terms and term phrases; associate user-defined facets with entries; display concept and term facets associated with entries; delete entries (rows in the microglossary); delete entry values; and delete entire microglossaries.
Any term from any taxonomy within the present invention can be added to a microglossary. From the GUI display as shown in
Term phrases are built by dragging terms onto the workbench on the GUI display as shown in
All functions related to microglossaries are accessed by selecting “Microglossary Manager” from the “File” menu of the GUI display as shown in
To edit a microglossary, the user selects the microglossary and the “Edit Microglossary Properties” option on the “Action” menu of the Microglossary Manager. This results in the display of a dialog box that allows the user to modify the name, group name and description of the microglossary.
To create a microglossary, the user selects “New Microglossary” from the “Action” menu of the Microglossary Manager. A dialog box is then displayed enabling the user to enter a name, group name and description for the new microglossary.
Microglossaries can be opened in a number of ways. First, the user opens the Microglossary Manager as described above. The user can then either double-click the desired microglossary or right-click the desired microglossary to display the context menu containing the “Open Microglossary” option.
A microglossary entry is a row in the microglossary that contains a term or term phrase and may also contain the term's associated concept or term facets as well as microglossary entry facets. Any number of terms can be added to a microglossary any number of times. Terms can be added by dragging them onto the cell that contains the words “no entries yet” or on top of terms already listed. New entries are added to the bottom of the list. A couple of ways to add a concept's display term to a microglossary is by dragging the concept to a microglossary from the workbench or from the concept display, both on the GUI display as shown in
Microglossary term phrase entries can be replaced by highlighting and then right-clicking the microglossary entry. The user then selects the “Edit Term Phrase” option from the resultant menu. Other terms and/or phrases can then be used to build the new term phrase. Once the desired term phrase has been created, the user then selects the destination as either the workbench or “Replace in Microglossary.” The user can also edit existing phrases in microglossaries by dragging them back to the term phrase editor.
User-defined facets can be associated with either entire microglossaries or with individual entries (rows) within a microglossary. To add facets to an entire microglossary, the user first selects or creates an appropriate facet definition. Then, the user opens the Microglossary Manager as described above. Next, the user highlights the microglossary with which the facet definition is to be associated. A facet panel will become visible at the bottom of the Microglossary Manager. The user then right-clicks the facet panel and selects “Add Facet” from the resultant menu. A dialog box appears with a drop down selection box from which the user can select an available facet. The label for the text data entry box indicates the type of data expected (string, floating point or integer, for example). The user enters the facet value in the data entry box and then clicks “Add.”
Microglossary entry facets associate miscellaneous data with individual entries in a microglossary. To add facets to microglossary entries, the user locates or creates an appropriate facet definition. Then, the user opens the Microglossary Manager as described above and opens the microglossary to which the entry facets are to be added. Next, the user right-clicks the “Term Name” column header and selects “dd Entry Facet Column” from the resultant menu. From the displayed dialog box, the user selects the name of the facet definition to be added and then clicks “OK.” Once the entry facet column has been created, entry facet values can be entered/edited by typing directly into the cell in the table at the intersection of the entry row and facet column.
Concept and term facets can be displayed using the Microglossary Manager. After opening the desired microglossary, the user right-clicks on the “Term Name” column header and selects either the “Display Concept Facet Column” or the “Display Term Facet Column” from the resultant menu. Select facets for inclusion in the microglossary by turning on their display values. The user then clicks “OK.”
To copy a term from an open microglossary the user hightlights, then right-clicks the term in the Microglossary Manager, then selects the “Copy to Open Microglossary” option from the resultant menu.
Individual cells (for entry facet columns), rows and columns can be deleted from microglossaries. To delete a microglossary entry, the user highlights, then right-clicks its “Term Name” cell, the selects “Delete Entry” from the resultant menu. To delete an entry facet, the user highlights, then right-clicks the cell to be deleted, then selects the “Delete [entry facet column name] values” from the resultant menu.
Microglossary entries can be rearranged/reordered. Columns can be reordered by clicking and dragging the column header. Rows can be sorted by value in a given column in either ascending or descending order. Rows can also be rearranged manually by clicking and dragging the entry.
Microglossaries can be copied. To accomplish this, the user highlights the microglossary to be copied and selects “Copy Microglossary” from the “Actions” menu of the Microglossary Manager. To close a microglossary, the user right-clicks the desired microglossary in the Microglossary Manager and selects “Close Microglossary” from the resultant menu. To delete a microglossary, the user right-clicks the desired microglossary in the Microglossary Manager and selects “Delete Microglossary” from the resultant menu.
Microglossaries can be searched for terms or properties (name, group or description) or any combination of these elements. To search a microglossary, the user selects the “Search” tab in the Microglossary Manager. Next, the user selects the search scope, such as properties, terms or both and a type of search, such as exact match, contains or starts with. Then, the user enters a search string into the text box and clicks “Search.” Search results can be displayed any number of ways, including in a hierarchical manner similar to the listing of microglossaries in the Microglossaries Manager. Users can use microglossary search results to navigate by either double-clicking the microglossary in the search results or right-clicking the microglossary in the search results and selecting “Open Microglossary” from the resultant menu.
Microglossaries can be exported for use in other applications. Microglossaries can be exported individually, as a set or entirely. As described above in relation to exporting concepts, the export file formats currently available are XML, CSV and query set. The export process places each microglossary in a separate file in a directory named after the microglossary group name. The export directory is currently specified in a separate properties file under the section “Export Properties.”
To export all microglossaries, the user selects “Export All Microglossaries” from the “Actions” menu of the Microglossaries Manager. The export process for single and multiple microglossaries is similar to that previously described in relation to exporting concepts. To export a single microglossary, the user highlights the desired microglossary, right-clicks and either selects “Export Now” or “Mark for Export.” The latter adds the microglossary to an export list. The former invokes the export process. To export numerous microglossaries, the user highlights and marks each microglossary, individually adding them to the export list.
While exporting all or a single microglossary automatically displays the list, marking microglossaries for export requires an extra step. The user must select “Export Now” from the “Actions” menu of the Microglossary Manager. Eventually, each microglossary export procedure displays the list of microglossaries marked for export. At this point, the user can remove microglossaries from the list, include related concepts and/or enable filters as previously described in relation to exporting concepts. After making selections, the user clicks “Next.” The procedure then differs based on whether or not filters have been enabled.
If filters have been enabled, a dialog box is displayed allowing the user to define and add filters based on facets. Various types of filters can be used, such as “include-if-present” and “exclude-if-present.” Selecting “Next” resumes the basic export procedure.
At this point, the user is allowed to select the format into which the concepts will be exported. If the microglossaries are to be exported in CSV format, additionally selections related to delimination will be required. As with Concept exports in CSV format, the user can select the set of facet values to export as columns in the output. The export may also be sorted by term text or by facet value. After the selections have been made, the user clicks “Next” to continue. The system then displays an export message indicating that the user may complete the export by selecting “Finish,” can the export by selecting “Stop Export” and/or save the export criteria, but do not export the microglossaries. The system displays status messages as the export progresses.
Several of the elements of
There are several things that can be accomplished by setting user preferences: the user's preferred configurations can be saved for later use; e-mail information can be recorded to facilitate sending system error messages; facets to be included in the content display can be identified; and the type of value to be included in the attributes panel can be selected for relations. To access user preferences, the user selects “Edit Preferences” from the “Edit” menu of the GUI display as shown in
The user can modify a wide variety of preferences, such as: restore last active concept; restore window position and dimensions; restore concept bookmarks; enable plex resizing. The last active concept is the concept that was in focus when the user last exited the system. If preferred, the system can restore that concept rather than returning the user to the root concept. Restoring window positions and dimensions restores the window settings established in previous sessions. Restoring concept bookmarks saves bookmarks. Enabling plex resizing turns on the circle in the concept display, enabling the user to resize display fonts. The user may also enter an e-mail address and SMTP host and set facet and relation display properties.
The user can also set navigation and modeling settings, such as: view coding concepts in navigation hierarchy, view retired concepts in navigation hierarchy; auto-replace subsumed parents on addParent; and restore term candidates. Viewing coding concepts in navigation hierarchy includes coding concepts in the concept display. View retired concepts in navigation hierarchy includes retired concepts in the concept display. Auto-replace subsumed parents on addParent, in effect, performs a delete parent on a child's current location, followed by an add new child to the new location when a user attempts to add a child that is already a descendent of the concept WITHOUT asking the user to verify the modification. Restore term candidates restores term candidates in the workbench from the previous session.
There are currently a limited number of predefined reports included in the present invention. They can be accessed from the “Reports” menu item of the GUI display as shown in
Java interface files can be generated using the present invention. There are currently two (2) main ways to accomplish this. The first is to extract the unique identifiers from the present invention and imbed them directly in the application. The second is to use the present invention to export literal constants of the unique identifiers as Java interface files.
When the present invention creates Java interface files by exporting literal constants of unique identifiers, it includes only identifiers for relation definitions, facet definitions, concept types and taxonomies. The generated interface files can then be included in an application so that these objects can be referenced by their nicknames, rather than by hard-coding the unique identifiers.
To generate interface code using the present invention, the user would select “Generate Interface Code” from the “File” menu of the GUI display as shown in
While specific alternatives to steps of the present invention have been described herein, additional alternatives not specifically disclosed but known in the art are intended to fall within the scope of this invention. Thus, it is understood that other applications of the present invention will be apparent to those skilled in the art upon the reading of the described embodiments and a consideration of the appended claims and drawings.
Claims
1.-30. (canceled)
31. A computer-implemented method for adding customized terms to a predefined medical taxonomy, comprising:
- providing a fixed medical taxonomy in a computer database comprising root concepts ordered according to a predefined hierarchy;
- displaying one or more root concepts on a display device;
- receiving a selection of a root concept;
- receiving a customized term;
- creating an association between the customized term and the selected root concept in the computer database;
- storing the association in the computer database; and
- displaying the association between the customized term and the selected root concept on a display device.
32. The computer-implemented method of claim 31, further comprising: receiving the customized term in a search query interface; and conducting a search for root concepts associated with the customized term.
33. The computer-implemented method of claim 31, wherein the fixed medical taxonomy comprises at least one of: Systematized Nomenclature of Medicine Reference Terminology (SNOMED RT); Healthcare Common Procedure Coding System 2000; International Statistical Classification of Disease and Related Health Problems, Tenth Revision (ICD-10); International Statistical Classification of Disease and Related Health Problems, Tenth Revision Australian Modification (ICD-10 AM); Physicians' Current Procedural Terminology (CPT); and International Classification of Diseases: 9th Revision-Clinical Modification (ICD-9 CM).
34. The computer-implemented method of claim 33, wherein the customized term comprises a non-medical term.
35. The computer-implemented method of claim 34, wherein the non-medical term comprises a consumer term.
36. The computer-implemented method of claim 33, wherein the customized term comprises at least one of a synonym; a consumer term; a grammatical variant; an abbreviation; a misspelling; a short phrase; a medium phrase; a long phrase; and a coding modifier.
37. The computer-implemented method of claim 31, wherein the display device comprises a computer display screen.
38. The computer-implemented method of claim 31, wherein displaying the association between the customized term and the selected root concept on a display device comprises displaying the selected root concept as alphanumeric text in a first window on the display device and displaying the customized term as alphanumeric text in a second window on the display device.
39. A computer-implemented method for creating new associations between two medical taxonomies, comprising:
- providing a first fixed medical taxonomy in a computer database comprising root concepts ordered according to a first predefined hierarchy;
- providing a second fixed medical taxonomy in a computer database comprising root concepts ordered according to a second predefined hierarchy;
- displaying a first root concept from the first fixed medical taxonomy and a second root concept from the second medical taxonomy on a display device;
- receiving input to define a new relationship between first and second root concepts;
- creating an association between the first and second root concepts based on the input;
- storing the association in the computer database; and
- displaying the association between the selected root concepts on a display device.
40. The computer-implemented method of claim 39, further comprising: receiving a input related to the new relationship in a search query interface; and conducting a search for root concepts associated with the input.
41. The computer-implemented method of claim 40, further comprising displaying the first and second root concepts on the display device in accordance with the new relationship.
42. The computer-implemented method of claim 39, wherein the first and second fixed medical taxonomies comprise at least one of: Systematized Nomenclature of Medicine Reference Terminology (SNOMED RT); Healthcare Common Procedure Coding System 2000; International Statistical Classification of Disease and Related Health Problems, Tenth Revision (ICD-10); International Statistical Classification of Disease and Related Health Problems, Tenth Revision Australian Modification (ICD-10 AM); Physicians' Current Procedural Terminology (CPT); and International Classification of Diseases: 9th Revision-Clinical Modification (ICD-9 CM).
43. The computer-implemented method of claim 42, wherein the first medical taxonomy comprises a computer file relating to medical nomenclature and the second medical taxonomy comprises a computer file related to healthcare codes for billing.
44. The computer-implemented method of claim 41, wherein the display device comprises a computer display screen.
45. The computer-implemented method of claim 41, wherein displaying the association between the selected root concepts on a display device comprises displaying the selected first root concept as alphanumeric text in a first window on the display device and displaying the selected second root concepts as alphanumeric text in a second window on the display device.
46. A computer program product comprising a computer usable medium having a computer readable program code embodied therein, said computer readable program code adapted to be executed to implement a method for adding customized terms to a predefined medical taxonomy, said method comprising:
- providing a fixed medical taxonomy in a computer database comprising root concepts ordered according to a predefined hierarchy;
- displaying one or more root concepts on a display device;
- receiving a selection of a root concept;
- receiving a customized term;
- creating an association between the customized term and the selected root concept in the computer database;
- storing the association in the computer database; and
- displaying the association between the customized term and the selected root concept on a display device.
47. The computer program product of claim 46, wherein the method further comprises receiving the customized term in a search query interface; and conducting a search for root concepts associated with the customized term.
48. The computer program product of claim 46, wherein the fixed medical taxonomy comprises at least one of: Systematized Nomenclature of Medicine Reference Terminology (SNOMED RT); Healthcare Common Procedure Coding System 2000; International Statistical Classification of Disease and Related Health Problems, Tenth Revision (ICD-10); International Statistical Classification of Disease and Related Health Problems, Tenth Revision Australian Modification (ICD-10 AM); Physicians' Current Procedural Terminology (CPT); and International Classification of Diseases: 9th Revision-Clinical Modification (ICD-9 CM).
49. The computer program product of claim 46, wherein the customized term comprises a non-medical term.
50. The computer-implemented method of claim 46, wherein the customized term comprises at least one of a synonym; a consumer term; a grammatical variant; an abbreviation; a misspelling; a short phrase; a medium phrase; a long phrase; and a coding modifier.
Type: Application
Filed: Dec 31, 2009
Publication Date: Aug 5, 2010
Inventor: Larry V. Streepy, JR. (Ridgway, CO)
Application Number: 12/651,403
International Classification: G06F 17/30 (20060101); G06Q 50/00 (20060101);
