Clinical data database system and method for a critical care and/or hospital environment
A system for capturing and maintaining a categorized flow of data in a clinical environment includes a distributed computer network, a plurality of data clusters dispersed over the network, a repository adapted to store data representative of the identity of patients, means for querying the repository to identify one of the data clusters associated with a particular patient and in response to such identification of the data cluster, allowing said particular patient or a user to query clinical data associated with the patient from said identified data cluster.
1 . A clinical data system, comprising:
A. a distributed computer network including a plurality of nodes, one or more of said nodes including at least one server,
B. a plurality of data clusters dispersed over said network, each of said data clusters being associated with one of said servers, and said data clusters each being adapted to store clinical data associated with one or more patients,
C. a repository adapted to store data representative of the identity of patients having clinical data associated with particular ones of said data clusters, and
D. means for querying said repository to identify one of said data clusters associated with a particular patient having clinical data associated therewith and residing on said identified data cluster, and in response to such identification of said data cluster, for querying said identified data cluster to request clinical data associated with said patient and residing thereon.
2 . A system according to claim 1 , wherein each of said data clusters stores medical record data for a predetermined number of patients.
3 . A system according to claim 2 , wherein said medical record data includes heart rate data, body temperature data, diagnosis code data, or demographic data of patients.
4 . A system according to claim 1 , wherein each of said servers is associated with zero, one or more said data clusters.
5 . A system according to claim 1 , wherein said means for querying is a user terminal.
6 . A system according to claim 1 , wherein each of said data clusters is classified by an active or a non-active status.
7 . A system according to claim 6 , wherein each of said data clusters is characterized by a predetermined capacity limit for an amount of data storable therein.
8 . A system according to claim 7 , wherein each of said data clusters changes status from active to non-active when an amount of data stored in said data cluster reaches said predetermined limit.
9 . A system according to claim 7 , wherein said active status for a data cluster indicates that the amount of data stored in said data cluster is below said capacity limit for said data cluster.
10 . A system according to claim 7 , wherein said inactive status for a data cluster indicates that the amount of data stored in said data cluster is at said capacity limit for said data cluster.
11 . A system according to claim 1 , wherein said repository is a single hospital-wide database.
12 . A system according to claim 1 , wherein said repository includes a cluster index, which is a list of all said data clusters in said system and physical locations of said data clusters.
13 . A system according to claim 1 , wherein said repository includes a patient master index data representative of said data clusters on which said clinical data associated with respective patients resides.
14 . A system according to claim 1 , wherein said data cluster is adapted to store at least one patient data for a patient being representative of one or more of a patient identifier, an admission data, demographic data, diagnosis data, vital sign data, analog wave data, running orders, care plans, or other clinical data.
15 . A method for capturing and maintaining a categorized flow of data in a clinical environment, comprising the steps of:
A. a user issuing a query to a repository, wherein said repository stores identification information of patients and an index of a plurality of data clusters storing clinical data of said patients;
B. said repository, in response, identifying an identity of a particular patient and identifying a data cluster having the clinical data associated with said particular patient;
C. the user issuing a query to said identified data cluster to request the clinical data associated with the particular patient; and
D. the user receiving the requested clinical data from said identified data cluster.
16 . A method according to claim 15 , wherein said user issues said queries from a user terminal.
17 . A method according to claim 15 , wherein said repository and said plurality of data clusters form a data network.