AU776068B2 - Patient medical data recordal system - Google Patents

Description

AUSTRALIA

Patents Act 1990 COMPLETE SPECIFICATION STANDARD PATENT Applicant(s): SMART CARD PRODUCTS PTY LTD Invention Title: PATIENT MEDICAL DATA RECORDAL SYSTEM The following statement is a full description of this invention, including the best method of performing it known to me/us: 2 A PATIENT MEDICAL DATA RECORDAL SYSTEM Field of the Invention The present invention relates to a patient medical data recordal system for facilitating secure recordal and retrieval of patient medical data.

In the context of the present specification, the following terms will be given the following meanings.

"ADMISSION"

An admission refers to a consultation or series of consultations which occur within a hospital for the purpose of providing a patient with a health service or health services.

"FUND"

A fund is an organisation with which patients have chosen to be associated for medical insurance purposes, the fund providing finance to pay for health services received by patients associated with the fund. A fund may be commercial or non-commercial and may be privately operated or government operated.

"OCCASION OF SERVICE" An occasion of service refers to a consultation whereby a patient is provided with a health service or health services, not being a health service provided as part of an admission.

"PROVIDER"

A provider is a person providing health services whether as part of an admission or as part of an occasion of service. Examples of providers are Doctors, medical specialists and pharmacists.

I 3

"OPERATOR"

An operator is a person who operates an interface terminal of the system. Examples of operators are providers, and support staff, administrators and managers associated with providers.

"PARTICIPANT"

A participant is a person associated with the system as a patient and/or as an operator.

"PRACTICE"

A practice refers to an organisation which either provides occasions of service or which provides admissions. Examples of practices include doctor's surgeries, pharmacies, medical laboratories, and hospitals.

"RECORD MANAGEMENT GROUP" A record management group is a collection of operators that are assigned the same access identifier to indicate that the operators are permitted to access a predetermined portion of stored patient data and/or are permitted to carry out certain actions. An operator may be a member of one or more than one record management group.

"REGULATOR"

A regulator is an organisation that is required to be notified of certain categories of occasion of service.

Summary of the Invention In accordance with an aspect of the present invention, there is provided a patient medical data recordal system including: at least one operator interface terminal arranged to receive patient medical data from an operator and to supply patient medical data to the operator; 4 at least one information storage device for storing patient medical data received from the at least one operator interface terminal; a central controller for coordinating transfer of information between the at least one operator interface terminal and the at least one information storage device; and communications means for facilitating transfer of information between the at least one operator interface terminal and the central controller and between the central controller and the at least one information storage device; wherein each operator terminal is arranged to forward patient medical data associated with a patient from the operator terminal to the central controller for storage in the at least one information storage device, and each operator terminal includes: identification means arranged to identify an operator and thereby permit or restrict operator access to the system by reading a data storage medium associated with the operator.

Preferably, the system also includes a patient data storage medium associated with the patient, the patient 00 "data storage medium providing identification means for 0 90 S: 25 identifying the patient to the system. Preferably, data transfer means provided which is arranged to transfer patient medical data associated with a patient to the data storage medium associated with the patient. Preferably, the arrangement is such that the patient medical data 30 stored on each respective patient data storage medium corresponds to at least a most recently received portion of the patient medical data associated with the patient ali .4 du u Ltu n i thle at Least one -nformticn ctcr a devJce 4 In this way, a patient medical data recordal system S 35 is provided which is secure because only operators holding an authorised data storage medium are allowed to access the stored medical data, and which (where there is a data 5 transfer means associated with a patient which is arranged to receive patient medical data) provides patients with a portable emergency backup of recent medical data.

In one embodiment, the system is arranged to allow a participant to access the system when a predetermined access identifier is associated with the participant.

Preferably, the access identifier indicates membership of at least one record management group. The system is preferably arranged such that each participant is a member of at least one record management group.

Preferably, the central controller is arranged to index patient medical data received as a result of each occasion of service or admission so as to indicate the storage location of the received patient medical data in the at least one information storage device and so as to indicate the identity of the patient with which the received patient medical data is associated.

