Method and system for concept-based terminology management
Inventors
Masarie, JR., Fred E. • Aldin, Gregory Richard • Alvin, David • BODAL, Aziz M. • Cardwell, Matthew Charles • Charlot, Régis J P • Frank, Eric Nathan • Kanter, Andrew S. • Kobashi, Masayo • MALDONADO, JR., Jose Antonio • Naeymi-Rad, Frank • Oganesova, Alina • YOUNG, JR., Andre L. • Wang, Amy Yunhsin
Assignees
Interested in licensing this patent?
MTEC can help explore whether this patent might be available for licensing for your application.
Publication Number
US-9594872-B2
Publication Date
2017-03-14
Expiration Date
Abstract
A method for implementing an interface terminology is described, the interface terminology comprising concepts and descriptions, a description being an alternative way to express a concept. The interface terminology also may include a plurality of domains, wherein each concept is unique within a domain. The method may include the steps of: storing a plurality of concepts in a database; storing a plurality of descriptions in a database; linking each description to a respective concept; storing an external code set in a database, the external code set comprising a plurality of external codes; and mapping an external code to a concept. The steps may occur via database table mapping. The method also may include deploying a front-end file, the front-end file comprises a link between the descriptions and the external code set.
Core Innovation
The invention implements an interface terminology in a longitudinal electronic medical record by representing medical knowledge as concepts and descriptions, where a description is an alternative way to express a concept. The interface terminology provides a unique terminology for a user and includes multiple descriptions that may link to one concept, including terms used by clinicians and patients, and for each concept one description is a preferred description and one description is a preferred consumer term.
Concepts are stored in a first table, descriptions are stored in a second table, and linking information that links each description to a respective concept is stored in a third table, with the linking performed using a directed graph structure. The system also stores an external code set in a fourth table, mapping each external code to a respective concept via a directed graph structure. The mapping supports multiple descriptions per concept and multiple external codes per concept, enabling update-friendly concept behavior such as adding, updating, deleting, and merging.
For longitudinal record continuity, the invention creates a longitudinal electronic medical record by generating first and additional instances of data objects during first and later encounters, linking a data object to a summarization reference with a pointer, and tracking relationships across instances using a directed graph data structure. It further tags elements within a domain with one or more descriptions and displays the preferred description and the preferred consumer term. A front-end deployment file can include concept-description and description-to-external code set links in CSV ASCII, tab-delimited ASCII, database export, or binary flat file format, and optionally supports cloud deployment with a stateless, in-memory database for providing clinician intent capture and continuity across time.
Claims Coverage
The independent claims cover implementing an interface terminology in a longitudinal electronic medical record using concepts, descriptions, preferred clinician and consumer terms, directed-graph mappings to external code sets, and directed-graph tracking for longitudinal continuity. Across the independent claims, the inventive features are: table-based concept/description/external-code storage and directed-graph mapping; directed-graph linking with preferred terms and external vocabulary table linkage; and front-end file deployment that links descriptions to an external code set alongside longitudinal EMR continuity and domain organization constraints.
Directed graph interface terminology tables with concept-description-external code mapping
Storing a plurality of concepts in a first table a database; storing a plurality of descriptions in a second table; storing in a third table linking information that links each description to a respective concept; storing an external code set in a fourth table comprising a plurality of external codes; and mapping an external code to a respective concept via a directed graph structure.
Longitudinal directed-graph continuity of data object instances across encounters
Creating a longitudinal electronic medical record by generating a first instance of data objects during a first encounter with an instance identifier and temporal identifiers; linking a data object in the first instance to a summarization reference with a pointer where the data objects and summarization reference are related as part of a directed graph data structure; creating an additional instance during a later encounter; and providing continuity by tracking a relationship between a data object of the first instance and a data object of the additional instance.
Preferred description and preferred consumer term tagging and display
Tagging elements within a domain within the longitudinal electronic medical record with one or more of said plurality of descriptions; and displaying the preferred descriptions and the preferred consumer term, where the descriptions include terms used by both clinicians and patients and for each concept one description is a preferred description and one is a preferred consumer term.
Concept and description tables linked via directed graph with external vocabulary table mapping
Generating a concept table including a column storing a plurality of concept identifiers; generating a description table including a column storing a plurality of description identifiers; linking the concept table to the description table via a directed graph structure; generating an external vocabulary table including a column storing a plurality of external vocabulary identifiers; and linking the concept table to the external vocabulary table via a directed graph structure.
Concept-description external vocabulary identifier mapping and longitudinal continuity with preferred term display
Creating a longitudinal electronic medical record by generating a first instance of a plurality of data objects during a first encounter and linking a data object in the first instance to a summarization reference with a pointer as part of a directed graph data structure; creating an additional instance during a later encounter; providing continuity by tracking a relationship between the data objects of the first and additional instances; tagging elements within a domain with one or more of said plurality of descriptions; and displaying the preferred descriptions and the preferred consumer term.
Front-end file linking between descriptions and external code set
Linking in a database each concept to two or more respective descriptions via a directed graph structure; storing an external code set comprising external codes; mapping each concept to a respective external code via a directed graph structure; and deploying a front-end file where the front-end file comprises a link between the descriptions and the external code set.
The independent claims collectively cover directed-graph-based storage and mapping of concepts, descriptions, and external codes or external vocabulary, explicit designation of preferred descriptions and preferred consumer terms, and directed-graph tracking of relationships between data-object instances across encounters to support longitudinal continuity, with deployment via a front-end file that links descriptions to an external code set.
Stated Advantages
Serves the ends of capturing clinician's intent.
Drives financial aspects including billing.
Drives analytical functions.
Supports capturing clinician intent and providing longitudinal continuity for data objects over time.
Documented Applications
Implementing interface terminology in a longitudinal electronic medical record for tagging and displaying preferred descriptions and preferred consumer terms.
Capturing clinician intent, driving financial aspects including billing, and driving analytical functions using the implemented interface terminology.
Creating longitudinal electronic medical record data objects across encounters using summarization references and directed-graph continuity tracking.
Deploying an interface terminology so that a front-end deployment file supports integration with clinical workflow such as search/selection populating EMR fields, and transforming mapping data into user-facing views.
Storing patient data in an electronic health record using the interface terminology.
Interested in licensing this patent?