WO2013066985A2

WO2013066985A2 - A system and method of managing healthcare operations in a healthcare enterprise

Info

Publication number: WO2013066985A2
Application number: PCT/US2012/062764
Authority: WO
Inventors: Parag Gadkari
Original assignee: Quadramed Corporation
Priority date: 2011-10-31
Filing date: 2012-10-31
Publication date: 2013-05-10
Also published as: WO2013066985A3

Abstract

A system and method of managing healthcare operations in a healthcare enterprise which minimizes redundancy and manual effort across the enterprise. An example method includes creating a first node representative of a corporate level of a node-based hierarchy, creating second nodes under the first node, the second nodes being representative of the healthcare facilities; and creating third nodes under the second nodes, the third nodes being representative of devices within the healthcare facilities, activating workflows and dictionaries at the healthcare facilities under the first node and the second nodes, and activating and provisioning the devices under the third nodes.

Description

A SYSTEM AND METHOD OF MANAGING HEALTHCARE

OPERATIONS IN A HEALTHCARE ENTERPRISE

BACKGROUND OF THE INVENTION

[0001] The present invention relates to healthcare systems, and more specifically to a system and method of managing healthcare operations in a healthcare enterprise.

[0002] Patients go to health care providers for treatment of health problems. Health care providers include physicians, technicians, and other healthcare personnel and the facilities they work in, including offices, clinics, and hospitals. A patient visit to a provider is known as an encounter.

[0003] Healthcare facilities often have the need for different operations at different locations within the facilities and/or for different campuses in a chain of healthcare facilities.

[0004] The need for different operations at different locations has typically led to separate or independent healthcare systems at different locations. However, separately managing operations at different facilities using different systems is difficult and inefficient.

[0005] Therefore, it would be desirable to provide a system and method of managing healthcare operations in a healthcare enterprise that overcomes these problems.

SUMMARY OF THE INVENTION

[0006] A system and method of managing healthcare operations in a healthcare enterprise is provided.

[0007] An example method includes creating a first node representative of a corporate level of a node-based hierarchy, creating second nodes under the first node, the second nodes being representative of the healthcare facilities; and creating third nodes under the second nodes, the third nodes being representative of devices within the healthcare facilities, activating workflows and dictionaries at the healthcare facilities under the first node and the second nodes, and activating and provisioning the devices under the third nodes.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Fig. 1 is a block diagram of a healthcare system;

[0009] Fig. 2 is a block diagram of a healthcare system enterprise hierarchy;

[0010] Fig. 3 is a screen of enterprise management software 22 illustrating selections at a corporate node level;

[0011] Fig. 4 is a screen of enterprise management software 22 illustrating selections at a group node level;

[0012] Fig. 5 is a screen of enterprise management software 22 illustrating selections at an organization node level; and

[0013] Fig. 6 is a screen of enterprise management software 22 illustrating selections at a device node level.

DETAILED DESCRIPTION OF THE DRAWINGS

[0014] With reference to Fig. 1, an example healthcare management system 10 includes enterprise server 12 and facility healthcare systems 14.

[0015] Enterprise server 12 executes enterprise manager software 20, which includes a software module for creating enterprise hierarchies to centrally manage dictionaries 40, workflows 42, and device provisioning at different places within a facility and/or at different facilities within a chain of facilities. For example, enterprise manager software 20 may activate or deactivate workflows 40 and dictionaries for each facility.

[0016] Device provisioning defines computers 36 and the configuration necessary to allow computers 36 to perform their intended functions. For example, provisioning may include establishing network protocols and credentials for accessing healthcare information within healthcare information system 32.

[0017] Workflows 40 are software objects which include procedural steps based upon rules. The procedural steps are implemented and appear to a user as a flow of different software generated screens. Each screen presents information or requires input associated with a step in the workflow. An example workflow includes a patient check-in workflow which takes a patient through a series of steps including patient identification steps compliant with the Health Insurance Portability and Accountability Act of 1996 (HIPAA).

[0018] Dictionaries 42 store data about data in healthcare information system 32. Dictionaries 42 may include meta-data.