The central controller is preferably also arranged to facilitate retrieval of medical data stored in the at least one information storage device on the basis of participant entered criteria.

The central controller is preferably also arranged to facilitate updating and/or modification of patient medical data stored in the at least one information storage 25 device.

The system may be arranged to store patient medical data as records with each record corresponding to an occasion of service or an admission. A record may include a request from a first provider for fulfilment by a second 30 provider, the record being updated by the second provider oooo when the fulfilment has occurred. The identity of the second provider may be specified in the record by the firqt nrnvi Her The central controller may also be arranged to record 35 all accesses to the system by providers and/or patients.

The central controller may also be arranged to forward selected medical data to a third party on request.

5a The third party may be a regulator or fund.

Where the system includes a data storage medium as arranged to store the patient medical data, the system may be arranged so that when a patient data storage medium has reached full capacity, the record corresponding to the oldest occasion of service or admission is overwritten first.

Each record may be classified according to the type oo* *o o.o* oo *ooo* o* go* *o• o* 6 of occasion of service or admission.

The system may be arranged so that patient medical data received as a result of an occasion of service or admission is transferred to a patient data storage medium during the occasion of service or admission. Preferably, if the patient medical data is not transferred to a patient data storage medium during an occasion of service or admission, the patient medical data is stored in the at least one data storage device and transferred to the patient data storage medium when the patient next attends an occasion of service or admission. For this purpose, a synchronisation data file may be stored on each patient data storage medium and on the system, the respective synchronisation data files on each patient data storage medium and on the system being changed when a change is made to the patient medical data stored on the patient data storage media and on the system, and a difference between respective synchronisation data files stored on a patient data storage medium and on the system indicating that transfer of patient medical data to the patient data storage media is required.

Preferably, the system is arranged such that specific data is securely exchanged between an interface terminal, the central controller and the information storage devices using asymmetric key cryptography.

Preferably, the system is arranged to create a session key when a participant accesses the system, the session key being used to secure all data transmitted between the operator interface terminal and the central controller.

Preferably, the identification means and the data transfer means are part of a card interface device arranged to read data from and write data to a data storage medium.

In a preferred embodiment, the card interface device is arranged to read a smart card and each data storage medium is a smart card.

7 Preferably, the communications means is the Internet.

Preferably, the at least one information storage device is at least one database.

In accordance with an alternative aspect of the present invention, there is provided a method of storing patient medical data, said method including the steps of: receiving patient medical data from an operator interface terminal; storing the received patient medical data in at least one information storage device; providing a central controller for coordinating transfer of information between the operator interface terminal and the at least one information storage device; providing communications means for facilitating transfer of information between the at least one operator interface terminal and the central controller and between the central controller and the at least one information storage device; forwarding the received patient medical data from the operator interface terminal to the central controller for storage in the at least one information storage device; identifying an operator and thereby permitting or restricting operator access to the system by reading a data storage medium associated with the operator.

o*oo 25 Preferably, the method includes the further step of identifying a patient by reading a data storage medium •associated with the patient. Preferably, the method includes the further step of transferring patient medical data associated with a patient to the data storage medium 30 associated with the patient. Preferably, the arrangement is such that the patient medical data stored on the patient data storage medium corresponds to at least a most e et l -L e -eV-L V- J.L ULU A L L±11 LLe"a with the patient and stored in the at least one 35 information storage device.

In accordance with a further aspect, the present invention provides a patient medical data apparatus 7a including: an operator interface terminal arranged to receive patient medical data from an operator and to

C

S

CC..

C

C

CC..

C

CC C

C*

C.

C C 8 supply patient medical data to the operator; the operator terminal being arranged to forward patient medical data associated with a patient from the operator terminal for storage in an information storage device for storing patient medical data; the operator terminal further including an identification means arranged to identify an operator and thereby permit or restrict operator access by reading a data storage medium associated with the operator; data transfer means arranged to transfer patient medical data associated with a patient to a respective data storage medium associated with the patient; and the arrangement being such that the patient medical data stored on each respective patient data storage medium corresponds to at least a most recently received portion of a medical data associated with the patient and stored in the information storage device.

