U.S. patent application number 15/394227 was filed with the patent office on 2017-04-20 for system for providing an overview of patient medical condition.
The applicant listed for this patent is CERNER INNOVATION, INC.. Invention is credited to Loretta A. Fitzgerald, Christian Lampone, Vickilyn Spiotta.
Application Number | 20170109487 15/394227 |
Document ID | / |
Family ID | 40589114 |
Filed Date | 2017-04-20 |
United States Patent
Application |
20170109487 |
Kind Code |
A1 |
Fitzgerald; Loretta A. ; et
al. |
April 20, 2017 |
System for Providing an Overview of Patient Medical Condition
Abstract
A system provides an overview of patient medical condition by
automatically converting a financial diagnosis description of a
medical condition, into clinical terminology and associating a
clinical diagnosis with a patient in a record that persists the
association across multiple patient visits for a lifetime type
medical condition. A system provides an overview of patient medical
condition identifying both long term and short term medical
conditions. The system includes a designation processor for
designating an identified patient medical condition as being long
term in response to user command. At least one repository stores
information associating a designated long term patient medical
condition with a patient and with a plurality of encounter
identifiers identifying corresponding interactions of the patient
with a healthcare provider organization and medical conditions
associated with the encounters. A user interface initiates
generation of data representing a composite display image window
including data identifying a designated long term patient medical
condition together with encounters and medical conditions
associated with the encounters providing a user an overview of long
term and short term medical conditions of a patient.
Inventors: |
Fitzgerald; Loretta A.;
(Collegeville, PA) ; Spiotta; Vickilyn; (Shaker
Heights, OH) ; Lampone; Christian; (Pipersville,
PA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
CERNER INNOVATION, INC. |
KANSAS CITY |
KS |
US |
|
|
Family ID: |
40589114 |
Appl. No.: |
15/394227 |
Filed: |
December 29, 2016 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
11862775 |
Sep 27, 2007 |
|
|
|
15394227 |
|
|
|
|
60827768 |
Oct 2, 2006 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G16H 40/63 20180101;
G16H 10/60 20180101; G06Q 50/22 20130101; G06Q 50/24 20130101; G16H
50/20 20180101; G16H 40/20 20180101 |
International
Class: |
G06F 19/00 20060101
G06F019/00 |
Claims
1. A system for providing an overview of patient medical condition
identifying both long term and short term medical conditions,
comprising: a designation processor for designating an identified
patient medical condition as being long term in response to user
command; at least one repository for storing information
associating a designated long term patient medical condition with a
patient and with a plurality of encounter identifiers identifying
corresponding interactions of said patient with a healthcare
provider organization and medical conditions associated with said
encounters; and a user interface for initiating generation of data
representing a composite display image window including data
identifying a designated long term patient medical condition
together with encounters and medical conditions associated with
said encounters providing a user an overview of long term and short
term medical conditions of a patient.
2. A system according to claim 1, wherein said designation
processor automatically parses data representing a patient
diagnosis and identifies data indicating a potentially long term
medical condition in said patient diagnosis and automatically
initiates providing a user with a prompt message prompting a user
to select a patient medical condition as being a long term medical
condition.
3. A system according to claim 2, wherein said designation
processor automatically identifies data indicating a potentially
long term medical condition based on a predetermined list of
potentially long term medical conditions.
4. A system according to claim 1, wherein said designation
processor automatically parses data representing a patient medical
condition and identifies data indicating at least one potentially
long term medical condition in said data representing a patient
medical condition and automatically initiates providing a user with
a corresponding candidate list of potentially long term medical
conditions enabling a user to select a particular long term medical
condition for association with a patient.
5. A system according to claim 1, including a workflow processor
for automatically prompting a user to confirm addition of a task to
a task list of a healthcare worker in response to, designation of
an identified patient medical condition as being long term and data
identifying at least one of, (a) a short term medical condition of
said patient, (b) an order for treatment to be administered to said
patient and (c) a laboratory test result of said patient.
6. A system according to claim 1, wherein said identified patient
medical condition is identified from a condition representative
code in a predetermined code set.
7. A system according to claim 6, including a converter for
automatically translating a code representing said identified
patient medical condition to a text phrase representing said
identified patient medical condition understandable by a
clinician.
8. A system according to claim 7, wherein said composite display
image window includes said text phrase.
9. A system according to claim 1, wherein said designation
processor associates a designated long term patient medical
condition with a particular patient.
10. A system for providing an overview of patient medical condition
identifying both long term and short term medical conditions,
comprising: a designation processor for automatically designating
an identified patient medical condition as being long term by
parsing data representing a patient medical condition and
identifying data indicating a potentially long term medical
condition in said data representing a patient medical condition
based on a predetermined list of potentially long term medical
conditions; at least one repository for storing information
associating a designated long term patient medical condition with a
patient and with a plurality of encounter identifiers identifying
corresponding interactions of said patient with a healthcare
provider organization and medical conditions associated with said
encounters; and a user interface for initiating generation of data
representing a composite display image window including data
identifying a designated long term patient medical condition
together with encounters and medical conditions associated with
said encounters providing a user an overview of long term and short
term medical conditions of a patient.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This is a divisional application of U.S. application Ser.
No. 11/862,775, filed Sep. 27, 2007, which claims the benefit of
priority to U.S. Provisional Application No. 60/827,768 filed Oct.
2, 2006, all of which are herein incorporated by reference in their
entirety.
FIELD OF THE INVENTION
[0002] This invention concerns a system for providing an overview
of patient medical condition identifying both long term and short
term medical conditions and associated encounters (e.g., visits,
treatment episodes).
BACKGROUND OF THE INVENTION
[0003] In known patient medical record management systems, a
clinical diagnosis is added to a patient record, but in the record
there is typically no association with a financial reimbursement
related code diagnosis description, such as an ICD9 code. The
financial diagnosis code is associated with a patient visit and
needs to be re-entered when a patient continues with visits to
treat medical conditions which continue with the patient for an
extended duration such as over a patient lifetime. Such medical
conditions include, diabetes, congestive heart failure, and cancer,
for example. Known systems employ financial system paradigms, in
which visit identifier, and clinical diagnosis and associated code
are typically re-entered for each visit.
[0004] In known systems, a clinical diagnosis is re-entered into a
patient medical record management system in association with a
visit record in response to a financial system requirement. Such
systems fail to automatically manage a diagnosis which persists for
a patient lifetime and burdens a clinician with a requirement to
repetitively re-enter a clinical diagnosis in association with a
visit record. Known systems also fail to provide a bridge between a
financial diagnosis and clinical diagnosis. For example, an ICD9
code 174.2 description is: Malignant neoplasm of female breast
Upper-inner quadrant and a corresponding clinical description is
Breast Cancer. Known systems fail to automatically link financial
and clinical diagnoses for use in appropriate record maintenance. A
system according to invention principles addresses these
deficiencies and related problems.
SUMMARY OF THE INVENTION
[0005] A system automatically converts a financial diagnosis
description of a medical condition, such as an ICD 9 code, into
clinical terminology used by clinicians and associates a clinical
diagnosis with a patient in a record that persists the association
across multiple patient visits and not just for one visit. A system
provides an overview of patient medical condition identifying both
long term conditions (e.g., diabetes, congestive heart failure, and
cancer) and short term medical conditions. The system includes a
designation processor for designating an identified patient medical
condition as being long term in response to user command. At least
one repository stores information associating a designated long
term patient medical condition with a patient and with a plurality
of encounter identifiers identifying corresponding interactions of
the patient with a healthcare provider organization and medical
conditions associated with the encounters. A user interface
initiates generation of data representing a composite display image
window including data identifying a designated long term patient
medical condition together with encounters and medical conditions
associated with the encounters providing a user an overview of long
term and short term medical conditions of a patient.
BRIEF DESCRIPTION OF THE DRAWING
[0006] FIG. 1 shows a system for providing an overview display of
patient medical condition identifying both long term and short term
medical conditions, according to invention principles.
[0007] FIG. 2 shows a flowchart of a process involving providing an
overview of patient medical condition and a care plan for long term
and short term medical conditions, according to invention
principles.
[0008] FIG. 3 shows user interface display images including data
identifying a designated long term patient medical condition,
encounters and medical conditions associated with the encounters as
an overview of long term and short term medical conditions of a
patient, according to invention principles.
[0009] FIG. 4 shows a flowchart of a process performed by a system
for providing an overview display of patient medical condition
identifying both long term and short term medical conditions,
according to invention principles.
DETAILED DESCRIPTION OF THE INVENTION
[0010] Known systems partition treatment and diagnostic procedure
information into records of multiple different visits of a patient
with one or more healthcare provider organizations. Known systems
thereby create a disjointed record which cannot be viewed in one
location. In contrast, a system according to invention principles
associates a clinical diagnosis with a patient, enabling
treatments, diagnostic studies and clinical documentation to be
stored in a patient record. The system provides a unified patient
history of a diagnosis and automatically converts a financial
diagnosis description of a medical condition, such as an ICD 9
code, into clinical terminology used by clinicians. The system
associates a clinical diagnosis with a patient, not a visit and
persists the association across multiple patient visits and not
just for one visit. Further, the system associates particular
processing functions with a certain diagnostic type, such as cancer
and the system triggers initiation of additional necessary clinical
procedures for performance by a clinician. For this purpose system
10 adds tasks to a clinician or device task list. For example, in
response to a cancer diagnosis the system initiates presentation of
diagnosis and disease staging dialogs to a user with appropriate
security credentials.
[0011] A processor, as used herein, operates under the control of
an executable application to (a) receive information from an input
information device, (b) process the information by manipulating,
analyzing, modifying, converting and/or transmitting the
information, and/or (c) route the information to an output
information device. A processor may use, or comprise the
capabilities of, a controller or microprocessor, for example. The
processor may operate with a display processor or generator. A
display processor or generator is a known element for generating
signals representing display images or portions thereof. A
processor and a display processor may comprise a combination of,
hardware, firmware, and/or software.
[0012] An executable application, as used herein, comprises code or
machine readable instructions for conditioning the processor to
implement predetermined functions, such as those of an operating
system, a context data acquisition system or other information
processing system, for example, in response to user command or
input. An executable procedure is a segment of code or machine
readable instruction, sub-routine, or other distinct section of
code or portion of an executable application for performing one or
more particular processes. These processes may include receiving
input data and/or parameters, performing operations on received
input data and/or performing functions in response to received
input parameters, and providing resulting output data and/or
parameters. A user interface (UI), as used herein, comprises one or
more display images, generated by a display processor and enabling
user interaction with a processor or other device and associated
data acquisition and processing functions.
[0013] The UI also includes an executable procedure or executable
application. The executable procedure or executable application
conditions the display processor to generate signals representing
the UI display images. These signals are supplied to a display
device which displays the image for viewing by the user. The
executable procedure or executable application further receives
signals from user input devices, such as a keyboard, mouse, light
pen, touch screen or any other means allowing a user to provide
data to a processor. The processor, under control of an executable
procedure or executable application, manipulates the UI display
images in response to signals received from the input devices. In
this way, the user interacts with the display image using the input
devices, enabling user interaction with the processor or other
device. The functions and process steps herein may be performed
automatically or wholly or partially in response to user command.
An activity (including a step) performed automatically is performed
in response to executable instruction or device operation without
user direct initiation of the activity. Workflow comprises a
sequence of tasks performed by a device or worker or both. An
object or data object comprises a grouping of data, executable
instructions or a combination of both or an executable
procedure.
[0014] A workflow processor, as used herein, processes data to
determine tasks to add to a task list, remove from a task list or
modifies tasks incorporated on, or for incorporation on, a task
list. A task list is a list of tasks for performance by a worker or
device or a combination of both. A. workflow processor may or may
not employ a workflow engine. A workflow engine, as used herein, is
a processor executing in response to predetermined process
definitions that implement processes responsive to events and event
associated data. The workflow engine implements processes in
sequence and/or concurrently, responsive to event associated data
to determine tasks for performance by a device and or worker and
for updating task lists of a device and a worker to include
determined tasks. A process definition is definable by a user and
comprises a sequence of process steps including one or more, of
start, wait, decision and task allocation steps for performance by
a device and or worker, for example. An event is an occurrence
affecting operation of a process implemented using a process
definition.
[0015] A Workflow Management System is a software system that
manages processes. It includes a process definition function that
allows users to define a process that should be followed, an Event
Monitor, which captures events from a Healthcare Information System
and communicates the results to the Workflow Management System. A
processor in the Management System tracks which processes are
running, for which patients, and what step needs to be executed
next, according to a process definition. The Management System
includes a procedure for notifying clinicians of a task to be
performed, through their worklists (task lists) and a procedure for
allocating and assigning tasks to specific users or specific teams.
A document or record comprises a compilation of data in electronic
form and is the equivalent of a paper document and may comprise a
single, self-contained unit of information.
[0016] FIG. 1 shows system 10 for providing an overview display of
patient medical condition identifying both long term and short term
medical conditions. System 10 includes client devices
(workstations) 12 and 14, repository 17 and server 20
bidirectionally communicating via network 21. Server 20 includes
designation processor 25, workflow processor 29, order entry system
35 and converter 15. Designation processor 25 designates an
identified patient medical condition as being long term in response
to user command. At least one repository 17 stores information
associating a designated long term patient medical condition with a
patient and with multiple encounter identifiers identifying
corresponding interactions of the patient with a healthcare
provider organization and with medical conditions associated with
the encounters. User interface 26 initiates generation of data
representing a composite display image window including data
identifying a designated long term patient medical condition
together with encounters and medical conditions associated with the
encounters providing a user an overview of long term and short term
medical conditions of a patient. The composite display image window
is presented on workstation 12 (or workstation 14).
[0017] Workflow processor 29 automatically prompts a user to
confirm addition of a task to a task list of a healthcare worker in
response to, designation of an identified patient medical condition
as being long term and data identifying at least one of, (a) a
short term medical condition of the patient, (b) an order for
treatment to be administered to the patient and (c) a laboratory
test result of the patient. The identified patient medical
condition is identified from a condition representative code in a
predetermined code set. Workflow processor 29 in server 20 manages
addition, deletion and modification of tasks to be performed by a
worker or device as well as presentation of task lists in a window
area in a composite display image window. Converter 15
automatically translates a code representing the identified patient
medical condition to a text phrase representing the identified
patient medical condition (clinical diagnosis) understandable by a
clinician. Converter 15 automatically translates a medical
condition representative code to a text phrase using a
predetermined map associating codes with one or more corresponding
text phrases indicating one or more medical conditions. Converter
15 uses additional patient information including patient
assessments, demographic data (e.g., age, weight, height gender),
diagnosis text and other information acquired from patient records
to select between different text phrases associated with a
particular code.
[0018] Converter 15 converts a financial description, which is not
used by clinicians (e.g., a code such as an ICD9 code), into a
corresponding commonly used clinical description of a diagnosis.
The clinical diagnosis is associated with a patient as well as with
records associated with multiple different patient visits involved
in an extended duration (e.g. a lifetime) medical condition such as
diabetes, congestive heart failure, and cancer. System 10 provides
a lifetime history of a clinical diagnosis and organizes clinically
relevant data (diagnostics, treatment, notes) by associating the
clinically relevant data with an appropriate clinical diagnosis.
Thereby providing a physician with a single entry point display
image window for viewing patient information. In situations in
which a primary physician may not be available, this expedites a
process for an attending physician to review patient history and
determine a course of action, for example.
[0019] FIG. 2 shows a flowchart of a process employed by system 10
in providing an overview of patient medical condition and a care
plan for long term and short term medical conditions. The steps of
FIG. 2 may be performed wholly or partially automatically in other
embodiments. The process of FIG. 2 employs user interface display
images as illustrated in FIG. 3 including data identifying a
designated long term patient medical condition, encounters and
medical conditions associated with the encounters providing as an
overview of long term and short term medical conditions of a
patient. In step 203 (FIG. 2), a user selects a particular patient
from a census list of patients presented in a user interface image
displayed on workstation 12 (FIG. 1) and that is associated with a
particular physician, for example. In step 205 a clinician selects
CDP (Clinical Data Processing) function 311 in display image 303
(FIG. 3) to initiate generation of data representing composite
display image window 323 including data identifying a designated
long term patient medical condition (e.g., lung cancer 310)
together with encounters and medical conditions (e.g., in section
315) associated with the encounters providing a user an overview of
long term and short term medical conditions of a patient. In step
213 system 10 and the FIG. 2 process are adaptively configured in
response to predetermined instruction to adapt processing to a
particular selected diagnosis so that data processing functions
employed are adaptively selected to correspond to a particular
diagnosis type. Thereby, for example, in response to a selected
cancer diagnosis, system 10 prompts a user to enter staging
information for use in identifying a cancer stage of a patient.
[0020] In step 208 (FIG. 2) a user selects a clinical diagnosis 310
(FIG. 3) and in step 211 associates clinical diagnosis 310 with
financial (i.e., ICD9) diagnosis codes 768.9 and 432.9 in visit
section 315. User interface display image 303 of FIG. 3 provides to
user 307 selectable functions and associated display images
indicated in column 330 including CDP (clinical data processing)
311, allergies, consent forms, flowsheets, assessments, notes,
medications/IVs, interventions and manually entered patient data
and results. Image window area 323 including Complaint 313,
Diagnosis 321 and 315 and Problem 317 sections for Medical/surgical
department 320 of a hospital is presented in response to user
selection of CPD item 311. Complaint, section item 313 is
selectable to initiate generation of an image menu enabling a user
to enter data indicating a complaint. Diagnosis section item 315 is
selectable to initiate generation of an image menu enabling a user
to enter data indicating a financial reimbursement associated
diagnosis code (e.g., an ICD9 code). A financial reimbursement
associated diagnosis code is typically entered in individual
records of each visit for use in accurate claim preparation for
reimbursement of costs by a healthcare payer organization.
[0021] Diagnosis section item 321 is selectable to initiate
generation of image menu 350 enabling a user to enter and associate
data indicating a long term medical condition diagnosis with a
financial reimbursement associated diagnosis code. The long term
medical condition diagnosis is also associated with a patient and
with visits in section 315 and multiple encounter identifiers
identifying corresponding interactions of the patient with a
healthcare provider organization and medical conditions associated
with the encounters. The long term medical condition diagnosis is
associated with a patient and this association persists for a time
span encompassing multiple patient visits (encounters) including up
to a patient lifetime for a lifetime type medical condition
diagnosis. An encounter is used interchangeably with visit herein
and comprises a patient interaction with a healthcare organization
including an inpatient or outpatient visit, data exchange or phone
call, for example.
[0022] Image menu 350 enables a user to enter and edit data
indicating a clinical diagnosis 353 and corresponding stage 356 as
well as an initial diagnosis date 359. The staging information is
based on a user selected appropriate staging scale and source. Menu
350 also enables a user to enter and edit status 363, disease site
365 and associated comments 368. In another embodiment, a short
term medical diagnosis may also be entered. Problem section item
317 is selectable to initiate generation of an image menu enabling
a user to enter data indicating a problem.
[0023] System 10, in step 215 (FIG. 2), adaptively configures
processing in response to predetermined instruction and selected
clinical diagnosis 310. Specifically, in response to selected lung
cancer diagnosis 310, system 10 prompts a user to enter staging
information for use in identifying a cancer stage of a patient via
image menu 350. System 10 prompts a user by initiating generation
of a message for communication to a user via a display image
prompt, adding a task to a worker task list or by another method of
communication such as by pager, phone voice message or email, for
example. In an alternative embodiment, system 10 provides a user
with image menu 350 without providing a prompt message. In step 218
a user initiates an order for tests or treatments to be
administered to the patient. The order is associated with the
selected lung cancer diagnosis 310 using order entry system 35
(FIG. 1). Order entry system 35 initiates generation of display
images for presentation on workstation 12 enabling a user to place
orders. The order entry display images include user selectable
links (e.g., hyperlinks) enabling a user to access best practice
and treatment guidelines associated with a medical condition and
diagnosis. System 10 in step 223 initiates generation of a proposed
plan of care based upon the selected lung cancer diagnosis 310. The
proposed plan of care indicates a course of treatment for the
medical condition indicated by patient diagnosis 310.
[0024] System 10 provides and stores in repository 17, a lifetime
history of a clinical diagnosis. Repository 17 organizes clinically
relevant data (diagnostics, treatment, notes) in association with
an appropriate clinical diagnosis, providing a physician with a
single entry point and display image for viewing patient
information. Repository 17 associates a financial reimbursement
associated diagnosis code with a clinically relevant description
(e.g. ICD9 code) known and used by the clinicians. For example, ICD
9 174.9 is Malignant Neoplasm of the Breast. In the clinical world,
this is translated into Breast Cancer.
[0025] Financial reimbursement associated diagnosis codes and code
sets include HIPAA (Health Information Portability and
Accountability Act) compatible code sets and other code sets used
in a health care operation. Such code sets include, for example,
ICD (International Classification of Diseases) codes, 9th Edition,
Clinical Modification, (ICD-9-CM), Volumes 1, 2 and 3, as well as
ICD-10 maintained and distributed by the U.S. Health and Human
Services department. The code sets also include code sets
compatible with HCPCS (Health Care Financing Administration Common
Procedure Coding System), NDC (National Drug Codes), CPT-4.
(Current Procedural Terminology), Fourth Edition CDPN (Code on
Dental Procedures and Nomenclature). Further the code sets and
terms include code sets compatible with SNOMED-RT "Systematicized
Nomenclature of Medicine, Reference Terminology" by the College of
American Pathologists, UMLS (Unified Medical Language System), by
the National Library of Medicine, LOINC Logical Observation
Identifiers, Names, and Codes Regenstrief Institute and the Logical
Observation Identifiers Names and Codes (LOINC.RTM.) Committee,
Clinical Terms also known as "Read Codes", DIN Drug Identification
Numbers, Reimbursement Classifications including DRGs Diagnosis
Related Groups. The code sets also include code sets compatible
with CDT Current Dental Terminology, NIC (Nursing intervention
codes) and Commercial Vocabulary Services (such as HealthLanguage
by HealthLanguage Inc., by Apelon Inc.) and other code sets used in
healthcare.
[0026] FIG. 4 shows a flowchart of a process performed by system 10
for providing an overview display of patient medical condition
(e.g., as illustrated in FIG. 3) identifying both long term and
short term medical conditions. The steps of FIG. 4 may be performed
automatically. In step 402 following the start at step 401,
designation processor 25 (FIG. 1) designates an identified patient
medical condition as being long term, in response to user command.
Designation processor 25 automatically parses data representing a
patient diagnosis and identifies data indicating a potentially long
term medical condition (such as cancer, diabetes or congestive
heart failure) in the patient diagnosis (or data representing a
patient medical condition) based on a predetermined list of
potentially long term medical conditions and automatically
initiates providing a user with a prompt message prompting a user
to select a patient medical condition as being a long term medical
condition. For this purpose designation processor 25 automatically
initiates providing a user with a corresponding candidate list of
potentially long term medical conditions enabling a user to select
a particular long term medical condition for association with a
patient. Designation processor 25 associates a designated long term
patient medical condition with a particular patient. In another
embodiment, designation processor 25 automatically identifies data
indicating a potentially long term medical condition based on a
predetermined list of potentially long tern medical conditions.
[0027] In step 404 system 10 stores information in at least one
repository 17 mutually associating a designated long term patient
medical condition with a patient and with multiple patient visits
and visit/encounter identifiers identifying corresponding
interactions of the patient with a healthcare provider organization
and medical conditions associated with the encounters and with at
least one financial reimbursement related diagnosis code (e.g.,
ICD9 code) supporting reimbursement for services provided during
multiple patient visits. User interface 26 in step 407 initiates
generation of data representing a composite display image window
including data identifying a designated long term patient medical
condition and a short term patient medical condition together with
multiple patient visits (encounters) and medical conditions
associated with the encounters providing a user an overview of long
term and short term medical conditions of a patient. The identified
patient medical condition is identified from a condition
representative code in a predetermined code set, for example. The
composite display image window enables a user to associate at least
one financial reimbursement related diagnosis code supporting
reimbursement for services provided during multiple patient visits
with a text phrase representing a clinical diagnosis. User
interface 26 adaptively alters user interface data processing in
response to a patient diagnosis. For example, a designated long
term patient medical condition is cancer and user interface 26
adaptively alters user interface data processing in response to a
patient diagnosis by initiating generation of data representing a
display image element supporting acquisition of data identifying a
stage of patient cancer from physician data entry. Further, user
interface 26 also initiates generation of data representing a care
plan in response to data indicating a patient diagnosis.
[0028] In step 409, workflow processor 29 automatically initiates
prompting a user to confirm addition of a task to a task list of a
healthcare worker in response to, designation of an identified
patient medical condition as being long term and data identifying
at least one of, (a) a short term medical condition of the patient,
(b) an order for treatment to be administered to the patient and
(c) a laboratory test result of the patient. Workflow processor 29
also adaptively alters user interface data processing in response
to data indicating a patient diagnosis. Converter 15 in step 413
automatically translates a code representing the identified patient
medical condition (e.g., a financial reimbursement related
diagnosis code) to a text phrase representing the identified
patient medical condition understandable by a clinician and the
composite display image window includes the text phrase. Converter
15 also automatically translates the financial reimbursement
related diagnosis code to multiple text phrases representing
clinical diagnoses understandable by a clinician using a
predetermined map associating codes with one or more corresponding
text phrases indicating one or more clinical diagnoses. Converter
15 uses additional patient information including one or more of,
patient assessments, patient demographic data and patient record
information, to select between different text phrases indicating
one or more clinical diagnoses. The process of FIG. 4 terminates at
step 421.
[0029] The system and processes of FIGS. 1-4 are not exclusive.
Other systems, processes and menus may be derived in accordance
with the principles of the invention to accomplish the same
objectives. Although this invention has been described with
reference to particular embodiments, it is to be understood that
the embodiments and variations shown and described herein are for
illustration purposes only. Modifications to the current design may
be implemented by those skilled in the art, without departing from
the scope of the invention. System 10 is usable by different
healthcare facilities, departments and specialties in automatically
converting a financial diagnosis description of a medical condition
into clinical terminology and associating a clinical diagnosis with
a patient and multiple patient visits. The processes and
applications may in alternative embodiments, be located on one or
more (e.g., distributed) processing devices accessing a network
linking the elements of FIG. 1. Further, any of the functions and
steps provided in FIGS. 1-4 may be implemented in hardware,
software or a combination of both and may reside on one or more
processing devices located at any location of a network linking the
elements of FIG. 1 or another linked network including the
Internet.
* * * * *