Data representation management in a database
First Claim
1. In a system including a legacy system sending clinical data including physical location data to a data repository, wherein the clinical data is processed with a health data dictionary before storing the clinical data in the data repository and wherein the physical location data has a representation stored in the health data dictionary, a method for managing the physical location data, the method comprising:
- an act of selecting physical location data at the legacy system;
an act of changing a current representation of the selected physical location data to a new representation of the selected physical location data, the current representation stored in the health data dictionary; and
an act of committing the new representation of the physical location data in the health data dictionary.
1 Assignment
0 Petitions
Accused Products
Abstract
Systems and methods for managing physical location data and representation data in a health data dictionary. Clinical data is represented in a health data dictionary using a vocabulary that includes concepts and representations. Each concept is a unique item or idea and each concept can be associated with multiple representations. The default representations are difficult to use because most legacy systems are already accustomed to other terms or identifiers. The present invention allows the representations in the health data dictionary to be changed, altered, or modified according to the desires, of the legacy systems. The representation to be changed is identified by the legacy system and changed in accordance with instructions received from the legacy systems. The instructions may be to update, change, add, delete or otherwise modify a representation. The location manager is used to modify physical location data including representations, contexts, and concepts. The representation manager is used to modify contexts and representations of multiple types of data. In this manner, representations can be searched, assigned to other concepts, updated, changed, deleted, created and the like. The modules that perform these actions are subject to rules and constraints of the health data dictionary. Also, these modules modify relationships in the health data dictionary that are associated with the representations being changed.
-
Citations
33 Claims
-
1. In a system including a legacy system sending clinical data including physical location data to a data repository, wherein the clinical data is processed with a health data dictionary before storing the clinical data in the data repository and wherein the physical location data has a representation stored in the health data dictionary, a method for managing the physical location data, the method comprising:
-
an act of selecting physical location data at the legacy system;
an act of changing a current representation of the selected physical location data to a new representation of the selected physical location data, the current representation stored in the health data dictionary; and
an act of committing the new representation of the physical location data in the health data dictionary. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 14, 15, 16, 17, 18, 19, 20)
-
-
13. In a system including a legacy system generating clinical data including physical location data for storage in a data repository, wherein the clinical data is processed using a health data dictionary to translate and normalize the clinical data before storing the clinical data in the data repository, wherein the health data dictionary has content for translating and normalizing the clinical data, the content including a plurality of concept identifiers and at least one representation for each concept, a method for modifying the content of the health data dictionary by the legacy system, the method comprising:
-
a step for determining a current representation of current physical location data stored in the health data dictionary;
a step for receiving input from the legacy system that identifies a new representation for the current physical location data;
a step for modifying the current representation to the new representation without affecting a concept identifier associated with the current representation;
a step for committing the new representation to the health data dictionary.
-
-
21. In a system including a legacy system having clinical data for storing in a data repository, the clinical data being mapped with a health data dictionary, the health data dictionary having a vocabulary including concept identifiers associated with at least one representations, the concept identifiers and associated at least one representations used to map the clinical data, a method for managing the at least one representations in the health data dictionary, the method comprising:
-
an act of receiving a current representation from the legacy system, wherein the current representation is associated with an interface code provided by the legacy system;
an act of searching the health data dictionary for the current representation, wherein the current representation is associated with a concept identifier; and
an act of changing the current representation without changing the concept identifier. - View Dependent Claims (22, 23, 24, 25, 26, 27, 28, 29)
-
-
30. In a system including a health data dictionary for mapping clinical data received from a legacy system for storage in a data repository, a method for mapping representations of the clinical data to the health data dictionary, the representations provided by the legacy system, the method comprising:
-
a step for receiving a current representation identified by the legacy system;
a step for searching the health data dictionary for the current representation;
a step for receiving instructions from the legacy system; and
a step for managing the current representation in accordance with the received instructions such that the current representation is mapped to the clinical data. - View Dependent Claims (31, 32, 33)
-
Specification