In accordance with yet a further aspect, the present invention provides a patient medical arrangement including an identification means arranged to identify an operator of an operator interface terminal and thereby permit or restrict operator access to the operator interface terminal by reading a data storage medium associated with the operator, and a data transfer means arranged to transfer patient medical data associated with a patient to a respective data storage medium associated with the patient, wherein the operator interface terminal is arranged to receive patient medical data from an operator and to supply patient medical data to the operator, and is arranged to forward patient medical data associated with a patient to an information storage device for storing patient medical data, whereby the arrangement is such that the patient medical data stored on each respective patient data storage medium corresponds to at least the most recently received portion of the patient medical data associated with the patient and stored in at least one 9 information storage device.

In accordance with yet a further aspect, the present invention provides a data storage medium arranged for use with the system discussed above, and being arranged to operate as the patient data storage medium for storing patient data corresponding to at least a most recently received portion of the patient medical data associated with the patient.

In accordance with a yet a further aspect, the present invention provides a data storage medium arranged for use with the system discussed above, and being arranged to store an identification means for identifying an operator and thereby permitting or restricting operator access to the system.

In accordance with yet a further aspect, the present invention provides an information storage device arranged for operation of the system discussed above as the at least one information storage device, and including a computing system providing a database for storing patient medical data for access by the system.

In accordance with yet a further aspect, the present invention provides a computing system arranged to operate o as a central controller for use as the central controller the system discussed above, and being arranged to

C

25 coordinate transfer of information between at least one .operator interface terminal and at least one information C. storage device.

Brief Description of the Drawings ooe 0*oC An embodiment of the present invention will now be described, by way of example only, with reference to the 1~ C o* L L& CA I IaAI .V VVAA... L -1 Figure 1 is a block diagram of a patient medical data S 35 recordal system in accordance with the present invention; and Figures 2 to 8 are diagrammatic representations of 10 screens displayed to operators of interface terminals of the patient medical data recordal system shown in Figure 1.

Description of an Embodiment of the Present Invention In a broad sense, the present invention relates to a data recordal system which operates such that patient medical data entered by an operator as a result of an occasion of service or an admission is remotely stored in information storage devices, the stored medical data being accessible using any interface terminal operatively associated with the system. Each operator and each patient associated with the system is provided with a data storage medium which serves to identify the respective operator or patient. Each data storage medium also serves to authenticate the identity of the operator to thereby allow or deny access of the operator to the medical data.

In addition, each patient data storage medium also serves to store recent medical data for use, for example, by emergency services or in the event that the information storage devices are temporarily inaccessible and recent medical data relating to the patient is required.

In this way, a patient medical data recordal system is provided which is secure in that only operators holding a data storage medium are permitted to access the stored medical data, and which provides patients with a portable emergency backup of recent medical data stored on the patient's data storage medium.

Referring to the drawings, in Figure 1 there is shown a patient medical data recordal system 10 which includes a plurality of operator interface terminals 12 each of which i. located at a oractice, and a Dlurality of information storage devices, in this example in the form of a plurality of databases 14 remotely located relative to the interface terminals 12.

The system 10 also includes a central controller 16 11 in operative communication with the interface terminals 12 through first communications means 18, in this example the Internet, and in operative communication with the databases 14 through second communications means 20, in this example the Internet.

Each interface terminal 12 includes a computing device 21, and a card interface device 22 for cooperating with a data storage medium so as to read information stored on the data storage medium and to write information to the data storage medium.

The computing device 21 operates as an interface between the central controller 16 and an operator and is arranged to receive information from an operator, to forward the information to the central controller 16 through the Internet 18, and to receive information from the central controller 16 through the Internet 20 for display to the operator.

The type of information which is receivable from an operator includes patient medical data for storage, and search criteria for locating a particular patient, for retrieving particular medical data of the patient, or for retrieving personal and/or demographic information relating to the patient.

The type of information which is receivable by the computing device 21 for display includes medical data relating to a patient retrieved from the databases 14, and/or personal or demographic information relating to a patient.

