System and method for using a relational database to enable the dynamic configuration of an application program

Abstract

A computer-based system for using a relational database to dynamically configure an application program easily comprises a relational database including first table means containing first data, second table means containing configuration data, and an engine coupled to the relational database for using the configuration data to configure manipulation of the first data. The engine uses the configuration data to configure the appearance of the user interface, to configure the fields being displayed, to configure the expected type of information to be received, to configure the privileges of the user, to configure the column headers, etc.

Claims

What is claimed is:

1. A method, comprising:

executing a software program having unconfigured behavior;

retrieving configuration data corresponding to the software program by the software program from a database having a database structure;

enabling dynamic configuration of a behavior of the software program by the software program in accordance with the configuration data without modifying the database structure;

obtaining non-configuration data by the configured software program; and

presenting the non-configuration data by the configured software program.

2. The method of claim 1, wherein the configuration data includes a set of items to be displayed.

3. The method of claim 2, wherein the configuration data includes a set of fields for each item.

4. The method of claim 1, wherein the configuration data includes font information.

5. The method of claim 1, wherein the configuration data includes user interface information.

6. The method of claim 1, wherein the configuration data includes order information.

7. The method of claim 1, wherein the configuration data includes version information.

8. The method of claim 1, wherein the configuration data includes preference information.

9. The method of claim 1, wherein the step of retrieving configuration data includes retrieving configuration data based on user information.

10. The method of claim 1, wherein the step of retrieving configuration data includes retrieving configuration data based on privilege information.

11. A system, comprising:

a software program having unconfigured behavior;

a database for storing configuration data corresponding to the software program, the database having a database structure; and

a processor, controlled by the software program, for enabling a behavior of the software program to be dynamically configured in accordance with the configuration data without modifying the database structure, the configured software program for obtaining, managing and presenting non-configuration data.

12. The system of claim 11, wherein the configuration data includes a table of items.

13. The system of claim 12, wherein the configuration data includes a table of fields.

14. The system of claim 11, wherein the configuration data includes font information.

15. The system of claim 11, wherein the configuration data includes user interface information.

16. The system of claim 11, wherein the configuration data includes order information.

17. The system of claim 11, wherein the configuration data includes version information.

18. The system of claim 11, wherein the configuration data includes preference information.

19. The system of claim 11, wherein the step of retrieving configuration data includes retrieving configuration data based on user information.

20. The system of claim 11, wherein the step of retrieving configuration data includes retrieving configuration data based on privilege information.

21. A system comprising:

means for executing a software program having unconfigured behavior;

software program means for retrieving configuration data corresponding to the software program means from a database, the database having a database structure; and

processor means, controlled by the software program means, for enabling a behavior of the software program means to be dynamically configured in accordance with the configuration data without modifying the database structure, the configured software program means for obtaining, managing and presenting non-configuration data.

22. A computer-readable storage medium storing program code for causing a computer to perform the steps of:

executing a software program having unconfigured behavior;

retrieving configuration data corresponding to the software program by the software program from a database having a database structure;

enabling a behavior of the software program to be dynmaically configured by the software program in accordance with the configuration data and without modifying the database structure;

obtaining non-configuration data by the configured software program; and

presenting the non-configuration data by the configured software program.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to relational databases and database engines, and more particularly provides a system and method for using a relational database to enable the dynamic configuration of an application program, and even more particularly as it relates to the health care industry.

2. Description of the Related Art

Relational databases store information in tables which are linked together using key fields. Accordingly, a first table may contain a list of available menu items, for example, Item A, Item B and Item C. Additional tables, which correspond to the first table using the menu items as key fields, may contain lists of menu item fields. That is, Item A may correspond to a second table which contains Field A and Field B, Item B may correspond to a third table which contains Field C and Field D, and Item C may correspond to a fourth table which contains Field E and Field F. The purpose of menu Item A may relate to maintaining information on individual patients, the purpose of Field A may relate to maintaining the individual patient's name, and the purpose of Field B may relate to maintaining the individual client's social security number. It will be appreciated that the second table may include other fields relating to Item A, such as birth date, birth location, height, weight, etc. The patient information entered related to each of the fields for a particular menu item is referred to as a "record." For example, the information such as name, social security number, etc. relating to the individual patient is collectively a first record.

