GB2533910A

GB2533910A - Wireless processing unit and method for collecting patient test data from point of care devices

Info

Publication number: GB2533910A
Application number: GB1419022.7A
Authority: GB
Inventors: Farish Neil; Stevens Marryat; Rentas Nestor
Original assignee: Goodmark Medical (international) Ltd
Current assignee: Goodmark Medical (international) Ltd
Priority date: 2014-10-24
Filing date: 2014-10-24
Publication date: 2016-07-13
Also published as: GB201419022D0

Abstract

A point of care processing unit (30) comprising a device interface for receiving patient test data for a patient test from at least one point of care device(11a-11d); a cellular wireless interface for transmitting the patient test data to a remote server system (60) over a cellular wireless communication system; and a processor programmed to control the device interface to receive the patient test data, and to control the cellular wireless network interface to transmit the patient test data to the server system over the cellular wireless communication system. Preferably, if the cellular wireless network is not available than a local area wireless network is used to transmit the patient test data to the remote server system.

Description

WIRELESS PROCESSING UNIT AND METHOD FOR COLLECTING PATIENT

TEST DATA FROM POINT OF CARE DEVICES

FIELD OF THE INVENTION

[0001] The present invention generally relates to a wireless processing unit and method for collecting patient test data from point of care devices.

BACKGROUND OF THE INVENTION

[0002] Point-of-care testing (POCT) is medical testing at or near the site of patient care. The driving notion behind POCT is to bring the test conveniently and immediately to the patient. This increases the likelihood that the patient, physician, and care team will receive the results quicker, which allows for immediate clinical management decisions to be made. POCT includes: blood glucose testing, blood gas and electrolytes analysis, rapid coagulation testing, rapid cardiac markers diagnostics, drugs of abuse screening, urine strips testing, pregnancy testing, faecal occult blood analysis, food pathogens screening, haemoglobin diagnostics, infectious disease testing and cholesterol screening.

[0003] POCT is often accomplished through the use of transportable, portable, and handheld instruments (e.g., blood glucose meter, nerve conduction study device) and test kits. Small bench analysers or fixed equipment can also be used when a handheld device is not available the goal is to collect the specimen and obtain the results in a very short period of time at or near the location of the patient so that the treatment plan can be adjusted as necessary before the patient leaves. Cheaper, smaller, faster, and smarter POCT devices have increased the use of POCT approaches by making it cost-effective for many diseases, such as diabetes, carpal tunnel syndrome (CTS) and acute coronary syndrome.

[0004] There is a desire to get output of a POCT device made available immediately within an electronic medical record. The advantage of such integration into electronic medical health records is that results can be shared instantaneously with all members of the medical team through the software interface enhancing communication by decreasing turnaround time (TAT). Also, errors caused by manual input are avoided. One of the challenges accompanying the use of POCT is the plethora of devices and tests which brings with it a high degree of complexity in integrating the POCT devices due to the lack of any agreed standard for data output from such devices. To further complicate matters, there are a number of electronic health record providers, each with its own requirements and non-standard data format.

SUMMARY OF THE INVENTION

[0005] One aspect of the invention provides a point of care processing unit comprising a device interface for receiving patient test data for a patient test from at least one point of care device; a cellular wireless interface for transmitting the patient test data to a remote server system over a cellular wireless communication system; and a processor programmed to control the device interface to receive the patient test data, and to control the cellular wireless network interface to transmit the patient test data to the server system over the cellular wireless communication system.

[0006] Another aspect of the invention provides a method of processing data from at least one point of care device at a point of care processing unit, the method comprising controlling a device interface to receive patient test data for a patient test from at least one point of care device; and controlling a cellular wireless network interface to transmit the patient test data to a remote server system over a cellular wireless communication system.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Figure 1 is a schematic diagram of a system for processing patient test data according to one embodiment; [0008] Figure 2 is a schematic diagram of a POC processor application according to one embodiment; [0009] Figure 3 is a schematic diagram of an application server according to one embodiment; [0010] Figure 4 is flow diagrams illustrating a method of installing and configuring the POC processor application according to one embodiment; [0011] Figure 5 is a flow diagram illustrating a method of configuring the POC processor application according to one embodiment; [0012] Figures 6 is a flow diagram illustrating the method of processing patient test data according to one embodiment; and [0013] Figure 7 is a schematic diagram of a POC processing unit according to one embodiment.

DETAILED DESCRIPTION OF EMBODIMENTS

[0014] A first generalised embodiment comprises a point of care processing unit comprising a device interface for receiving patient test data for a patient test from at least one point of care device; a cellular wireless interface for transmitting the patient test data to a remote server system over a cellular wireless communication system; and a processor programmed to control the device interface to receive the patient test data, and to control the cellular wireless network interface to transmit the patient test data to the server system over the cellular wireless communication system.