In order for the computing device 21 to carry out the above-mentioned functions, to communicate with the central controller 16 through the Internet, and to communicate with the card interface device 22, the computing device 21 is provided with suitable software and hardware.

The card interface device 22 is arranged to cooperate with a data storage medium of the type known as a "smart card" wherein information is stored on an integrated circuit embedded into a card. Each smart card serves to 12 securely identify a participant by authentication of the smart card. Each smart card also serves to store data necessary for authentication and/or to store data relating to medical records. However, it will be understood that although the present embodiment is described in relation to smart cards, other data storage media may be used to facilitate authentication and thereby secure identification of a patient and/or to store data.

Each database 14 is arranged to store patient medical data and personal and/or demographic patient information.

The arrangement is such that patient medical data received by the interface terminals 12 as a result of an occasion of service or an admission is stored in the databases 14 and constitutes a medical record for the patient which is accessible by an operator from any of the interface terminals 12. All medical records relating to a particular patient are grouped together and constitute the medical history of the patient.

The central controller 16 coordinates transfer of information between the interface terminals 12 and the databases 14 through the Internet, and ensures that patient medical data received by an interface terminal 12 as a result of an occasion of service or an admission is indexed. Indexing serves to indicate the location of the data in the databases 14 and to indicate that the data is associated with a particular patient. The central controller 16 also serves to log all accesses to patient data for future reference and to coordinate authentication of the smart cards and thereby the identity of the operators and the patients.

The central controller 16 also operates so as to allow an operator to create a new medical data record as a result of dAta received by an interface terminal 12.

During a new record creation operation, a request for creation of a new record is checked to see whether the requesting operator has the authority to make the request and, if so, the received data is indexed and transferred 13 to an appropriate database 14 for storage. Indexing the new record ensures that the record is associated with the correct patient and is retrievable from the correct database 14.

The central controller 16 also operates so as to allow an operator to retrieve medical data previously stored in the databases 14. During a data retrieve operation, a request for retrieval of data is checked to see whether the requesting operator has the authority to make the request and, if so, the requested medical data is retrieved from the appropriate database 14 or databases 14 and forwarded to the appropriate interface terminal 12 for display to the operator.

The central controller 16 also allows an operator to create a new version of a previously created medical data record. During a record replace operation, a request for replacement of a record is checked to see whether the requesting operator has the authority to make the request and, if so, a new index relating to the new record is created to replace the previous index relating to the previous record. However, the previous version of the record remains in the databases 14 together with the new version of the record.

The central controller 16 also operates so as to forward selected medical data to a third party such as a regulator or fund. This data may be automatically forwarded as part of a record creation operation or a record update operation.

The central controller 16 also operates so as to allow an operator to search for a patient when the patient has not been identified using a smart card. With such a patient search operation, patient identification criteria are entered 11using an intprface terminal 12 and potential matches are determined by the central controller 16 and forwarded to the interface terminal 12.

The central controller 16 also allows a patient to retrieve their own medical data. During a patient data 14 retrieve operation, a patient request is checked to see whether the patient is authorised to make the request and, if so, the requested data is retrieved from the database 14 or databases 14 and forwarded to the requesting patient for display.

Each provider is given a smart card including information in an encrypted form which serves to identify the provider. Each patient is given a smart card which includes information in an encrypted form which serves to securely identify the patient. Each patient smart card is also provided with encrypted medical data specific to the patient. The medical data on the patient's smart card corresponds to relatively recent medical data received as a result of relatively recent occasions of service and/or admissions. For example, the medical data on the patient's smart card may correspond to the five most recent occasions of service or admissions. When a patient smart card has reached full capacity, the record corresponding to the oldest occasion of service or admission is overwritten with the current occasion of service or admission.

The system 10 and each patient and provider are issued with one or more unique asymmetric key pairs which are identified by the patient or provider unique card number. Each key pair includes a private key and a public key and serves to secure the transfer of information between the interface terminal, the central controller 16 and the databases 14.

The patient or provider private keys are stored on the respective patient or provider smart card in a write only file, and the patient and provider public keys are stored at the central controller 16 as public key crtficates, certified by an appropriate certification authority.