A database engine enables a user to peruse through the relational database and enables a user to apply search parameters or indexes to locate desired information in the relational database. Using the perusal search technique, the database engine retrieves the menu items and based upon its configuration specifies, for example, the appearance of the user interface, i.e., the font, color, size and location, the technique for selecting a menu item such as Item A, etc. Upon selection of a menu item, the database engine enables a user to view, select and modify each of the fields contained in the second table, namely, Field A and Field B, as specified by its particular configuration. For simplicity, each of viewing, adding, selecting, editing, etc. is referred to as "manipulating."

Using the parametric search technique, the database engine uses its particular configuration to prompt the user for parameters indicating a desired group of menu items (such as the menu items created after a particular date). The database engine compares the menu items and the fields of each menu item contained in the relational database against the selected parameters and generates the search results. Similar to the perusal technique, the database engine displays the results to the user also based on its particular configuration.

Using the indexing technique, the database engine need not perform a search, but need only locate the proper index identifying the grouping of menu items and fields desired. Again, the database engine enables the manipulation of items, fields and records according to the particular configuration of the database engine.

Regardless of the technique being used, the database engine manipulates records according to the predetermined configuration of the database engine. That is, the database engine is preset to display the data onto the display according to the font, color, organization, etc. as indicated by the database engine program. In order to modify the configuration characteristics of the database engine, the programmer must modify the database engine program itself. However, this is quite cumbersome process and takes a significant amount of time. Thus, manufacturers have avoided customizing application programs and in particular database engines. Therefore, a system and method are needed for using relational databases to dynamically configure an application program easily.

SUMMARY OF THE INVENTION

The present invention provides a system and method for using relational database structures to dynamically configure an application program. The system comprises first retrieving means such as an activities engine, a list view engine or a search engine for retrieving configuration data. The system further comprises second retrieving means such as the activities engine, the list view engine or the search engine for retrieving desired data such as patient or transaction records. The first retrieving means and the second retrieving means may each include the same engine. The system further comprises manipulation means such as the activities engine, the list view engine or the search engine for manipulating the desired data according to the configuration data.

For example, the list view engine may retrieve the column header information specifying the information that should be presented in the patient record window. The list view engine may then retrieve the desired records, possibly based on the results of a search by the search engine, and then present the patient record window including the desired records based on the configuration information retrieved.

The configuration information may be contained in a relational database. More particularly, first table means in the relational database may contain the desired data and second table means in the relational database may contain the configuration data. Accordingly, a database engine may more easily retrieve the data, and customization of the database may be a less cumbersome process.

Another system embodying the present invention comprises a relational database containing services for identifying a case manager, a first table for containing a menu item corresponding to the case manager, a second table coupled to the first table for containing patient data corresponding to the menu item, and a third table coupled to the first table and to the second table for containing configuration data corresponding to the menu item and to the patient data. The system further comprises an engine coupled to the relational database for using the configuration data to enable a user to manipulate the menu item and the patient data.

The method comprises the steps of retrieving configuration data, retrieving desired data, and manipulating the desired data according to the configuration data. The configuration information and the desired data may be contained in a relational database.

The system and method advantageously enable easy customization of a database. Instead of forcing a particular configuration based on the configuration of the application program accessing the data in the database, the configuration data is contained separately in the database. Accordingly, a application program common to all case managers can extract configuration data from the database and can use the extracted data to configure itself, thereby facilitating the customization of the application program.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an example network system in accordance with the present invention;

FIG. 2A is a block diagram illustrating details of the Case Manager (CM) system of FIG. 1;

FIG. 2B is a block diagram illustrating details of the CM database server of FIG. 1;

FIG. 2C is a block diagram illustrating details of the CM client of FIG. 1;

FIG. 3 is a block diagram illustrating details of the CM database of FIG. 2B;

FIG. 4 is a block diagram illustrating details of the CM client engine of FIG. 2C;

FIG. 5 is a block diagram illustrating details of the CM database creator of FIG. 1;

FIG. 6A is table illustrating an activity template;

FIG. 6B is a table illustrating an activity template field of an activity;

FIG. 6C is a table illustrating a field description of an activity template field;