[0015] This embodiment of the invention provides a standalone processing unit capable of communicating with a number of point of care devices in a point of care location to gather patient test data and transmit it over a cellular wireless communication link to a remote server system for processing and storage. The use of the cellular wireless communication link enables the unit to communicate with the remote server independent of the computer technology and network of the location in which it is operating. The inventors have realised that point of care devices are often provided at point of care centres which have in place a local network with access to the interaet which is under the control of the point of care centre. It is not under the control of the service provider operating the server system communicating with the point of care processing unit. Thus the provision of the cellular wireless communications capability to communicate with the server system of the service provider enables the service provider to provide a patient test gathering service that is independent of the point of care location technology i.e. the point of care processing unit does not require to be interfaced into the local network of the point of care provider and the issues of control and network limitations, such as firewalls and permissions are overcome. The network connection between the point of care processing unit and the server system can be direct via a cellular wireless service provider e.g. an internet connection (Internet Protocol -IF). This configuration also provides a system which is easy to set up and requires minimal involvement of the POCT facility personnel.

[0016] As used herein, patient test data comprises any data output from point of care devices, including test data for a patient test, calibration data from the calibration of the point of care device and any other data output from the point of care device for regulatory or safety purposes.

[0017] In one embodiment, no user interface is provided locally and physically connected to the unit i.e. no display, keyboard or pointing device. The intention of this embodiment is that the POC facility staff should play no role in configuring or maintaining the unit. The unit should be self-sufficient or remotely configurable. This avoids the need for training POC facility staff to use the unit and provides security by the lack of local on-site user interface.

[0018] In one embodiment, the point of care processing unit includes a local area wireless network interface for connection to a local area wireless network and for transmission of the patient test data to the remote server system over the local area wireless network; wherein the processor is configured to control the cellular wireless interface and the local area wireless network interface to initially try to connect the cellular wireless interface to the cellular wireless communication system, and if connection to the cellular wireless communication system cannot be achieved, to control the local area network wireless interface to connect to a local area wireless network.

[0019] In one embodiment, the point of care processing unit includes a local area wireless network parameter store storing parameters for known local area wireless networks; wherein the processor is configured to control the local area network wireless interface to identify any available local area wireless networks, to determine if any of the available local area wireless networks are known using the stored parameters for known local area wireless networks, and to control the local area wireless network interface to connect to a known local area wireless network in accordance with the determination.

[0020] In one embodiment, the point of care processing unit includes an update interface configured to receive a device storing updated parameters for known local area wireless networks, and the processor is configured to store the updated parameters for known local area wireless networks in the local area wireless network parameter store.

[0021] In one embodiment a said point of care device can communicate using one of a plurality of communication connection types, and the device interface comprises a plurality of port types, each port type corresponding to a communication connection type. This embodiment of the invention provides a point of care processing unit capable of connecting with multiple different point of care devices with different interface protocols and port types such as, WiFiTM, USB, serial, Ethernet, BluetoothTM [0022] In one embodiment the cellular wireless communication system comprises a 3G or 40 wireless system. Embodiments also encompass any intermediate cellular wireless standards such as 3.5G.

[0023] Tn one embodiment the processor is adapted to execute code specific to the or each said point of care device to control the device interface to communicate with the or each point of care device to obtain the patient test data as a set of data for a patient test, and to control the cellular or local area network wireless interface to transmit the set of patient test data to the server system over the cellular or local area wireless communication system.

[0024] In one embodiment the processor is adapted to execute the code specific to the or each point of care device to bidirectionally communicate with the or each point of care device to obtain the patient test data as the set of data for a patient test. In order to obtain a set of patient test data, the point of care device may require a two way communication session such as receiving acknowledgements for packages of data and in response to enquiry messages.

[0025] ffi one embodiment the processor is adapted to receive the code specific to the or each point of care device over the cellular or local area wireless communication system, or to receive configuration parameters speci lie to the or each point of care device over the cellular or local area wireless communication system and to generate the code specific to the or each point of care device using the received configuration parameters. The server system can download the code for execution by a processor in the point of care processing unit or just parameters can he downloaded. Such parameters can identify the code or code objects to be executed by the processor. In one embodiment, the code for execution to communicate with a point of care device is generated by use of the parameters and common objects (i.e. code objects which can be used to generate executable code for the processing of communications with many different point of care devices).

[0026] In one embodiment the processor is adapted to he configurable for a plurality of different point of care devices in response to communications received over the cellular or local area wireless communication system.

[0027] In one embodiment the processor is adapted to implement a web server to enable remote access for configuration over the cellular or local area wireless communication system.

[0028] In one embodiment the processor is adapted to be automatically configured when first connected to the cellular or local area wireless communication system by connecting to the remote server system and receiving initial configuration code and/or parameters. The initial configuration enables the point of care device to be simply installed out of the box with no point of care location user input. In one specific embodiment, once the unit is connected to the network, it may be configured on auto set up with code to communicate one or more point of care devices. Also, further configurations can take place later.