The system private key is stored at the central controller 16 and the system public key is stored on each patient card and each provider card.

15 When a provider (or patient) introduces a smart card into the card interface device 22, the provider (or patient) smart card and the central controller 16 carry out mutual authentication to verify the authenticity of the smart card.

The public and private keys may also be used to secure transmission of specific data between an interface terminal and the central controller 16 and between the central controller 16 and the databases 14. When a provider logs onto the system 10 a session is established and a session key is created using the public and private keys which is used to secure specific data transmitted during the session.

Patients and providers are also assigned a password.

The password is used by the system 10 to confirm the identity of the participant.

Each participant may belong to at least one record management group. Each record management group allows its members to view certain data and/or to carry out predetermined operations. For example, only admission staff and ward staff may be authorised to create new patient admission records but all participants may be authorised to read the admission records once they have been created and/or updated. Membership of a record management group is indicated by a record management group identifier.

Generally, medical data will be transferred to the appropriate patient smart card during an occasion of service or admission when the patient smart card is present in the card interface device 22.

Data transfer to a patient smart card will be carried out in such a way that the data can not be partially updated evei f po. 7r nr crommunications are lost. Also, if for any reason a patient smart card is not updated at the time of the occasion of service or admission, the medical data relating to the occasion of service or admission is stored in the databases 14 and transferred to 16 the patient smart card automatically when the patient smart card is next inserted into a card interface device 22. This is done by checking whether the medical data on the patient smart card matches corresponding medical data stored in the databases. For this purpose, a synchronisation data file is included on each patient smart card and in the databases 14. The synchronisation data file includes sequence and revision numbers, the sequence numbers being changed when a new record is written to the card or the databases, and the revision numbers being changed when change is made to an existing record on the patient card or in the databases 14. A difference in either of these indicates that the medical data on the patient smart card does not match corresponding data stored in the databases. Before a record is written, its sequence and revision numbers are set to 0. When the record write operation is completed, the sequence number is set to the next available number and the revision number is set to 1. If a record sequence or revision number is found to be equal to 0 then the record is transferred from the databases 14 to the patient smart card.

Each medical data record is identified and classified as one of the following types: GP consultation; Specialist consultation, such as consultations with a cardiologist, psychologist, gastroenterologist, neurologist etc; Diagnostic test, such as radiology, pathology etc.

Drug, such as a prescription or non-prescription; Other, such as dentistry, optical, physiotherapy, prothesis, acupuncture, podiatry, naturopathy, homoeopathyv, chiropractic etc; and Hospital admission.

All types of records are managed and stored in the same way by the system. However, different classification types may be presented in different ways and access to 17 particular classification types may be restricted to particular record management groups.

A health service carried out by a provider may be identified as a request by a first provider for subsequent fulfilment by a second provider. For example, a prescription is written by a doctor and fulfilled sequentially by a pharmacist. In this type of situation a single record may be created for the occasion of service with the doctor, and the record updated by the pharmacist when the prescription has been fulfilled. However, it will be understood that for some situations a first record may be created for the request and a second record created for the subsequent fulfilment.

The record including the request may specify the provider who is to fulfil the request, for example where a specialist consultation is recommended by a GP and carried out by a specialist chosen by the GP. The request may also indicate a date by which the request should be fulfilled.

Operation of the system 10 will now be described in relation to the screen representations shown in Figures 2 to 8.

When an operator interface terminal 12 commences operation at the beginning of a day the system log on screen 24 as shown in Figure 2 is displayed. To log on, the provider associated with the operator interface terminal inserts his/her provider smart card into the card interface device 22, and the card interface device 22, the computing device 21 and the central controller 16 cooperate so as to authenticate the smart card. The provider then enters a unique password to verify the identity of the provider into the password box 28 on the system log in screen 24. Until this process has been carried out, the provider is not able to access the central controller 16 and thereby the medical data stored in the databases 14.

Following authentication of the patient smart card 18 and identification of the provider, a session is established and using the public and private keys a session key is created which is used to secure specific data transmitted during the session. The operator interface terminal 12 then displays a card waiting screen as shown at 30 Figure 3. The card waiting screen indicates to the provider that the system 10 is ready to accept a patient smart card.