FIG. 7 is a table illustrating activity records for the MEDS activity and the DISPOSITION activity;

FIG. 8A is a display screen view of a patient menu window;

FIG. 8B is a display screen view of a patient record of FIG. 8A;

FIG. 8C is a display screen view of a patient record edit window;

FIG. 8D is a display screen view of an activity pick-list menu;

FIG. 8E is a display screen view of the activity list field for the MEDICATION SUMMARY activity;

FIG. 8F1 is a display screen view of a generic search window;

FIG. 8F2 is a display screen view of a provider search window;

FIG. 8F3 is a display screen view of an advanced search window;

FIG. 8G is a display screen view of a medication record edit window;

FIG. 8H is a display screen view of a group provider screen window;

FIG. 8I is a display screen view of a resulting care plan;

FIG. 8J is a display screen view of a questionnaire;

FIG. 9 is a flowchart illustrating a method for generating a relation database configuration table;

FIG. 10 is a flowchart illustrating a method for using the configuration tables to configure an application program;

FIG. 11 is a flowchart illustrating a method for using the configuration tables to enable viewing data stored in the relational database; and

FIG. 12 is a flowchart illustrating a method for using the configuration tables to enable entering data into the relational database.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 is a block diagram illustrating an example network system 100 in accordance with the present invention. Network system 100 comprises a doctor 105 in communication with case managers 115 (i.e., persons who track the care of patients) via a first communications channel 110 such as a telephone line. The case managers 115 access a Case Manager (CM) system 125 via a second communications channel 120 such as a conventional graphical user interface. The CM system 125 includes a CM database server 130 and CM clients 135. The CM database server 130 stores a CM database 155, which contains configuration data 310 (described in detail with reference to FIG. 3) for configuring the CM clients 135 and patient data 305 (also described in detail with reference to FIG. 3). Further, a CM database creator 140 is coupled via a third communications channel 145 to the second communications channel 120, and enables the creation of the CM database 155 including the creation of the configuration data 310. One skilled in the art will recognize that communications channels 110, 120 and 145 may all be components of a single network system such as the Wide Area Network (WAN) commonly referred to as the Internet.

For example, a patient (not shown) goes to the doctor 105 complaining of specific symptoms, and the doctor 105 recommends a responsive care plan. The doctor 105 then contacts a case manager 115 assigned to this patient. The case manager 115 accesses the case manager system 125 to compare the doctor's recommendations against standard medical guidelines and against the patient's medical history, to prepare a response to the doctor 105, for example, accepting the care plan or recommending another, and to record the event. Because the configuration data 310 is stored in the CM database 155, the CM client 135 may be configured at run-time, i.e., during the boot-up of the client 135. It will be appreciated that the client 135 may be configured to authenticate the user, provide access to only a corresponding set of functions, provide access to only a corresponding list of patient records, display selected data in a desired arrangement, etc.

FIG. 2A is a block diagram illustrating details of the CM system 125, which includes a CM database server 130 coupled via a Local Area Network (LAN) 210 to, for example, four CM clients 135. The CM database server 130 includes a CM database 155, preferably maintained in a relational database format and preferably storing patient data 305 and configuration data 310 (each described in detail with reference to FIG. 3). As illustrated, the CM database server 130 may be stored remotely from CM clients 135. Each of the CM clients 135 may access the CM database 155, for example, to review the patients medical history or to review the conventional medical guidelines. Each CM client 135 will be configured according to the configuration data 310 stored in the CM database 155 and thus will maintain a consistent appearance regardless of which terminal the case manager 115 uses.

FIG. 2B is a block diagram illustrating details of the CM database server 130 including a Central Processing Unit (CPU) 215 such as an Intel Pentium.RTM. microprocessor or a Motorola Power PC.RTM. microprocessor. An input device 220 such as a keyboard and mouse, and an output device 225 such as a Cathode Ray Tube (CRT) display are coupled via signal bus 230 to CPU 215. A communications interface 235, a data storage device 240 such as a magnetic disk, and memory 245 such as Random Access Memory (RAM) are further coupled via signal bus 230 to CPU 215. The communications interface 235 is coupled to communications channel 150 (FIG. 1), which may in turn be coupled to LAN 210 (FIG. 2A).