[0019] Enterprise manager software 20 may include additional modules including, but not limited to, a dictionary module for creating and maintaining dictionaries 42, a workflow module for creating and maintain workflows 40, a device manager for device provisioning, and a language module for managing language preferences at each facility.

[0020] Enterprise server 12 may include one or computers, each including a processor, memory, and program and data storage. Enterprise server 12 may further be part of one of the facility healthcare systems 14. Enterprise server 12 may execute an operating system such as a Microsoft operating system. Enterprise server 12 may execute other computer software that may be stored in a computer readable medium, such as a memory.

[0021] Enterprise server 12 further includes network circuitry for connecting to network 50. Network 50 may include any combination of wireless or wired networks, including a global communication network, also known as the Internet. Network 50 may include a local or wide area network portion shared by facility healthcare systems 14.

[0022] In an example embodiment, enterprise server 12 may include a World Wide Web or "web" server with addresses for web sites for delivering web pages. Healthcare administrators may interact with enterprise server 12 using computers equipped with browser software, such as Microsoft Internet Explorer software.

[0023] Facility healthcare systems 14 are located at different places within a healthcare facility and/or at different healthcare facilities in a chain of healthcare facilities. Healthcare facilities may include a front desk, a lounge, offices, and examination rooms.

[0024] An example facility healthcare system 14 primarily includes health care information system 32, customer value management (CVM) system 34, and one or more computers 36.

[0025] Healthcare information system 32 stores patient information including patient records and patient appointment schedules in one or more databases.

[0026] Healthcare information system 32 may be located at the healthcare facility or may be external to the healthcare facility. [0027] CVM system 34 matches patient information to patient identifying information presented by patients during check-in and determines workflows 40 based upon patient appointment schedules.

[0028] CVM system 34 performs the matching process in a way that is compliant with a local security policy. The local security policy typically complies with HIPAA. The local security policy may require that certain types of identifying information be presented by a patient during a visit to a healthcare provider facility, and that a potential match between the information presented by the patient and information in patient records in healthcare information system 32 satisfy a minimum confidence level. The security policy can be defined at any level, including specific documents, forms, specific elements of a document/form, and can be specialized for the type of access, including viewing, creating, updating, deleting, and versioning.

[0029] In an example local security policy, a patient may be required to provide his/her name, phone number, and date of birth. CVM system 34 uses this information to find a corresponding patient record in healthcare information system 32.

[0030] Workflows 40 are tailored to reasons for patient visits. In an example encounter, CVM system 34 may determine that a patient has an appointment for a blood sugar test and determine a corresponding workflow 40 for the blood sugar test. For a walk-in, CVM system 34 examines the purpose of the visit entered by the patient and identifies a workflow 40 based on the purpose.

[0031] CVM system 34 may also be located at the healthcare facility or may be external to the healthcare facility. If healthcare information system 32 is located externally, CVM system 34 may access healthcare information system 32 using several methods, including one or more network protocols, and optionally higher level protocols for messaging and file transfer. A common standard for exchanging healthcare data between health care information systems 32 is HL7. CVM system 34 can receive patient information and schedule information via messages formatted in HL7 from health care information system 32. Alternatively, it can receive patient information via a flat file in a comma separated value (CSV) format.

[0032] Computer 36 may include one or more computers intended for patient use, provider use, or both, or intended for a particular purpose. Computer 36 executes transaction software 48, which patients and healthcare providers use to complete tasks. Facility healthcare systems 14 may include computers 36 at reception areas, at front desks, in provider offices, and in examination rooms.

[0033] An example computer 36 may include a self-service kiosk. The kiosks may be located in the lounge, or near an entrance to the healthcare facility.

[0034] A corresponding example transaction software 48 may include self- service check-in software which implements a patient check-in workflow 40 based upon the reason for the patient visit. The self-service check-in software causes a sequence of screens to be displayed by the kiosk in accordance with the workflow 40.

[0035] Another example computer 36 includes a tablet computer used by physicians or other healthcare providers.