[0029] In one embodiment the point of care processing unit has a unique identifier, and the processor is adapted to transmit the unique identifier to the remote server system to request the initial configuration code and/or parameters. The unique identifier enables a unique configuration of the point of care processing unit.

[0030] In one embodiment the configuration code and/or parameters are dependent upon information registered for the point of care processing unit stored at the remote server system.

[0031] Another generalised embodiment comprises a method of processing data from at least one point of care device at a point of care processing unit, the method comprising controlling a device interface to receive patient test data for a patient test from at least one point of care device; and controlling a cellular wireless network interface to transmit the patient test data to a remote server system over a cellular wireless communication system.

[0032] In one embodiment, if connection to the cellular wireless communication system cannot be achieved, the method including controlling a local area network wireless interface to connect to a local area wireless network.

[0033] In one embodiment, parameters for known local area wireless networks are stored; and the local area network wireless interface is controlled to identify any available local area wireless networks, to determine if any of the available local area wireless networks are known using the stored parameters for known local area wireless networks, and to control the local area wireless network interface to connect to a known local area wireless network in accordance with the determination.

[0034] In one embodiment the method includes receiving a device storing updated parameters for known local area wireless networks in an update interface, and storing the updated parameters for known local area wireless networks in the local area wireless network parameter store.

[0035] In one embodiment a said point of care device can communicate using one of a plurality of communication connection types, and the device interface comprises a plurality of port types, each port type corresponding to a communication connection type.

100361 In one embodiment the cellular wireless communication system comprises a 30 or 40 wireless system.

[0037] In one embodiment the method includes executing computer code specific to the or each said point of care device to control the device interface to communicate with the or each point of care device to obtain the patient test data as a set of data for a patient test, and controlling the cellular or local area wireless interface to transmit the set of patient test data to the server system over the cellular or local area wireless communication system.

[0038] In one embodiment the code specific to the or each point of care device is executed to bidirectionally communicate with the or each point of care device to obtain the patient test data as the set of data for a patient test.

[0039] In one embodiment the method includes receiving the code specific to the or each point of care device, or receiving configuration parameters specific to the or each point of care device and generating the code specific to the or each point of care device using the received configuration parameters.

[0040] In one embodiment, the method includes receiving communications to configure the point of care unit for a plurality of different point of care devices.

[0041] In one embodiment, the method includes implementing a web server to enable remote access.

[0042] In one embodiment, the method includes automatically configuring the point of care processing unit when first connected to the cellular or local area wireless communication system by connecting to the remote server system and receiving initial configuration code and/or parameters.

[0043] In one embodiment, the point of care processing unit has a unique identifier, the method including transmitting the unique identifier to the remote server system to request the initial configuration code and/or parameters.

[0044] In one embodiment the configuration code and/or parameters are dependent upon information registered for the point of care processing unit stored at the remote server system.

[0045] In one embodiment a non-transient storage medium stores computer readable code for controlling a point of care processing unit having a device interface and a cellular wireless network interface to carry out any of the methods as described above.

[0046] In one embodiment a carrier medium carries computer readable code for controlling a point of care processing unit having a device interface and a cellular wireless network interface to carry out any of the methods as described above.

[0047] In the following detailed description, reference is made to the accompanying drawings that form a part hereof, and in which is shown by way of illustration specific embodiments in which the inventive subject matter may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice them, and it is to be understood that other embodiments may be utilized and that structural, logical, and electrical changes may be made without departing from the scope of the inventive subject matter. Such embodiments of the inventive subject matter may be referred to, individually and/or collectively, herein by the term "invention" merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed.

[0048] The following desmiption is, therefore, not to be taken in a limited sense, and the scope of the inventive subject matter is defined by the appended claims.

[0049] Some embodiments implement the functions in two or more specific interconnected hardware or software modules or devices with related control and data signals communicated between and through the modules, or as portions of an application-specific integrated circuit. Thus, the exemplary process flow is applicable to software, firmware, and hardware implementations.

100501 Embodiments of the present invention can be implemented on a processing unit using one or more computer programs or applications (software). The computer program(s) can be provided to the processing unit on any suitable carrier medium. One such type of medium is a computer storage medium which represents a non-transient medium. Computer storage media include random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM) and electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD ROM), Digital Versatile Disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium capable of storing computer-readable instructions. Another form of medium is a transient medium such as a signal. A signal can comprise an electrical signal over a wire, an electromagnetic signal transmitted over a wire or wirelessly, an optical signal, an acoustic signal, or even a magnetic signal. Once common form of signal is transmitted over a communication network which can be wired or wireless or a combination of both, e.g. a local area network (LAN), a wide area network (WAN) or the intcmct.