An operating system 255 includes a program for controlling processing by CPU 215, and is typically stored in data storage device 240 and loaded into memory 245 (as illustrated) for execution. The CM database 155 is stored in data storage device 240, but may alternatively be stored in memory 245. A database server engine 250 for accessing the CM database 155 may also be stored in data storage device 240 and loaded into memory 245 (as illustrated) for execution by CPU 215. Since the CM database 155 is being maintained as a relational database, the database server engine 250 preferably performs relational database management techniques for storing, searching and retrieving data from the tables of the CM database 155.

FIG. 2C is a block diagram illustrating details of an example CM client 135, which includes a CPU 260 such as an Intel Pentium.RTM. microprocessor or a Motorola Power PC.RTM. microprocessor. An input device 265 such as a keyboard and mouse, and an output device 270 such as a CRT display are coupled via signal bus 275 to CPU 260. A communications interface 280, a data storage device 285 such as a magnetic disk, and memory 290 such as RAM are further coupled via signal bus 275 to CPU 260. The communications interface 280 is coupled to communications channel 150 (FIG. 1), which may in turn be coupled to LAN 210 (FIG. 2A).

An operating system 297 includes a program for controlling processing by CPU 260, and is typically stored in data storage device 285 and loaded into memory 290 (as illustrated) for execution. A CM client engine 293 for managing the CM database 155 remotely may also be stored in data storage device 285 and loaded into memory 290 (as illustrated) for execution by CPU 260.

FIG. 3 is a block diagram illustrating details of the CM database 155. The CM database 155 contains patient data 305, which includes patient records for each of the patients assigned to the case managers 115 accessing the particular database 305. The patient data 305 is preferably maintained in a relational database format, and may be divided into common records and extension records. The division of data 305 into common and extension records is described in detail with reference to FIG. 7.

The CM database 155 further includes configuration data 310. The configuration data 310 contains information indicating the menus, activities, records, etc. available to the case manager 115 accessing the CM database 155. The configuration data 310 may further include information indicating the fields to be included in each of the menus, activities, records, etc. Accordingly, the configuration data 310 controls the data needed for input, display and modification of patient records 305, field descriptions and dialog fields. The configuration data 310 is also preferably maintained in a relational database format, i.e., in tables. Examples of the configuration data 310 are illustrated in FIGS. 6A, 6B, 6C and 7.

The CM database 155 further includes clinical support data 315. The clinical support data 315 includes information available for comparison with the medical care plan recommended by the doctor 105. Examples of clinical support data 315 include conventional clinical guidelines and code sets for addressing the patient's symptoms.

FIG. 4 is a block diagram illustrating details of the CM client engine 293. The CM client engine 293 includes a list view engine 405, security services 410, an activities engine 415, a clinical support data reader 420, an import/export engine 425, a search engine 430, a questionnaire engine 435 and a case assignment engine 440. Although each of these elements is illustrated as coupled to a signal bus 445, one skilled in the art will recognize that the connections are merely software based.

The security services 410 identify and authenticate the case manager 115 accessing the CM database 155, for example, using a case manager identification number and a password. Upon authentication, the security services 410 obtain the configuration data 310 indicating the menus, activities, patients, etc. corresponding to the case manager's privileges. The security services 410 allow easy ad hoc specification of individual roles and group memberships, as well as the specification of privileges (based on role and group membership) with respect to entry, edit and view. The security services 410 are then used to enforce the security privileges. An example group privileges screen 890 is illustrated in FIG. 8H. Namely, the group "authorization nurses" lists the case managers 115 authorized to access the CM database 155. The role indicates whether the case manager 115 is a subscriber or owner (each providing different privileges. The function list indicates the available functions that the case manager 115 can access. Selecting a case manager 115 function provides in the privileges window 891 a list of actions authorized to the case manager 115.

The clinical support reader 420 enables the case manager 115 to read the clinical support data 315, and to compare the clinical support data 315 against the doctor's recommended care plan. After the case manager 115 compares the clinical support data 315 and the recommended care plan, the case manager 115 can generate a resulting care plan. An example resulting care plan is illustrated in FIG. 8I.

