CA2247915A1 - Medical record management system and process with improved workflow features - Google Patents
Medical record management system and process with improved workflow features Download PDFInfo
- Publication number
- CA2247915A1 CA2247915A1 CA002247915A CA2247915A CA2247915A1 CA 2247915 A1 CA2247915 A1 CA 2247915A1 CA 002247915 A CA002247915 A CA 002247915A CA 2247915 A CA2247915 A CA 2247915A CA 2247915 A1 CA2247915 A1 CA 2247915A1
- Authority
- CA
- Canada
- Prior art keywords
- caregiver
- patient
- access
- chart
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99938—Concurrency, e.g. lock management in shared database
Landscapes
- Health & Medical Sciences (AREA)
- Engineering & Computer Science (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Medical Treatment And Welfare Office Work (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
A patient medical record system includes a number of caregiver computers, and a patient record database with patient data coupled to the caregiver computers selectively providing access to the patient data from one of the caregiver computers responsive to a predetermined set of access rules. The predetermined set of rules includes a rule that access to a predetermined portion of the patient data by a first caregiver must be terminated before access to the same predetermined portion by a second caregiver is allowed.
Description
Description Medical F~ecord Mana~ement System and Process With Improved Workflow Features BACKGROUND OF THE INVENIION
This invention relates generally to systems and methods of clinical information management and specifically to sy~stems and processes by which electronic medical records may be m~int~inPrl in an envh~ lle-ll in which a patient encounter may involve multiple caregivers and in which a caregiver may have need to .simlllt~n~.ously access information for multiple patients.
The liteltltulG is replete with references to systems for mzlint~ining electronic patient records. Such electronic records are touted as possible replacements for traditional paper patient records, permitting faster access to patient information, search capabilities, and facilities for imm~ te tr~n.smi.s.sion of information from caregivers in one location (e.g., an attending physician's office) to another location (e.g., a hospital emergency room).
As medical records become ever more detailed and complex, the need for automatedprocesses for collecting, storing, tr~nsmitting, and retrieving patient medical information becomes more critical. Historically, hand-entered medical records were very brief and were sometimes of limited value for future care, either because entries were illegible, used non-standard abbreviations, lacked sufficient detail, or were difficult to search. It has been widely CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97/03257 reported in the literature that such dif~lculties resulled in neg;lti-e el'i'ects on clinical judgrnent. patient care plans, medical record audits~ medical educa~ion. and physician performance evaluation.
Early attempts at providing automated patient records typically used codes to represent a dia~nosis or problem, with additional detail being provided in narrative form.
These first-generation systems provided some advantages over traditional hard-copy records, but were never widely adopted by the medical community. It has been speculated that such systems never provided the practical ease of use required to convince caregivers to switch from paper-based records.
One example of a more advanced electronic patient record system was MEDAS, or Medical Emergency Decision Assistance System. MEDAS was developed starting in the 1970s at the University of Southern California and hen at the IJniversity of Health Sciences/The Chicago Medical School. MEDAS included features for the capture of patient history, physical ex:llnin~tion, and chief complaint information.
Another system, MEDRIS, or Medical Record Input System, employed hypermedia approach to capture patient history and physical ex~min~tion data. MEDRIS sought to guide physicians through the particular tasks used for these encounters, and also permitted the collection of data from other types of encounters, such as brief drop-in visits.As smaller desktop computers, as well as notebook computers and pen-based computers, became widely avai~able, attention turned to multi-user systems to permit a network of caregivers to store and access patient information. One such system integrated MEDAS with an Intelligent Medical Record Entry module for data entry and also provided a portable patient file.
Despite the various advantages they provide over paper-based records. even current-generation systems have not enjoyed widespread acceptance by the medical profession. ~t is believed that a number of practical factors continue to limit the use of electronic patient records by physicians and other caregivers.
One problem that has not been fully addressed by known automated patient record systems involves caregiver work flow. The types of interactions that caregivers have with CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97/03257 patients vary ~ idely t'rom hour to hour and from office ~o office. In some clinical environments. it is cornmon for several caregivers to interact with a patient durin~ a sin~,le visit. Sirnilarly. it is common for a single c~regiver to need to access several patient records at nearly the sarne ~ime.
Due to data integrity concerns (e.g., that a patient record not be open for modification by two users at the same time), it can be confusing and difficult using existing systems to allo-v multiple caregivers to access information for the sarne patient or to access information for multiple pa~ients at nearly the same time.
It has also been found that existing systems suffer certain inefhciencies is people in different positions access patient records. For example, a doctor may enter diagnosis information in one format, but insurance requirements may call for an adminis~rator to enter redundant information in a different format.
Therefore, it would be advantageous if an improved patient medical record system and process could provide efficient workflow management by facilitating multiple caregiver access, multiple patient record access, and automatic formatting of diagnostic information.
No kno~ n solution adequately addresses these needs in a simple, flexible, robust, and inexpensive manner.
SUMMAR~ OF THE INVENTION
In accordance w ith the present invention, a patient record system (100~ includes a first caregiver's terminal (I 1()~, a second caregiver's terminal (ll?), and a patient record database with patient dat:3 coupled to the first and second terrninals and selectively providing access to the patient data from one of the first and second terminals responsive to a predetermined set of access rules Further in accordance with the present invention, the predetermined set of rules~ includes a rule that access to a predetermined portion of the patient data by a first caregiver is terrnin~tPrl before access to the same predetermined portion by a second caregiver is allowed.
CA 0224791~ 1998-08-28 W O 97/32271 PCTrUS97103257 Still further in accordance with Ihe present invention. the predetermined set of rules includes a rule arbitrating access to a portion of the patient data when more than one caregiver seeks access to the portion of the patient data.
In yet another aspect of the invention, a patient record system includes a patient chart workflow subsystern configured to allow a caregiver to engage in a first patient encounter corresponding to a first patient while also eng~ging in a second patient encounter corresponding to a second patient.
In still another aspect of the invention, the patient char~ workflow subsystem is configured to allow a caregiver to open encounters for a plurality of patients upon commencing a round of activities.
In another aspect of the invention, a method of m~int~ining a patient record includes providing a first caregiver with a terminal, providing a second caregiver with a terrninal, and selectively permitting the first and second caregivers, using the t~rmin~l~ to access patent data from a patent record database according to a predetermined set of access rules.
In still another aspect of the invention, a method of m~inr~ining a patent record includes selectively permitting a first caregiver and a second caregiver, using a terminal, to access patient data from a patient record database according to a predet~A~nined set of access rules.
The features and advantages described in the specification are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the art in view of the drawings, specifications, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necçc~zlry to determine such inventive subject matter.
BRIEF DESCRIPTION OF T~E DRAWINGS
Figure 1 is a block diagram of a patent record system in accordance with the present invention.
CA 0224791~ 1998-08-28 W O 97132271 PCT~US97/~3257 Figure 2 is a block diagram of the patient chart ~vorktlo~v subsystem illustrated in figure 1.
FLgure 3 is a flow dia"ram of the operation of a pull chart component of patient chart workflow subsystem in accordance with the present invention.
DETAILE~D DESCRIPTIOl~ OF THE DRAWI~I~S
The figures depict a preferred embodiment of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
Referring now to figure l, there is sho~vn a patient record s~stem l00 in accordance with the present invention. System l00 includes a patient record database 107, a database management system 104 with a patient chart workilow subsystem l05, a diagnostic inforrnation database 106, a reporting information database l08, and user computers 110, 112. 1 I~, 116. In figure 1, four separate types of user computers are illustrated: a doctor's computer 110, a nurse's computer 1 l2, a transcriber's computer l I4, and an insurance ,lrlministrator's computer l l6.
It should be recognized that as system l 00 is intended to provide a ~eneralized medical record in a variety of clinical settin"s, the number and types of user computers, e.g., l 10, will vary with each application. For instance, a practice having five e~min;ng rooms, three doctor's of~lces and two nurse/~.lminis~rators may have ten terminals: five doctor's computers 110 in the examining rooms, three doctor's computers 110 in the doctors' offices, and two nurse's/:-~lministrator's computers l l2, l l4 at the nurses' stations. It should also be recognized that system l00 may be implemented using any appropriate computer for each user computer, e.g., 110. For example, the nurse's computer l l~ may be a standard desktop personal computer, while the doctor's computer l 10 may be a notebook-style computer or personal digital assistant-type computer. Computers 110,112,114, 116 are sometimes referred to herein as terminals, as such computers are used primarily for input and output of data. In a preferred embodiment, personal computers are used to implement such terminals. It should be CA 0224791~ 1998-08-28 W O 97132271 PCTrUS971032~7 recognized that there may be applications for alternate embodiments in w hich such terminals may be implemented by devices other than personal computers. such as client w or~;stations, personal digital assistants, or even possibly terminals that do not function as standalone independent computers at all, but rely in part on other equipment connected by a network for their operation.
In operation, system 100 permits any of several caregivers to enter and re[rieve data for a patient's medical record. In a typical "intake" situation. an administrator. through ~rlminictrator's computer 116, may input new patient information such as name. address, and insurance identification data. A nurse 112 may take the patient's vital signs observed during an office visit and enter them into system 100 using nurse's computer 1 1~. A doctor e~mining the patient may enter the results of the ex~min:-~ion, or a diagnosis from the patient's chief complaint. using doctor's computer 110. In some cases, the doctor dictates a detailed description of the encounter with the patient using conventional dictation apparatus, and this dictation is later entered as text into system 100 by a transcriber operating a transcriber's computer 114. After an office visit, the insurance administrator typically processes insurance inforrnation pertaining to the visit using computer 116. In a preferred embodiment, system 100 includes a conventional interface ~vith insurance processing programs operating on the insurance administrator's computer 116 to allow the insurance atlminiclrator to use information from system 100 in performing insurance-related data processing.
Information used by system 100 takes a variety of forms. Patien~-specific information includes patient identification information, patient medical history information. patient visit records~ and the like. Information of this sort is stored in patient record database 102.
System 100 also provides medical information not specific to a particular patient that a doctor may use in diagnosing a patient's complaint or for other purposes. For ins~ance, system 100 provides a listing of commonly encountered diagnoses, coupled with links to pertinent related symptom and e~t~min~tion information. This information is stored in a diagnostic information database 106. In a preferred embodiment, this information includes the CA 0224791~ 1998-08-28 W O 97132271 PCT~US97/03257 SNOMED database of diagnostic terms~ provided commerciaily by th~ Americ;lll College of Pathologists.
System 100 further provides administrative information not specific to a partlcular patient that a clinic may use, c~.g., for purposes of generating insurance reimbursemen~
requests. This information is stored in a reporting information database 108. In a preferred embodiment. this information includes the ICD-9 database of medical diagnostic codes that are typically used for insurance reportin~ purposes.
System 100 provides correspondence between diagnostic information from diagnostic information database 10~ and a~lmini~trative information accessed through reporting information database 10~. Specifically, in a preferred embodiment. each item of dia~nostic information from diagnostic information database 106 is mapped to a correspondin~ ICD-9 code that is recorded along, with the item of diagnostic information. By providing the corresponding ICD-9 code for each diagnostic entry, a caregiver such as a doctor need only enter in the patient record once, during an encounter with a patient. a diagnosis in conventional form for-that record to include the ICD-g mode that will be used for insurance reportin~ purposes with respect to that encounter.
As a specific example, if a doctor selects from diagnostic information database 106 an entry for "acute bronchitis." there is a predetermined correspondence between that entry and an entry from the reporting information database 108. In a preferred embodiment. the correspondino entry for acute bronchitis is the number ~66.0, the ICD-9 code corresponding to the diagnosis of acute bronchitis. Thus. when an l~lminictrator operating administrator's computer 116 performs administrative data processin~ for this encounter, the ~iminictrator will automaticallv have presented not only the doctor's diagnosis, but the ICD-9 code corresponding IO the diagnosis. In a preferred embodiment, the correspondences between diagnosis entries and DCD-9 codes is predetermined manually and the ICD-9 codes are stored as text along ~~ ith each diagnostic entry. Accordingly, in a preferred embodiment the diagnostic information database 106 and the reportin~ information database 108 are implemented together as a single database. In alternative embodiments, the correspondence could be determined. either statically or dynamically, in numerous other ways, for instance by CA 0224791~ 1998-08-28 W O 97/32271 PCTrUS97/03257 using an expert system-based mapping processor Ihat dynamically selects entries in reporting information database 108 to correspond with entries in diagnostic information database 106.
A database managcment system 104 coordinates and facilitates movement of data into and among patient record database 102. diagnostic information database 106, and reporting information ~ hace 108. In a preferred embodiment, the ORACLE database management system is used for database management system 104.
ln a preferred embodiment, components 10~,104, and 106 -108 are implemented as asystem server 101 using a conventional NT- or UNIX-capable server-class computerinterconnected with usercomputers 110,112, 114, 116, which are configured as client computers.
Both the direct caregivers, such as doctors and nurses, and indirect caregivers, such as insurance administrators and transcribers, have need to access a patent's record at various times. As is evident from the above description, the workflow of typical patient care may call for one caregiver to seek access to information for a particular patient at a time when another caregiver also seeks access to information for that patient.
System 100 manages the flow of patient information during an encounter in a number of ways. System 100 allows multiple caregivers to record information for the same patient visit. System 100 displays all patient information recorded during a visit, regardless of which caregiver recorded the information. System 100 m:~int~3in.c the integrity of patient information that is recorded by each caregiver. System 100 provides a vehicle for a patient's chart to be sent from one caregiver to another.
To provide these features"l~h~ce management system 104 includes a patient chart wor~;flow subsystem 105. Referring now also to figure 2, patent-chart workflow subsystem 105 includes a pull chart component 201, a chart management component 202, a send chart component 203, and a file chart component 204. Before ~ cuc.cing these components in detail, it will be helpful to provide the following list of terrninology:
Ghart: A patient's medical record.
Chart List: A list or patients' charts that have been pulled by a caregiver and not yet filed or sent.
CA 0224791~ 1998-08-28 W O 97132271 PCTrUS97/03257 Contact: A specific interaction with the patient~ or t'unction performed against the patient's chart (e.g., obtaining vital signs, entering chief complaints~ recording history of present illness conducting a physical examination. reviewing medications, reviewin;, laboratory results). As used herein, a contact is performed by a single caregiver.
Contact Data: The clinical information in a patient's chart that is being recorded for the encounter in progress.
Encounter: Any interaction with a patient's chart (e.g., office visit, phone visit, chart review, medication refill, consultation). An encounter comprises one or more contacts, performed by one or more caregivers.
Preferred Care~iver: The physician who is primarily responsible for the patient's care, also known as the primary caregiver.
Surnmary Data: The demographic and historical information in the patient's chart that has been recorded during previous encounters. Also included in the category of information are patient reminders, patient orders, and patient laboratory tests.
Patient workflow subsystem 105 enforces predetermined rules for ~-~cP.scing a patient's chart and manages who can pull such charts, as well as under what conditions they can be pulled. The predetermined rules include:
1. Each encounter is considered to be a unique event that can have multiple contacts associated with it. In one embodiment, a unique encounter code is used as a fi~t~ha~e key to an encounter table that records and manages each encounter.
This invention relates generally to systems and methods of clinical information management and specifically to sy~stems and processes by which electronic medical records may be m~int~inPrl in an envh~ lle-ll in which a patient encounter may involve multiple caregivers and in which a caregiver may have need to .simlllt~n~.ously access information for multiple patients.
The liteltltulG is replete with references to systems for mzlint~ining electronic patient records. Such electronic records are touted as possible replacements for traditional paper patient records, permitting faster access to patient information, search capabilities, and facilities for imm~ te tr~n.smi.s.sion of information from caregivers in one location (e.g., an attending physician's office) to another location (e.g., a hospital emergency room).
As medical records become ever more detailed and complex, the need for automatedprocesses for collecting, storing, tr~nsmitting, and retrieving patient medical information becomes more critical. Historically, hand-entered medical records were very brief and were sometimes of limited value for future care, either because entries were illegible, used non-standard abbreviations, lacked sufficient detail, or were difficult to search. It has been widely CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97/03257 reported in the literature that such dif~lculties resulled in neg;lti-e el'i'ects on clinical judgrnent. patient care plans, medical record audits~ medical educa~ion. and physician performance evaluation.
Early attempts at providing automated patient records typically used codes to represent a dia~nosis or problem, with additional detail being provided in narrative form.
These first-generation systems provided some advantages over traditional hard-copy records, but were never widely adopted by the medical community. It has been speculated that such systems never provided the practical ease of use required to convince caregivers to switch from paper-based records.
One example of a more advanced electronic patient record system was MEDAS, or Medical Emergency Decision Assistance System. MEDAS was developed starting in the 1970s at the University of Southern California and hen at the IJniversity of Health Sciences/The Chicago Medical School. MEDAS included features for the capture of patient history, physical ex:llnin~tion, and chief complaint information.
Another system, MEDRIS, or Medical Record Input System, employed hypermedia approach to capture patient history and physical ex~min~tion data. MEDRIS sought to guide physicians through the particular tasks used for these encounters, and also permitted the collection of data from other types of encounters, such as brief drop-in visits.As smaller desktop computers, as well as notebook computers and pen-based computers, became widely avai~able, attention turned to multi-user systems to permit a network of caregivers to store and access patient information. One such system integrated MEDAS with an Intelligent Medical Record Entry module for data entry and also provided a portable patient file.
Despite the various advantages they provide over paper-based records. even current-generation systems have not enjoyed widespread acceptance by the medical profession. ~t is believed that a number of practical factors continue to limit the use of electronic patient records by physicians and other caregivers.
One problem that has not been fully addressed by known automated patient record systems involves caregiver work flow. The types of interactions that caregivers have with CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97/03257 patients vary ~ idely t'rom hour to hour and from office ~o office. In some clinical environments. it is cornmon for several caregivers to interact with a patient durin~ a sin~,le visit. Sirnilarly. it is common for a single c~regiver to need to access several patient records at nearly the sarne ~ime.
Due to data integrity concerns (e.g., that a patient record not be open for modification by two users at the same time), it can be confusing and difficult using existing systems to allo-v multiple caregivers to access information for the sarne patient or to access information for multiple pa~ients at nearly the same time.
It has also been found that existing systems suffer certain inefhciencies is people in different positions access patient records. For example, a doctor may enter diagnosis information in one format, but insurance requirements may call for an adminis~rator to enter redundant information in a different format.
Therefore, it would be advantageous if an improved patient medical record system and process could provide efficient workflow management by facilitating multiple caregiver access, multiple patient record access, and automatic formatting of diagnostic information.
No kno~ n solution adequately addresses these needs in a simple, flexible, robust, and inexpensive manner.
SUMMAR~ OF THE INVENTION
In accordance w ith the present invention, a patient record system (100~ includes a first caregiver's terminal (I 1()~, a second caregiver's terminal (ll?), and a patient record database with patient dat:3 coupled to the first and second terrninals and selectively providing access to the patient data from one of the first and second terminals responsive to a predetermined set of access rules Further in accordance with the present invention, the predetermined set of rules~ includes a rule that access to a predetermined portion of the patient data by a first caregiver is terrnin~tPrl before access to the same predetermined portion by a second caregiver is allowed.
CA 0224791~ 1998-08-28 W O 97/32271 PCTrUS97103257 Still further in accordance with Ihe present invention. the predetermined set of rules includes a rule arbitrating access to a portion of the patient data when more than one caregiver seeks access to the portion of the patient data.
In yet another aspect of the invention, a patient record system includes a patient chart workflow subsystern configured to allow a caregiver to engage in a first patient encounter corresponding to a first patient while also eng~ging in a second patient encounter corresponding to a second patient.
In still another aspect of the invention, the patient char~ workflow subsystem is configured to allow a caregiver to open encounters for a plurality of patients upon commencing a round of activities.
In another aspect of the invention, a method of m~int~ining a patient record includes providing a first caregiver with a terminal, providing a second caregiver with a terrninal, and selectively permitting the first and second caregivers, using the t~rmin~l~ to access patent data from a patent record database according to a predetermined set of access rules.
In still another aspect of the invention, a method of m~inr~ining a patent record includes selectively permitting a first caregiver and a second caregiver, using a terminal, to access patient data from a patient record database according to a predet~A~nined set of access rules.
The features and advantages described in the specification are not all-inclusive, and particularly, many additional features and advantages will be apparent to one of ordinary skill in the art in view of the drawings, specifications, and claims hereof. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necçc~zlry to determine such inventive subject matter.
BRIEF DESCRIPTION OF T~E DRAWINGS
Figure 1 is a block diagram of a patent record system in accordance with the present invention.
CA 0224791~ 1998-08-28 W O 97132271 PCT~US97/~3257 Figure 2 is a block diagram of the patient chart ~vorktlo~v subsystem illustrated in figure 1.
FLgure 3 is a flow dia"ram of the operation of a pull chart component of patient chart workflow subsystem in accordance with the present invention.
DETAILE~D DESCRIPTIOl~ OF THE DRAWI~I~S
The figures depict a preferred embodiment of the present invention for purposes of illustration only. One skilled in the art will readily recognize from the following discussion that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the invention described herein.
Referring now to figure l, there is sho~vn a patient record s~stem l00 in accordance with the present invention. System l00 includes a patient record database 107, a database management system 104 with a patient chart workilow subsystem l05, a diagnostic inforrnation database 106, a reporting information database l08, and user computers 110, 112. 1 I~, 116. In figure 1, four separate types of user computers are illustrated: a doctor's computer 110, a nurse's computer 1 l2, a transcriber's computer l I4, and an insurance ,lrlministrator's computer l l6.
It should be recognized that as system l 00 is intended to provide a ~eneralized medical record in a variety of clinical settin"s, the number and types of user computers, e.g., l 10, will vary with each application. For instance, a practice having five e~min;ng rooms, three doctor's of~lces and two nurse/~.lminis~rators may have ten terminals: five doctor's computers 110 in the examining rooms, three doctor's computers 110 in the doctors' offices, and two nurse's/:-~lministrator's computers l l2, l l4 at the nurses' stations. It should also be recognized that system l00 may be implemented using any appropriate computer for each user computer, e.g., 110. For example, the nurse's computer l l~ may be a standard desktop personal computer, while the doctor's computer l 10 may be a notebook-style computer or personal digital assistant-type computer. Computers 110,112,114, 116 are sometimes referred to herein as terminals, as such computers are used primarily for input and output of data. In a preferred embodiment, personal computers are used to implement such terminals. It should be CA 0224791~ 1998-08-28 W O 97132271 PCTrUS971032~7 recognized that there may be applications for alternate embodiments in w hich such terminals may be implemented by devices other than personal computers. such as client w or~;stations, personal digital assistants, or even possibly terminals that do not function as standalone independent computers at all, but rely in part on other equipment connected by a network for their operation.
In operation, system 100 permits any of several caregivers to enter and re[rieve data for a patient's medical record. In a typical "intake" situation. an administrator. through ~rlminictrator's computer 116, may input new patient information such as name. address, and insurance identification data. A nurse 112 may take the patient's vital signs observed during an office visit and enter them into system 100 using nurse's computer 1 1~. A doctor e~mining the patient may enter the results of the ex~min:-~ion, or a diagnosis from the patient's chief complaint. using doctor's computer 110. In some cases, the doctor dictates a detailed description of the encounter with the patient using conventional dictation apparatus, and this dictation is later entered as text into system 100 by a transcriber operating a transcriber's computer 114. After an office visit, the insurance administrator typically processes insurance inforrnation pertaining to the visit using computer 116. In a preferred embodiment, system 100 includes a conventional interface ~vith insurance processing programs operating on the insurance administrator's computer 116 to allow the insurance atlminiclrator to use information from system 100 in performing insurance-related data processing.
Information used by system 100 takes a variety of forms. Patien~-specific information includes patient identification information, patient medical history information. patient visit records~ and the like. Information of this sort is stored in patient record database 102.
System 100 also provides medical information not specific to a particular patient that a doctor may use in diagnosing a patient's complaint or for other purposes. For ins~ance, system 100 provides a listing of commonly encountered diagnoses, coupled with links to pertinent related symptom and e~t~min~tion information. This information is stored in a diagnostic information database 106. In a preferred embodiment, this information includes the CA 0224791~ 1998-08-28 W O 97132271 PCT~US97/03257 SNOMED database of diagnostic terms~ provided commerciaily by th~ Americ;lll College of Pathologists.
System 100 further provides administrative information not specific to a partlcular patient that a clinic may use, c~.g., for purposes of generating insurance reimbursemen~
requests. This information is stored in a reporting information database 108. In a preferred embodiment. this information includes the ICD-9 database of medical diagnostic codes that are typically used for insurance reportin~ purposes.
System 100 provides correspondence between diagnostic information from diagnostic information database 10~ and a~lmini~trative information accessed through reporting information database 10~. Specifically, in a preferred embodiment. each item of dia~nostic information from diagnostic information database 106 is mapped to a correspondin~ ICD-9 code that is recorded along, with the item of diagnostic information. By providing the corresponding ICD-9 code for each diagnostic entry, a caregiver such as a doctor need only enter in the patient record once, during an encounter with a patient. a diagnosis in conventional form for-that record to include the ICD-g mode that will be used for insurance reportin~ purposes with respect to that encounter.
As a specific example, if a doctor selects from diagnostic information database 106 an entry for "acute bronchitis." there is a predetermined correspondence between that entry and an entry from the reporting information database 108. In a preferred embodiment. the correspondino entry for acute bronchitis is the number ~66.0, the ICD-9 code corresponding to the diagnosis of acute bronchitis. Thus. when an l~lminictrator operating administrator's computer 116 performs administrative data processin~ for this encounter, the ~iminictrator will automaticallv have presented not only the doctor's diagnosis, but the ICD-9 code corresponding IO the diagnosis. In a preferred embodiment, the correspondences between diagnosis entries and DCD-9 codes is predetermined manually and the ICD-9 codes are stored as text along ~~ ith each diagnostic entry. Accordingly, in a preferred embodiment the diagnostic information database 106 and the reportin~ information database 108 are implemented together as a single database. In alternative embodiments, the correspondence could be determined. either statically or dynamically, in numerous other ways, for instance by CA 0224791~ 1998-08-28 W O 97/32271 PCTrUS97/03257 using an expert system-based mapping processor Ihat dynamically selects entries in reporting information database 108 to correspond with entries in diagnostic information database 106.
A database managcment system 104 coordinates and facilitates movement of data into and among patient record database 102. diagnostic information database 106, and reporting information ~ hace 108. In a preferred embodiment, the ORACLE database management system is used for database management system 104.
ln a preferred embodiment, components 10~,104, and 106 -108 are implemented as asystem server 101 using a conventional NT- or UNIX-capable server-class computerinterconnected with usercomputers 110,112, 114, 116, which are configured as client computers.
Both the direct caregivers, such as doctors and nurses, and indirect caregivers, such as insurance administrators and transcribers, have need to access a patent's record at various times. As is evident from the above description, the workflow of typical patient care may call for one caregiver to seek access to information for a particular patient at a time when another caregiver also seeks access to information for that patient.
System 100 manages the flow of patient information during an encounter in a number of ways. System 100 allows multiple caregivers to record information for the same patient visit. System 100 displays all patient information recorded during a visit, regardless of which caregiver recorded the information. System 100 m:~int~3in.c the integrity of patient information that is recorded by each caregiver. System 100 provides a vehicle for a patient's chart to be sent from one caregiver to another.
To provide these features"l~h~ce management system 104 includes a patient chart wor~;flow subsystem 105. Referring now also to figure 2, patent-chart workflow subsystem 105 includes a pull chart component 201, a chart management component 202, a send chart component 203, and a file chart component 204. Before ~ cuc.cing these components in detail, it will be helpful to provide the following list of terrninology:
Ghart: A patient's medical record.
Chart List: A list or patients' charts that have been pulled by a caregiver and not yet filed or sent.
CA 0224791~ 1998-08-28 W O 97132271 PCTrUS97/03257 Contact: A specific interaction with the patient~ or t'unction performed against the patient's chart (e.g., obtaining vital signs, entering chief complaints~ recording history of present illness conducting a physical examination. reviewing medications, reviewin;, laboratory results). As used herein, a contact is performed by a single caregiver.
Contact Data: The clinical information in a patient's chart that is being recorded for the encounter in progress.
Encounter: Any interaction with a patient's chart (e.g., office visit, phone visit, chart review, medication refill, consultation). An encounter comprises one or more contacts, performed by one or more caregivers.
Preferred Care~iver: The physician who is primarily responsible for the patient's care, also known as the primary caregiver.
Surnmary Data: The demographic and historical information in the patient's chart that has been recorded during previous encounters. Also included in the category of information are patient reminders, patient orders, and patient laboratory tests.
Patient workflow subsystem 105 enforces predetermined rules for ~-~cP.scing a patient's chart and manages who can pull such charts, as well as under what conditions they can be pulled. The predetermined rules include:
1. Each encounter is considered to be a unique event that can have multiple contacts associated with it. In one embodiment, a unique encounter code is used as a fi~t~ha~e key to an encounter table that records and manages each encounter.
2. A contact is considered to be a unique event within an encounter. In one embodiment, a unique contact code, to~ether with the corresponding encounter code, are used as a database Icey to a contact table that records and manages each contact.
3. A new contact is started each time a caregiver pulls a patient's chart, unless the patient's chart has already been pulled by that caregiver.
4. A user interface screen for a new contact displays all the data entered during previous contacts for the same encounter.
CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97/03257 ~ . Onlv one care~iver at a time is allowed to updale patient conmcI d.1~a. Any attempt bv one care~iver to update a contact being updated by ~nolhcr results in a message that the conIact is already in the process of being updated.
6. ~'hen one caregiver begins to record patient contact data after ;Inother caregiver has recorded patient contacI data for a new contact during the same encounter7 a user interface messa_e asks the new caregiver whether that caregiver wants IO assume control of the patient's chart. Bv keeping track of chart "ownership," all caregivers know ~ ho is responsible for any particular chart at any particular time.
7. Data from a contact are saved in patient record database 102 whenever a user navigates from one type of contact data ~e.g., vital signs~ to another (e.g., chief complaint), sends the patienI s chart to another caregiver, Iocks the system (indicating that the user will be awav from the user's computer, c~.g., 1 12, for some period of time)~ e,Yits the pro_ram, or views another pa~ient's chart.
8. A contact is considered to be complete whenever the caregiver "files" the patient's chart in patient record ~l~t~h~e 102, sends the patient's hart to another caregiver, locks the svstem. exits the program, or views another patient's chart.
9. An encounter is considered complete when the patient's chart is "sioned." A
chart is signed in svstem 100 by a doctor saving in patient record database 10' a file providin~ a History and Physical (H&P) report for the encounter. Whenever cont;3ct data have been recorded during an encounter, system 100 requires that the patient's chart be so signed. Ii no contact data have been entered, such as when a chart is opened for administrative updates or laboratorv review. the patient's chart can be filed without saving the ~&P report.
10. In a preferred embodiment, until an encounter is saved, all data or that encounter may be modified. Some applications may have data inlegrity requirements that preclude modification of any data once entered, and an alternate embodiment for use with such an application does not allow such modification of data.
In a preferred embodiment, components 201-204 are implemented by software programs operatin~g as described herein. It should be recognized that other implementations, CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97103257 such as dedicated circLlitrv. could alsv be used to implemenl some or all of tlle ~unctions o~
components ~01-70~.
Pull Charl component 201 manages u.sers' ability to pull patient ch~rts tbaseci on t patienl privacv iniormation and based upon application security levels of a particular caregiver.
Referring now also to figure 3~ when a user of system 100 requests to see a patient chart, processing is initiated 301 for pull chart component 201. Firstt a checlc 30' is made to see whether the caregiver is authorized to have any chart access. If so~ a check 303 is made to see whether the caregiver is authorized user of system 100. If either check is ne~ative, an access denial message is displayed and the pull chart component 201 terminates. Otherwise, a check 305 is made to see ~vhether an encounler is already in process for the palient. If not, an encounter is started 306.
In either event, a check 307 is then made to see whether a chart is alreadv open on the caregiver's computer, e.g., 110, for this encounter. If not, a chart is opened and added 308 to a list of pulled charts for that caregiver. A contact is then started 309. A determination 310 is made as to the caregiver's security level, and the parts of the patient chart for which access is allowed arc then made available for display 311. At this point the pull chart component 201 is complete 3 1 ' .
In some instances. a patient may have a particular sensitivity to privacy and there may be specific information on which caregivers are authorized to review particular portions of the patient's record. In other cases, there may be no specific privacy instructions, in ~ hich case the inquiry ~vill simply be ~vhether the caregiver requesting to pull the chart is authorized to view any patients charts. Also in a preferred embodiment~ a facility is provided for a level of security in ~~hich all caregivers authorized to view any patient data may pull a chart. but must always enter a reason for pulling the chart. Still another facility provided in a preferred embodiment allo- s a preferred provider, someone who is defined as being in the preferred ~ provider's group. or someone on a list of referrals from the preferred provider to have access to some or all of the patient information. The preferred embodiment also provides a feature CA 0224791~ 1998-08-28 W O 97/32271 PCTrUS97/032S7 whereby a pref'erred provider may have sul'ficient p~ivileges to o~ elTide a privacy status, such as one that may have been set by another caregiver.
If it is determined that full access is allowed, the entire chart is accessible for display to the caregiver. ~n a preferred embodiment, a patient face sheet screen of data is displayed first. If the caregiver is not deterrnined to have full access, the parts or the chart for which access is allowable are ~ecescihle for display to the caregiver. In some instances, the caregiver may only have available patient name, address, and billing iniormation; in others, some laboratory or ex~minz~tion results but not doctors' comments may be accessible.
It should be recognized that the processing described above in connection with figure 3 may be implemented in various ways. In one embodiment, access levels, encounters and contacts are referenced and maintained using rows of tables or similar conven~ional data structures. It should also be recognized that numerous variations on the processing described in connection w-ith figure 3 could also be used.
In a preferred embodiment, the pull chart component 201 may be seiected as a user interface button and menu choice from a variety of display screens on a user computer, e.g., 112. It should be recognized that numerous other ways of implementing the pull chart component ~01 could also be used, or instance a dedicated key on a keyboard.
In operation, a caregiver who is a doctor may use system 100 by opening patient encounters for all of the patients who are scheduled to be examined on the doctor's upcoming rounds. The doctor may choose to close these encounters one by one as patients are e7c~min~rl, or may leave all of hem open until the doctor's rounds are completed and the doctor can enter further comments and notes for each of the patients examined during the rounds. IJsed in this manner, system 100 allows a doctor to be called away from one patient to care for another for a brief period of time, and then to return to the first patient without having to first close the first patient encounter, open the second patient encounter, close it. and then start a new encounter for the first patient again.
In a preferred embodiment, users may lock their computers, e.g., 112, by a keystroke sequence to ensure that no passers-by attempt to review patient information while the user is away from the computer. If a chart has been pulled by a caregiver who subsequently locks his CA 022479l~ l998-08-28 W O 97/32271 PCT~US97/03257 or her computer~ a new pull chart process is initiated ~vhen the compuier is again unlocked. In sLIch a situatiom the user is returned to the portion of the ch~rt th~t ~ as bein;, viewed ~vhen the computer ~ as locked. In some instances. a particular computer may be locked by one caregiver and unlocked by another. ~f the new caregiver is not authorized with respect to that chart, it is not displayed. If the new caregiver is authorized, the chart is pulled for the new caregiver.
In some instances, a caregiver r~ay open one patient chart ~vithout closing another first. As a result, a chart may not appear on any caregiver's computer screen, but will still remain open in the sense that it ~vas never signed. This will also happen when a caregiver exits one or more of the programs used in implementing system 100. or when system 100 stops operating due to a compu~er system crash while a patent contact is in process. To account for such possible situations, patient workflow su~system 105 m~int~lin~ a record of all such open patient charts, and provides each caregiver with an indication of all open patient charts for which that caregiver remains responsible. The number of open encounters for a caregiver is indicated on the caregiver's computer, e.g., 110. In one embodiment, this is achieved by using a numeral next to an icon repros-on~ing stack of open patient charts. rt should be recognized that numerous other user interfaces could be used to provide caregivers with visual or other indication of the encounters they currently have open.
In a preferred embodiment, there is no limit to the number of caregivers who can pull a patient's chart. Each request to open a patient chart starts a patient contact with the chart status set to that of a readable copy, as discussed below. A caregiver's access to patient summary and contact informa~ion is restricted only by the security controls discussed herein.
Even if a caregiver is denied access to a chart because it is being updated, the caregiver still has access to information for that patient from previous encounters.
Once a caregiver requests access to patient contact information, chart management component 202 is automatical~y invoked.
Turning now to chart management component 202, once a caregiver pulls a patient's chart, chart management component 202 monitors the status of that chart. This component keeps track of whether contact data have been recorded for this contact and which caregiver, CA 022479l~ l998-08-28 W O 97/32271 PCT~US97/03257 if anv~ is in the process or recordin2 contact data. This component also man;1C~es con~rol of which caregiver can update the patient contact data and how the chart ma~ lae ~ d once the contact is complete.
In a prefelTed embodiment, the overall status of a chart is tracl;ed by characterizing a copy of the chart as being in one of three modes. A readable copy ot a char~ is one in which the carcgiver has not entered contact data, for inct~nCe entering data on a patient s-lmmary screen. ~ writeable copv of a chart is one in which a caregiver has entered contac~ data, such as by entering data usin2 a patient contact screen. A locked copy of a chart is one in which contact data is currently being entered by a caregiver, thus locking other caregivers out of access to the patient contact screens.
If a caregiver has a readable copy of a patient's chart, the caregiver can file the chart without being required to save an H&P report even if contact data have been en~ered for the encounter by another caregiver. For example, nurse can pull a chart, update demo~raphic information and file the chart imm~ .ly even though physical examination recordings are being simultaneouslv recorded by another caregiver.
If a care~iver has a writeable copy of a patient's chart~ the caregiver can file the chart but first is required to save an H~P report for that encounter, because contact data have been entered. When a second caregiver takes over a writeable copy from another caregiver, system 100 displays a message asking the second caregiver if he or she wants to ta~;e over the chart fiom the first caregiver. If so, then the writeable copy is transferred to the second caregiver and becomes a loclied copy. Thus, for example, a first caregiver may record contact data and then movc to a summary screen before transferring a chart to a second care~Jiver. Upon receiving the chart, the second caregiver moves to a contact data screen and thereby causes the chart to become a locked copy.
As suggested earlier, when a contact is in read only mode and no data have been recorded for the contact. the patient's chart can be filed from any user's computer. e.g., 114, without being signed. This permits a caregiver to open a patient's chart to review and update demographics and patient summary information without interrupting another caregiver who may be recording contact information for a patient encounter. For example. a nurse operating CA 0224791~ 1998-08-28 nurse's comp-ller I 1~ ha~ the ability to update test re~sult information lor a pa~ien~ ~ hile a physici.ln operating docror's computer 11(? continues to report tïndin~s tlom an ongoin~
physical examination.
When contact data have already been recorded, the chart will not be removed from a caregiver's computer display until it is signed (by saving an H&P report as earlier described) or sent {o another caregiver. This ensures that the patient's H&P report ~vili be re- ie- ed before the patient's chart is closed, thus helping to maintain the integritv between the con~act data recorded during an encounter and the final ~I&P report summ~ri7ing the encounter.
The update mode indicates that information for a contact is being recorded b~ a caregiver. All other carevivers who attempt to pull the patient's chart are restricted from entering contact data~ and as a further reminder a unique identifier~ for instance the phrase "(IN USE)." is displayed next to the patient's name in the overall listing of patients for whom charts are available. This ensures that the integrity of the informa~ion entered during each contact is maintained, and allows system 100 to ensure that when each caregiver is e.Y~mining patient contact information. the system can display the most up-to-date information on which decisions can be made.
The send chart component 203 permits one caregiver to send a message to another concerning a particular patient. and to attach the patient's chart to that message. The recipient of the chart message must be an authorized caregiver and must have authorization ~o pull the patient's chart. as well as have the requisite access to see the patient summary or pa~ient contact informa~ion to which the message may pertain.
When a caregiver invokes the send chart component 203, that caregiver's contact w ith that patient ends. the patient's chart is filed from that caregiver's computer, and the patient name is remo-ed from a display of pulled charts on the caregiver's computer.
Sending a chart from one caregiver to another does not end the current patient encounter. This provides a mechanism for a caregiver to transfer a patient's chart to another caregiver to facilitate the recording of additional contact data during an encounter.
In order to keep track of such charts, for instance to make sure that the encounter ultimately _ets saved. a message is created when a chart is sent from one caregiver ~o another, CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97/032S7 and the message and the corresponding pa~ient s chart are .n~,sociated ~vith one another. The new caregiver is presented with the message and is reqLIired to pull the chart.
If the caregiver is sent a writeable copy of a chart. the caregiver is called upon to either pull the patient's chart or forward it to another caregi~!er. Conventional logic is used to prevent a caregiver from removing the message until the chart is pulled. Conventional logic also checks to determine whether the target caregiver has permission to view the chart to be sent; if not, the re~uest to send the chart to that caregiver is denied.
The file chart component 204 is used to end a patient contact and save a patient encounter. Whether an H&P report must be saved when a chart is filed depends upon whether contact data was entered during the encounter. If no contact data has been recorded during a contact. the patient's chart can be fïled (i.e., the contact ended and the encounter closed) without saving an H&P report. When contact data have been recorded during that contact, executing the file chart component 204 will open a displav window allowing the caregiver to produce an H&P report. If the caregiver has the proper level of security clearance, the caregi~er can save the H&P report ~thereby ending the contact and closing the encounter) and file the patient's chart from the caregiver's computer. If the caregiver does not have sufficient securitv clearance, the caregiver can end a contact by using the send chart component to transfer the chart to a caregiver who has the autholity to save the H&P report.
When an encounter has only one contact, filing the patient's chart (thereby ending the contact) also serves to end the current encounter.
Whenever a chart is filed, either along with saving an encounter or not, the patient's name is removed from the display of open charts on the caregiver's computer.
A patient's chart that is open on one caregiver's computer, e.g., 100, may simultaneously be opened on another caregiver's computer, e.g., 112, after the first caregiver has sa~ ed the H&P report for that patient encounter. Thus, a physician may complete work on a patient encounter but the contact may remain open so that a nurse may continue to update patient information such as lab results. The nurse is provided with access to such patient summary data but not to patient data relating to the concluded encounter. Once the nurse's CA 0224791~ 1998-08-28 W O 97/32271 PC~rUS97/03257 wor~ is complete, the nu}se files the patient chart (i.e., ends the contact), without the need for any further H&P report.
In a preferred embodiment, a cancel contact user interface selection is also available to a caregiver. When executed, the cancel contact selection deletes the various data structures created as a result of the current contact, and all other entries corresponding to that contact are deleted.
A caregiver re~uest to switch from display of a first chart to display of a second chart is implemented by relinquishing control of the first chart so that it is available for use by other caregivers, if such caregiver had control of the first chart to begin with; ending the contact corresponding to the first chart, and invoking the pull chart component 201 to obtain access to the second hart.
From the above description, it will be apparent that the invention disclosed herein provides a novel and advantageous medical record management system and process with workflow management features. The foregoing discussion discloses and describes merely exemplary methods and embodiments of the present invention. As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or ess~nti~l characteristics thereof. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limi~ing, of the scope of the invention which is set forth in the following claims.
CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97/03257 ~ . Onlv one care~iver at a time is allowed to updale patient conmcI d.1~a. Any attempt bv one care~iver to update a contact being updated by ~nolhcr results in a message that the conIact is already in the process of being updated.
6. ~'hen one caregiver begins to record patient contact data after ;Inother caregiver has recorded patient contacI data for a new contact during the same encounter7 a user interface messa_e asks the new caregiver whether that caregiver wants IO assume control of the patient's chart. Bv keeping track of chart "ownership," all caregivers know ~ ho is responsible for any particular chart at any particular time.
7. Data from a contact are saved in patient record database 102 whenever a user navigates from one type of contact data ~e.g., vital signs~ to another (e.g., chief complaint), sends the patienI s chart to another caregiver, Iocks the system (indicating that the user will be awav from the user's computer, c~.g., 1 12, for some period of time)~ e,Yits the pro_ram, or views another pa~ient's chart.
8. A contact is considered to be complete whenever the caregiver "files" the patient's chart in patient record ~l~t~h~e 102, sends the patient's hart to another caregiver, locks the svstem. exits the program, or views another patient's chart.
9. An encounter is considered complete when the patient's chart is "sioned." A
chart is signed in svstem 100 by a doctor saving in patient record database 10' a file providin~ a History and Physical (H&P) report for the encounter. Whenever cont;3ct data have been recorded during an encounter, system 100 requires that the patient's chart be so signed. Ii no contact data have been entered, such as when a chart is opened for administrative updates or laboratorv review. the patient's chart can be filed without saving the ~&P report.
10. In a preferred embodiment, until an encounter is saved, all data or that encounter may be modified. Some applications may have data inlegrity requirements that preclude modification of any data once entered, and an alternate embodiment for use with such an application does not allow such modification of data.
In a preferred embodiment, components 201-204 are implemented by software programs operatin~g as described herein. It should be recognized that other implementations, CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97103257 such as dedicated circLlitrv. could alsv be used to implemenl some or all of tlle ~unctions o~
components ~01-70~.
Pull Charl component 201 manages u.sers' ability to pull patient ch~rts tbaseci on t patienl privacv iniormation and based upon application security levels of a particular caregiver.
Referring now also to figure 3~ when a user of system 100 requests to see a patient chart, processing is initiated 301 for pull chart component 201. Firstt a checlc 30' is made to see whether the caregiver is authorized to have any chart access. If so~ a check 303 is made to see whether the caregiver is authorized user of system 100. If either check is ne~ative, an access denial message is displayed and the pull chart component 201 terminates. Otherwise, a check 305 is made to see ~vhether an encounler is already in process for the palient. If not, an encounter is started 306.
In either event, a check 307 is then made to see whether a chart is alreadv open on the caregiver's computer, e.g., 110, for this encounter. If not, a chart is opened and added 308 to a list of pulled charts for that caregiver. A contact is then started 309. A determination 310 is made as to the caregiver's security level, and the parts of the patient chart for which access is allowed arc then made available for display 311. At this point the pull chart component 201 is complete 3 1 ' .
In some instances. a patient may have a particular sensitivity to privacy and there may be specific information on which caregivers are authorized to review particular portions of the patient's record. In other cases, there may be no specific privacy instructions, in ~ hich case the inquiry ~vill simply be ~vhether the caregiver requesting to pull the chart is authorized to view any patients charts. Also in a preferred embodiment~ a facility is provided for a level of security in ~~hich all caregivers authorized to view any patient data may pull a chart. but must always enter a reason for pulling the chart. Still another facility provided in a preferred embodiment allo- s a preferred provider, someone who is defined as being in the preferred ~ provider's group. or someone on a list of referrals from the preferred provider to have access to some or all of the patient information. The preferred embodiment also provides a feature CA 0224791~ 1998-08-28 W O 97/32271 PCTrUS97/032S7 whereby a pref'erred provider may have sul'ficient p~ivileges to o~ elTide a privacy status, such as one that may have been set by another caregiver.
If it is determined that full access is allowed, the entire chart is accessible for display to the caregiver. ~n a preferred embodiment, a patient face sheet screen of data is displayed first. If the caregiver is not deterrnined to have full access, the parts or the chart for which access is allowable are ~ecescihle for display to the caregiver. In some instances, the caregiver may only have available patient name, address, and billing iniormation; in others, some laboratory or ex~minz~tion results but not doctors' comments may be accessible.
It should be recognized that the processing described above in connection with figure 3 may be implemented in various ways. In one embodiment, access levels, encounters and contacts are referenced and maintained using rows of tables or similar conven~ional data structures. It should also be recognized that numerous variations on the processing described in connection w-ith figure 3 could also be used.
In a preferred embodiment, the pull chart component 201 may be seiected as a user interface button and menu choice from a variety of display screens on a user computer, e.g., 112. It should be recognized that numerous other ways of implementing the pull chart component ~01 could also be used, or instance a dedicated key on a keyboard.
In operation, a caregiver who is a doctor may use system 100 by opening patient encounters for all of the patients who are scheduled to be examined on the doctor's upcoming rounds. The doctor may choose to close these encounters one by one as patients are e7c~min~rl, or may leave all of hem open until the doctor's rounds are completed and the doctor can enter further comments and notes for each of the patients examined during the rounds. IJsed in this manner, system 100 allows a doctor to be called away from one patient to care for another for a brief period of time, and then to return to the first patient without having to first close the first patient encounter, open the second patient encounter, close it. and then start a new encounter for the first patient again.
In a preferred embodiment, users may lock their computers, e.g., 112, by a keystroke sequence to ensure that no passers-by attempt to review patient information while the user is away from the computer. If a chart has been pulled by a caregiver who subsequently locks his CA 022479l~ l998-08-28 W O 97/32271 PCT~US97/03257 or her computer~ a new pull chart process is initiated ~vhen the compuier is again unlocked. In sLIch a situatiom the user is returned to the portion of the ch~rt th~t ~ as bein;, viewed ~vhen the computer ~ as locked. In some instances. a particular computer may be locked by one caregiver and unlocked by another. ~f the new caregiver is not authorized with respect to that chart, it is not displayed. If the new caregiver is authorized, the chart is pulled for the new caregiver.
In some instances, a caregiver r~ay open one patient chart ~vithout closing another first. As a result, a chart may not appear on any caregiver's computer screen, but will still remain open in the sense that it ~vas never signed. This will also happen when a caregiver exits one or more of the programs used in implementing system 100. or when system 100 stops operating due to a compu~er system crash while a patent contact is in process. To account for such possible situations, patient workflow su~system 105 m~int~lin~ a record of all such open patient charts, and provides each caregiver with an indication of all open patient charts for which that caregiver remains responsible. The number of open encounters for a caregiver is indicated on the caregiver's computer, e.g., 110. In one embodiment, this is achieved by using a numeral next to an icon repros-on~ing stack of open patient charts. rt should be recognized that numerous other user interfaces could be used to provide caregivers with visual or other indication of the encounters they currently have open.
In a preferred embodiment, there is no limit to the number of caregivers who can pull a patient's chart. Each request to open a patient chart starts a patient contact with the chart status set to that of a readable copy, as discussed below. A caregiver's access to patient summary and contact informa~ion is restricted only by the security controls discussed herein.
Even if a caregiver is denied access to a chart because it is being updated, the caregiver still has access to information for that patient from previous encounters.
Once a caregiver requests access to patient contact information, chart management component 202 is automatical~y invoked.
Turning now to chart management component 202, once a caregiver pulls a patient's chart, chart management component 202 monitors the status of that chart. This component keeps track of whether contact data have been recorded for this contact and which caregiver, CA 022479l~ l998-08-28 W O 97/32271 PCT~US97/03257 if anv~ is in the process or recordin2 contact data. This component also man;1C~es con~rol of which caregiver can update the patient contact data and how the chart ma~ lae ~ d once the contact is complete.
In a prefelTed embodiment, the overall status of a chart is tracl;ed by characterizing a copy of the chart as being in one of three modes. A readable copy ot a char~ is one in which the carcgiver has not entered contact data, for inct~nCe entering data on a patient s-lmmary screen. ~ writeable copv of a chart is one in which a caregiver has entered contac~ data, such as by entering data usin2 a patient contact screen. A locked copy of a chart is one in which contact data is currently being entered by a caregiver, thus locking other caregivers out of access to the patient contact screens.
If a caregiver has a readable copy of a patient's chart, the caregiver can file the chart without being required to save an H&P report even if contact data have been en~ered for the encounter by another caregiver. For example, nurse can pull a chart, update demo~raphic information and file the chart imm~ .ly even though physical examination recordings are being simultaneouslv recorded by another caregiver.
If a care~iver has a writeable copy of a patient's chart~ the caregiver can file the chart but first is required to save an H~P report for that encounter, because contact data have been entered. When a second caregiver takes over a writeable copy from another caregiver, system 100 displays a message asking the second caregiver if he or she wants to ta~;e over the chart fiom the first caregiver. If so, then the writeable copy is transferred to the second caregiver and becomes a loclied copy. Thus, for example, a first caregiver may record contact data and then movc to a summary screen before transferring a chart to a second care~Jiver. Upon receiving the chart, the second caregiver moves to a contact data screen and thereby causes the chart to become a locked copy.
As suggested earlier, when a contact is in read only mode and no data have been recorded for the contact. the patient's chart can be filed from any user's computer. e.g., 114, without being signed. This permits a caregiver to open a patient's chart to review and update demographics and patient summary information without interrupting another caregiver who may be recording contact information for a patient encounter. For example. a nurse operating CA 0224791~ 1998-08-28 nurse's comp-ller I 1~ ha~ the ability to update test re~sult information lor a pa~ien~ ~ hile a physici.ln operating docror's computer 11(? continues to report tïndin~s tlom an ongoin~
physical examination.
When contact data have already been recorded, the chart will not be removed from a caregiver's computer display until it is signed (by saving an H&P report as earlier described) or sent {o another caregiver. This ensures that the patient's H&P report ~vili be re- ie- ed before the patient's chart is closed, thus helping to maintain the integritv between the con~act data recorded during an encounter and the final ~I&P report summ~ri7ing the encounter.
The update mode indicates that information for a contact is being recorded b~ a caregiver. All other carevivers who attempt to pull the patient's chart are restricted from entering contact data~ and as a further reminder a unique identifier~ for instance the phrase "(IN USE)." is displayed next to the patient's name in the overall listing of patients for whom charts are available. This ensures that the integrity of the informa~ion entered during each contact is maintained, and allows system 100 to ensure that when each caregiver is e.Y~mining patient contact information. the system can display the most up-to-date information on which decisions can be made.
The send chart component 203 permits one caregiver to send a message to another concerning a particular patient. and to attach the patient's chart to that message. The recipient of the chart message must be an authorized caregiver and must have authorization ~o pull the patient's chart. as well as have the requisite access to see the patient summary or pa~ient contact informa~ion to which the message may pertain.
When a caregiver invokes the send chart component 203, that caregiver's contact w ith that patient ends. the patient's chart is filed from that caregiver's computer, and the patient name is remo-ed from a display of pulled charts on the caregiver's computer.
Sending a chart from one caregiver to another does not end the current patient encounter. This provides a mechanism for a caregiver to transfer a patient's chart to another caregiver to facilitate the recording of additional contact data during an encounter.
In order to keep track of such charts, for instance to make sure that the encounter ultimately _ets saved. a message is created when a chart is sent from one caregiver ~o another, CA 0224791~ 1998-08-28 W O 97/32271 PCT~US97/032S7 and the message and the corresponding pa~ient s chart are .n~,sociated ~vith one another. The new caregiver is presented with the message and is reqLIired to pull the chart.
If the caregiver is sent a writeable copy of a chart. the caregiver is called upon to either pull the patient's chart or forward it to another caregi~!er. Conventional logic is used to prevent a caregiver from removing the message until the chart is pulled. Conventional logic also checks to determine whether the target caregiver has permission to view the chart to be sent; if not, the re~uest to send the chart to that caregiver is denied.
The file chart component 204 is used to end a patient contact and save a patient encounter. Whether an H&P report must be saved when a chart is filed depends upon whether contact data was entered during the encounter. If no contact data has been recorded during a contact. the patient's chart can be fïled (i.e., the contact ended and the encounter closed) without saving an H&P report. When contact data have been recorded during that contact, executing the file chart component 204 will open a displav window allowing the caregiver to produce an H&P report. If the caregiver has the proper level of security clearance, the caregi~er can save the H&P report ~thereby ending the contact and closing the encounter) and file the patient's chart from the caregiver's computer. If the caregiver does not have sufficient securitv clearance, the caregiver can end a contact by using the send chart component to transfer the chart to a caregiver who has the autholity to save the H&P report.
When an encounter has only one contact, filing the patient's chart (thereby ending the contact) also serves to end the current encounter.
Whenever a chart is filed, either along with saving an encounter or not, the patient's name is removed from the display of open charts on the caregiver's computer.
A patient's chart that is open on one caregiver's computer, e.g., 100, may simultaneously be opened on another caregiver's computer, e.g., 112, after the first caregiver has sa~ ed the H&P report for that patient encounter. Thus, a physician may complete work on a patient encounter but the contact may remain open so that a nurse may continue to update patient information such as lab results. The nurse is provided with access to such patient summary data but not to patient data relating to the concluded encounter. Once the nurse's CA 0224791~ 1998-08-28 W O 97/32271 PC~rUS97/03257 wor~ is complete, the nu}se files the patient chart (i.e., ends the contact), without the need for any further H&P report.
In a preferred embodiment, a cancel contact user interface selection is also available to a caregiver. When executed, the cancel contact selection deletes the various data structures created as a result of the current contact, and all other entries corresponding to that contact are deleted.
A caregiver re~uest to switch from display of a first chart to display of a second chart is implemented by relinquishing control of the first chart so that it is available for use by other caregivers, if such caregiver had control of the first chart to begin with; ending the contact corresponding to the first chart, and invoking the pull chart component 201 to obtain access to the second hart.
From the above description, it will be apparent that the invention disclosed herein provides a novel and advantageous medical record management system and process with workflow management features. The foregoing discussion discloses and describes merely exemplary methods and embodiments of the present invention. As will be understood by those familiar with the art, the invention may be embodied in other specific forms without departing from the spirit or ess~nti~l characteristics thereof. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limi~ing, of the scope of the invention which is set forth in the following claims.
Claims (18)
1. A patient record system for recording and maintaining medical information for a patient, comprising:
a first caregiver's terminal to allow a first caregiver to access the patient record system;
a second caregiver's terminal to allow a second caregiver to access the patient record system:
a patient record database having patient data, the patient record database being coupled to said first and second caregivers terminals, the patient record database selectively providing access to the patient data from one of the first and second caregiver's terminals responsive to a predetermined set of access rules.
a first caregiver's terminal to allow a first caregiver to access the patient record system;
a second caregiver's terminal to allow a second caregiver to access the patient record system:
a patient record database having patient data, the patient record database being coupled to said first and second caregivers terminals, the patient record database selectively providing access to the patient data from one of the first and second caregiver's terminals responsive to a predetermined set of access rules.
2. A patient record system as in claim 1, wherein the predetermined set of rules includes a rule that access to a predetermined portion of the patient data by the first caregiver is terminated before access to the predetermined portion by the second caregiver is allowed.
3. A patient record system as in claim 1, wherein the predetermined set of rules includes a rule arbitrating access to a portion of the patient data when more than one caregiver seeks access to said portion of the patient data.
4. A patient record system as in claim 3, wherein the rule arbitrating access permits access responsive to the first caregiver having authorization for access to said portion of the patient data and responsive to the portion of data not being accessed by another caregiver.
5. A system as in claim 1, further comprising a patient chart workflow subsystem operatively coupled to said patient record database and said first and second caregiver's terminals, the patient chart workflow subsystem configured to allow the first caregiver to engage in a first patent encounter corresponding to a first patient while engaging in a second patient encounter corresponding to a second patient.
6. A system as in claim 5, wherein the patient chart workflow subsystem is further configured to allow said first caregiver to open a plurality of encounters for a plurality of patients, upon commencing a round of activities.
7. A method of maintaining a patient record, comprising:
providing a first caregiver with a terminal;
providing a second caregiver with a terminal; and selectively permitting the first and second caregivers, using said terminals, to access portions of patient data from a patient record database according to a predetermined set of access rules.
providing a first caregiver with a terminal;
providing a second caregiver with a terminal; and selectively permitting the first and second caregivers, using said terminals, to access portions of patient data from a patient record database according to a predetermined set of access rules.
8. A method as in claim 7, wherein the predetermined set of rules includes a rule that access to the portions of patient data by the first caregiver must be terminated before access to the portions of patient data by the second caregiver is allowed.
9. A method as in claim 7, wherein the predetermined set of rules includes a rule arbitrating access to said portions of the patient data when more than one caregiver seeks access to said portions of the patient data.
10. A method of maintaining patient records, comprising:
providing a first caregiver with a first terminal;
providing a second caregiver with a second terminal;
creating encounter records for a plurality of patients; and selectively permitting the first and second caregivers, using said first and second terminals, to access portions of patient data corresponding to a subset of said plurality of patients from a patient record database according to a predetermined set of access rules.
providing a first caregiver with a first terminal;
providing a second caregiver with a second terminal;
creating encounter records for a plurality of patients; and selectively permitting the first and second caregivers, using said first and second terminals, to access portions of patient data corresponding to a subset of said plurality of patients from a patient record database according to a predetermined set of access rules.
11. A method as in claim 10, wherein said predetermined set of rules includes a rule permitting said first caregiver to access said portions for all of said plurality of patients for whom said first caregiver is authorized, other than ones of said patients for whom said second caregiver is accessing corresponding portions of said patient data.
12. A method as in claim 10, further comprising maintaining the patient record in a locked mode responsive to the first caregiver entering data in said selected portions; said locked mode preventing access to said selected portions by the second caregiver.
13. A method as in claim 10, further comprising maintaining the patient record in a writeable mode permitting said first caregiver to transfer, to said second caregiver, access to said selected portions.
14. A method as in claim 10, further comprising sending a patient record from said first caregiver performing a first type of processing, to said second caregiver performing a second type of processing.
15. A method as in claim 10, further comprising accessing a second record for a second patient while maintaining said patient record as an open patient chart.
16. A method as in claim 10, further comprising maintaining a list of said subset of patients.
17. A method of maintaining a patient record, comprising:
providing a terminal; and selectively permitting a first caregiver and a second caregiver, using said terminal, to access portions of patient data from a patient record database according to a predetermined set of access rules.
providing a terminal; and selectively permitting a first caregiver and a second caregiver, using said terminal, to access portions of patient data from a patient record database according to a predetermined set of access rules.
18. A method as in claim 17, further comprising:
locking said terminal by said first caregiver; and accessing said portions of patient data by said second caregiver responsive to said second caregiver unlocking said terminal and said second caregiver having access privileges to said portions of patient data.
locking said terminal by said first caregiver; and accessing said portions of patient data by said second caregiver responsive to said second caregiver unlocking said terminal and said second caregiver having access privileges to said portions of patient data.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/609,844 US5974389A (en) | 1996-03-01 | 1996-03-01 | Medical record management system and process with improved workflow features |
US08/609844 | 1996-03-01 |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2247915A1 true CA2247915A1 (en) | 1997-09-04 |
Family
ID=24442571
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002247915A Abandoned CA2247915A1 (en) | 1996-03-01 | 1997-03-03 | Medical record management system and process with improved workflow features |
Country Status (6)
Country | Link |
---|---|
US (1) | US5974389A (en) |
EP (1) | EP0883854A1 (en) |
JP (1) | JP2000506291A (en) |
AU (1) | AU732221B2 (en) |
CA (1) | CA2247915A1 (en) |
WO (1) | WO1997032271A1 (en) |
Families Citing this family (191)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6206829B1 (en) | 1996-07-12 | 2001-03-27 | First Opinion Corporation | Computerized medical diagnostic and treatment advice system including network access |
US5660176A (en) | 1993-12-29 | 1997-08-26 | First Opinion Corporation | Computerized medical diagnostic and treatment advice system |
USRE43433E1 (en) | 1993-12-29 | 2012-05-29 | Clinical Decision Support, Llc | Computerized medical diagnostic and treatment advice system |
US5935060A (en) | 1996-07-12 | 1999-08-10 | First Opinion Corporation | Computerized medical diagnostic and treatment advice system including list based processing |
US7076436B1 (en) * | 1996-07-08 | 2006-07-11 | Rlis, Inc. | Medical records, documentation, tracking and order entry system |
IL131873A0 (en) | 1997-03-13 | 2001-03-19 | First Opinion Corp | Disease management system |
US6192345B1 (en) * | 1997-03-21 | 2001-02-20 | Marc Edward Chicorel | Computer keyboard-generated medical progress notes via a coded diagnosis-based language |
AU2110599A (en) * | 1998-01-09 | 1999-07-26 | Millermed Software, Inc. | Computer-based system for automating administrative procedures in a medical office |
US6973434B2 (en) * | 1998-01-09 | 2005-12-06 | Millermed Software, Inc. | Computer-based system for automating administrative procedures in an office |
AU753707B2 (en) * | 1998-09-09 | 2002-10-24 | Yeong Kuang Oon | Automation oriented healthcare delivery system based on medical scripting language |
AUPP577298A0 (en) | 1998-09-09 | 1998-10-01 | Oon, Yeong Kuang Dr | Automation oriented health care delivery system based on medical scripting language |
US7305347B1 (en) | 1998-09-09 | 2007-12-04 | Raymond Anthony Joao | Apparatus and method for providing employee benefits and /or employee benefits information |
US6674449B1 (en) * | 1998-11-25 | 2004-01-06 | Ge Medical Systems Global Technology Company, Llc | Multiple modality interface for imaging systems |
US6603494B1 (en) * | 1998-11-25 | 2003-08-05 | Ge Medical Systems Global Technology Company, Llc | Multiple modality interface for imaging systems including remote services over a network |
US6381576B1 (en) * | 1998-12-16 | 2002-04-30 | Edward Howard Gilbert | Method, apparatus, and data structure for capturing and representing diagnostic, treatment, costs, and outcomes information in a form suitable for effective analysis and health care guidance |
US8073712B2 (en) * | 1999-04-02 | 2011-12-06 | Cybernet Systems Corporation | Method for consolidating medical records through the world wide web |
US6287252B1 (en) | 1999-06-30 | 2001-09-11 | Monitrak | Patient monitor |
WO2001008040A1 (en) * | 1999-07-23 | 2001-02-01 | Pathology Institute Of Middle Georgia | System for labeling and encoding pathology specimens |
US6651107B1 (en) * | 1999-09-21 | 2003-11-18 | Intel Corporation | Reduced hardware network adapter and communication |
US7020618B1 (en) * | 1999-10-25 | 2006-03-28 | Ward Richard E | Method and system for customer service process management |
US8894577B2 (en) * | 1999-11-05 | 2014-11-25 | Elite Care Technologies, Inc. | System and method for medical information monitoring and processing |
US20030177030A1 (en) * | 1999-11-17 | 2003-09-18 | Michael McNeil | Patient information system and method of using same |
US7490048B2 (en) * | 1999-12-18 | 2009-02-10 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US7464040B2 (en) * | 1999-12-18 | 2008-12-09 | Raymond Anthony Joao | Apparatus and method for processing and/or for providing healthcare information and/or healthcare-related information |
US6845448B1 (en) * | 2000-01-07 | 2005-01-18 | Pennar Software Corporation | Online repository for personal information |
US8117644B2 (en) | 2000-01-07 | 2012-02-14 | Pennar Software Corporation | Method and system for online document collaboration |
FR2803931A1 (en) * | 2000-01-19 | 2001-07-20 | Mediavet | Creation and updating of medical records for a pet on a central server that can subsequently be accessed by other vets or later owners over the Internet, thus greatly increasing availability and ease of access to medical records |
US6879959B1 (en) | 2000-01-21 | 2005-04-12 | Quality Care Solutions, Inc. | Method of adjudicating medical claims based on scores that determine medical procedure monetary values |
GB0003197D0 (en) | 2000-02-11 | 2000-04-05 | Aid Medic Ltd | Improvements in and relating to controlling drug delivery |
UA73967C2 (en) * | 2000-02-14 | 2005-10-17 | First Opinion Corp | Structure-based automatic processing for diagnostics (variants) |
US6941271B1 (en) * | 2000-02-15 | 2005-09-06 | James W. Soong | Method for accessing component fields of a patient record by applying access rules determined by the patient |
IL151720A0 (en) * | 2000-03-29 | 2003-04-10 | Univ Virginia | Method, system, and computer program product for the evaluation of glycemic control in diabetes from self-monitoring data |
US7403901B1 (en) | 2000-04-13 | 2008-07-22 | Accenture Llp | Error and load summary reporting in a health care solution environment |
US6701345B1 (en) * | 2000-04-13 | 2004-03-02 | Accenture Llp | Providing a notification when a plurality of users are altering similar data in a health care solution environment |
US20020116227A1 (en) * | 2000-06-19 | 2002-08-22 | Dick Richard S. | Method and apparatus for requesting, retrieving, and obtaining de-identified medical informatiion |
US20010053986A1 (en) * | 2000-06-19 | 2001-12-20 | Dick Richard S. | Method and apparatus for requesting, retrieving, and normalizing medical information |
US8688474B2 (en) * | 2000-06-26 | 2014-04-01 | Epic Systems Corporation | Patient health record access system |
US7337123B2 (en) * | 2000-06-26 | 2008-02-26 | Epic Systems Corporation | Rules based ticketing for self-scheduling of appointments |
US20020016923A1 (en) * | 2000-07-03 | 2002-02-07 | Knaus William A. | Broadband computer-based networked systems for control and management of medical records |
US20020004727A1 (en) * | 2000-07-03 | 2002-01-10 | Knaus William A. | Broadband computer-based networked systems for control and management of medical records |
US7653557B2 (en) * | 2000-07-17 | 2010-01-26 | Sweetser Christine B | Client driven healthcare system and process |
WO2002013047A2 (en) | 2000-08-04 | 2002-02-14 | Athenahealth, Inc. | Practice management and billing automation system |
US7251610B2 (en) * | 2000-09-20 | 2007-07-31 | Epic Systems Corporation | Clinical documentation system for use by multiple caregivers |
US8050944B2 (en) * | 2000-09-20 | 2011-11-01 | Epic Systems Corporation | Intelligent patient visit information management and navigation system |
AU2001277643A1 (en) * | 2000-09-27 | 2002-04-08 | Aventis Pharma (Pty) Ltd | A method of supplying information relating to the care of a patient |
US7533030B2 (en) * | 2000-10-11 | 2009-05-12 | Malik M. Hasan | Method and system for generating personal/individual health records |
JP2004518187A (en) * | 2000-10-11 | 2004-06-17 | ヘルストリオ,インコーポレイテッド | Health management data communication system |
US7428494B2 (en) * | 2000-10-11 | 2008-09-23 | Malik M. Hasan | Method and system for generating personal/individual health records |
US7475020B2 (en) * | 2000-10-11 | 2009-01-06 | Malik M. Hasan | Method and system for generating personal/individual health records |
US7509264B2 (en) * | 2000-10-11 | 2009-03-24 | Malik M. Hasan | Method and system for generating personal/individual health records |
US7440904B2 (en) * | 2000-10-11 | 2008-10-21 | Malik M. Hanson | Method and system for generating personal/individual health records |
US20020055918A1 (en) * | 2000-11-08 | 2002-05-09 | Patrick Hlathein | Operating room resource management system incorporating an interactive, visual method for coordinating multiple, interdependent |
US7734480B2 (en) * | 2000-11-13 | 2010-06-08 | Peter Stangel | Clinical care utilization management system |
US7860729B2 (en) * | 2000-11-13 | 2010-12-28 | Peter Stangel | Clinical care utilization management system |
US6904161B1 (en) | 2000-11-17 | 2005-06-07 | Siemens Medical Solutions Usa | Workflow configuration and execution in medical imaging |
US20020120472A1 (en) * | 2000-12-22 | 2002-08-29 | Dvorak Carl D. | System and method for integration of health care records |
US7275220B2 (en) | 2000-12-22 | 2007-09-25 | Epic Systems Corporation | System and method for a seamless user interface for an integrated electronic health care information system |
US6983423B2 (en) * | 2000-12-22 | 2006-01-03 | Epic Systems Corporation | Electronic system for collecting and communicating clinical order information in an acute care setting |
US20020082868A1 (en) * | 2000-12-27 | 2002-06-27 | Pories Walter J. | Systems, methods and computer program products for creating and maintaining electronic medical records |
US7921123B2 (en) * | 2001-02-20 | 2011-04-05 | Hartford Fire Insurance Company | Method and system for processing physician claims over a network |
US20020138746A1 (en) * | 2001-03-23 | 2002-09-26 | Mark Buttner | Method of generating a secure output file |
US20020138636A1 (en) * | 2001-03-23 | 2002-09-26 | Mark Buttner | Method for automatically mass generating personalized data report outputs |
US7181017B1 (en) | 2001-03-23 | 2007-02-20 | David Felsher | System and method for secure three-party communications |
US20090024417A1 (en) * | 2001-03-26 | 2009-01-22 | Marks Richard D | Electronic medical record system |
US6684276B2 (en) | 2001-03-28 | 2004-01-27 | Thomas M. Walker | Patient encounter electronic medical record system, method, and computer product |
US7120646B2 (en) * | 2001-04-09 | 2006-10-10 | Health Language, Inc. | Method and system for interfacing with a multi-level data structure |
US20020188466A1 (en) * | 2001-04-18 | 2002-12-12 | Barrette Pierre Philip | Secure digital medical intellectual property (IP) distribution, market applications, and mobile devices |
US20020165732A1 (en) * | 2001-05-02 | 2002-11-07 | Matchmd, Llc | System and method for automated and interactive scheduling |
US20020165898A1 (en) * | 2001-05-03 | 2002-11-07 | Joe Duffy | Recipient-determined method for sharing tasks in an advanced electronic messaging/workflow system |
WO2002095653A2 (en) * | 2001-05-18 | 2002-11-28 | Mayo Foundation For Medical Education And Research | Ultrasound laboratory information management system and method |
US20020188473A1 (en) * | 2001-06-12 | 2002-12-12 | Jackson W. Charles | Method and system for healthcare management |
US20030018496A1 (en) * | 2001-06-29 | 2003-01-23 | Siemens Medical Solutions Health Services Corporation | System and user interface for use in billing for services and goods |
US6643493B2 (en) | 2001-07-19 | 2003-11-04 | Kevin P. Kilgore | Apparatus and method for registering students and evaluating their performance |
US20030061073A1 (en) * | 2001-08-01 | 2003-03-27 | Khiang Seow | Method and system for displaying patient information |
US7406424B2 (en) * | 2001-08-29 | 2008-07-29 | Hewlett-Packard Development Company, L.P. | Migration of a workflow system to changed process definitions |
US20030154110A1 (en) * | 2001-11-20 | 2003-08-14 | Ervin Walter | Method and apparatus for wireless access to a health care information system |
US20030130872A1 (en) * | 2001-11-27 | 2003-07-10 | Carl Dvorak | Methods and apparatus for managing and using inpatient healthcare information |
US20030115084A1 (en) * | 2001-12-19 | 2003-06-19 | Research Foundation Of State University Of New York | System and method for electronic medical record keeping |
US20030120527A1 (en) * | 2001-12-26 | 2003-06-26 | Andres Palomo | Computer-implemented system and method for productivity enhancement |
US7299465B2 (en) * | 2002-01-08 | 2007-11-20 | International Business Machines Corporation | Configurable application integrating service request and fulfillment process |
US8271202B1 (en) | 2002-02-11 | 2012-09-18 | Fernandez Dennis S | Modified host bio-data management |
US6996558B2 (en) | 2002-02-26 | 2006-02-07 | International Business Machines Corporation | Application portability and extensibility through database schema and query abstraction |
US7580831B2 (en) | 2002-03-05 | 2009-08-25 | Siemens Medical Solutions Health Services Corporation | Dynamic dictionary and term repository system |
US20030233252A1 (en) * | 2002-03-06 | 2003-12-18 | Haskell Robert Emmons | System and method for providing a generic health care data repository |
US20030216945A1 (en) * | 2002-03-25 | 2003-11-20 | Dvorak Carl D. | Method for analyzing orders and automatically reacting to them with appropriate responses |
US20030220815A1 (en) * | 2002-03-25 | 2003-11-27 | Cathy Chang | System and method of automatically determining and displaying tasks to healthcare providers in a care-giving setting |
US20030191669A1 (en) * | 2002-04-09 | 2003-10-09 | Fitzgerald David | System for providing consumer access to healthcare related information |
US7797172B2 (en) * | 2002-04-16 | 2010-09-14 | Siemens Medical Solutions Usa, Inc. | Healthcare financial data and clinical information processing system |
US20030220816A1 (en) * | 2002-04-30 | 2003-11-27 | Andy Giesler | System and method for managing interactions between machine-generated and user-defined patient lists |
US7080098B2 (en) * | 2002-05-02 | 2006-07-18 | Smirniotopoulos James G | Medical multimedia database system |
US20030212576A1 (en) * | 2002-05-08 | 2003-11-13 | Back Kim | Medical information system |
US7865371B2 (en) * | 2002-05-10 | 2011-01-04 | Shen Michael Y | Management of information flow and workflow in medical imaging services |
US20050131738A1 (en) * | 2002-05-15 | 2005-06-16 | Morris Tommy J. | System and method for handling medical information |
EP1512102A4 (en) | 2002-05-15 | 2010-03-17 | Us Gov Sec Army | System and method for handling medical information |
US20030220817A1 (en) * | 2002-05-15 | 2003-11-27 | Steve Larsen | System and method of formulating appropriate subsets of information from a patient's computer-based medical record for release to various requesting entities |
US20040010465A1 (en) * | 2002-05-20 | 2004-01-15 | Cliff Michalski | Method and apparatus for exception based payment posting |
US20040010422A1 (en) * | 2002-05-20 | 2004-01-15 | Cliff Michalski | Method and apparatus for batch-processed invoicing |
US20040006495A1 (en) * | 2002-07-02 | 2004-01-08 | Jda Ehealth Systems, Inc. | Letter communication method, an apparatus, and a computer program product for a healthcare provider to effectively expedite reimbursement process from a patient |
US7979294B2 (en) | 2002-07-31 | 2011-07-12 | Epic Systems Corporation | System and method for providing decision support to appointment schedulers in a healthcare setting |
US20040172520A1 (en) * | 2002-09-19 | 2004-09-02 | Michael Smit | Methods and apparatus for visually creating complex expressions that inform a rules-based system of clinical decision support |
US20040267703A1 (en) * | 2002-10-02 | 2004-12-30 | Board Of Regents, The University Of Texas System | System and method for accessing medical records |
US7890341B2 (en) * | 2002-12-09 | 2011-02-15 | Baxter International Inc. | System and a method for providing integrated access management for peritoneal dialysis and hemodialysis |
US20040111293A1 (en) * | 2002-12-09 | 2004-06-10 | Catherine Firanek | System and a method for tracking patients undergoing treatment and/or therapy for renal disease |
US20040128268A1 (en) * | 2002-12-26 | 2004-07-01 | Anuthep Benja-Athon | Best American healthcare system |
US9818136B1 (en) | 2003-02-05 | 2017-11-14 | Steven M. Hoffberg | System and method for determining contingent relevance |
US20040172307A1 (en) * | 2003-02-06 | 2004-09-02 | Gruber Martin A. | Electronic medical record method |
US20050165627A1 (en) * | 2003-03-10 | 2005-07-28 | Medem, Inc. | Electronic personal health record system |
US8090590B2 (en) * | 2003-03-10 | 2012-01-03 | Intuit Inc. | Electronic personal health record system |
US8041579B2 (en) * | 2003-03-10 | 2011-10-18 | Intuit Inc. | Method, system and article of manufacture, such as a card, to provide user selectable medical information and information to obtain eligibility of healthcare payments |
US20040186746A1 (en) * | 2003-03-21 | 2004-09-23 | Angst Wendy P. | System, apparatus and method for storage and transportation of personal health records |
US7780595B2 (en) | 2003-05-15 | 2010-08-24 | Clinical Decision Support, Llc | Panel diagnostic method and system |
US7399205B2 (en) | 2003-08-21 | 2008-07-15 | Hill-Rom Services, Inc. | Plug and receptacle having wired and wireless coupling |
US7899843B2 (en) * | 2003-09-19 | 2011-03-01 | International Business Machines Corporation | Expanding the scope of an annotation to an entity level |
US7577988B2 (en) * | 2003-10-07 | 2009-08-18 | Sentillion, Inc. | Methods and apparatus for facilitating execution of context sharing applications in an environment with a less than fully enabled context manager |
US8029454B2 (en) | 2003-11-05 | 2011-10-04 | Baxter International Inc. | High convection home hemodialysis/hemofiltration and sorbent system |
US7900133B2 (en) | 2003-12-09 | 2011-03-01 | International Business Machines Corporation | Annotation structure type determination |
US7840416B2 (en) * | 2003-12-23 | 2010-11-23 | ProVation Medical Inc. | Naturally expressed medical procedure descriptions generated via synchronized diagrams and menus |
US8090599B2 (en) | 2003-12-30 | 2012-01-03 | Hartford Fire Insurance Company | Method and system for computerized insurance underwriting |
US7783505B2 (en) | 2003-12-30 | 2010-08-24 | Hartford Fire Insurance Company | System and method for computerized insurance rating |
US20060080140A1 (en) * | 2004-02-09 | 2006-04-13 | Epic Systems Corporation | System and method for providing a clinical summary of patient information in various health care settings |
US7949545B1 (en) | 2004-05-03 | 2011-05-24 | The Medical RecordBank, Inc. | Method and apparatus for providing a centralized medical record system |
US7761463B2 (en) * | 2004-05-20 | 2010-07-20 | The United States Of America As Represented By The Secretary Of The Army | Self-serve patient check-in and preventive services kiosk |
US20080162496A1 (en) * | 2004-06-02 | 2008-07-03 | Richard Postrel | System and method for centralized management and monitoring of healthcare services |
US20060064320A1 (en) * | 2004-06-02 | 2006-03-23 | Richard Postrel | System and method for centralized management and monitoring of healthcare services |
US20060004605A1 (en) * | 2004-06-21 | 2006-01-05 | Epic Systems Corporation | System and method for a comprehensive interactive graphical representation of a health care facility for managing patient care and health care facility resources |
US20050283387A1 (en) * | 2004-06-21 | 2005-12-22 | Epic Systems Corporation | System for providing an interactive anatomical graphical representation of a body for use in a health care environment |
US20060004588A1 (en) * | 2004-06-30 | 2006-01-05 | Mohan Ananda | Method and system for obtaining, maintaining and distributing data |
US7852208B2 (en) | 2004-08-02 | 2010-12-14 | Hill-Rom Services, Inc. | Wireless bed connectivity |
US7319386B2 (en) | 2004-08-02 | 2008-01-15 | Hill-Rom Services, Inc. | Configurable system for alerting caregivers |
US20060053034A1 (en) * | 2004-09-08 | 2006-03-09 | Epic Systems Corporation | System and method for providing a real-time status for managing encounters in health care settings |
US20060085381A1 (en) * | 2004-10-20 | 2006-04-20 | Epic Systems Corporation | Remote deployment access system and method |
US9081879B2 (en) | 2004-10-22 | 2015-07-14 | Clinical Decision Support, Llc | Matrix interface for medical diagnostic and treatment advice system and method |
US20060136265A1 (en) * | 2004-12-21 | 2006-06-22 | Summers Jennifer R | System and method for managing restorative care |
US7443303B2 (en) | 2005-01-10 | 2008-10-28 | Hill-Rom Services, Inc. | System and method for managing workflow |
US8140370B2 (en) * | 2005-01-20 | 2012-03-20 | Epic Systems Corporation | System and method for reducing the steps involved in searching for available appointment times and scheduling appointments in a health care environment |
US20110145018A1 (en) * | 2005-03-21 | 2011-06-16 | Fotsch Edward J | Drug and medical device safety and support information reporting system, processing device and method |
US20060212312A1 (en) * | 2005-03-21 | 2006-09-21 | Medem, Inc. | Healthcare notification system |
US8401871B2 (en) * | 2005-03-21 | 2013-03-19 | Pnc Bank, National Association | Healthcare notification method and system including a healthcare website |
US20080306768A1 (en) * | 2005-03-21 | 2008-12-11 | Medem, Inc. | Healthcare Notification Method And System Including A Healthcare Website |
US20060293925A1 (en) * | 2005-06-22 | 2006-12-28 | Leonard Flom | System for storing medical records accessed using patient biometrics |
US20070038628A1 (en) * | 2005-08-12 | 2007-02-15 | Quixam, Llc | System and method for exchanging documents |
US8666759B2 (en) * | 2005-08-12 | 2014-03-04 | Quixam, Llc | System and method for exchanging documents |
US8874477B2 (en) | 2005-10-04 | 2014-10-28 | Steven Mark Hoffberg | Multifactorial optimization system and method |
US20070136090A1 (en) * | 2005-12-12 | 2007-06-14 | General Electric Company | System and method for macro-enhanced clinical workflow |
US20070294114A1 (en) * | 2005-12-14 | 2007-12-20 | Healthunity Corporation | Record sharing privacy system and method |
RU2477078C2 (en) * | 2006-01-05 | 2013-03-10 | Юниверсити Оф Вирджиния Пэйтент Фаундейшн | Method, system and software product for estimating changeability of glucose content in blood in case of diabetes by self-control data |
DE102006017839A1 (en) * | 2006-04-18 | 2007-10-25 | Siemens Ag | Method for monitoring in an image-based clinical study |
US20070276197A1 (en) * | 2006-05-24 | 2007-11-29 | Lifescan, Inc. | Systems and methods for providing individualized disease management |
US20100179852A1 (en) * | 2006-08-11 | 2010-07-15 | Frank Morito Tomizuka | EMR Template for Workflow Management and Workflow Information Capture |
US7644068B2 (en) * | 2006-10-06 | 2010-01-05 | International Business Machines Corporation | Selecting records from a list with privacy protections |
US20080154513A1 (en) * | 2006-12-21 | 2008-06-26 | University Of Virginia Patent Foundation | Systems, Methods and Computer Program Codes for Recognition of Patterns of Hyperglycemia and Hypoglycemia, Increased Glucose Variability, and Ineffective Self-Monitoring in Diabetes |
US20080177576A1 (en) * | 2007-01-18 | 2008-07-24 | Tom Jennings | System and method for interactive integration of electronic medical health records |
US20080235053A1 (en) * | 2007-03-20 | 2008-09-25 | Pinaki Ray | Communication medium for diabetes management |
US20080234943A1 (en) * | 2007-03-20 | 2008-09-25 | Pinaki Ray | Computer program for diabetes management |
US8758245B2 (en) * | 2007-03-20 | 2014-06-24 | Lifescan, Inc. | Systems and methods for pattern recognition in diabetes management |
US20090156947A1 (en) * | 2007-05-22 | 2009-06-18 | Seward James B | Knowledgebased image informatics system and method |
US9721315B2 (en) | 2007-07-13 | 2017-08-01 | Cerner Innovation, Inc. | Claim processing validation system |
US7868740B2 (en) | 2007-08-29 | 2011-01-11 | Hill-Rom Services, Inc. | Association of support surfaces and beds |
US8461968B2 (en) | 2007-08-29 | 2013-06-11 | Hill-Rom Services, Inc. | Mattress for a hospital bed for use in a healthcare facility and management of same |
US8082160B2 (en) | 2007-10-26 | 2011-12-20 | Hill-Rom Services, Inc. | System and method for collection and communication of data from multiple patient care devices |
US10438694B2 (en) * | 2007-11-19 | 2019-10-08 | Medicalis Corporation | Management of medical workflow |
US20090138282A1 (en) * | 2007-11-28 | 2009-05-28 | Chuck Lee | System and Method for Tracking and Maintaining Vascular Access Medical Records |
US8046625B2 (en) | 2008-02-22 | 2011-10-25 | Hill-Rom Services, Inc. | Distributed fault tolerant architecture for a healthcare communication system |
US20090240127A1 (en) * | 2008-03-20 | 2009-09-24 | Lifescan, Inc. | Methods of determining pre or post meal time slots or intervals in diabetes management |
US8799010B2 (en) * | 2008-05-07 | 2014-08-05 | Unitedhealth Group Incorporated | Telehealth scheduling and communications network |
FR2926152A1 (en) * | 2009-01-13 | 2009-07-10 | Cie Des Animaux Sa | Medical record constituting and updating system for treating e.g. cat, has comparison units comparing code of medical record contained in database with code of animal transmitted by carrier to provide access to database if codes are same |
US20110029592A1 (en) * | 2009-07-28 | 2011-02-03 | Galen Heathcare Solutions Inc. | Computerized method of organizing and distributing electronic healthcare record data |
US20110141116A1 (en) | 2009-12-16 | 2011-06-16 | Baxter International Inc. | Methods and apparatus for displaying flow rate graphs and alarms on a dialysis system |
US8779924B2 (en) | 2010-02-19 | 2014-07-15 | Hill-Rom Services, Inc. | Nurse call system with additional status board |
US20120030122A1 (en) * | 2010-07-27 | 2012-02-02 | Sap Ag | Agile workflow modeling and execution based on document |
US10511609B2 (en) * | 2010-09-15 | 2019-12-17 | Core Mobile Networks, Inc. | Context-based analytics and intelligence |
US9411934B2 (en) | 2012-05-08 | 2016-08-09 | Hill-Rom Services, Inc. | In-room alarm configuration of nurse call system |
US10318923B1 (en) | 2012-08-01 | 2019-06-11 | Cognizant Trizetto Software Group, Inc. | Payment assurance and claim pre-validation |
US9314159B2 (en) | 2012-09-24 | 2016-04-19 | Physio-Control, Inc. | Patient monitoring device with remote alert |
US10383580B2 (en) | 2012-12-31 | 2019-08-20 | Abbott Diabetes Care Inc. | Analysis of glucose median, variability, and hypoglycemia risk for therapy guidance |
US9351670B2 (en) | 2012-12-31 | 2016-05-31 | Abbott Diabetes Care Inc. | Glycemic risk determination based on variability of glucose levels |
US10010291B2 (en) | 2013-03-15 | 2018-07-03 | Abbott Diabetes Care Inc. | System and method to manage diabetes based on glucose median, glucose variability, and hypoglycemic risk |
US9830424B2 (en) | 2013-09-18 | 2017-11-28 | Hill-Rom Services, Inc. | Bed/room/patient association systems and methods |
US11587688B2 (en) | 2014-03-27 | 2023-02-21 | Raymond Anthony Joao | Apparatus and method for providing healthcare services remotely or virtually with or using an electronic healthcare record and/or a communication network |
US10510439B2 (en) | 2014-06-09 | 2019-12-17 | Upmc | System and method for processing healthcare information |
US10490306B2 (en) | 2015-02-20 | 2019-11-26 | Cerner Innovation, Inc. | Medical information translation system |
US10783448B2 (en) | 2015-08-07 | 2020-09-22 | Flatiron Health, Inc. | Extracting facts from unstructured data |
US10984897B2 (en) | 2016-10-27 | 2021-04-20 | Snaps Solutions, Llc | Systems and methods for surfacing contextually relevant content into the workflow of a third party system via a distributed architecture |
US11309075B2 (en) | 2016-12-29 | 2022-04-19 | Cerner Innovation, Inc. | Generation of a transaction set |
US11123014B2 (en) | 2017-03-21 | 2021-09-21 | Stryker Corporation | Systems and methods for ambient energy powered physiological parameter monitoring |
US10872321B2 (en) | 2017-05-05 | 2020-12-22 | Bank Of America Corporation | Machine initiated user status update system |
US10269456B2 (en) | 2017-05-05 | 2019-04-23 | Bank Of America Corporation | System for identification of treatment and resource deployment based on treatment interaction |
US10454941B2 (en) | 2017-05-05 | 2019-10-22 | Bank Of America Corporation | Person-to-person network architecture for secure authorization and approval |
US10437899B2 (en) | 2017-05-05 | 2019-10-08 | Bank Of America Corporation | System for distributed server data management with multi-user access |
US10034608B1 (en) | 2017-08-14 | 2018-07-31 | Bank Of America Corporation | System for receiving transmissions from disparate node and triggering automatic portal action |
US11911325B2 (en) | 2019-02-26 | 2024-02-27 | Hill-Rom Services, Inc. | Bed interface for manual location |
Family Cites Families (101)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3656687A (en) * | 1969-10-24 | 1972-04-18 | Russell H Romney | Data system for medical and other environments |
US4370983A (en) * | 1971-01-20 | 1983-02-01 | Lichtenstein Eric Stefan | Computer-control medical care system |
US4130881A (en) * | 1971-07-21 | 1978-12-19 | Searle Medidata, Inc. | System and technique for automated medical history taking |
JPS5335422B2 (en) * | 1973-02-28 | 1978-09-27 | ||
US4116470A (en) * | 1975-09-15 | 1978-09-26 | Johnsen Edward L | Medical information form for plurality of individual reports |
US4290114A (en) * | 1976-07-01 | 1981-09-15 | Sinay Hanon S | Medical diagnostic computer |
US4121574A (en) * | 1977-04-11 | 1978-10-24 | Medicgraph Systems, Inc. | Method and apparatus for measuring and recording vital signs of a patient |
US4277089A (en) * | 1977-09-09 | 1981-07-07 | Lockhart James L | Pharmaceutical record and label system |
US4159129A (en) * | 1977-09-09 | 1979-06-26 | Lockhart James L | Pharmaceutical record and label system |
US4221404A (en) * | 1978-06-12 | 1980-09-09 | Shuffstall Richard M | Medical history record filing system |
US4228506A (en) * | 1978-11-09 | 1980-10-14 | Del Mar Avionics | Charter with automatic editing |
US4665004A (en) * | 1981-02-27 | 1987-05-12 | Drexler Technology Corporation | Method for dual image recording of medical data |
US4503135A (en) * | 1981-02-27 | 1985-03-05 | Drexler Technology Corporation | Medium for recording visual images and laser written data |
US4489387A (en) * | 1981-08-20 | 1984-12-18 | Lamb David E | Method and apparatus for coordinating medical procedures |
US4533221A (en) * | 1983-01-25 | 1985-08-06 | Trachtman Joseph N | Methods and apparatus for accommodation training |
US4625276A (en) * | 1983-08-31 | 1986-11-25 | Vericard Corporation | Data logging and transfer system using portable and resident units |
US4667292A (en) * | 1984-02-16 | 1987-05-19 | Iameter Incorporated | Medical reimbursement computer system |
US4622013A (en) * | 1984-05-21 | 1986-11-11 | Interactive Research Corporation | Interactive software training system |
US5274749A (en) * | 1984-08-23 | 1993-12-28 | Health Care Expert Systems, Inc. | Interpretative system for systematic learning and support for decision-making |
US4845739A (en) * | 1985-07-10 | 1989-07-04 | Fdr Interactive Technologies | Telephonic-interface statistical analysis system |
US4792968A (en) * | 1985-07-10 | 1988-12-20 | Fdr Interactive Technologies | Statistical analysis system for use with public communication facility |
US5255309A (en) * | 1985-07-10 | 1993-10-19 | First Data Resources Inc. | Telephonic-interface statistical analysis system |
US5259023A (en) * | 1985-07-10 | 1993-11-02 | First Data Resources Inc. | Telephonic-interface statistical analysis system |
US5048075A (en) * | 1985-07-10 | 1991-09-10 | First Data Resources Inc. | Telephonic-interface statistical analysis system |
US4835372A (en) * | 1985-07-19 | 1989-05-30 | Clincom Incorporated | Patient care system |
US5146562A (en) * | 1985-08-30 | 1992-09-08 | International Business Machines Corporation | Patient care communication system |
US5101476A (en) * | 1985-08-30 | 1992-03-31 | International Business Machines Corporation | Patient care communication system |
US4857713A (en) * | 1986-02-14 | 1989-08-15 | Brown Jack D | Hospital error avoidance system |
US4850009A (en) * | 1986-05-12 | 1989-07-18 | Clinicom Incorporated | Portable handheld terminal including optical bar code reader and electromagnetic transceiver means for interactive wireless communication with a base communications station |
US4893270A (en) * | 1986-05-12 | 1990-01-09 | American Telephone And Telegraph Company, At&T Bell Laboratories | Medical information system |
US4857716A (en) * | 1986-05-12 | 1989-08-15 | Clinicom Incorporated | Patient identification and verification system and method |
US4972496A (en) * | 1986-07-25 | 1990-11-20 | Grid Systems Corporation | Handwritten keyboardless entry computer system |
US4799712A (en) * | 1986-11-18 | 1989-01-24 | Physicians' Pharmaceutical Services, Inc. | Prescription sheet and medication distribution system |
US4858121A (en) * | 1986-12-12 | 1989-08-15 | Medical Payment Systems, Incorporated | Medical payment system |
US5018067A (en) * | 1987-01-12 | 1991-05-21 | Iameter Incorporated | Apparatus and method for improved estimation of health resource consumption through use of diagnostic and/or procedure grouping and severity of illness indicators |
US5019976A (en) * | 1987-06-08 | 1991-05-28 | New World Down Hole Tools | Method and system for retrieving text associated with a reference image correspondence to a selected patient image |
US5070452A (en) * | 1987-06-30 | 1991-12-03 | Ngs American, Inc. | Computerized medical insurance system including means to automatically update member eligibility files at pre-established intervals |
US4855842A (en) * | 1987-08-06 | 1989-08-08 | Professional Training Systems, Inc. | Dedicated programmable controller for interactive video disc system |
US5315505A (en) * | 1987-08-12 | 1994-05-24 | Micro Chemical, Inc. | Method and system for providing animal health histories and tracking inventory of drugs |
JPH0191834A (en) * | 1987-08-20 | 1989-04-11 | Tsuruta Hiroko | Abnormal data detection and information method in individual medical data central control system |
US4945477A (en) * | 1987-10-22 | 1990-07-31 | First Medic | Medical information system |
US4878175A (en) * | 1987-11-03 | 1989-10-31 | Emtek Health Care Systems | Method for generating patient-specific flowsheets by adding/deleting parameters |
US5006699A (en) * | 1987-11-13 | 1991-04-09 | Felkner Donald J | System for collecting medical data |
US5025374A (en) * | 1987-12-09 | 1991-06-18 | Arch Development Corp. | Portable system for choosing pre-operative patient test |
US4945476A (en) * | 1988-02-26 | 1990-07-31 | Elsevier Science Publishing Company, Inc. | Interactive system and method for creating and editing a knowledge base for use as a computerized aid to the cognitive process of diagnosis |
US4869531A (en) * | 1988-04-01 | 1989-09-26 | Rees Michael K | Apparatus and method for documenting physical examinations |
DE3817052A1 (en) * | 1988-05-19 | 1989-11-30 | Draegerwerk Ag | METHOD FOR MONITORING PATIENT DATA AND CIRCUIT ARRANGEMENT THEREFOR |
US4975842A (en) * | 1988-08-11 | 1990-12-04 | Schering Corporation | Electronic patient diary and patient monitoring process |
US5292029A (en) * | 1989-11-08 | 1994-03-08 | Pearson Walter G | Patient medication dispensing and associated record |
US4916441A (en) * | 1988-09-19 | 1990-04-10 | Clinicom Incorporated | Portable handheld terminal |
US5253164A (en) * | 1988-09-30 | 1993-10-12 | Hpr, Inc. | System and method for detecting fraudulent medical claims via examination of service codes |
US5054096A (en) * | 1988-10-24 | 1991-10-01 | Empire Blue Cross/Blue Shield | Method and apparatus for converting documents into electronic data for transaction processing |
US4939508A (en) * | 1988-10-31 | 1990-07-03 | Emtek Health Care Systems, Inc. | Point and select device |
US5077666A (en) * | 1988-11-07 | 1991-12-31 | Emtek Health Care Systems, Inc. | Medical information system with automatic updating of task list in response to charting interventions on task list window into an associated form |
US5072383A (en) * | 1988-11-19 | 1991-12-10 | Emtek Health Care Systems, Inc. | Medical information system with automatic updating of task list in response to entering orders and charting interventions on associated forms |
US4918572A (en) * | 1988-12-27 | 1990-04-17 | Motorola Computer X, Inc. | Modular electronic package |
US5193855A (en) * | 1989-01-25 | 1993-03-16 | Shamos Morris H | Patient and healthcare provider identification system |
CA2003687C (en) * | 1989-03-13 | 1999-11-16 | Richard Edward Shelton | Forms manager |
JP2690782B2 (en) * | 1989-05-30 | 1997-12-17 | 富士写真フイルム株式会社 | Image filing system |
US5016172A (en) * | 1989-06-14 | 1991-05-14 | Ramp Comsystems, Inc. | Patient compliance and status monitoring system |
US5067834A (en) * | 1989-07-07 | 1991-11-26 | Szmanda Jeffrey P | Input keyboard apparatus for information processing device and other keyboard devices |
US5099424A (en) * | 1989-07-20 | 1992-03-24 | Barry Schneiderman | Model user application system for clinical data processing that tracks and monitors a simulated out-patient medical practice using data base management software |
US5247611A (en) * | 1989-09-15 | 1993-09-21 | Emtek Health Care Systems, Inc. | Spreadsheet cell having multiple data fields |
US5301319A (en) * | 1989-09-15 | 1994-04-05 | Emtek Health Care Systems, Inc. | Data storage audit trail |
US5325478A (en) * | 1989-09-15 | 1994-06-28 | Emtek Health Care Systems, Inc. | Method for displaying information from an information based computer system |
US5253361A (en) * | 1989-09-15 | 1993-10-12 | Emtek Health Care Systems, Inc. | System for accessing a row of time-dependent data by referring to a composite index table indicating page locations of linked row labels |
US5148366A (en) * | 1989-10-16 | 1992-09-15 | Medical Documenting Systems, Inc. | Computer-assisted documentation system for enhancing or replacing the process of dictating and transcribing |
US5065315A (en) * | 1989-10-24 | 1991-11-12 | Garcia Angela M | System and method for scheduling and reporting patient related services including prioritizing services |
US5296688A (en) * | 1989-12-04 | 1994-03-22 | Hamilton David W | Apparatus and method for recording progress notes |
US5253362A (en) * | 1990-01-29 | 1993-10-12 | Emtek Health Care Systems, Inc. | Method for storing, retrieving, and indicating a plurality of annotations in a data cell |
US5121470A (en) * | 1990-02-01 | 1992-06-09 | Intellimetrics Instrument Corporation | Automated interactive record system |
US5235702A (en) * | 1990-04-11 | 1993-08-10 | Miller Brent G | Automated posting of medical insurance claims |
US5265010A (en) * | 1990-05-15 | 1993-11-23 | Hewlett-Packard Company | Method and apparatus for performing patient documentation |
US5272625A (en) * | 1990-05-17 | 1993-12-21 | Kabushiki Kaisha Toshiba | Medical image data managing system |
US5133045A (en) * | 1990-07-13 | 1992-07-21 | Integrated Systems, Inc. | Method for operating a real-time expert system in a graphical programming environment |
US5291399A (en) * | 1990-07-27 | 1994-03-01 | Executone Information Systems, Inc. | Method and apparatus for accessing a portable personal database as for a hospital environment |
US5276612A (en) * | 1990-09-21 | 1994-01-04 | New England Medical Center Hospitals, Inc. | Risk management system for use with cardiac patients |
EP0487110B1 (en) * | 1990-11-22 | 1999-10-06 | Kabushiki Kaisha Toshiba | Computer-aided diagnosis system for medical use |
US5324077A (en) * | 1990-12-07 | 1994-06-28 | Kessler Woodrow B | Medical data draft for tracking and evaluating medical treatment |
US5225976A (en) * | 1991-03-12 | 1993-07-06 | Research Enterprises, Inc. | Automated health benefit processing system |
US5325523A (en) * | 1991-04-10 | 1994-06-28 | International Business Machines Corporation | Method for deleting objects from library resident optical disks by accumulating pending delete requests |
US5287414A (en) * | 1991-06-21 | 1994-02-15 | Esselte Pendaflex Corporation | Coded file locator system |
US5277188A (en) * | 1991-06-26 | 1994-01-11 | New England Medical Center Hospitals, Inc. | Clinical information reporting system |
US5136502A (en) * | 1991-10-02 | 1992-08-04 | Fred Van Remortel | System for funding, analyzing and managing health care liabilities |
US5287459A (en) * | 1991-10-03 | 1994-02-15 | International Business Machines Corporation | Method and apparatus for reducing response time in automated library data retrieval systems |
US5262943A (en) * | 1991-10-15 | 1993-11-16 | National Computer Systems, Inc. | System and process for information management and reporting |
US5327341A (en) * | 1991-10-28 | 1994-07-05 | Whalen Edward J | Computerized file maintenance system for managing medical records including narrative reports |
US5307262A (en) * | 1992-01-29 | 1994-04-26 | Applied Medical Data, Inc. | Patient data quality review method and system |
US5325293A (en) * | 1992-02-18 | 1994-06-28 | Dorne Howard L | System and method for correlating medical procedures and medical billing codes |
US5305748A (en) * | 1992-06-05 | 1994-04-26 | Wilk Peter J | Medical diagnostic system and related method |
US5319543A (en) * | 1992-06-19 | 1994-06-07 | First Data Health Services Corporation | Workflow server for medical records imaging and tracking system |
US5325294A (en) * | 1992-06-29 | 1994-06-28 | Keene Sharon A | Medical privacy system |
US5331549A (en) * | 1992-07-30 | 1994-07-19 | Crawford Jr John M | Medical monitor system |
US5555388A (en) * | 1992-08-20 | 1996-09-10 | Borland International, Inc. | Multi-user system and methods providing improved file management by reading |
US5307263A (en) * | 1992-11-17 | 1994-04-26 | Raya Systems, Inc. | Modular microprocessor-based health monitoring system |
US5493724A (en) * | 1993-04-01 | 1996-02-20 | International Business Machines Corporation | Locking a non-busy device for accessing a data record stored on another device |
US5721943A (en) | 1993-10-14 | 1998-02-24 | International Business Machines Corporation | Negotiable locks for concurrent access of control data by multiple programs |
US5594638A (en) * | 1993-12-29 | 1997-01-14 | First Opinion Corporation | Computerized medical diagnostic system including re-enter function and sensitivity factors |
US5546580A (en) * | 1994-04-15 | 1996-08-13 | Hewlett-Packard Company | Method and apparatus for coordinating concurrent updates to a medical information database |
US5742813A (en) | 1994-11-10 | 1998-04-21 | Cadis, Inc. | Method and apparatus for concurrency in an object oriented database using lock inheritance based on class objects |
US5606679A (en) * | 1995-02-28 | 1997-02-25 | International Business Machines Corporation | Method for optimal retrieval of non-volume-specific data |
-
1996
- 1996-03-01 US US08/609,844 patent/US5974389A/en not_active Expired - Fee Related
-
1997
- 1997-03-03 WO PCT/US1997/003257 patent/WO1997032271A1/en not_active Application Discontinuation
- 1997-03-03 EP EP97908811A patent/EP0883854A1/en not_active Withdrawn
- 1997-03-03 AU AU20626/97A patent/AU732221B2/en not_active Ceased
- 1997-03-03 JP JP9531190A patent/JP2000506291A/en active Pending
- 1997-03-03 CA CA002247915A patent/CA2247915A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
AU2062697A (en) | 1997-09-16 |
JP2000506291A (en) | 2000-05-23 |
WO1997032271A1 (en) | 1997-09-04 |
US5974389A (en) | 1999-10-26 |
AU732221B2 (en) | 2001-04-12 |
EP0883854A1 (en) | 1998-12-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2247915A1 (en) | Medical record management system and process with improved workflow features | |
US8086468B2 (en) | Method for computerising and standardizing medical information | |
US6347329B1 (en) | Electronic medical records system | |
JP3074536B2 (en) | Input / output control method of electronic medical record system | |
US8751501B2 (en) | Longitudinal electronic record system and method with task-based workflow | |
US7802183B1 (en) | Electronic record management system | |
JP2005508054A (en) | Healthcare system and user interface for integrating patient related information from various sources | |
US9471751B1 (en) | Telemedicine system for preliminary remote diagnosis of a patient | |
WO2004104742A2 (en) | System and method for generating a report using a knowledge base | |
US20030217111A1 (en) | Method and system for implementing an information portal for viewing information from disparate system's databases | |
CN112700873A (en) | Intelligent nursing information interaction system | |
Mantas | 3.4 Electronic Health Record | |
Guadagno et al. | Using PDAs for data collection | |
Carpenter | The electronic medical record: perspective from Mayo Clinic | |
CA2502887A1 (en) | Method and system for medical communications | |
Waegemann et al. | Healthcare documentation: A report on information capture and report generation | |
Kolodner | Mental health clinical computer applications that succeed: The VA experience | |
Douglass | Computer-assisted de-identification of free-text nursing notes | |
Lindberg et al. | The Unified Medical Language System (UMLS) and computer-based patient records | |
US11551791B2 (en) | Key note | |
Grummitt | Real-time record management in general practice | |
MXPA98006944A (en) | System and process for the handling of medical records with improved characteristics of the circuit deproc | |
Barrows Jr et al. | A decision-supported outpatient practice system. | |
JP2000276538A (en) | Electronic chart system provided with communication function | |
Foy | Integrating non-proprietary workstations into proprietary systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FZDE | Discontinued | ||
FZDE | Discontinued |
Effective date: 20030303 |