When an occasion of service or admission has taken place, the patient inserts his/her smart card into the card interface device 22, and the authenticity of the card is verified by the computing device 21 and the central controller 16. Following authentication of the patient smart card, the provider may retrieve or create a record for the patient subject to access rights governed by the record management groups of which the provider is a member.

When a patient smart card is not available, retrieval or creation of records relating to the patient may only occur after carrying out a patient search. This may be done using a patient search screen 34 as shown in Figure 4 by entering the family name and date of birth of the patient into name and date of birth boxes 36, 38.

Once a patient smart card has been authenticated by the system or the patient has been located using the patient search screen 34, a patient details screen 40 as shown in Figure 5 is displayed.

The patient details screen 40 shows personal and demographic information relating to the patient and also gives the provider the option of entering a new record relating to a new occasion of service by selecting an occasion of service button 42, of entering a new record relatina to a new admission by selecting an admission button 44, or of reviewing a patient history by selecting the patient history button 46.

When the occasion of service button 42 is activated, an occasion of service screen 48 as shown in Figure 6 is 19 displayed. The occasion of service screen 48 allows the provider to enter information relating to an occasion of service into the system 10 for storage in a database 14.

Likewise, when the admission button 44 is activated, a hospital admission screen 50 as shown in Figure 7 is displayed. Using the hospital admission screen 50, the provider may enter appropriate information relating to the admission into the system 10 for storage in a database 14.

The entered information is securely transmitted to the central controller 16 using the session key.

When the patient history button 46 is activated, a patient history screen 52 as shown in Figure 8 is displayed. As shown in Figure 8, the patient history screen shows details of occasions of service and hospital admissions for the patient in a tabulated form. More complete views of each occasion of service or admission may be viewed by activating an appropriate view button 54.

In a further optional arrangement of the system, as well as providing medical data from operators, automated updates of medical data may be provided from external patient record management systems for storage in the database 14. The same security mechanisms are implemented in this embodiment as for operators at work stations (eg.

asymmetric key cryptography).

For example, medical data may be "dumped" from the desktop system of a doctor's surgery (eg. Medical Directorm) or from a hospital management system, in addition to the information input by the operator.

In the embodiment described above, a plurality of databases 14 for storing patient medical data are disclosed. It will be appreciated that there may be a single database only. In one embodiment, however, information relatina to a particular patient may be split between databases (deagregated) for the purposes of security. Central controller 16 may then need to access a plurality of databases to bring back patient information.

Where methods and apparatus of the present invention 20 may be implemented by software applications, or partly implemented by software, then they may take the form of program code stored or available from computer readable media, such as CD-ROMS or any other machine readable media, the program code comprising instructions which, when loaded onto a machine such as a computer, the machine then becomes an apparatus for carrying out the invention.

The computer readable media may include transmission media, such as cabling, fibre optics or any other form of transmission media.

It will also be appreciated that, where methods and apparatus of the present invention are implemented by computing systems, or partly implemented by computing systems, then any appropriate computing system architecture may be utilised. This will include standalone computers, networked computers, and dedicated computing devices. Where the terms "computing system" and "computing device" are used, then these terms are intended to cover any appropriate arrangement of computer hardware for implementing the function described.

It will be appreciated that the present patient medical data recordal system provides improved data security and privacy for patient medical data since access to medical data by providers is only allowed after authentication of a smart card associated with the provider.

It will also be appreciated that the present system decreases paper work and facilitates easier retrieval of the medical history of patients than systems known hitherto.

It will also be appreciated that the system provides patients with an important safety measure since critical data relatina to most recent occasions of service and/or hospital admissions for the patient are stored on the patient's smart card.

Furthermore, it will be appreciated that by providing a system in accordance with the present invention, costs 21 for patients and providers may be reduced.

It will also be appreciated that the system 10 may be interfaced with medical insurance companies and/or governments so that medical payments and admission operations may be simplified.

Modifications and variations as would be apparent to a skilled addressee deemed to be within the scope of the present invention.