[0051] The point of care devices can comprises any device for carrying out any patient medical test at a point of care facility or even at the patients premises, such as blood glucose testing, blood gas and electrolytes analysis, rapid coagulation testing, rapid cardiac markers diagnostics, drugs of abuse screening, urine strips testin2, pregnancy testing, faecal occult blood analysis, food pathogens screening, haemoglobin diagnostics, infectious disease testing and cholesterol screening. A point of care facility can comprise any medical facility capable of providing such patient tests such as a doctor's surgery, a clinic, or a specialist centre. Where a point of care device is used by a patient in their own facilities either by themselves or by a visiting medical practitioner, the patient test data can be obtained as an output from the device on a storage media for later upload to a point of care computer, or as a signal to be transmitted over a communications network (wired or wireless) to the point of care computer).

[0052] Embodiments of the invention can be implemented with the systems and methods disclosed in US patent application number 14/462,722 filed on 19th August 2014, and co-pending application number GB1419021.9 fled herewith by the same applicants and entitled "System and method for generating patient test data processing code", the contents of both of which are hereby incorporated in their entirety by reference.

[0053] A first embodiment of the present invention will now be described with reference to figure 1.

[0054] Figure 1 schematically illustrates a patient test data gathering and processing system. Point of care devices lla to lld are provided to obtain patient test data. The point of care devices lla to llf are connected to input ports 31 in a point of care (POC) processing unit 30. The POC processing unit 30 is provided at a POC facility or accessible to a POC facility. Although only one POC processing unit 30 is illustrated connected to a network such as the interact 10 in this embodiment, many such units can be connected to access the point of care processing service provider as will be discussed in more detail hereinafter The POC devices lla to 1 If may be present at the POC facility or used at a remote location when portable e.g. at the patients premises or in a mobile facility. The POC devices lla to llf generate output patient test data as a result of a test being performed by an operator on a patient. The patient test data can be output using any known convenient method which depends upon the output capabilities of the POC device and includes: From POC device A (11a) over a serial line to a serial port in the POC processing unit 30 From POC device B (1 lb) over a USB link to a USB port in the POC processing unit 30 From POC device C (11c) over a wireless Wi-Fi link to a wireless port in the POC processing unit 30 From POC device D (11d) over a Bluetooth0 link to a Bluctooth0 port in the POC processing unit 30 From POC device E (11e) over an Ethernet line to an Ethernet port in the POC processing unit 30 From POC device F (11f) over an Internet connection to a an intcrnct network interface the POC processing unit 30 From a POC device the patient test data can also be stored onto a storage device such as a solid state memory device, an optical disk or even a magnetic disk to be read by an appropriate storage device port in the POC processing unit 30.

[0055] The POC processing unit 30 comprises a processor 32 connected to the input ports 31 for their control and to memory 33 for using by the processor 32 as working memory. A wireless transceiver 34 is provided under the control of the processor 32 for the transmission and reception of communications over a cellular wireless network using 30 or 40 communication protocols to establish an Internet Protocol (IP) connection to the internet 10. The wireless transceiver 34 communicates with a cellular wireless mast 71 operated by a mobile service provide operating a mobile service provider system 70 to provide the 11P connection with the internet 10. In order to communicate over the cellular wireless network, the wireless transceiver includes a Subscriber Identification Module (SIM) card. Also, the wireless transceiver 34 is able to communicate over a local area wireless network such as a WiFi network and hence also provides a local area wireless network interface. A local area wireless network provider system 20 is provided to which the POC processing unit 30 connects using the wireless transceiver 34. The local area wireless network can be any unsccure network e.g. a public network provided by an independent provider, or a public network provided by the POC facility such that the network connection is not subject to the facility's security constraints. Hence, a network connection to the service provider's computer 60 can be provided by a cellular wireless network or a local area wireless network in a manner which will be described hereinafter with reference to figure 4.