[0036] In an example embodiment, facility healthcare system 14 may include a web server with addresses for web sites for delivering web pages. Patients may interact with facility healthcare system 14 using their own smart phones, tablets, or home personal computers through network 50. For example, a patient may perform a remote check-in procedure using a smart phone by connecting to a corresponding facility healthcare system 14 through network 50. An example connection may include a web-based portal connection using the Hypertext transfer Protocol Secure (HTTPS).

[0037] Computers 36 may each include a processor, memory, and program and data storage. Computers 36 may execute an operating system and other computer software that may be stored in a computer readable medium, such as a memory. Computers 36 may additionally include peripherals necessary to their purpose, including but not limited to, a display, input device, a card reader, a biometric reader, and a printer.

[0038] Healthcare information system 32 and CVM system 34 may be combined into a single computer. One or more of the systems may be combined with other information systems or may be absent based on specific circumstances.

[0039] In an example patient encounter, a patient visiting a healthcare provider office has an appointment. The patient walks up to a kiosk. The kiosk executes patient check-in software to obtain patient identifying information. The patient check-in software interacts with CVM system 34 to complete the patient record identification procedure. CVM system 34 positively identifies the patient record in healthcare information system 32. The patient check-in software interacts with CVM system 34 to obtain a workflow 40 based upon the details of the patient's appointment in the patient's record. The patient check-in software then executes the workflow 40.

[0040] With reference to Fig. 2, an example enterprise hierarchy 60 is illustrated. In this example embodiment, enterprise manager software 20 uses a node-based enterprise hierarchy 60 to manage and monitor operations, including creating and managing nodes and managing workflows 40, dictionaries 42, and language options, at different locations and/or at different facilities.

[0041] Primary types of nodes in enterprise hierarchy 60 may include a corporate node 62, an organization node 66, and a device node 68.

[0042] Corporate node 62 is the top level. Corporate node 62 may represent a main office or corporate headquarters for a chain of healthcare facilities. Workflows 40, dictionaries 42, and language options can be defined at this level. A healthcare administrator may manage exception logs and audit logs from corporate node 62.

[0043] Organization node 66 may represent a particular facility in the chain of healthcare facilities. For example, a particular clinic may appear as an organization node 66. Workflows 40, dictionaries 42, and filters establishing limits on organizations may be defined at the organization node level.

[0044] Device node 68 may represent one or more devices provisioned to complete particular functions. Device provisioning is an important feature of device node 68. Device nodes 68 tied to a common organization node 66 indicate that the device nodes 68 all share the same provisioning.

[0045] For example, a particular computer 36 for completing a check-in process within a facility may appear as a device node 68 under an organization node 66 associated with a facility. As another example, another computer 36 for completing a check-out process may appear as another device node 68 under the facility's organization node 66.

[0046] Enterprise hierarchy 60 may additionally include a group node 64 representing a grouping of organization nodes. Group node 64 may be used by an administrator to group a set of facilities that have common properties, filters, and dictionaries 42. For example, an administrator may create a group node 64 to include facilities in a state or other location that use the same predetermined set of dictionaries 42. Each facility appears as an organization node 66 under the group node 64. Workflows 40 cannot be defined at the group level.

[0047] Enterprise manager software 20 displays information based upon the properties of a selected node from enterprise hierarchy 60. As a general rule, lower level nodes may inherit workflows 40, dictionaries 42, and other properties of higher level nodes unless overridden by administrator settings at the lower level nodes.

[0048] Advantageously, enterprise manager software 20 provides healthcare administrators with the ability to easily manage different properties of devices and organizations within a healthcare enterprise while at the same time minimizing redundancy and manual effort across the enterprise.

[0049] With reference to Fig. 3, an example screen 70 showing selections available at a corporate node 62 are illustrated.

[0050] At this node level, enterprise management software 22 has available selections including dictionary manager 80, language manager 82, workflow manager 84, device manager 86, exception log 88, and audit log 90. [0051] Dictionary manager 80 allows an administrator to add, delete, edit, activate, and deactivate a dictionary 42.

