Patent Grant
9539155
The present disclosure relates to a patient support apparatus, and particularly, to a patient support apparatus and a control system configured to control various functions of the patient support apparatus. More particularly, the present disclosure relates to a control system configured to control interaction between caregivers, patients, and service providers regarding the use and implementation of features included in the patient support apparatus.
It is known to provide patient support apparatuses that are configured to provide various features and therapies which caregivers and patients may desire to use. The cost of a patient support apparatus having many features and therapies available may be significant to the caregiver or patient. As a result, caregivers and patients may rent such patient support apparatuses for the limited times such features and therapies are needed. As a result, scheduling, shipping, and service of the patient support apparatus must be managed and coordinated.
It is also known to adjust features and therapies of the patient support apparatuses in the event maintenance or patient care necessitates such changes. When such an adjustment is needed, service providers often send a technician to the patient support apparatus to make adjustments. In the event of a maintenance event, the technician may enable alternative therapies or features until the desired feature or therapy is repaired. In the event of patient care calls for a change, the technician may enable the desired feature or therapy or provide an alternate therapy where patient care may be maximized as a result.
It is also known that certain therapies and features may not be covered by a patient's insurance provider. As a result, a caregiver may enable a feature or therapy which is not reimbursable by the insurance. Such cost may not be readily chargeable back to the patient and costs to the caregiver and patient are not optimized.
It is also know that billing of patients and caregivers for the time features and therapies are actually in use is inaccurate due to the limited availability of information. Caregivers and patients may be billed from the time the patient support apparatus is delivered from the service provider to the time the patient support apparatus is returned to the service provided. Caregivers may also be billed from the time a technician enables a feature or therapy to the time patient support apparatus is reconfigured for another patient. As a result, billing is inaccurate and inefficient.
The present application discloses one or more of the features recited in the appended claims and/or the following features which, alone or in any combination, may comprise patentable subject matter:
According to a first aspect of the present disclosure, a system comprises a first patient support apparatus having a plurality of devices that are independently operational and a server spaced apart from the patient support apparatus. Each of the plurality of devices provides a distinct therapy to a patient supported on the patient support apparatus. The patient support apparatus includes a control system operable to enable or disable each independently operational device under software control. The server is in communication with the control system of the first patient support apparatus. The server is operable to provide instructions to the control system to enable or disable one or more of the plurality of devices.
In some embodiments, the server is in communication with a computer device at a service provider operable to provide information to the server regarding approved therapies for the first patient support apparatus.
In some embodiments, the server is operable to request approval for a therapy to be enabled on the first patient support apparatus from the service provider through the computer device.
In some embodiments, the first patient support apparatus includes a user input device coupled to the control system, the user input device operational to receive a user input requesting enablement or disablement of a therapy device and communicate the request to the server.
In some embodiments, the server is operable to transmit an authorization of the instructions to the control system to enable or disable the device.
In some embodiments, the server is in communication with a hospital information system, the hospital information system operational to receive a user input requesting enablement or disablement of a therapy device and communicate the request to the server.
In some embodiments, the server is operable to transmit an authorization of the instructions to the control system to enable or disable the devices through the hospital information system to the control system.
According to another aspect of the present disclosure, a patient support apparatus comprises a controller including a processor in communication with a memory device, a plurality of features under control of the controller, and a plurality of user inputs in communication with the controller. The user inputs are operable to provide a signal to the controller indicative of a user input requesting enablement or disablement of at least one of the features. The memory device includes instructions that, when executed by the processor, cause the processor to detect a signal from one the user inputs indicative of a requested change in the operational state of at least one of the features. The memory device includes further instructions that, when executed by the processor, cause the processor to transmit the request for a change in the operational state of at least one of the features to an authorization entity. The memory device includes further instructions that, when executed by the processor, cause the processor to monitor for a signal from the authorization entity that the change in the operational state of at least one of the features is permitted. The memory device includes further instructions that, when executed by the processor, causes the processor to, if the change in the operational state of at least one of the features is permitted, log the request, and enable the feature.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to activate the feature.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to, if the requested change in the operational state of at least one of the features is not permitted, communicate the denial of the request.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to monitor for a signal from the authorization entity indicative that an alternative feature is permissible, and, if an alternative feature is permissible, communicate the permissible alternative feature to the requester.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to determine if the permissible alternative feature is an acceptable substitute, and, if the alternative feature is an acceptable substitute, log the feature request.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to activate the alternative feature.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to monitor for deactivation of the feature. The memory device includes further instructions that, when executed by the processor, causes the processor to, if the feature is deactivated, transmit a signal that the deactivation has occurred to the authorization entity. The memory device includes further instructions that, when executed by the processor, causes the processor to monitor for a signal from the authorization entity authorizing deactivation of the feature. The memory device includes further instructions that, when executed by the processor, causes the processor to, if the signal from the authorization entity authorizing deactivation of the feature is received, deactivate the feature.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to transmit information regarding the usage of a feature to a third party to be used to establish a bill for use of the feature.
According to yet another aspect of the present disclosure, a patient support apparatus comprises a controller including a processor in communication with a memory device, a plurality of features under control of the controller, and a plurality of user inputs in communication with the controller. The user inputs are operable to provide a signal to the controller indicative of a user input requesting enablement or disablement of at least one of the features. The memory device includes instructions that, when executed by the processor, cause the processor to detect the occurrence of an event. The memory device includes further instructions that, when executed by the processor, causes the processor to determine whether to log the event. The memory device includes further instructions that, when executed by the processor, causes the processor to determine the nature of the event. The memory device includes further instructions that, when executed by the processor, causes the processor to respond to the event by communicating the event occurrence to a computer system resident at a third party.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to determine the nature of the event by distinguishing the event as either a patient event, a maintenance event, or a feature request event.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to respond to a patient event by communicating the patient event to a remote caregiver, wait for a signal from the remote caregiver in response to the event, and act on the response from the remote caregiver to change an operating parameter of the patient support apparatus.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to respond to a maintenance event by communicating the maintenance to a remote entity, wait for a signal from the remote entity in response to the event, and act on the response from the remote entity to change an operating parameter of the patient support apparatus.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to respond to the feature request event by, transmit the feature request to an authorization entity, monitor for a signal from the authorization entity that the feature request permitted, if the change in the operational state of at least one of the features is permitted, log the request, and enable the feature.
In some embodiments, the memory device includes further instructions that, when executed by the processor, causes the processor to transmit information regarding the usage of a feature to a third party to be used to establish a bill for use of the feature.
Additional features, which alone or in combination with any other feature(s), including those listed above and those listed in the claims, may comprise patentable subject matter and will become apparent to those skilled in the art upon consideration of the following detailed description of illustrative embodiments exemplifying the best mode of carrying out the invention as presently perceived.
The detailed description particularly refers to the accompanying figures in which:
A patient support apparatus 10 in accordance with the present disclosure includes a patient support structure 12, a patient support surface 14, and a control system 16 as shown in
As a further example, the control system 16 may be configured to communicate with a hospital information system 18 and a service provider 20 to obtain permission to take various actions, request and receive instructions from caregivers and the service provider 20. The control system 16 may also communicate when various bed features are in use so that billing efficiency may be maximized. As an example, the control system 16 may determine that the air fluidized therapy was only in use for a brief period time, and thus, the caregiver and patient are only charged the brief period of time the bed feature was in use.
As shown in
The patient support surface 14 includes, for example, a tank system 32, a fluidizable medium 34, and a fluid supply 36 as shown in
The tank system 32 includes a tank base 40, a tank liner 42, a tank bladder 44, and a filter cover 46 as shown in
The filter cover 46 is positioned over the opening 50 and is coupled to the tank liner 42 as shown in
The diffuser 52 is configured to support the fluidizable medium 34 thereon and provide substantially uniform fluid flow to the fluidizable medium 34 from the fluid supply 36 as suggested, for example, in
The fluid supply 36 is configured to supply fluid having various fluid properties to the diffuser. The fluid properties include pressure, relative humidity, and temperature. As shown, for example in
The control system 16 is also coupled to each component of the fluid supply 36 to control the fluid properties of the fluid as it passes through the fluidizable medium 34. The control system 16 may command the source 54 to provide the fluid at various pressures and flow rates. The control system 16 may command the cooler 56 to withdraw heat from the pressurized fluid so as to remove excess humidity and achieve a desired relative humidity of the pressurized fluid and provide cool pressurized fluid to the patient when desired. The control system 16 may also command the heater 58 to add heat to the pressurized fluid after the cooler 56 has controlled for humidity so that the output temperature is configured to maximize patient comfort and health.
The control system 16 may vary the pressure, humidity, and temperature of fluid to accomplish various bed features. In one example, the control system 16 and the fluid supply 36 cooperate to provide air fluidized therapy. Additional features of air fluidized therapy are discussed in U.S. application Ser. No. 13/246,886, filed Sep. 28, 2011 and entitled “SYSTEMS, METHODS, AND DEVICES FOR FLUIDIZING A FLUIDIZABLE MEDIUM,” which is hereby incorporated in its entirety by reference herein. In another example, the control system 16 and the fluid supply 36 cooperate to provide micro-climate management of the patient support surface 14. Additional features of micro-climate management are discussed in U.S. Application No. PCT/US09/40661, filed Apr. 15, 2009 and entitled “MICROCLIMATE MANAGEMENT SYSTEM,” which is hereby incorporated in its entirety by reference herein. In still yet another example, the control system 16 and the fluid supply 36 cooperate to provide adverse condition detection, assessment, and response in the patient support surface 14. Addition discussion of systems for adverse condition detection, assessment, and response is found in U.S. Application No. 61/650,436, filed May 22, 2012 and entitled “ADVERSE CONDITION DETECTION, ASSESSMENT, AND RESPONSE SYSTEMS, METHODS AND DEVICES,” which is hereby incorporated in its entirety by reference herein.
As shown in
The pressure sensor 60 may be used to develop a high interface pressure hot spot map that tracks the development of hot spots over time and determines when a predetermined threshold is exceeded. When the predetermined threshold is exceeded, the control system 16 recognizes this as a patient event which causes the control system 16 to take action as suggested in
In another example, the pressure sensor 60 may be used to develop a quantified Braden Assessment for pressure ulcer risk. Measures provided by pressure sensor 60 may be used to calculate objective values for sub-scores within the overall Braden score. The Braden score uses sub scores for mobility and activity which may be provided by pressure sensor 60. The Braden score also uses share and moisture sub scores which may be provided by other sensors. The control system 16 may be configured to monitor the Braden Assessment and determines a patient event occurs when the Braden Assessment estimate passes a predetermined threshold and take action as suggested in
In yet another example, the pressure sensor 60 may be used to provide turn tracking of the patient. As an example, the control system 16 may use the sensor date provided by pressure sensor 60 to determine when a patient has turned on the patient support surface 14. If the patient has not moved relative to the patient support surface 14, the control system 16 for a predetermined time period, the control system 16 may again determine a patient event has occurred and take action as suggested in
In another example, the sensor 60 is configured sense temperature. The temperature sensor 60 may be woven into the filter cover 46 or applied to the surface of the filter cover 46. In one example, the temperature sensor 60 is configured to provide a signal representative of the temperature measured. In another example, the temperature sensor 60 is configured to provide a signal only if a predetermined threshold temperature is sensed. Such temperature readings may be useful for providing feedback to the control system 16 to change the temperature of fluid exiting the fluid supply 36 so that patient comfort and health may be maximized.
In still yet another example, the sensor 60 may be a humidity sensor. The humidity sensor 60 may be integrated with the filter cover 46 or arranged to lie in close proximity to the filter cover 46 in the fluidizable medium 34. The humidity sensor 60 may be used to measure the relative humidity of the fluid supplied by the fluid supply 36 to provide feedback to the control system 16. In another example, the humidity sensor 60 may be used to measure the humidity of the fluid after passing over the patient to detect if patient sweating is occurring or likely to occur.
In yet another example, the sensor 60 may be a moisture sensor. The moisture sensor 60 may be configured to provide a signal that is indicative that a predetermined amount of moisture is detected between the patient and the patient support surface. The moisture sensor 60 may also be used to detect the occurrence of an incontinence by the patient. Incontinence may be detected and determined to be a patient event by the control system 16. As a result, the control system 16 may take one or more predetermined actions such as contacting the caregiver.
In another example, the sensor 60 may be configured to sense one or more pathogens. The detection of a pathogen may considered a patient event that requires associated action to be taken either through caregiver intervention or as a predetermined action to be taken automatically by the patient support apparatus 10 in response to command by the control system 16. U.S. application Ser. No. 13/654,649, filed May 16, 2012 and entitled “PATHOGEN DETECTION SYSTEMS AND METHODS” is hereby incorporated in its entirety by reference herein for disclosure related detection of pathogens and responses to the detection of pathogens.
In still yet another example, the sensor 60 may be embodied as a user input, for example, integrated in the operation of graphical display screen 60B including a touch screen or virtual keyboard as shown in
The control system 16 includes, for example, the sensor 60, a controller 62, and a communication link 64 as shown in
The controller 62 includes memory 68 and a processor 70 as shown in
The process 200 includes a series of decision steps, process steps, and subroutines as shown in
After the decision step 206 and the logging subroutine 208, the process 200 proceeds to a decision step 210 which determines if the event is a patient event as shown in
When the event is determined not to be one of a patient event, a maintenance event, or a feature-request event, the process 200 proceeds to a decision step 216 which determines if the event should be canceled. If the event should be canceled, the process 200 proceeds to a process step 218 that cancels the event and process 200 proceeds back to the process step 202 which is the patient support apparatus 10 is powered on. If the event should not be canceled, the process 200 returns to the process step 204 in which the event is detected by sensor 60 to see if the event should go through the process 200.
Decision step 210 determines whether the event detected by sensor 60 is a patient event. A patient event is an event which is caused by a patient condition such as sweating on incontinence. Characteristics describing such events are stored in memory 68, on computers in the hospital information system 18, or computers at the service provider. The process 70 compares the obtained sensor data to the stored characteristics to determine whether an event should be classified as a patient event. In one illustrative example, incontinence may be defined as substantial moisture on the patient support surface detected by sensor 60. When sensor 60 detects substantial moisture, the sensor signal is communicated to processor 70 where the processor compares the sensor signal to stored values in memory 68 and determines whether or not the detected event is a patient event.
If the detected event is a patient event, the patient-event subroutine 220 is called by the process as shown in
If the patient support apparatus 10 does require permission, the patient-event subroutine 220 proceeds a subsequent decision step 230 which determines whether permission may be given remotely from the patient support apparatus 10. If the permission may be given remotely, the patient-event subroutine 220 proceeds to a process step 232 which requests permission remotely from the caregiver. In one example, processor 70 uses communication link 64 to communicate with the caregiver via a computer in the hospital information system 18, a cell phone, tablet, or any other suitable alternative. The patient support apparatus 10 may communicate the type of patient event, the proposed predetermined action, the time of the event, the location, and any other information relevant to the decision of the caregiver. After notifying the caregiver, the patient-event subroutine 220 then proceeds a decision step 234. If permission may not be given remotely, the patient-event subroutine 220 then proceeds to a process step 236 which summons the caregiver to the patient support apparatus 10. Once the caregiver is at the patient support apparatus, the patient-event subroutine 220 proceeds to decision step 234.
Decision step 234 determines whether the caregiver is authorized to give permission. If the caregiver is authorized, the patient-event subroutine 220 proceeds to a decision step 238 which determines whether the caregiver gives permission. If the caregiver is not authorized, the patient-event subroutine 220 returns to the decision step 226 to determine whether permission is required for action and another caregiver can respond. If the caregiver is authorized, then the patient-event subroutine 220 proceeds to the decision step 238 which determines whether the caregiver has authorized the predetermined action of the patient support apparatus 10 as shown in
Decision step 238 determines whether the caregiver has authorized the predetermined action of the patient support apparatus 10 as shown in
The decision step 242 of the patient-event subroutine 220 determines whether the caregiver desires to make an adjustment to the predetermined action of the patient support apparatus 10. If the caregiver desires to make an adjustment, the patient-event subroutine 220 proceeds to a process step 244 in which the caregiver makes the adjustment. The patient-event subroutine 220 then proceeds to a subsequent process step 246 in which the patient support apparatus 10 performs the adjusted action. In an example, the original predetermined action in response to an incontinence event may be to stop source 54 until a linen change has occurred. However, the caregiver, knowing that a patient may be at high risk of pressure ulcers, adjusts the predetermined action so that air flow is only reduced or blocked in certain areas on the patient support surface 14.
In the instance where the caregiver does not desire to make an adjustment, the patient-event subroutine 220 proceeds to a determination step 248 as shown in
After the patient-event subroutine 220 has performed either the process step 246 or the process step 228, the patient-event subroutine 220 proceeds to the decision step 240 which determines whether performing the actions should be logged as shown in
When the control system 16 determines that the event detected at process step 204 is not a patient event, the process 200 proceeds to the decision step 212 as shown in
When the control system 16 determines that the event is a maintenance event in decision step 212, the process 200 then proceeds to the maintenance-event subroutine 222 as suggested in
The maintenance-event subroutine 222 begins with the decision step 256 as shown in
If decision step 260 determines that permission is needed, the maintenance-event subroutine 222 proceeds to a subsequent decision step 264 which determines whether permission may be given remotely from the patient support apparatus. If permission may be given remotely, the maintenance-event subroutine 222 proceeds to a process step 266 which requests permission remotely from the caregiver. After notifying the caregiver, the maintenance-event subroutine 222 then proceeds a decision step 267. If permission may not be given remotely, the maintenance-event subroutine 222 then proceeds to a process step 268 which summons the caregiver to the patient support apparatus 10. Once the caregiver is at the patient support apparatus, the maintenance-event subroutine 222 proceeds to the decision step 267.
Decision step 267 determines whether the caregiver is authorized to give permission. If the caregiver is authorized, the maintenance-event subroutine 222 proceeds to a decision step 270 which determines whether the caregiver gives permission. If the caregiver is not authorized, the maintenance-event subroutine 222 returns to the decision step 260 to determine whether permission is required for action and another caregiver can respond. If the caregiver is authorized, then the maintenance-event subroutine 222 proceeds to the decision step 270 which determines whether the caregiver has authorized the predetermined action of the patient support apparatus 10 as shown in
If the caregiver gives permission, the maintenance-event subroutine 222 proceeds to take action in the process step 262 as suggested in
Decision step 238 determines whether the caregiver has authorized the predetermined action of the patient support apparatus 10 as shown in
If permission is not given by the caregiver at decision step 270, the maintenance-event subroutine 222 then proceeds to a decision step 274 as shown in
In the instance where the caregiver does not desire to make an adjustment, the maintenance-event subroutine 222 proceeds to a determination step 280 as shown in
After the maintenance-event subroutine 222 has performed the process step 278, the maintenance-event subroutine 222 proceeds to a decision step 288 which determines whether performing the actions should be logged as shown in
As shown in
When the event is determined to be a component failure in decision step 258, the maintenance-event subroutine 222 then proceeds to a decision step 296 as shown in
If the patient support apparatus 10 does require permission, the maintenance-event subroutine 222 proceeds a subsequent decision step 300 which determines whether permission may be given remotely from the patient support apparatus 10. If the permission may be given remotely, the maintenance-event subroutine 222 proceeds a process step 302 which requests permission remotely from the caregiver. After notifying the caregiver, the maintenance-event subroutine 222 then proceeds to a decision step 304. If permission may not be given remotely, the maintenance-event subroutine 222 then proceeds to a process step 306 which summons the caregiver to the patient support apparatus 10. Once the caregiver is at the patient support apparatus, the maintenance-event subroutine 222 proceeds to decision step 304.
Decision step 304 determines whether the caregiver is authorized to give permission. If the caregiver is authorized, the maintenance-event subroutine 222 proceeds to a decision step 307 which determines whether the caregiver gives permission. If the caregiver is not authorized, the maintenance-event subroutine 222 returns to the decision step 296 to determine whether permission is required for action and another caregiver can respond. If the caregiver is authorized, then the maintenance-event subroutine 222 proceeds to the decision step 307 which determines whether the caregiver has authorized the predetermined action of the patient support apparatus 10 as shown in
Decision step 307 determines whether the caregiver has authorized the predetermined action of the patient support apparatus 10 as shown in
The decision step 308 of the maintenance-event subroutine 222 determines whether the caregiver desires to make an adjustment to the predetermined action of the patient support apparatus 10. If the caregiver desires to make an adjustment, the maintenance-event subroutine 222 proceeds to a process step 310 in which the caregiver makes the adjustment. The maintenance-event subroutine 222 then proceeds to a decision step 312 which determines whether the adjusted action proposed by the caregiver should be reviewed by one of a supervisor, doctor, or the service provider 20.
In the instance where the caregiver does not desire to make an adjustment, the maintenance-event subroutine 222 proceeds to a determination step 314 as shown in
As described above, the maintenance-event subroutine 222, after caregiver makes an adjustment to the predetermined response in process step 310, advances to decision step 312 as shown in
If no review of the caregiver's adjustment is necessary, the maintenance-event subroutine 222 proceeds to process step 322 in which the adjusted action is performed by the patient support apparatus 10. If review is necessary, the maintenance-event subroutine 222 proceeds to the process step 324 and communicates the request for review to the appropriate party (supervisor, doctor, maintenance technician, or service provider). The maintenance-event subroutine 222 then proceeds to a decision step 326 in which the reviewing party determines whether the proposed adjusted action is acceptable. In the example of the broken actuator, the service provider may determine that movement of the upper frame 24 relative to the lower frame 22 using a limited number of actuators is unsafe and thus should not be allowed.
If the proposed adjustment is acceptable, the maintenance-event subroutine 222 proceeds to the process step 322 and then returns to the process step 202 of the process 200 in which the patient support apparatus 10 is powered on. If the proposed adjustment is not acceptable, the maintenance-event subroutine 222 proceeds to a subsequent decision step 328 which determines whether the adjusted action should be revised. If the proposed action should not be revised, then the maintenance-event subroutine 222 proceeds to a process step 330 that communicates to the caregiver the proposed adjusted action is not acceptable. The maintenance-event subroutine 222 then returns back to decision step 308 which determines if the caregiver wants to make an adjustment to the action.
Decision step 328 determines whether the reviewing party wishes to revise the adjusted action as shown in
After the maintenance-event subroutine 222 has performed the process step 336, the maintenance-event subroutine 222 proceeds to a decision step 338 which determines whether performing the actions should be logged as shown in
When the control system 16 determines that the event is a feature-request event in decision step 214, the process 200 then proceeds to the feature-request subroutine 224 as suggested in
In decision step 342, the control system 16 may look in memory 68 or communicate with the service provider 20 to determine if the requested feature should be enabled. In one example, the requested feature may not be enabled because the hardware comprising the patient support surface 14 is not capable of providing the requested feature. In another example, the requested feature may not be enabled because a doctor has determined such a feature is not beneficial to the patient. In still yet another example, the requested feature may not be enabled because the patient's insurance will not reimburse for use of the requested feature.
If the requested feature is permitted in decision step 342, the feature-request subroutine 224 proceeds to a process step 344 in which the feature request is logged in one or more of memory 68, memory included in computer on the hospital information system 18, and the service provider 20. The feature-request subroutine 224 then proceeds to a subsequent process step 346 in which the requested feature is enabled as suggested in
If the requested feature is not permitted in decision step 342, the feature-request subroutine 224 proceeds to a process step 350 in which the communication is provided to the caregiver that the requested feature is not permitted. The feature-request subroutine 224 proceeds to a subsequent decision step 352 which determines if another similar feature is permitted. In one illustrative example, the caregiver may request the use of a microclimate management system for the patient support surface 14. The service provider may determine that the requested bed feature will not be reimbursed for by the patient's insurance provider. As a result, the service provider may offer a feature such as passing air through the patient support surface 14 to minimize sweating of the patient without the effort, expense, and time required to get the microclimate management system approved by the insurance provider or added the patient support apparatus 10.
If another similar feature is permitted, the feature-request subroutine 224 then communicates the alternative feature to the caregiver in a process step 354 as shown in
After the process step 348 activates the requested feature, the feature-request subroutine 224 proceeds until a process step 360 occurs as suggested in
The decision step 364 determines if the caregiver should be notified of the feature deactivation as shown in
After the process step 368, the feature-request subroutine 224 proceeds to a decision step 370 which determines whether the caregiver action should be logged. If the action should be logged, the feature-request subroutine 224 proceeds to the logging subroutine 208 before returning to the process step 202 of the process 200. If the action should not be logged, the feature-request subroutine 224 returns to the process step 202 of the process 200.
In the event the caregiver should not be notified, the feature-request subroutine 224 proceeds to a decision step 372 which determines if the feature should have been deactivated as shown in
The decision step 378 determines if the deactivation of the feature is authorized. If the feature deactivation is not authorized, the feature-request subroutine 224 returns to process step 348 which is the activation of the requested feature. If the feature deactivation is authorized, the feature-request subroutine 224 proceeds to deactivate the feature in a process step 380 as shown in
As discussed above, the process 200, the patient-event subroutine 220, the maintenance-event subroutine 220, or the feature-request subroutine 224 may call on the logging subroutine 208 at various instances in process 200. The logging subroutine 208 begins with a decision step 390 that determines whether the event should be validated by a caregiver or other suitable person as shown in
Logging subroutine 208 then proceeds to a decision step 396 which determines if the caregiver is authorized to validate the information as shown in
If the caregiver is authorized to validate the information, the logging subroutine 208 proceeds to a decisions step 402 that determines if the information is valid and should be changed as suggested in
The process 200 also calls on the cancel-event subroutine 358 as shown in
The process 200 is configured to respond once an event is detected by one or more sensors 60. Once the event is detected, the process 200 determines if the event is one of a patient event, a maintenance event, and a feature-request event. Depending on the event type, the process 200 takes appropriate action and returns to a state prior to the detection of an event. While several different patient events such as sweating, bed exit, and incontinence are mentioned, any other suitable patient events may be detected by and responded to by the control system 16. In addition, several different maintenance events such as a dirty filter, a broken actuator, and a malfunctioning fluid supply 36, any other suitable maintenance events may be detected by and responded to by the control system 16. Furthermore, several bed features such as air fluidized therapy 72, microclimate management 74, percussion therapy 76, vibration therapy 78, patient history and tracking 80, deep vain thrombosis therapy 82 are mentioned and shown in
Referring now to the embodiment of
In another embodiment shown in
In still another embodiment shown in
In some embodiments, the system will aggregate all of the therapies enabled by the server 500 and consolidate a monthly bill for the hospital 502 from the service provider 20. The operation of the therapy or therapies may operate against a capitated amount, such as a total time or expense of therapy enablement for the hospital 502. The capitated amount may be a budgeted amount or a pre-authorized amount, such as by a purchase order to the service provider 20.
Although the invention has been described in detail with reference to certain illustrative embodiments, variations and modifications exist with the scope and spirit of this disclosure as described and defined in the following claims.
This application claims priority under 35 U.S.C. §119(e) to U.S. Provisional Application Ser. No. 61/719,239, filed Oct. 26, 2012, which is expressly incorporated by reference herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3599199 | Bunting | Aug 1971 | A |
| 3643219 | Heimann | Feb 1972 | A |
| 3910659 | Peterson et al. | Oct 1975 | A |
| 3913153 | Adams et al. | Oct 1975 | A |
| 3946159 | Fay | Mar 1976 | A |
| 4183015 | Drew et al. | Jan 1980 | A |
| 4216462 | McGrath et al. | Aug 1980 | A |
| 4237344 | Moore | Dec 1980 | A |
| 4356475 | Neumann et al. | Oct 1982 | A |
| 4410158 | Maffei et al. | Oct 1983 | A |
| 4452499 | Verburg | Jun 1984 | A |
| 4489454 | Thompson | Dec 1984 | A |
| 4539560 | Fleck et al. | Sep 1985 | A |
| 4557453 | McCloskey | Dec 1985 | A |
| 4584989 | Stith | Apr 1986 | A |
| 4601064 | Shipley | Jul 1986 | A |
| 4607897 | Schwartz et al. | Aug 1986 | A |
| 4638313 | Sherwood et al. | Jan 1987 | A |
| 4640485 | Day et al. | Feb 1987 | A |
| 4680790 | Packard et al. | Jul 1987 | A |
| 4687167 | Skalka et al. | Aug 1987 | A |
| 4708312 | Rohr | Nov 1987 | A |
| 4715385 | Cudahy et al. | Dec 1987 | A |
| 4724555 | Poehner et al. | Feb 1988 | A |
| 4738369 | Desjardins | Apr 1988 | A |
| 4747172 | Hohol et al. | May 1988 | A |
| 4756706 | Kerns et al. | Jul 1988 | A |
| 4768241 | Beney | Sep 1988 | A |
| 4783036 | Vossoughi | Nov 1988 | A |
| 4800384 | Snijders | Jan 1989 | A |
| 4835372 | Gombrich et al. | May 1989 | A |
| 4836478 | Sweere | Jun 1989 | A |
| 4848710 | Newman et al. | Jul 1989 | A |
| 4852500 | Ryburg et al. | Aug 1989 | A |
| 4857713 | Brown et al. | Aug 1989 | A |
| 4872679 | Bohaski et al. | Oct 1989 | A |
| 4890856 | Mursch et al. | Jan 1990 | A |
| 4934933 | Fuchs | Jun 1990 | A |
| 4945592 | Sims et al. | Aug 1990 | A |
| 4967195 | Shipley et al. | Oct 1990 | A |
| 4981139 | Pfohl | Jan 1991 | A |
| 4993683 | Kreuzer et al. | Feb 1991 | A |
| 5023967 | Ferrand et al. | Jun 1991 | A |
| 5036852 | Leishman | Aug 1991 | A |
| 5065154 | Kaiser et al. | Nov 1991 | A |
| 5072906 | Foster et al. | Dec 1991 | A |
| 5077843 | Dale et al. | Jan 1992 | A |
| 5108063 | Koerber, Sr. et al. | Apr 1992 | A |
| 5117521 | Foster et al. | Jun 1992 | A |
| 5177616 | Riday | Jan 1993 | A |
| 5187641 | Muskatello et al. | Feb 1993 | A |
| 5246240 | Romich et al. | Sep 1993 | A |
| 5272318 | Gorman | Dec 1993 | A |
| 5274311 | Littlejohn et al. | Dec 1993 | A |
| 5276813 | Elliott et al. | Jan 1994 | A |
| 5279010 | Ferrand et al. | Jan 1994 | A |
| 5283781 | Buda et al. | Feb 1994 | A |
| 5284255 | Foster et al. | Feb 1994 | A |
| 5291399 | Chaco et al. | Mar 1994 | A |
| 5319816 | Ruehl et al. | Jun 1994 | A |
| 5330415 | Storti et al. | Jul 1994 | A |
| 5335651 | Foster et al. | Aug 1994 | A |
| 5337845 | Foster et al. | Aug 1994 | A |
| 5357396 | Alm | Oct 1994 | A |
| 5361755 | Schraag et al. | Nov 1994 | A |
| 5362021 | Phillips | Nov 1994 | A |
| 5375604 | Kelly et al. | Dec 1994 | A |
| 5377371 | Foster et al. | Jan 1995 | A |
| 5396673 | Foster | Mar 1995 | A |
| 5398359 | Foster | Mar 1995 | A |
| 5400991 | Werner et al. | Mar 1995 | A |
| 5407163 | Kramer et al. | Apr 1995 | A |
| 5416695 | Stutman et al. | May 1995 | A |
| 5417222 | Dempsey et al. | May 1995 | A |
| 5455975 | Foster et al. | Oct 1995 | A |
| 5457831 | Foster et al. | Oct 1995 | A |
| 5473536 | Wimmer et al. | Dec 1995 | A |
| 5473997 | Solomon et al. | Dec 1995 | A |
| 5494051 | Schneider et al. | Feb 1996 | A |
| 5497766 | Foster et al. | Mar 1996 | A |
| 5502480 | Kuga et al. | Mar 1996 | A |
| 5513406 | Foster et al. | May 1996 | A |
| 5527289 | Foster et al. | Jun 1996 | A |
| 5536084 | Curtis et al. | Jul 1996 | A |
| 5537459 | Price et al. | Jul 1996 | A |
| 5542138 | Williams et al. | Aug 1996 | A |
| 5544649 | David et al. | Aug 1996 | A |
| 5556065 | Wadley et al. | Sep 1996 | A |
| 5561412 | Novak et al. | Oct 1996 | A |
| 5562091 | Foster et al. | Oct 1996 | A |
| 5579001 | Dempsey et al. | Nov 1996 | A |
| 5579775 | Dempsey et al. | Dec 1996 | A |
| 5600311 | Rice et al. | Feb 1997 | A |
| 5618090 | Montague et al. | Apr 1997 | A |
| 5623925 | Swenson et al. | Apr 1997 | A |
| 5630566 | Case et al. | May 1997 | A |
| 5640953 | Bishop et al. | Jun 1997 | A |
| 5647491 | Foster et al. | Jul 1997 | A |
| 5651775 | Walker et al. | Jul 1997 | A |
| 5664270 | Bell et al. | Sep 1997 | A |
| 5687717 | Halpern et al. | Nov 1997 | A |
| 5699038 | Ulrich et al. | Dec 1997 | A |
| 5712482 | Gaiser et al. | Jan 1998 | A |
| 5715138 | Choi | Feb 1998 | A |
| 5732401 | Conway et al. | Mar 1998 | A |
| 5732712 | Adair et al. | Mar 1998 | A |
| 5738102 | Lemelson | Apr 1998 | A |
| 5738316 | Sweere et al. | Apr 1998 | A |
| 5743503 | Voeller et al. | Apr 1998 | A |
| 5749374 | Schneider et al. | May 1998 | A |
| 5752917 | Fuchs | May 1998 | A |
| 5769440 | Jones | Jun 1998 | A |
| 5771511 | Kummer et al. | Jun 1998 | A |
| 5772585 | Lavin et al. | Jun 1998 | A |
| 5772599 | Nevo et al. | Jun 1998 | A |
| 5788851 | Kenley et al. | Aug 1998 | A |
| 5791263 | Watt et al. | Aug 1998 | A |
| 5799917 | Li | Sep 1998 | A |
| 5820623 | Ng et al. | Oct 1998 | A |
| 5822544 | Chaco et al. | Oct 1998 | A |
| 5826846 | Buccieri et al. | Oct 1998 | A |
| 5831816 | Johns et al. | Nov 1998 | A |
| 5838223 | Gallant et al. | Nov 1998 | A |
| 5841373 | Mason | Nov 1998 | A |
| 5842672 | Sweere et al. | Dec 1998 | A |
| 5842976 | Williamson | Dec 1998 | A |
| 5867821 | Ballantyne et al. | Feb 1999 | A |
| 5876008 | Sweere et al. | Mar 1999 | A |
| 5883370 | Walker et al. | Mar 1999 | A |
| 5889568 | Seraphim et al. | Mar 1999 | A |
| 5895354 | Simmons | Apr 1999 | A |
| 5895571 | Utterberg | Apr 1999 | A |
| 5898961 | Ambach et al. | May 1999 | A |
| 5903211 | Flego et al. | May 1999 | A |
| 5907291 | Chen et al. | May 1999 | A |
| 5918328 | Ramsey | Jul 1999 | A |
| 5918331 | Hall et al. | Jul 1999 | A |
| 5918841 | Sweere et al. | Jul 1999 | A |
| 5924665 | Sweere et al. | Jul 1999 | A |
| 5944659 | Flach et al. | Aug 1999 | A |
| 5947429 | Sweere et al. | Sep 1999 | A |
| 5957838 | Rantala | Sep 1999 | A |
| 5960085 | De La Huerga | Sep 1999 | A |
| 5961448 | Swenson et al. | Oct 1999 | A |
| 5966760 | Gallant et al. | Oct 1999 | A |
| 5973598 | Beigel | Oct 1999 | A |
| 5975081 | Hood et al. | Nov 1999 | A |
| 5978211 | Hong | Nov 1999 | A |
| 5991947 | Lavin et al. | Nov 1999 | A |
| 5992809 | Sweere et al. | Nov 1999 | A |
| 5993006 | Takeuchi et al. | Nov 1999 | A |
| 5997147 | Tatoian et al. | Dec 1999 | A |
| 6001057 | Bongiovanni et al. | Dec 1999 | A |
| 6008598 | Luff et al. | Dec 1999 | A |
| 6011701 | Kopp et al. | Jan 2000 | A |
| 6012693 | Voeller et al. | Jan 2000 | A |
| 6015120 | Sweere et al. | Jan 2000 | A |
| 6019332 | Sweere et al. | Feb 2000 | A |
| 6026318 | Bernstein et al. | Feb 2000 | A |
| 6027247 | Tachi et al. | Feb 2000 | A |
| 6061104 | Evanicky et al. | May 2000 | A |
| 6064373 | Ditzik | May 2000 | A |
| 6065732 | Cho | May 2000 | A |
| 6073285 | Ambach et al. | Jun 2000 | A |
| 6089518 | Nilsson | Jul 2000 | A |
| 6102476 | May et al. | Aug 2000 | A |
| 6102855 | Kehr et al. | Aug 2000 | A |
| 6104443 | Adcock et al. | Aug 2000 | A |
| 6112182 | Akers et al. | Aug 2000 | A |
| 6125350 | Dirbas et al. | Sep 2000 | A |
| 6134103 | Ghanma | Oct 2000 | A |
| 6143181 | Falkvall et al. | Nov 2000 | A |
| 6144848 | Walsh et al. | Nov 2000 | A |
| 6146523 | Kenley et al. | Nov 2000 | A |
| 6147592 | Ulrich et al. | Nov 2000 | A |
| 6150942 | O'Brien | Nov 2000 | A |
| 6155603 | Fox | Dec 2000 | A |
| 6155975 | Urich et al. | Dec 2000 | A |
| 6168250 | Rogov | Jan 2001 | B1 |
| 6170102 | Kreuzer | Jan 2001 | B1 |
| 6175779 | Barrett | Jan 2001 | B1 |
| 6175977 | Schumacher et al. | Jan 2001 | B1 |
| 6176456 | Wisniewski | Jan 2001 | B1 |
| 6179260 | Ohanian | Jan 2001 | B1 |
| 6183417 | Geheb et al. | Feb 2001 | B1 |
| 6189842 | Bergeron Gull et al. | Feb 2001 | B1 |
| 6202360 | Rattner et al. | Mar 2001 | B1 |
| 6202923 | Boyer et al. | Mar 2001 | B1 |
| 6205601 | Nessmann et al. | Mar 2001 | B1 |
| 6208250 | Dixon et al. | Mar 2001 | B1 |
| 6219587 | Ahlin et al. | Apr 2001 | B1 |
| 6234172 | Ausbourne et al. | May 2001 | B1 |
| 6246573 | Khan et al. | Jun 2001 | B1 |
| 6260761 | Peoples, Jr. | Jul 2001 | B1 |
| 6320510 | Menkedick et al. | Nov 2001 | B2 |
| 6352504 | Ise et al. | Mar 2002 | B1 |
| 6396224 | Luff et al. | May 2002 | B1 |
| 6481688 | Welling et al. | Nov 2002 | B1 |
| 6486792 | Moster et al. | Nov 2002 | B1 |
| 6493568 | Bell et al. | Dec 2002 | B1 |
| 6510049 | Rosen | Jan 2003 | B2 |
| 6560492 | Borders | May 2003 | B2 |
| 6560798 | Welling et al. | May 2003 | B2 |
| 6591239 | McCall et al. | Jul 2003 | B1 |
| 6616606 | Petersen et al. | Sep 2003 | B1 |
| 6640363 | Pattee et al. | Nov 2003 | B1 |
| 6642836 | Wang et al. | Nov 2003 | B1 |
| 6759959 | Wildman | Jul 2004 | B2 |
| 6761344 | Welling et al. | Jul 2004 | B2 |
| 6781517 | Moster et al. | Aug 2004 | B2 |
| 6785922 | Bretschger et al. | Sep 2004 | B2 |
| 6791460 | Dixon et al. | Sep 2004 | B2 |
| 6829796 | Salvatini et al. | Dec 2004 | B2 |
| 6840117 | Hubbard, Jr. | Jan 2005 | B2 |
| 6876303 | Reeder et al. | Apr 2005 | B2 |
| 6897780 | Ulrich et al. | May 2005 | B2 |
| 6907630 | Treon | Jun 2005 | B2 |
| 6911916 | Wang et al. | Jun 2005 | B1 |
| 6915538 | Treon | Jul 2005 | B2 |
| 6924441 | Mobley et al. | Aug 2005 | B1 |
| 6943663 | Wang et al. | Sep 2005 | B2 |
| 6944896 | Treon | Sep 2005 | B2 |
| 6947411 | Parker | Sep 2005 | B2 |
| 6957458 | Nagaoka et al. | Oct 2005 | B2 |
| 6972683 | Lestienne et al. | Dec 2005 | B2 |
| 6980111 | Nolte | Dec 2005 | B2 |
| 7010369 | Borders et al. | Mar 2006 | B2 |
| 7017208 | Weismiller et al. | Mar 2006 | B2 |
| 7032522 | George et al. | Apr 2006 | B2 |
| 7038588 | Boone et al. | May 2006 | B2 |
| 7103419 | Engleson et al. | Sep 2006 | B2 |
| 7119688 | Wildman | Oct 2006 | B2 |
| 7154307 | Pradhan et al. | Dec 2006 | B2 |
| 7154397 | Zerhusen et al. | Dec 2006 | B2 |
| 7174678 | Gallant | Feb 2007 | B2 |
| 7176391 | Metz et al. | Feb 2007 | B2 |
| 7197148 | Nourse et al. | Mar 2007 | B2 |
| 7213279 | Weismiller et al. | May 2007 | B2 |
| 7237287 | Weismiller | Jul 2007 | B2 |
| 7242308 | Ulrich et al. | Jul 2007 | B2 |
| 7310839 | Salvatini et al. | Dec 2007 | B2 |
| 7335839 | Metz et al. | Feb 2008 | B2 |
| 7346945 | Phillips et al. | Mar 2008 | B2 |
| 7399205 | McNeely et al. | Jul 2008 | B2 |
| 7421474 | Motoyama et al. | Sep 2008 | B2 |
| 7426760 | Vrzalik | Sep 2008 | B2 |
| 7443302 | Reeder et al. | Oct 2008 | B2 |
| 7451506 | Kummer et al. | Nov 2008 | B2 |
| 7461009 | Haulk et al. | Dec 2008 | B1 |
| 7467093 | Newton et al. | Dec 2008 | B1 |
| 7480951 | Weismiller | Jan 2009 | B2 |
| 7506390 | Dixon et al. | Mar 2009 | B2 |
| 7538659 | Ulrich et al. | May 2009 | B2 |
| 7568246 | Weismiller et al. | Aug 2009 | B2 |
| 7679520 | Zerhusen et al. | Mar 2010 | B2 |
| 7730562 | Hornbach et al. | Jun 2010 | B2 |
| 7757318 | Poulos et al. | Jul 2010 | B2 |
| 7784128 | Kramer | Aug 2010 | B2 |
| 7805785 | Rawls-Meehan | Oct 2010 | B2 |
| 7827632 | Vrzalik | Nov 2010 | B2 |
| 7834768 | Dixon et al. | Nov 2010 | B2 |
| 7860726 | Connely, III et al. | Dec 2010 | B2 |
| 7911349 | Zerhusen et al. | Mar 2011 | B2 |
| 7945451 | Cosentino et al. | May 2011 | B2 |
| 7971300 | Wilker, Jr. | Jul 2011 | B2 |
| 7978084 | Dixon et al. | Jul 2011 | B2 |
| 7986242 | Dixon et al. | Jul 2011 | B2 |
| 8026821 | Reeder et al. | Sep 2011 | B2 |
| 8032078 | Donich et al. | Oct 2011 | B1 |
| 8032263 | Rawls-Meehan | Oct 2011 | B2 |
| 8032960 | Rawls-Meehan | Oct 2011 | B2 |
| 8065764 | Kramer | Nov 2011 | B2 |
| 8069512 | Rawls-Meehan | Dec 2011 | B2 |
| 8091162 | Wurdeman | Jan 2012 | B2 |
| 8111165 | Ortega et al. | Feb 2012 | B2 |
| 8112836 | Tesar et al. | Feb 2012 | B2 |
| 8121856 | Huster et al. | Feb 2012 | B2 |
| 8125318 | Heimbrock et al. | Feb 2012 | B2 |
| 8161826 | Taylor | Apr 2012 | B1 |
| 8258963 | Dixon et al. | Sep 2012 | B2 |
| 8258965 | Reeder et al. | Sep 2012 | B2 |
| 8266742 | Andrienko | Sep 2012 | B2 |
| 8280748 | Allen et al. | Oct 2012 | B2 |
| 8314781 | Pittenger et al. | Nov 2012 | B2 |
| 8327479 | Wurdeman | Dec 2012 | B2 |
| 8334777 | Wilson et al. | Dec 2012 | B2 |
| 8334779 | Zerhusen et al. | Dec 2012 | B2 |
| 8344860 | Collins, Jr. et al. | Jan 2013 | B2 |
| 8368545 | Zerhusen et al. | Feb 2013 | B2 |
| 8375488 | Rawls-Meehan | Feb 2013 | B2 |
| 8393026 | Dionne et al. | Mar 2013 | B2 |
| 8400311 | Dixon et al. | Mar 2013 | B2 |
| 8413274 | Weismiller et al. | Apr 2013 | B2 |
| 8416088 | Ortega et al. | Apr 2013 | B2 |
| 8419650 | Cosentino et al. | Apr 2013 | B2 |
| 8419660 | Shaw | Apr 2013 | B1 |
| 8432287 | O'Keefe et al. | Apr 2013 | B2 |
| 8438038 | Cosentino et al. | May 2013 | B2 |
| 8438680 | Wurdeman | May 2013 | B2 |
| 8461982 | Becker et al. | Jun 2013 | B2 |
| 8464380 | Bobey et al. | Jun 2013 | B2 |
| 8474072 | O'Keefe et al. | Jul 2013 | B2 |
| 8474076 | Hornbach | Jul 2013 | B2 |
| 8487774 | Reeder et al. | Jul 2013 | B2 |
| 8499385 | Horitani | Aug 2013 | B2 |
| 8525682 | Dixon et al. | Sep 2013 | B2 |
| 8533879 | Taylor | Sep 2013 | B1 |
| 8537008 | Tallent et al. | Sep 2013 | B2 |
| 8565934 | Rawls-Meehan | Oct 2013 | B2 |
| 8593284 | Tallent et al. | Nov 2013 | B2 |
| 8616438 | Zerhusen et al. | Dec 2013 | B2 |
| 8618918 | Tallent et al. | Dec 2013 | B2 |
| 20020014951 | Kramer et al. | Feb 2002 | A1 |
| 20020044059 | Reeder et al. | Apr 2002 | A1 |
| 20020053086 | Vanderpohl, III et al. | May 2002 | A1 |
| 20020059679 | Weismiller et al. | May 2002 | A1 |
| 20020152211 | Jam | Oct 2002 | A1 |
| 20020196150 | Wildman | Dec 2002 | A1 |
| 20030052787 | Zerhusen et al. | Mar 2003 | A1 |
| 20050172405 | Menkedick | Aug 2005 | A1 |
| 20060058587 | Heimbrock | Mar 2006 | A1 |
| 20060180054 | George et al. | Aug 2006 | A1 |
| 20060260054 | Lubbers | Nov 2006 | A1 |
| 20070120689 | Zerhusen et al. | May 2007 | A1 |
| 20070124177 | Engleson et al. | May 2007 | A1 |
| 20070180616 | Newkirk | Aug 2007 | A1 |
| 20070210917 | Collins, Jr. | Sep 2007 | A1 |
| 20090096615 | Reeder | Apr 2009 | A1 |
| 20100073168 | Tallent et al. | Mar 2010 | A1 |
| 20100154124 | Zerhusen et al. | Jun 2010 | A1 |
| 20110208541 | Wilson | Aug 2011 | A1 |
| 20110234411 | Harrington et al. | Sep 2011 | A1 |
| 20110245979 | Koch | Oct 2011 | A1 |
| 20120004789 | Wilker, Jr. | Jan 2012 | A1 |
| 20120086575 | Dixon et al. | Apr 2012 | A1 |
| 20120137439 | Heimbrock | Jun 2012 | A1 |
| 20130043997 | Cosentino et al. | Feb 2013 | A1 |
| Number | Date | Country |
|---|---|---|
| 101668503 | Sep 2013 | CN |
| 10141053 | Jan 2006 | DE |
| 102010031530 | Jan 2012 | DE |
| 0168158 | Jan 1986 | EP |
| 0 376 066 | Aug 1995 | EP |
| 656183 | Aug 2001 | EP |
| 1524759 | Apr 2005 | EP |
| 2093724 | Aug 2009 | EP |
| 2093988 | Aug 2009 | EP |
| 2119421 | Nov 2009 | EP |
| 2181685 | May 2010 | EP |
| 2460503 | Jun 2012 | EP |
| 2495708 | Sep 2012 | EP |
| 2495711 | Sep 2012 | EP |
| 2495712 | Sep 2012 | EP |
| 2575263 | Apr 2013 | EP |
| 2586413 | May 2013 | EP |
| 2599435 | Jun 2013 | EP |
| 2 218 149 | Nov 1989 | GB |
| 2 333 391 | Jul 1999 | GB |
| WO 9413198 | Jun 1994 | WO |
| WO 9422098 | Sep 1994 | WO |
| 9705844 | Feb 1997 | WO |
| WO 9802107 | Jan 1998 | WO |
| WO 9808203 | Feb 1998 | WO |
| WO 9829775 | Jul 1998 | WO |
| WO 9942021 | Aug 1999 | WO |
| WO 9952487 | Oct 1999 | WO |
| WO 0003344 | Jan 2000 | WO |
| WO 0157610 | Aug 2001 | WO |
| 0185085 | Nov 2001 | WO |
| WO 0197745 | Dec 2001 | WO |
| 2005102242 | Nov 2005 | WO |
| 2006046928 | May 2006 | WO |
| 2010088575 | Aug 2010 | WO |
| 2012010588 | Jan 2012 | WO |
| Entry |
|---|
| Partial European Search Report for Application No. EP 13189571 dated Feb. 6, 2014, 6 pages. |
| Extended European Search Report for Application No. EP 13189571 dated May 28, 2014, 9 pages. |
| Pyxis PatientStation . . . Copyrgt. Bedside Computing System by CardinalHealth, http://www.pyxis.com/prodDetails.aspx?pid=55, last accessed Jan. 18, 2007, original date of publication unknown. |
| Tierney, W., Miller, M., & McDonald, C. (1990). The effect on test ordering of informing physicians of the charges for outpatient diagnostic tests. The New England journal of medicine, 322(21), 1499-1504. |
| McDonald, C. J., Overhage, J. M., Abernathy, G., Harris, L., Smith, R. N., Terry Hogan, R. N., . . . & Tucker, M. The Regenstrief Medical Record System (RMRS): Physician use for input and output and Web browser based computing. |
| European Search Report dated Mar. 21, 2011 for EP 10 00 3711, 7 pages. |
| Partial European Search Report dated Mar. 23, 2011 for EP 10 07 5540, 3 pages. |
| Partial European Search Report dated Mar. 24, 2011 for EP 10 07 5542, 3 pages. |
| European Search Report dated Aug. 10, 2011 for EP 10 07 5540, 9 pages. |
| European Search Report dated Aug. 10, 2011 for EP 10 07 5542, 12 pages. |
| Extended European Search Report, European Application No. 15202342.0, completed Apr. 12, 2016, (9 pages). |
| Number | Date | Country | |
|---|---|---|---|
| 20140115784 A1 | May 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61719239 | Oct 2012 | US |