The questionnaire engine 435 enables the case manager 115 to prepare a report of the patient's symptoms. For example, the questionnaire engine 435 lists possible questions to ask the patient, and enables the case manager 115 to input the responses into a questionnaire screen. An example questionnaire screen 894 is shown in FIG. 8J. The questionnaire screen 894 is configurable using the configuration data 310 described with reference to FIG. 3 and with reference the remaining figures.

The search engine 425 enables the case manager 115 to prepare a query for searching the CM database 155. Preferably, the search engine 430 dialogs the case manager 115 for search parameters and compiles the parameters into an SQL query. An example generic search window 884 is illustrated in FIG. 8F1. An example provider search window 886 is illustrated in FIG. 8F2. An example advanced search window 888 is illustrated in FIG. 8F3. The search engine 430 then communicates with the database server engine 250, which searches the CM database 155. For example, the case manager 115 may select the parameters for the patients assigned to case manager John Smith and admitted to James Hospital after Jan. 1, 1997.

The list view engine 405 enables the case manager 115 to view lists of records of the patient data 305 assigned to the case manager 115 according to the search results of the search engine 430. The list view engine 405 uses the configuration data 310 to configure the user interface and the data being displayed. The list view engine 405 preferably operates entirely on dynamically defined data determining the content, column headers, sort and filter qualities of each list at run-time.

The case assignment engine 440 examines the case data and determines which case manager 115 should be given the assignment. The determination may be made based on the patient, the hospital, available case manager staff, the date admitted, etc. The case assignment engine 440 can be configured to use a parameter such as any fields from the case, for example, case, patient and assessment tabs (including customized data) along with a number of comparison and arithmetic operators.

The activities engine 415 determines which activities such as medication summaries, patient discharge summaries, assessment results, care plan variance summaries, etc. exist, determines which activities are available, enables the case manager 115 to select one of the available activities, enables the case manager 115 to select one of the available activity fields such as the start date of a medicinal program, enables the case manager 115 to enter new data into the activity record, etc.

The import/export engine 425 translates records to and from another format, such as the Health Level Seven format or the ANSI X.12 format. The import/export engine 425 can import and export base and customized data (i.e., data defined by a customer and not known to the application prior to run-time). The import/export engine 425 preferably uses mapping tables. Should any additional configuration data 310 be needed, the import/export engine 425 either requests the information from the user or uses predetermined default values. If the original format has additional data unnecessary for the intended format, the import/export engine 425 discards the data 310.

It will be appreciated that the elements of the CM client engine 293 are configured according to the configuration data 310. That is, the activities engine 415 may retrieve configuration data 310 specifying, for example, the available activities, configuration data 310 indicating the fields in each activity, configuration data 310 indicating predetermined characteristics of the user interface, e.g., the location for viewing the available activities, the order the activities are placed, etc. Examples of the configuration data 310 are shown in FIGS. 6A, 6B,6C and 7. Examples of screen shot views of the user interface are illustrated in FIGS. 8A, 8B, 8C, 8D and 8E. The activities engine 415 effectively retrieves the configuration data 310 from the tables of the CM database 155.

