US5832450A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Electronic medical record using text database
Assignee: Scott & White Memorial Hospital
•
Filing: 1997-05-05
•
Granted: 1998-11-03
•
Expires: 2017-05-05
Abstract
Abstract An electronic medical record system stores data about patient encounters arising from a content generator in free-form text. A header for each encounter record also uses text to store context information for each encounter record. Each header comprises a plurality of attributes embodied as a field descriptor and a value, bound together as a text object. By binding the field descriptors to the values, each encounter record is complete in itself, without reference to database keys, thereby providing a self-validating record storage system.
Inventors
- 👤 Dennis Lee Myers
- 👤 Kim Steven Culp
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-01 16:30
CPC Classifications
G; G16; G16H; G16H10/00; G16H10/20; G16H10/60; G16H40/00; G16H40/20; G16H40/60; G16H40/67; G16H70/00; G16H70/60
Claims Analysis
Total Claims: 28
Claim 1
Independent Claim
132 words
A method of maintaining electronic medical records, comprising the steps of: receiving output about individual patient encounters from a content generator; generating context information related to the output of the content generator in a free form text output; storing context information for each individual patient encounter in a textual database comprising a plurality of encounter records, said storing step comprising: forming a textual header for an encounter record in the database corresponding to the individual patient encounter, said textual header having a variable plurality of descriptors and associated values bound together as a string of text; and appending the textual header to the generated context information to form the encounter record, wherein a text object is formed; and responsive to a user command, displaying information from said textual database on a display.
Claim 2
Independent Claim
132 words
A method of maintaining electronic medical records, comprising the steps of: receiving output about individual patient encounters from a content generator; generating context information related to the output of the content generator in a free form text output; storing context information for each individual patient encounter in a textual database comprising a plurality of encounter records, said storing step comprising: forming a textual header for an encounter record in the database corresponding to the individual patient encounter, said textual header having a variable plurality of descriptors and associated values bound together as a string of text; and appending the textual header to the generated context information to form the encounter record, wherein a text object is formed; and responsive to a user command, displaying information from said textual database on a display.
Claim 3
Dependent Claim
24 words
The method of claim 1 wherein said generating step comprises the step of generating tokenized text related to the output of the content generator.
Claim 4
Dependent Claim
36 words
The method of claim 1 wherein said generating step comprises the step of generating textual context information related to the output of the content generator and indicating whether an image is associated with textual context information.
Claim 5
Dependent Claim
38 words
The method of claim 1 wherein said generating step comprises the step of generating textual context information related to the output of the content generator and indicating whether a relational database object is associated with textual context information.
Claim 6
Independent Claim
148 words
A method of maintaining electronic medical records, comprising the steps of: receiving output about individual patient encounters from a content generator; generating context information related to the output of the content generator; storing context information for each individual patient encounter in a textual database comprising a plurality of encounter records, said storing step comprising: forming a textual header for an encounter record in the textual database corresponding to the individual patient encounter, said textual header having a plurality of descriptors and associated values bound together as a string of text; appending the textual header to the generated context information to form the encounter record in the textual database, wherein a text object is formed; and storing the headers for each encounter record in a header database separate from said textual database; and responsive to a command from a user, displaying information from said textual database on a display.
Claim 7
Independent Claim
148 words
A method of maintaining electronic medical records, comprising the steps of: receiving output about individual patient encounters from a content generator; generating context information related to the output of the content generator; storing context information for each individual patient encounter in a textual database comprising a plurality of encounter records, said storing step comprising: forming a textual header for an encounter record in the textual database corresponding to the individual patient encounter, said textual header having a plurality of descriptors and associated values bound together as a string of text; appending the textual header to the generated context information to form the encounter record in the textual database, wherein a text object is formed; and storing the headers for each encounter record in a header database separate from said textual database; and responsive to a command from a user, displaying information from said textual database on a display.
Claim 8
Dependent Claim
54 words
The method of claim 5 and further comprising the steps of: searching the textual database to retrieve encounter records with headers having a predefined context value; searching the header database to retrieve headers having said predefined context value; and comparing the retrieved headers from the header database with headers of the retrieved encounter records.
Claim 9
Dependent Claim
19 words
The method of claim 6 and further comprising the step of forming a chart from the retrieved encounter records.
Claim 10
Dependent Claim
32 words
The method of claim 7 and further comprising the step of notifying the user if the retrieved headers from the header database do not match the headers of the retrieved encounter records.
Claim 11
Dependent Claim
36 words
The method of claim 8 wherein, if the retrieved headers from the header database do not match the headers of the retrieved encounter records, the user may selectively display a chart of the retrieved encounter records.
Claim 12
Dependent Claim
54 words
The method of claim 8 wherein, if the retrieved headers do not match the headers of the retrieved encounter records, the user may selectively perform a text search of the encounter records to locate one or more encounter records corresponding to retrieved headers which were not retrieved from the search of the text database.
Claim 13
Dependent Claim
156 words
An electronic medical record system comprising: one or more content generators; a plurality of workstations for storing and retrieving information related to electronic medical records; and a central controller coupled to said workstations and said content generators for: receiving output about individual patient encounters from a content generator; generating context information related to the output of the content generator; storing context information for each individual patient encounter in an encounter record in a textual database comprising a plurality of encounter records, said storing step comprising: forming a textual header for an encounter record in the database corresponding to the individual patient encounter, said textual header having a plurality of descriptors and associated values bound together as a string of text; and appending the textual header to the generated context information to form the encounter record, wherein a text object is formed; and responsive to a user command, displaying information from said textual database on a display.
Claim 14
Dependent Claim
156 words
An electronic medical record system comprising: one or more content generators; a plurality of workstations for storing and retrieving information related to electronic medical records; and a central controller coupled to said workstations and said content generators for: receiving output about individual patient encounters from a content generator; generating context information related to the output of the content generator; storing context information for each individual patient encounter in an encounter record in a textual database comprising a plurality of encounter records, said storing step comprising: forming a textual header for an encounter record in the database corresponding to the individual patient encounter, said textual header having a plurality of descriptors and associated values bound together as a string of text; and appending the textual header to the generated context information to form the encounter record, wherein a text object is formed; and responsive to a user command, displaying information from said textual database on a display.
Claim 15
Dependent Claim
16 words
The electronic medical record system of claim 11 wherein the content generators include a transcription system.
Claim 16
Dependent Claim
31 words
The electronic medical record system of claim 11 wherein one or more of said workstations include an interface for retrieving and displaying the encounter records responsive to inputs from a user.
Claim 17
Dependent Claim
23 words
The electronic medical record system of claim 11 wherein said workstations, content generators and central controller are coupled via a local area network.
Claim 18
Dependent Claim
21 words
The electronic medical record system of claim 14 and further comprising a wide area network coupled to the local area network.
Claim 19
Dependent Claim
19 words
The electronic medical record system of claim 11 wherein said central controller tokenizes the output of the content generator.
Claim 20
Dependent Claim
27 words
The electronic medical record system of claim 11 wherein said central controller stores the output of said one content generator in the encounter record as free-form text.
Claim 21
Dependent Claim
25 words
The electronic medical record system of claim 11 wherein said central controller stores said bound descriptors and associated values in a predefined header text format.
Claim 22
Dependent Claim
29 words
The electronic medical record system of claim 11 wherein said central controller stores context information in said header indicating whether an image object is associated with the encounter record.
Claim 23
Dependent Claim
30 words
The electronic medical record system of claim 11 wherein said central controller stores context information in said header indicating whether an relational database object is associated with the encounter record.
Claim 24
Dependent Claim
26 words
The electronic medical record system of claim 11 wherein said central controller includes a header database for storing the header information associated with each encounter record.
Claim 25
Dependent Claim
24 words
The electronic medical record system of claim 11 wherein said central controller searches the textual database for selected encounter records to form a chart.
Claim 26
Dependent Claim
61 words
The electronic medical record system of claim 22 wherein said central controller searches the textual database by: searching the textual database to retrieve encounter records with headers having a predefined context value; searching the header database to retrieve headers having said predefined context value; and comparing the retrieved headers from the header database with the headers of the retrieved encounter records.
Claim 27
Dependent Claim
22 words
The electronic medical record system of claim 23 wherein said central controller includes a lookup table for storing encounter record location information.
Claim 28
Dependent Claim
24 words
The electronic medical record of claim 24 wherein said central controller is operable to search the textual database without reference to the lookup table.
References Cited (Backward Citations)
US4857716A
Cited
US5054096A
Cited
US5072383A
Cited
US5247611A
Cited
US5065315A
Cited
US5155726A
Cited
US5185860A
Cited
US5265010A
Cited
US5247437A
Cited
US5319543A
Cited
US5361202A
Cited
US5473537A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2001-11-02 | 2002-05-04 | 2002-11-03 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2005-11-02 | 2006-05-04 | 2006-11-03 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2009-11-02 | 2010-05-04 | 2010-11-03 | $7700.00 | Window Closed / Lapsed |