Claims (37)

1. 3. A system as claimed in claim 2, wherein the system is arranged to store patient medical data as records, each record corresponding to an occasion of service or an admission, and wherein when a patient data storage medium has reached full capacity, the record corresponding to the oldest occasion of service or admission is overwritten first.
2. 4. A system as claimed in any one of claims 2 or 3, wherein the system is arranged to store patient medical data as records, each record corresponding to an occasion of service or an admission, and each record being classified according to the type of occasion of service or admission.
3. 5. A system as claimed in any one of claims 2 to 4, wherein patient medical data received as a result of an occasion of service or admission is transferred to a patient data storage medium during the occasion of service or admission.
4. 6. A system as claimed in claim 5, wherein if patient medical data is not transferred to a patient data oeee storage medium during an occasion of service or admission, the patient medical data is stored in the at o least one data storage device and transferred to the oooo 25 patient data storage medium when the patient next attends an occasion of service or admission.
5. 7. A system as claimed in claim 6, wherein a synchronisation data file is stored on each patient data storage medium and on the system, the respective ooeo synchronisation data files on each patient data storage .medium and on the system being changed when a change is made to the patient medical data stored on the patient oooo 3n -3iffeMeC data storaye irnedi ducid oUn Liie yaey.i, a a differece between respective synchronisation data files stored on a patient data storage medium and on the system indicating that transfer of patient medical data to the patient data storage media is required. 24
6. 8. A system as claimed in any one of the preceding claims, wherein the system is arranged to allow a participant to access the system when a predetermined access identifier is associated with the participant.
7. 9. A system as claimed in claim 8, wherein the access identifier indicates membership of at least one record management group. A system as claimed in claim 9, wherein the system is arranged such that each participant may be member of at least one record management group.
8. 11. A system as claimed in any one of the preceding claims, wherein the central controller is arranged to index patient medical data received as a result of each occasion of service or admission so as to indicate the storage location of the received patient medical data in the at least one information storage device and so as to indicate the identity of the patient with which the received patient medical data is associated.
9. 12. A system as claimed in any one of the preceding claims, wherein the central controller is arranged to facilitate retrieval of medical data stored in the at least one information storage device on the basis of participant entered criteria.
10. 13. A system as claimed in any one of the preceding 25 claims, wherein the central controller is arranged to facilitate updating and/or modification of patient medical data stored in the at least one information storage device.
11. 14. A system as claimed in any one of the preceding claims, wherein the system is arranged to store patient medical data as records with each record corresponding to an occasion of service or an ~admission.
12. 15. A system as claimed in claim 14, wherein a record includes a request from a first provider for fulfilment by a second provider, the record being updated by the second provider when the fulfilment has 25 occurred.
13. 16. A system as claimed in claim 15, wherein the identity of the second provider is specified in the record by the first provider.
14. 17. A system as claimed in any one of the preceding claims, wherein the central controller is arranged to record all accesses to the system by providers and/or patients.
15. 18. A system as claimed in any one of the preceding claims, wherein the central controller is arranged to forward selected medical data to a third party on request.
16. 19. A system as claimed in claim 18, wherein the third party is a regulator or fund.
17. 20. A system as claimed in any one of the preceding claims, wherein the system is arranged such that specific data is securely exchanged between a participant, the central controller and the at least one information storage device using asymmetric key cryptography.
18. 21. A system as claimed in claim 20, wherein the system is arranged to create a session key when a participant V* accesses the system, the session key being used to :o:secure specific data transmitted between the operator S 25 interface terminal, the central controller and the at least one information storage device.
19. 22. A system as claimed in any one of the preceding claims, wherein the identification means and the data transfer means are part of a card interface device S 30 arranged to read data from and write data to a data storage medium.
20. 23. A system as claimed in any one of the preceding ~claims, wherein the card interface device is arranged read a smart card and each data storage medium is a smart card.
21. 24. A system as claimed in any one of the preceding claims, wherein the communications means is the 26 Internet. A system as claimed in any one of the preceding claims, wherein the at least one information storage device is at least one database.
22. 26. A method of storing patient medical data, said method including the steps of: receiving patient medical data from an operator interface terminal; storing the received patient medical data in at least one information storage device; providing a central controller for coordinating transfer of information between the operator interface terminal and the at least one information storage device; providing communications means for facilitating transfer of information between the at least one operator interface terminal and the central controller and between the central controller and the at least one information storage device; forwarding the received patient medical data from the operator interface terminal to the central controller for storage in the at least one information storage device, and eidentifying an operator and thereby permitting 25 or restricting operator access to system by reading a data storage medium associated with the operator.
23. 27. A method in accordance with claim 26, including the further step of transferring patient medical data associated with a patient to a respective data storage medium associated with the patient; the arrangement being such that the patient medical data stored on each respective patient data storage medium corresponds to at least a most recently received portion of the patient medical data associated with the patient and stored in the at least one information storage device.
24. 28. A patient medical data recordal system substantially as 27 hereinbefore described with reference to the accompanying drawings.
25. 29. A method of storing patient medical data substantially as hereinbefore described with reference to the accompanying drawings. A patient medical data apparatus including: an operator interface terminal arranged to receive patient medical data from an operator and to supply patient medical data to the operator; the operator terminal being arranged to forward patient medical data associated with a patient from the operator terminal for storage in an information storage device for storing patient medical data; the operator terminal further including an identification means arranged to identify an operator and thereby permit or restrict operator access by reading a data storage medium associated with the operator, and data transfer means arranged to transfer patient medical data associated with a patient to a respective data storage medium associated with the patient; and the arrangement being such that the patient S: medical data stored on the patient data storage medium 25 corresponds to at least a most recently received portion of a medical data associated with the patient and stored in the information storage device.
26. 31. A patient medical data arrangement including an identification means arranged to identify an operator 30 of an operator interface terminal and thereby permit or restrict operator access to the operator interface :terminal by reading a data storage medium associated with the operator, and S.a data transfer means arranged to transfer patient medical data associated with a patient to a respective data storage medium associated with the patient, 28 wherein the operator interface terminal is arranged to receive patient medical data from an operator and to supply patient medical data to the operator, and is arranged to forward patient medical data associated with a patient to an information storage device for storing patient medical data, whereby the arrangement is such that the patient medical data stored on each respective patient data storage medium corresponds to at least the most recently received portion of the patient medical data associated with the patient and stored in at least one information storage device.
27. 32. An arrangement in accordance with claim 31, wherein the identification means and data transfer means are included in a smart card reader/writer.
28. 33. A data storage medium adapted for use with the system of any one of claims 1 to 25, and being arranged to operate as a patient data storage medium for storing patient data corresponding to at least a most recently received portion of the patient medical data associated with the patient.
29. 34. A data storage medium adapted for use with the system of any one of claims 1 to 25, and being arranged to store an identification means for identifying an operator and thereby permitting or restricting operator 25 access to the system.
30. 35. An information storage device adapted for operation of the system of any one of claims 1 to 25 as the at least one information storage device, and including a computing system providing a database for storing S 30 patient medical data for access by the system.
31. 36. A computing system adapted to operate as a central o :controller for use as the central controller of the system of any one of claims 1 to 25, and being arranged to coordinate transfer of information between at least one operator interface terminal and at least one information storage device.
32. 37. A computer program, arranged, when loaded onto a 29 computing system, to control the computing system to implement a patient medical data recordal system in accordance with any one of claims 1 to
33. 38. A computer readable medium providing a computer program in accordance with claim 37.
34. 39. A computer program arranged to, when loaded onto a computing system, control the computing system to implement a patient medical data apparatus in accordance with claim
35. 40. A computer readable medium providing a computer program in accordance with claim 39.
36. 41. A computer program arranged, when loaded onto a computing device, to control the computing device to implement a patient medical data arrangement in accordance with claim 31.
37. 42. A computer readable medium providing a computer program in accordance with claim 41. Dated this 14 th day of April 2004 SMART CARD PRODUCTS PTY LTD By their Patent Attorneys GRIFFITH HACK .oo oO* a o o o*,o o oo. *go.