[0052] Language manager 82 allows an administrator to set language preferences.

[0053] Workflow manager 84 allows an administrator to add, delete, edit, and activate a workflow 40.

[0054] Device manager 86 allows an administrator to add, delete, and edit a device and its provisioning.

[0055] With reference to Fig. 4, an example screen 100 showing selections available at a group node 64 are illustrated.

[0056] At this node level, enterprise management software 22 has available selections including dictionary manager 80 and group properties 92.

[0057] Selection of properties 92 allows an administrator to create, delete, activate, or deactivate a group, including giving the group a name, identifying a parent of the group, and setting filters limiting the group.

[0058] In this example, the group is all facilities in the state of North Carolina and the group name is "North Carolina". The parent of the group is corporate node 62 or "Corporate". Additional groups of facilities are also defined by state names.

[0059] With reference to Fig. 5, an example screen 110 showing selections available at an organization node 66 are illustrated.

[0060] At this node level, enterprise management software 22 has available selections including dictionary manager 80, workflow manager 84, and group properties 92. [0061] Selection of properties 92 allows an administrator to create, delete, activate, deactivate, open or close, and define language options for an organization, including giving the group a name, an organization code, and setting filters limiting the organization. The organization address and time zone may also be entered.

[0062] In this example, the organization is a facility in Huntersville, North Carolina, and the organization name is "Huntersville". If there were more than one facility in Huntersville, each facility would appear with a unique organization name.

[0063] With reference to Fig. 6, an example screen 120 showing selections available at a device node 68 are illustrated.

[0064] At this node level, enterprise management software 22 has available selections including workflow manager 84, device manager 86, and group properties 92.

[0065] Selection of properties 92 allows an administrator to create, delete, activate, deactivate a device, including giving the device a name, identifying a parent, and setting filters limiting the device.

[0066] In this example, the device is a kiosk provisioned to complete a check- in process at the Huntersville facility, and the device name is "Huntersville Check-in". If there were more than one device at the Huntersville facility, each device would appear with a unique device name.

[0067] A healthcare administrator at a corporate level may use enterprise management software 20 to manage an enterprise of healthcare facilities. Enterprise management software 20 may create a corporate node 62 at the top of the enterprise under administrator control. Enterprise management software 20 can create and manage workflows 40 and dictionaries 42 and monitor exception logs and audit logs for errors that propagate from facility healthcare systems 14 lower node levels.

[0068] Enterprise management software 20 may create organization nodes 66 for each facility under administrator control, using filters to uniquely define and limit the organization nodes 66. The administrator may manage workflows 40 and dictionaries 42, including workflows 40 and dictionaries 42 unique to each facility.

[0069] Enterprise management software 20 may further create group nodes

64 under administrator control, each group node 64 containing groups of facilities with one or more common properties, filters, and dictionaries 42. The administrator may manage workflows 40 for the groups of facilities.

[0070] Enterprise management software 20 may define device nodes 68 within each organization node 66 and provision each device under administrator control.

[0071] Advantageously, enterprise manager software 20 provides healthcare administrators with the ability to easily manage different properties of devices and organizations within a healthcare enterprise while at the same time minimizing redundancy and manual effort across the enterprise.

[0072] Although particular reference has been made to certain embodiments, variations and modifications are also envisioned within the spirit and scope of the following claims.

Claims

What is claimed is:

1. A computerized method of managing an enterprise of healthcare facilities comprising:

creating a first node representative of a corporate level of a node-based hierarchy;

creating second nodes under the first node, the second nodes being representative of the healthcare facilities; and

creating third nodes under the second nodes, the third nodes being representative of devices within the healthcare facilities;

activating workflows and dictionaries at the healthcare facilities under the first node and the second nodes;

and activating and provisioning the devices under the third nodes.

2. The method of claim 1, further comprising:

creating a fourth node between the first node and the second nodes, the fourth node being representative of a group containing predetermined healthcare facilities; and

activating workflows at the predetermined healthcare facilities within the group under the fourth node.