The tables being used to implement the elements of the CM client engine 293 of FIG. 4 are listed.

        Tables for Activities Engine
        Activity
        activityId         templateName       templateVersion      whenEntered
               author
        ActivityTemplate
        templateName       templateVersion    description          category
               calendarFlag
        ActivityTempltFld
        templateName       templateVersion    tabOrder             fieldName
               controlType
        FieldDescription
        fieldName          abbrLabel          shortLabel           longLabel
               locationType
        DialogFields
        dialogId           fieldId            fieldName            labelType
               fieldType
        Tables for Questionairre Engine
        Questionnaire
        qstnnId            qstnnType          qstnnHdrFntName
     qstnnftdrFntSzQty      qstnnHdrFntClrId
        QuestionnaireType
        qstnnTypeId        qstnnTypeName      qstnnTypeInsertTs
        QinQ
        qstnnId            qstnTd             qInOrderQty
     qinqAnsSQLColName      qInQInsertTS
        Question
        qstnId             qstnType           qstnLeftId           qstnRightId
               qstnText
        QuestionType
        qstnTypeId         qstnTypeName       qstnTypeInsertTS
        ControlType
        controlTypeId      controlTypeName
        DataType
        dataTypeId         dataTypeName       dataTypeInsertTS
        SkipAction
        qstnId             domExtId           skipSectionInd
     skipToQuestionId       skipInsertTS
        Domain
        domainId           domainName         domainDataType
     domainScaleQty         domainWidthQty
        DomainExtension
        domExtId           domainId           domExtOrderQty
     domExtInsertTS         domExtCaptionText
        Tables for Security Services
        CaseManager
        cmId               nameLast           nameFirst            loginId
               cmDeactivatedFlag
        GroupMembership
        cmld               secGroupId         grpMemAssignedById
     grpMemInsertTS
        GroupRole
        secGrpRoleId       secRoleId          secGroupId
     grpRoleInsertTS
        GrpRolePriv
        secGrpRoleId       privCtxtId         grpRolPrivInsertTS
        PrivilegeForContext
        privCtxtId         privCtxtDbId       secContextId
     secContextDbId         secPrivilegeId
        ValidPrivilege
        secRoleId          privCtxtId         valPrivInsertTS
        SecurityContext
        secContextId       secContextDbId     secContextName
     secContextTxt          secSubContextName
        SecurityGroup
        secGroupId         secGroupDbId       secGroupName
     secGroupInsertTS       secGroupUndeleteFlag
        SecurityPrivilege
        secPrivilegeId     secPrivilegeDbId   secPrivilegeName
     secPrivilegeTxt        secPrivilegeInsertTS
        SecurityRole
        secRoleId          secRoleDbId        secRoleName
     secRoleDisplayTxt      secRoleInsertTS
        Tables for List View Engine
        ListViewColumns
        name               colOrder           colName              header
               showit
        ListViewQuery
        name               description        category             selFrom
               selWhere
        MenuConfiguration
        mcId               mcText             mcTypeName
     mcContextName          mcApplicCtxtName
        Tables for Case Assignment Engine
        TriageRule
        Sequence           cmId               status
     trulReqApproveFlag
        TriageRuleItem
        Sequence           ColName            RuleItem
        TriageRuleModel
        Sequence           Hard               RuleColumnName       TableName
               FieldName
        Tables for Search Engine
        ProviderMaster
        ConfigTables.doc
        pvdrMstrId         providerId         panelId              whenAltered
               whenModified
        ExtendedInfo
        providerId         panelId            infoName             infoValue
        ValidValues
        validName          validValue         vvalSeqQty
        code_table
        proc_code          code_description
        Tables for Clinical Support Data Reader (Care Plan Wizard)
        CarePlanTemplate
        name               description        comments             guideline
    CarePlanActivities
    name sequence templateName quantity startDateIx startDelta repeatDateIx
     repeatDelta calendarFlag checkOffFlag cost descriptio
    Tables for Import/Export Engine
    ImportDataMap
    Idx Msg Evt Segment FieldNum Rep Type SubTypeID TranTbIID Entity Container
     Width Offset CrtFlag
    ImportRules
    Idx RuleID Entity Container Literal Operator
    ExportDataMap
    Idx Msg Evt Segment FieldNum Rep Type SubTypeID TranTbIID Entity Container
     Width Offset CrtFlag RuleID
    ExportRules
    Idx RuleID Entity Container Literal Operator
    TranslationMap
    Idx TableID KeyTxt LiteralTxt OperatorTxt

• Inventors
  Evans, Arnold Kerry; Peters, John Martin; Barker, Dwight John; Weinberger, William Keith; Barnum, William Goodell; Chu-hu, Jennifer; West, David E.; Cordero, Joseph Rommel; Ledbury, Mary J.;
• Assignee
  PhyCom Corporation (Bellvue, WA)
• Published
  Jul-24-2001
• Current US Classes:
  705/3
  707/104.1
  707/3
• Application #
  946282
• International Classes
  G06F 019/00; G06F 017/30
• Field of Search
  707/3 707/4 707/5 707/6 707/2 707/100 707/102 707/200 707/104 705/3
• Examiner
  Kulik; Paul V.
• Agent
  Squire, Sanders & Dempsey L.L.P.
• US Patent References:
  5369778
  5432931
  5434971
  5446575
  5566330
  5583758
  5621884
  5727158
  5784635
  5802511
  5809266
  5900870
  5950190