[00561 Electronic health records (EHR) are stored and maintained by EHR providers. There are a number of such providers available and different medical care providers use different EHR providers. The EHR providers host the EHR records in databases on computers 50. Each EHR provider's computer 50 implements a web server for interfacing via a network interface to the intemet 10 and an application server for providing the required functionality and interface to the EHR databases.

[00571 In this embodiment, the patient test data processing is hosted in a service provider's computer 60 comprising a server system implementing a Software as a Service (SaaS) model, where a 'thin client' in the form of the client application code is implemented on a POC processing unit 30.0n the service provider's computer 60 web services are implemented to provide the functionality. On the POC processing unit 30 a Windows® service is implemented to provide the functionality.

[00581 As shown in figure 1 schematically, a web server 61 is provided with access to web server data 66 to provide a web interface. This enables an operator of a client computer 40 operating a web browser 41 to login into the service and interact with interfaces generated by the web server 61 e.g. to view lists of and select cached patient test data, to input any required additional patient test data, to access and input operator qualification data etc. An application server 62 is provided to provide the functionality and access the device and user database 63, the test data database 64 and the compliance database in the data warehouse 600. Both the application server 62 and the web server 61 are connected by a network interface 67 to the internet 10. The device and user database 63 stores a library of test type objects defining a common data format for a type of test and hence forms a library store.

[0059] In the embodiment illustrated in figure 1, the system operates such that the operators of the POC devices lla to llf require access to the EHR records hosted by the EHR provider's computer 50 i.e. the POC facility does not have its own proprietary EHR and instead access EHR providers available to many POC facilities and providers.

[0060] Although in the embodiment of figure 1, for logical simplicity the wireless transceiver unit 34 is shown to perform as an interface to both the cellular wireless communication system and the local area wireless network, separate components (interfaces) can be provides for these.

[0061] Figure 2 is a schematic diagram of a client application according to one embodiment. The client application 31 comprises two functional code modules, namely a device interface code module 351 for sending and receiving data to and from POC devices lla to llf, and a service interface code module 352 for interfacing with the service provider's computer 60. In this embodiment, the device interface code module 351 is responsible for receiving the patient test data output from the POC devices lla to llf, and the service interface code module 352 is responsible for transmitting the patient test data to the service provider's computer 60. The service interface code 352 accesses local area wireless network parameters for the configuration of the local area network interface by accessing parameters stored in a local area wireless network connection parameters store 353. The parameters can include parameters identifying known networks e.g. network names, and parameters giving network security keys for the known networks to enable the unit to login and connect to the networks when required.

[0062] Figure 3 is a schematic diagram of an application server 62 hosted on the service provider's computer system 60 according to one embodiment. The application server 62 operates a core web services module 610 which has access to a cache memory 670 for temporary storage of patient test data pending approval and completion by operators, and which provides an interface 640 to the data warehouse 600. A compliance module 650 is implemented to provide regulatory compliance functionality. A reports module 660 is provided to enable users of the service with access to reports on patient tests and compliance. A device interface module 620 is provided which implements specific device modules 621 dependent upon the identity of the devices detected in the patient test data. The device modules 621 receive the patient test data and perform device specific processing on it, namely the data which is in a format specific to the device is parsed using a parser specific to the device to reformat the data according to a test type object dependent upon the test type identified for the patient test data. The library of test type objects in the data warehouse 600 is accessed to identify the test type. The patient test data reformatted according to the identified test type can then be stored in the cache 670 pending approval and completion by the operator. An EHR interface 630 is also provided and implements EHR modules 631 which are specific to the EHR provider to which the patient test data is to be transmitted. The EHR provider can be identified from an order identifier associated with the patient test. When a medical practitioner places an order for a POCT in an EHR, the order is assigned a unique identifier and it is associated with the patient record and patient identifier in the EHR. When a patient test is performed an operator will input a patient name or identifier enabling the order to be found in the EHR and hence associated with the patient test data in the cache 670 of the service provider's computer 60 pending completion and acceptance of the patient test data by the operator.

[0063] Figure 4 is a flow diagram illustrating a method of auto configuring the POC processing unit 30. In step S1 when the POC processing unit 30 is switched on it looks for a cellular wireless connection (step S2). A cellular wireless connection comprises an Internet Protocol (IIP) connection over a 3G or 4G network for example. When such a network connection is found in step S2, a connection is made over the IP network to the service provider's computer 60 in step S3 and a unique identifier for the POC processing unit 30 is transmitted to the service provider's computer 60, where it is used to look up configuration parameters and/or code for auto provisioning the POC processing unit 30.The code and/or parameters are transmitted by the service provider's computer 60 and received and stored by the POC processing unit 30 in step S5. Thus, the POC processing unit is uniquely configured automatically upon start up. In an alternative embodiment, auto-configuration is not performed (step S5), and configuration parameters can be communicated to the unit as and when required.

[0064] If in step S2, no cellular network connection is found within a predefined period of time, the processor 32 can control the local area wireless network interface component of the wireless transceiver 34 to determine whether there are any known local area wireless networks detected (step S6). The determination of whether the local area wireless networks are known is made by the processor with reference to the stored parameters in the parameter store 353. If no known local area wireless networks are detected in step S6, a warning is displayed on the unit e.g. a red light (step S7) and the process returns to step S2. If known local area wireless networks are detected in step S6, one is selected e.g. on the basis of a priority listing included in the parameters in the parameter store 353, and a network security key for the network determined from the stored parameters is transmitted to log into the network (step S8). If the network key is accepted by the network hub, the connection is successful (step S9) and the process returns to step S3. If the connection is not successful, a warning is displayed on the unit e.g. a red light (step S7) and the process returns to step S2.

[0065] It can be seen from the embodiment of figure 4 that in this embodiment, the unit 30 attempts to first connect to a cellular wireless network. Such a network can be a network subscribed to by the service provider to provide a network connection without any restrictions and under at least some control by the service provider. If the unit 30 is not within signal range of a cellular wireless network, a local area wireless network connection is made if possible to a network which is in a predefined list in the parameter store 353. The local area wireless networks in the list can comprise known public networks such as those offered by commercial providers as well as known public networks in geographic regions offered free for public use by businesses, including POC facilities. The parameter store 3253 of the unit 30 can be preconfigured with these parameters, which can the tailored for the known locations of deployment of the unit 30 or based on the company using the unit 30. Alternatively the parameter store 353 of the unit 30 can be preconfigured with a generic set of parameters. The parameters in the parameters store 353 can be later updated by connection of a storage device such as a solid state memory device (e.g. USB memory device, SD card, or Compact Flash) to the unit 30 via an update interface such as a USB port or a card reader. If a USB device is used, the USB port can comprise a USB port of the input ports 31 used for receiving data from the POC devices 11. Alternatively, a configuration computer can be connected to the unit e.g. by an Ethernet connection and a direct login to an IP address of the unit 30, to load the parameters into the parameter store 353 and to perform other configuration functions. Access to the unit 30 in this way can be protected by a password requirement for login.

[0066] The configuration code and/or parameters can be set up by an operator at the service provider's computer 60 or by a user using the client computer 40 to access the service. The user of the client computer 40 can be an operator at the POCT facility. Such as user can use any standard computer with internet access to access the service provider's computer.

[0067] Figure 5 is a flow diagram illustrating a method of configuring the POC processing unit 30 after die initial configuration. In step S 10 an operator uses the client computer 40 to login to the service at the service provider's computer 60. When a user selects to connect a new POC device lla to llf (step S11) a list of POC devices supported by the service is retrieved (step S12) and displayed listing the available POC devices for configuration for the service (step S13). A user then selects the appropriate POC device for installation from the displayed list (step S14) and configuration data parameters or code for the selected POC device is then retrieved. Such parameters include a device identifier and name, a connection type e.g. USB, Wi-Fi, serial, Ethernet, or Bluetooth, connection parameters e.g. port number, baud rate, parity etc. In addition to the POC device name, each POC device is assigned a unique identifier since a POC computer may be connected with more than one POC device with the same name e.g. ABC Inc Blood Tester. These retrieved configuration parameters are then transmitted to the POC processing unit 30 for storage (step S16). This process of downloading parameters avoids the need for the operator to have to input the configuration parameters and instead relics on having a library of configuration parameters for POC devices stored in the service provider's computer 60. Also, the parameters can comprise parameters associated with definition objects defining functions performed by the POC processing unit during the communication of the patient test data. The POC processing unit 30 can store a library of definition objects which are common to a plurality of POC processing units. The parameters can comprise parameters for the instantiation of a set of definition objects so that the POC processor unit can generate the code necessary for the processing of communication with a POC device. This will be described in more detail herein after with reference to figure 7.

[0068] A method of operating the patient test processing system according to one embodiment will now be described with reference to figure 6.

[0069] A patient test is perfoinied on a patient in step 520 and the POC device outputs the patient test data (step S21). The patient test data is received by the POC processing unit 30 via a POC port such as a serial port, a USB port, an Ethernet port, a Wi-Fi port or a Bluetooth® port (step S22) and the POC processor application 35 adds an identifier for the device POC processing unit 30, and a unique identifier and name for the POC device to the patient test data. The patient test data is then transmitted over a network interface to the service provider's computer 60 (step S24). Upon receipt at the service provider's computer 60 the device name is used to identify the device module 621 to implemented to process the patient test data from the POC device. The device module 621 verifies that the data is of the format that was expected for the POC device, parses the patient test data (step S25), and stores the parsed patient test data in the cache 670 (step S26). The parsing performed by the device modules 621 takes the patient test data from the POC device and formats the patient test data according to a test type determined from a test type library on the basis of the POC device name. In other words, each device module 621 is associated with a test type since it is associated with a device type, which can only produce patient test data of a certain test type. More than one device type can be associated with a test type, since different device types could be used to provide a test of the same type e.g. ABC Inc's Blood Monitor is one device type and XYZ's Blood Monitor is another device type but both provide patient test data of the same test type -Blood Test A. [0070] Hence the patient test data in the cache 670 (step S26) comprises unverified patient test data which is assigned a unique test identifier.

[0071] In step S28, the web browser 41 of the client computer 40 is used by an operator to open a user interface in the form of a web page retrieved from the web server 61 of the service provider's computer 60. The web page prompts the operator (assumed to be the operator of the POC device or at least the medical person responsible for verifying and completing the patient test) to enter operator login parameters. The operator is validated in step S29 in the conventional manner using a database of valid operators on the service provider's computer 60. The web page (user interface) at the client computer 40 then displays an input interface allowing the operator to input the patient name or unique identifier or an order identifier (step S30).The input patent name or identifier or order identifier is transmitted via the service provider's computer to the EHR provider's computer 50 in order look up pending orders matching the patient name or identifier or order identifier (steps S31 and S32). The resultant list of orders, which may be just a list of one, is returned via the service provider's computer 60 to the client computer 40 for display as a web page (a user interface) (step S33). The list will include order identifiers which will either inherently include an EHR provider identifier or a separate EHR provider identifier will be provided. The operator then selects an appropriate order that matches the patient test performed (step S34).

[0072] An operator can then use the web page to request a list of all patient tests held in the cache 670 requiring completion and verification from the service provider's computer (step S35). The request will identify the operator by their unique operator identifier. The service provider's computer 60 looks up all patient test data in the cache 670 and returns the test identifier, device name, test type and test date (step S36). The returned data is displayed at the client computer enabling the operator to use the web page (user interface) to acknowledge the test that they performed (step S37). In response to the selection by the operator to acknowledge or verify patient test data, the patient test data for the test is stored in the cache 670 with the order identifier and patient identifier (step S38).

[0073] The patient test data is then passed to the EHR interface 630 where the EHR provider to which the patient test data is to be sent is identified from the order identifier and any additional EHR identifier. This identification is used to implement a specific EHR module 631 for the patient test data to be transmitted to the EHR provider. The EHR module 631 has knowledge of the format of the data structure of patient test data in the EHR and can hence parse the patient test data from the test type format common to all patient test data in the service provider's computer 60 to the EHR specific data format or structure (step S39). The patient test data is then transmitted to the EHR provider's computer 50 for storage in the EHR database associated with the order identifier and the patient identifier (step S40).

[0074] A POC processing unit 30 of an alternative embodiment will now be described with reference to figure 7.

[0075] The POC processing unit includes input ports 31 connected to a processor 32, which is also connected to memory 33 and the wireless transceiver 34 as described with reference to the embodiment of figure 1. In this embodiment, the POC processing unit also included storage 36 storing object code 361, parameters 362 and code 363. The code in the code store 363 is executed by the processor 32 in a processor application 351 to control the communications to and from the POC devices 11 and to and from the service provider's computer 60. Hence, the code has to include code specific to each POC device II that is connected to the POC processing unit to handle the different communication protocols and even the different communication port. In one embodiment, the service provider's computer can download each code module for each POC device for storage in the code store 363. In another embodiment, the object store 361 stores a library of definition objects comprising objects or code for each of a plurality of functions which can be used to generate code for controlling communications between the POC processing unit and the POC devices. The service provider's computer can in this embodiment simply download parameters for each POC device to the POC processing unit for storage in the parameter store 362. The parameters identify the definition objects and instantiation parameters to instantiate the identified definition objects to generate the code for the POC device communications. The storage 36 also includes the local area wireless network store 353 storing the parameters for local area wireless network connection including local area wireless network names, security keys and order of connection priority in case more than one known network is detected by the unit 30, in order that a network connection preference is set by the parameters. The parameters are read and used by the processor 32 in the control of the wireless transceiver 34 when acting as a local area wireless network interface.

[0076] The processor 32 also implements a web server 322 to enable communications over the internet to the service provider's computer 60 and to the client computer 40. The web server can provide the service interface code 352 of the embodiment of figure 2. It can also allow operators to connect with the POC processing unit 30 using the web browser 41 to configure parameters of the POC processing unit. For example, the operator may directly enter configuration or instantiation parameters or cause the web server to request the required code or configuration parameters.

[0077] In an alternative embodiment, an operator can login to the web server of the service provider's computer and select the code or configuration parameters to be pushed to the POC processing device.

[0078] Communications between the POC processing unit 30 and the POC devices can be two way since many POC devices require some sort of return signal e.g. an acknowledgement in response to output data or an enquiry output. In one embodiment the POC processing unit is configured to carry out the two way communication in accordance with a code module specific for the communication with the POC device in order to collect a complete set of patient test data for onward transmission to the service provider's computer. Alternatively, the POC processing unit can simply pass on any data or control signals it receives from the POC devices to the service provider's computer and pass back to the POC devices any responses from the service provider's computer.

[0079] It will be readily understood to those skilled in the art that various other changes in the details, material, and arrangements of the parts and method stages which have been described and illustrated in order to explain the nature of the inventive subject matter may be made without departing from the principles and scope of the inventive subject matter as expressed in the subjoined claims.

Claims

CLAIMS1. A point of care processing unit comprising: a device interface for receiving patient test data for a patient test from at least one point of care device; a cellular wireless network interface for transmitting the patient test data to a remote server system over a cellular wireless communication system; and a processor programmed to control the device interface to receive the patient test data, and to control the cellular wireless network interface to transmit the patient test data to the server system over the cellular wireless communication system.
2. A point of care processing unit according to claim I. including a local area wireless network interface for connection to a local area wireless network and for transmission of the patient test data to the remote server system over the local area wireless network; wherein the processor is configured to control the cellular wireless interface and the local area wireless network interface to initially try to connect the cellular wireless interface to the cellular wireless communication system, and if connection to the cellular wireless communication system cannot be achieved, to control the local area network wireless interface to connect to a local area wireless network.
3. A point of care processing unit according to claim 2, including a local area wireless network parameter store storing parameters for known local area wireless networks; wherein the processor is configured to control the local area network wireless interface to identify any available local area wireless networks, to determine if any of the available local area wireless networks are known using the stored parameters for known local area wireless networks, and to control the local area wireless network interface to connect to a known local area wireless network in accordance with the determination.
4. A point of care processing unit according to claim 3, including an update interface configured to receive a device storing updated parameters for known local area wireless networks, and the processor is configured to store the updated parameters for known local area wireless networks in the local area wireless network parameter store.
5. A point of care processing unit according to any preceding claim, wherein a said point of care device can communicate using one of a plurality of communication connection types, and the device interface comprises a plurality of port types, each port type corresponding to a communication connection type.
6. A point of care processing unit according to any preceding claim, wherein the cellular wireless communication system comprises a 3G or 4G wireless system.
7. A point of care processing unit according to any preceding claim, wherein the processor is adapted to execute code specific to the or each said point of care device to control the device interface to communicate with the or each point of care device to obtain the patient test data as a set of data for a patient test.
8. A point of care processing unit according to claim 7, wherein the processor is adapted to execute the code specific to the or each point of care device to bidirectionally communicate with the or each point of care device to obtain the patient test data as the set of data for a patient test.
9. A point of care processing unit according to claim 7 or claim 8, wherein the processor is adapted to receive the code specific to the or each point of care device from the server system, or to receive configuration parameters specific to the or each point of care device from the server system and to generate the code specific to the or each point of care device using the received configuration parameters.
10. A point of care processing unit according to any one of claims 1 to 8, wherein the processor is adapted to he configurable for a plurality of different point of care devices in response to communications received from the server system
11. A point of care processing unit according to claim 10, wherein the processor is adapted to implement a web server to enable remote access.
12. A point of care processing unit according to any preceding claim, wherein the processor is adapted to be automatically configured when first connected to the remote server system to receive initial configuration code and/or parameters.
13. A point of care processing unit according to claim 12, wherein the point of care processing unit has a unique identifier, and the processor is adapted to transmit the unique identifier to the remote server system to request the initial configuration code and/or parameters.
14. A point of care processing unit according to claim 12 or claim 13, wherein the configuration code and/or parameters are dependent upon information registered for the point of care processing unit stored at the remote server system.
15. A method of processing data from at least one point of care device at a point of care processing unit, the method comprising: controlling a device interface to receive patient test data for a patient test from at least one point of care device; and controlling a cellular wireless network interface to transmit the patient test data to a remote server system over a cellular wireless communication system.
16. A method according to claim 15, wherein, if connection to the cellular wireless communication system cannot be achieved, the method including controlling a local area network wireless interface to connect to a local area wireless network.
17. A method according to claim 16, wherein parameters for known local area wireless networks are stored; and the local area network wireless interface is controlled to identify any available local area wireless networks, to determine if any of the available local area wireless networks are known using the stored parameters for known local area wireless networks, and to control the local area wireless network interface to connect to a known local area wireless network in accordance with the determination.
18. A method according to claim 17, including receiving a device storing updated parameters for known local area wireless networks in an update interface, and storing the updated parameters for known local area wireless networks in the local area wireless network parameter store.
19. A method according to any one of claims 15 to 18, wherein a said point of care device can communicate using one of a plurality of communication connection types, and the device interface comprises a plurality of port types, each port type corresponding to a communication connection type.
20. A method according to any one of claims 15 to 19. wherein the cellular wireless communication system comprises a 30 or 40 wireless system.
21. A method according to any one of claims 1152 to 20, including executing computer code specific to the or each said point of care device to control the device interface to communicate with the or each point of care device to obtain the patient test data as a set of data for a patient test.
22. A method according to claim 21, wherein the code specific to the or each point of care device is executed to bidirectionally communicate with the or each point of care device to obtain the patient test data as the set of data for a patient test.
23. A method according to claim 21 or claim 22, including receiving the code specific to the or each point of care device, or receiving configuration parameters specific to the or each point of care device and generating the code specific to the or each point of care device using the received configuration parameters.
24. A method according to any one of claims 15 to 22, including receiving communications to configure the point of care unit for a plurality of different point of care devices.
25. A method according to claim 24, including implementing a web server to enable remote access.
26. A method according to any one of claims 15 to 25, including automatically initially configuring the point of care processing unit by connecting to the remote server system and receiving initial configuration code and/or parameters.
27. A method according to claim 26, wherein the point of care processing unit has a unique identifier, the method including transmitting the unique identifier to die remote server system to request the initial configuration code and/or parameters.
28. A method according to claim 26 or claim 27, wherein the configuration code and/or parameters are dependent upon information registered for the point of care processing unit stored at the remote server system
29. A non-transient storage medium storing computer readable code for controlling a point of care processing unit having a device interface and a cellular wireless network interface to carry out the method of any one of claims 15 to 28.
30. A carrier medium carrying computer readable code for controlling a point of care processing unit having a device interface and a cellular wireless network interface to carry out the method of any one of claims 15 to 28.