WO2013161458A1 - サーバ装置、データ連携方法およびコンピュータプログラム - Google Patents
サーバ装置、データ連携方法およびコンピュータプログラム Download PDFInfo
- Publication number
- WO2013161458A1 WO2013161458A1 PCT/JP2013/058032 JP2013058032W WO2013161458A1 WO 2013161458 A1 WO2013161458 A1 WO 2013161458A1 JP 2013058032 W JP2013058032 W JP 2013058032W WO 2013161458 A1 WO2013161458 A1 WO 2013161458A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- information
- pharmacy
- user
- individual
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
- G16H20/13—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered from dispensers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
Definitions
- the present disclosure relates to a server device, a data linkage method, and a computer program.
- EHR Electronic Health Record
- a technique related to a medicine notebook a technique has been proposed in which information such as a medicine name and a medication method is recorded in advance, a medicine instruction book is generated based on the information, and printed (for example, , See Patent Document 1).
- information for storage is provided in a part of the medicine instruction book so that information on the medicine can be stored in a notebook or the like owned by the patient.
- the electronic medicine notebook can acquire immediate data and accumulate information, but the data acquisition timing is voluntarily presented by the user, so the information is not comprehensive or the information is limited. There is a side to be done. In addition, personal information may be miswritten or some information may remain unclassified.
- the present disclosure proposes a new and improved server device, data linkage method, and computer program capable of improving the security of electronic health data and improving the reliability of information.
- a data holding unit that holds at least data for each individual without holding information that can identify a specific individual, information that can identify a specific individual, and data for each individual
- a data registration unit that obtains at least the data from another held system and registers the data in the data holding unit, and the data registration unit uses the link ID linked with the other system.
- a server device is provided that acquires data from a system and registers the data in the data holding unit.
- information that can identify a specific individual and information that can identify the specific individual by obtaining at least the data from another system that holds at least data for each individual. And registering in the data holding unit that holds at least individual data without holding the data, and the step of registering in the data holding unit includes data from the other system using a linkage ID that cooperates with the other system. Is provided, and is registered in the data holding unit.
- information that can identify a specific individual and information that can identify the specific individual by obtaining at least the data from another system that holds at least data for each individual.
- the step of registering in the data holding unit is executed by using a linkage ID linked to the other system, and the step of registering in the data holding unit is executed by the computer.
- a computer program is provided for acquiring data from a system and registering it in the data holding unit.
- a new and improved server device, data linkage method, and computer program capable of improving security and improving information reliability for digitized health data. Can be provided.
- FIG. 1 is an explanatory diagram illustrating a configuration example of an information processing system 1 according to an embodiment of the present disclosure.
- FIG. 4 is an explanatory diagram illustrating a configuration example of a data center 100 included in an information processing system 1 according to an embodiment of the present disclosure.
- FIG. It is explanatory drawing which shows the structural example of the in-hospital system 300 contained in the information processing system 1 concerning one Embodiment of this indication.
- FIG. It is a flowchart shown in the example of a registration process of the user drug history information by the pharmacy system 400. It is a flowchart shown in the example of a registration process of the user drug history information by the pharmacy system 400. It is explanatory drawing which shows the operation
- 5 is a flowchart illustrating an example of a processing operation of the information processing system 1 according to an embodiment of the present disclosure. It is explanatory drawing which shows the operation
- 5 is a flowchart illustrating an example of a processing operation of the information processing system 1 according to an embodiment of the present disclosure. It is explanatory drawing which shows the operation
- FIG. 1 is an explanatory diagram illustrating a configuration example of an information processing system 1 according to an embodiment of the present disclosure.
- FIG. 1 is an explanatory diagram illustrating a configuration example of an information processing system 1 according to an embodiment of the present disclosure.
- FIG. 1 is an explanatory diagram illustrating a configuration example of an information processing system 1 according to an embodiment of the present disclosure.
- FIG. 1 is an explanatory diagram illustrating a configuration example of an information processing system 1 according to an embodiment of the present disclosure.
- FIG. 1 is an explanatory diagram illustrating a configuration example of an information processing system 1 according to an embodiment of the present disclosure.
- the information processing system 1 includes a data center 100, a health insurance association system 200, a hospital system 300, and a pharmacy system 400. Is done. As shown in FIG. 1, the data center 100, the health insurance association system 200, the in-hospital system 300, and the in-pharmacy system 400 are connected to each other via the network 10.
- the data center 100 stores information sent from the health insurance association system 200, the hospital system 300, and the pharmacy system 400 via the network 10.
- the information sent from the health insurance association system 200, the in-hospital system 300, and the in-pharmacy system 400 stored in the data center 100 via the network 10 is, for example, data on health for each individual.
- the data relating to health includes, for example, medical information and dispensing information of each individual.
- the data center 100 provides the recorded information in response to a request from the in-hospital system 300 or the pharmacy system 400. In the following description, it is assumed that the information stored in the data center 100 is data relating to health for each individual. A configuration example of the data center 100 will be described later.
- the health insurance association system 200 stores electronic receipt data generated based on medical information and dispensing information sent from a medical institution using the hospital system 300 or a pharmacy using the pharmacy system 400.
- the electronic receipt data held by the health insurance association system 200 is provided to the data center 100 in response to a request from the data center 100 or automatically.
- Information exchanged between the data center 100 and the health insurance association system 200 is very sensitive information such as medical information and dispensing information. Therefore, between the data center 100 and the health insurance association system 200, In addition to the network 10, it is desirable to be connected by a secure communication line 2 such as a dedicated line or a VPN (Virtual Private Network).
- a secure communication line 2 such as a dedicated line or a VPN (Virtual Private Network).
- the in-hospital system 300 is a system provided in a hospital where a patient (user) visits.
- the in-hospital system 300 holds, for each patient, personal / diagnosis information including patient personal information and drug history data as health data that is data related to the patient's health.
- the personal / medical examination information includes medical examination data including information on a prescription issued to a patient in a hospital or the like.
- personal / examination information held by the in-hospital system 300 is sent to the data center 100 through the network 10. When information is sent from the in-hospital system 300 to the data center 100, information that can identify the individual user is not sent.
- a configuration example of the in-hospital system 300 will be described later.
- the pharmacy system 400 is a system provided in a pharmacy where a patient purchases a prescribed medicine.
- the in-pharmacy system 400 holds personal / medical history information including patient personal information and drug history data as health data, which is data related to patient health, for each patient.
- the personal / medicine history information includes dispensing data including information regarding a drug dispensed for a patient at a pharmacy or the like, information regarding the drug, and the like.
- the personal / diagnosis information held by the pharmacy system 400 is sent to the data center 100 through the network 10. When information is sent from the pharmacy system 400 to the data center 100, information that can identify the individual user is not sent. A configuration example of the pharmacy system 400 will be described later.
- FIG. 1 also shows the IC card 20 used in the hospital system 300 and the pharmacy system 400.
- the IC card 20 stores a personal identification ID, which is a patient-specific ID, and performs proximity non-contact communication at a predetermined frequency with reader / writers 330 and 430 to be described later. 330, 430.
- the personal identification ID is identification information that can uniquely identify a user.
- the individual user identified by the personal identification ID is generally specified.
- personal information such as a user's name, address, and telephone number can specify the user almost directly from the information.
- an ID consisting of a number or a symbol is given to a user as a personal identification ID, it is not possible to specify the user of that personal identification ID from the personal identification ID unless the correspondence between the personal identification ID and the user is known. Have difficulty.
- the medium for obtaining the personal identification ID is not limited to an IC card or the like in which the personal identification ID is directly recorded, and may be a unique medium that cannot be rewritten or replaced.
- the medium for acquiring the personal identification ID is a part or all of the human body.
- FIG. 2 is an explanatory diagram illustrating a configuration example of the data center 100 included in the information processing system 1 according to an embodiment of the present disclosure.
- a configuration example of the data center 100 will be described with reference to FIG.
- the data center 100 includes a data server 110 and an information processing server 120.
- the data server 110 manages the drug history data supplied from the in-hospital system 300 or the pharmacy system 400, and records the recorded drug history data in response to a request from the hospital system 300 or the pharmacy system 400. provide.
- the data server 110 includes an in-server database 111, a communication unit 112, an update unit 113, a user search unit 114, and a drug history search unit 115.
- the in-server database 111 records drug history information for each patient.
- the pharmacy history information for each patient includes information specifying a pharmacy that uses the pharmacy system 400, patient identification information used in the pharmacy system 400, and patient history data supplied from the pharmacy system 400. Etc. are included.
- the communication unit 112 communicates with the in-hospital system 300 and the pharmacy system 400 via the network 10 to transmit and receive data such as drug history data.
- the communication unit 112 transmits / receives data to / from the health insurance association system 200 via, for example, the secure communication line 2.
- the updating unit 113 updates the in-server database 111 based on the data.
- the updating unit 113 updates the in-server database 111 based on the electronic receipt data held by the health insurance association system 200.
- the update unit 113 updates the in-server database 111 based on the electronic receipt data held by the health insurance association system 200, so that the data server 110 has the electronic health data held in the in-server database 111.
- the reliability of the information can be improved.
- the user search unit 114 searches the drug history information recorded in the in-server database 111 for information specifying a desired patient, that is, patient identification information used in the pharmacy system 400.
- the drug history search unit 115 searches for drug history data of a desired patient from the drug history information recorded in the database 111 in the server.
- the information processing server 120 accesses the in-server database 111 of the data server 110 as necessary, and performs processing of drug history information, notification processing to a patient based on the drug history information, and the like.
- the configuration example of the data center 100 has been described above with reference to FIG. Next, a configuration example of the in-hospital system 300 included in the information processing system 1 according to an embodiment of the present disclosure will be described.
- FIG. 3 is an explanatory diagram illustrating a configuration example of the in-hospital system 300 included in the information processing system 1 according to an embodiment of the present disclosure.
- a configuration example of the in-hospital system 300 will be described with reference to FIG.
- the in-hospital system 300 includes an in-hospital receipt computer 310, an in-hospital device 320, and a reader / writer 330.
- the in-hospital reception computer 310 and the in-hospital apparatus 320 are connected to each other via a local network. This local network is connected to the network 10 by a router (not shown).
- the hospital receipt computer 310 includes an in-hospital database 311, an input unit 312, and a control unit 313.
- the in-hospital receipt computer 310 updates information in the in-hospital database 311 in response to an input operation of the input unit 312 by a doctor or staff of the hospital.
- the in-hospital database 311 stores individual / diagnosis information including patient personal information, drug history data as health data, which is data related to the patient's health, in a database for each patient.
- the medical history data included in the personal / medical information includes medical data including information on prescriptions issued to patients in hospitals and the like.
- the medical history data recorded in the in-hospital database 311 is transmitted to the data center 100 for recording as necessary, and is shared by a plurality of in-hospital systems 300 and in-pharmacy systems 400.
- the input unit 312 is an input device including, for example, a keyboard, a mouse, a touch panel, and the like, and supplies information corresponding to a user input operation to the control unit 313.
- the control unit 313 controls the operation of the hospital receipt computer 310 according to information supplied from the input unit 312.
- the in-hospital device 320 includes, for example, a desktop computer or a notebook computer.
- the in-hospital apparatus 320 executes various processes in accordance with the personal identification ID supplied from the reader / writer 330 and the input operation of doctors / employees.
- the in-hospital device 320 includes an acquisition unit 321, a control unit 322, a communication unit 323, and a display unit 324.
- the acquisition unit 321 acquires the personal identification ID acquired by the reader / writer 330 through proximity non-contact communication with the IC card 20.
- the control unit 322 performs control to exchange various data with the hospital receipt computer 310 via the local area network and to display various data on the display unit 324.
- the communication unit 323 transmits / receives information to / from other devices via the local area network or the network 10.
- the display unit 324 displays various data (character information, image information, etc.).
- the reader / writer 330 is connected to the in-hospital device 320 by a USB (Universal Serial Bus) or other interface, and performs proximity contactless communication with the IC card 20 at a predetermined frequency (for example, 13.56 MHz).
- the reader / writer 330 provides the personal identification ID acquired from the IC card 20 to the in-hospital device 320 by performing proximity contactless communication with the IC card 20.
- the configuration example of the hospital system 300 has been described above with reference to FIG. Note that the in-hospital receipt computer 310, the in-hospital system 320, and the reader / writer 330 shown in FIG. 3 may be configured as a single device. Next, a configuration example of the pharmacy system 400 will be described.
- FIG. 4 is an explanatory diagram illustrating a configuration example of the in-pharmacy system 400 included in the information processing system 1 according to an embodiment of the present disclosure.
- a configuration example of the pharmacy system 400 will be described with reference to FIG.
- the in-pharmacy system 400 includes an in-pharmacy receipt computer 410, an in-pharmacy device 420, and a reader / writer 430.
- the pharmacy receipt computer 410 and the pharmacy device 420 are connected to each other via a local network. This local network is connected to the network 10 by a router (not shown).
- the in-pharmacy receipt computer 410 includes an in-pharmacy database 411, an input unit 412, and a control unit 413.
- the pharmacy receipt computer 410 updates information in the pharmacy database 411 in response to an input operation of the input unit 412 by a pharmacist or staff of the pharmacy.
- the in-pharmacy database 411 stores personal / medical history information including personal information of patients, health data that is data on patient health, and the like for each patient.
- the health data includes data related to the patient's drug history (medical history data) and the like.
- the medical history data included in the personal / medical history data includes dispensing data including information regarding a drug dispensed for a user in a pharmacy or the like, information regarding a prescription of the drug, and the like.
- the health data managed in the pharmacy database 411 is not limited to drug history data, but may be any data as long as it relates to patient health.
- the drug history data recorded in the pharmacy database 411 is transmitted to the data center 100 and recorded as necessary, and is shared by a plurality of hospital systems 300 and pharmacy systems 400.
- the input unit 412 is an input device including, for example, a keyboard, a mouse, a touch panel, and the like, and supplies information corresponding to a user input operation to the control unit 413.
- the control unit 413 controls the operation of the in-pharmacy receipt computer 410 according to the information supplied from the input unit 412.
- the in-pharmacy device 420 includes, for example, a desktop computer or a notebook computer.
- the in-pharmacy device 420 executes various processes in accordance with the personal identification ID supplied from the reader / writer 430 and input operations of a pharmacist / staff and the like.
- the in-pharmacy device 420 includes an acquisition unit 421, a control unit 422, a communication unit 423, and a display unit 424.
- the acquisition unit 421 acquires the personal identification ID acquired by the reader / writer 430 through proximity non-contact communication with the IC card 20.
- the control unit 422 performs control to exchange various data with the in-pharmacy receipt computer 410 and display various data on the display unit 424 via the local area network.
- the communication unit 423 transmits / receives information to / from other devices via the local area network or the network 10.
- the display unit 424 displays various data (character information, image information, etc.).
- the reader / writer 430 is connected to the pharmacy device 420 by a USB (Universal Serial Bus) or other interface, and performs proximity non-contact communication with the IC card 20 at a predetermined frequency (for example, 13.56 MHz).
- the reader / writer 430 provides the personal identification ID acquired from the IC card 20 to the in-pharmacy device 420 by performing proximity contactless communication with the IC card 20.
- the configuration example of the pharmacy system 400 has been described above with reference to FIG. Note that the pharmacy receipt computer 410, the in-pharmacy device 420, and the reader / writer 430 shown in FIG. 4 may be configured as a single device. Next, a specific example of personal / medical history information recorded in the pharmacy database 410 of the pharmacy system 400 will be described.
- FIG. 5 is an explanatory diagram showing an example of individual / medicine history information recorded in the pharmacy database 410 of the pharmacy system 400.
- the individual / pharmaceutical history information includes “Dispensing pharmacy ID”, “Dispensing pharmacy user ID”, “Receive cooperation ID”, “Name”, “Birth date”, “Address”, “ “Phone number”, “Insurance card number”, and "Medical history data” are included.
- Dispensing pharmacy ID is information for identifying an in-pharmacy system 400, that is, a pharmacy, that can be identified by each device constituting the information processing system 1 shown in FIG.
- an insurance medical institution code used when each institution such as a pharmacy makes a payment request to an insurer is used as the dispensing pharmacy ID.
- the “dispensing pharmacy user ID” is information for identifying a user that is used only in the pharmacy system 400, that is, the local system including the pharmacy receipt computer 410, the pharmacy device 420, and the reader / writer 430. is there. For example, a user number registered in the in-pharmacy receipt computer 410 constituting the in-pharmacy system 400 is set as the dispensing in-pharmacy user ID.
- each device constituting the pharmacy system 400 such as the pharmacy device 420 can specify the patient indicated by the dispensing pharmacy user ID based on the dispensing pharmacy user ID.
- a user ID in the dispensing pharmacy is information that cannot directly identify a patient just by obtaining it by another person.
- Receiveipt cooperation ID is information for linking a personal identification ID for identifying an individual patient with data held in the health insurance association system 200.
- the “name”, “birth date”, “address”, “phone number”, and “insurance number” included in the personal / medical history information are specified by the “Dispensing Pharmacy User ID”.
- These “name” to “insurance card number” are so-called personal information of a patient that allows another person to directly identify the user.
- the “medical history data” included in the personal / medical history information is the medical history data of the user specified by the “dispensing pharmacy user ID”, and this pharmacy history data is input by the pharmacy system 400. Dispensing data is included. That is, the drug history data recorded in the pharmacy database 411 of each pharmacy (pharmacy system 400) includes only the information input at the pharmacy, and other pharmacies and hospitals (other medical institutions). Etc.) does not include information on drug history entered in
- the drug history data includes, for example, a dispensed drug ID for identifying a dispensed drug, a type of dispensed drug such as an internal use, a dispensed date, a prescribed number of days for the drug, a frequency of use of the drug, a drug The amount of each dose taken, information on side effects, etc. are included as dispensing data.
- the dispensing pharmacy ID for specifying the pharmacy the user ID in the dispensing pharmacy for identifying the user in the pharmacy, the user's personal information such as the name, and the pharmacy are input.
- the medical history data included in the personal / examination information managed by the in-hospital database 311 includes information (examination data) related to prescriptions issued to patients at the hospital. Specifically, for example, in the medical history data, the prescription issuance date and time, whether or not to change to a generic drug, the prescription drug ID that identifies the prescription drug, the type of prescription drug such as internal use, the number of days prescribed for the drug, Includes information on frequency of use, number of medications taken per dose, and side effects.
- the personal / examination information managed by the in-hospital database 311 includes “hospital ID” and “in-hospital user ID” instead of “dispensing pharmacy ID” and “dispensing pharmacy user ID” in FIG. It is.
- the “hospital ID” is information corresponding to the “dispensing pharmacy ID”, and is information for specifying the in-hospital system 300 in the information processing system.
- the “in-hospital user ID” is information corresponding to the “dispensing pharmacy user ID” and is patient identification information used only in the in-hospital system 300.
- FIG. 6 is an explanatory diagram showing a specific example of user medication history information recorded in the in-server database 111 of the data server 110.
- each user drug history information includes “personal identification ID”, “dispensing pharmacy ID”, “dispensing pharmacy user ID”, “receipt linkage ID”, “medicine history data”, and “ Last modified date "is included.
- “Personal identification ID” included in the user medication history information is a personal identification ID recorded on the IC card 20 shown in FIG. This personal identification ID is used as information for specifying the patient who owns the IC card 20 as described above.
- the “dispensing pharmacy ID” is a dispensing pharmacy ID for specifying the in-pharmacy system 400. More specifically, the “dispensing pharmacy ID” included in the user drug history information is a hash value obtained by hashing the dispensing pharmacy ID.
- Dispensing pharmacy user ID is a dispensing pharmacy user ID for identifying a patient used in the pharmacy system 400.
- Receiveipt cooperation ID is a personal identification ID for identifying a patient and a health. This is information for linking data held in the insurance association system 200.
- Pharmaacy history data is drug history data input by the pharmacy system 400 specified by the dispensing pharmacy ID.
- the “last update date” is the date when the data of each personal identification ID in the in-server database 111 was last updated.
- FIG. 7 is a flowchart showing an example of registration processing of user drug history information by the pharmacy system 400.
- a registration process example of user drug history information by the pharmacy system 400 will be described with reference to FIG.
- the pharmacy When a new user comes to the pharmacy where the pharmacy system 400 is provided and submits a prescription, the pharmacy operates the input unit 412 of the pharmacy receipt computer 410 based on the prescription submitted by the pharmacist, etc. Start input of dispensing data. Then, the control part 413 receives the input of dispensing data, and acquires the information according to operation to the input parts 412, such as a pharmacist, as dispensing data (step S101).
- the input unit 412 is operated to input personal information such as the user's name and date of birth. Further, the pharmacist or the like operates the input unit 412 to input a receipt cooperation ID for associating a personal identification ID described later with the user's insurance card number, or a pass code that is the basis of the reception cooperation ID.
- the control unit 413 When these pieces of information are input, the control unit 413 generates drug history data from the dispensing data acquired from the input unit 412, and the input information such as the name of the user, the generated drug history data, Personal / medical history information is generated from the given dispensing pharmacy user ID.
- the personal / medical history information of the user is already recorded in the pharmacy database 411, the personal / medical history information is not generated.
- control unit 413 supplies the generated personal / medical history information to the in-pharmacy database 411 to record it, and also dispenses in-dispensing pharmacy user ID, the user's name, and the dispensing data ( (Medical history data) is supplied to the in-pharmacy device 420 via the local area network (step S102).
- control unit 422 of the in-pharmacy device 420 temporarily holds the dispensing pharmacy user ID, the receipt linkage ID (or passcode), the user name, and the dispensing data supplied from the control unit 413 (step). S103).
- the pharmacist When the pharmacist finishes inputting the user's dispensing data, personal information, etc., the pharmacist dispenses the prescribed medicine as necessary and dispenses it to the user. Furthermore, when the user first visits the pharmacy, the pharmacist or the like confirms the user's desire to newly register the electronic medicine notebook. That is, the pharmacist confirms the desire for user registration in the data center 100.
- the pharmacist or the like operates the in-pharmacy device 420 and performs processing for new registration.
- the control unit 422 of the in-pharmacy device 420 supplies the dispensation in-pharmacy user ID, the user's name, and the dispensation data temporarily stored in the display unit 424 and displays them in response to an operation by a pharmacist or the like.
- the pharmacist and the user confirm information such as the name displayed on the display unit 424, and then the user holds the IC card 20 possessed over the reader / writer 430. Then, the reader / writer 430 performs proximity contactless communication with the IC card 20 and receives a personal identification ID from the IC card 20.
- the acquisition unit 421 acquires the user's personal identification ID from the reader / writer 430 and supplies the acquired personal identification ID to the control unit 422 (step S104).
- control unit 422 associates the temporarily stored user ID in the dispensing pharmacy with the personal identification ID supplied from the acquisition unit 421 (step S105). And the control part 422 acquires the dispensing pharmacy ID of the system 400 in a pharmacy from the receipt computer 410 in a pharmacy as needed, and performs hashing with respect to dispensing pharmacy ID. Then, the control unit 422 supplies the hash value (dispensing pharmacy ID) obtained by the hashing calculation, the personal identification ID, the dispensing pharmacy user ID, the receipt cooperation ID, and the dispensing data to the communication unit 433.
- the communication unit 423 transmits the dispensing pharmacy ID (hash value), the personal identification ID, the dispensing pharmacy user ID, the receipt cooperation ID, and the dispensing data supplied from the control unit 422 to the data server 110 via the network 10. (Step S106), the registration request process ends. That is, the communication unit 423 transmits a request for new registration of the user including the dispensing pharmacy ID, the personal identification ID, the user ID within the dispensing pharmacy, the receipt cooperation ID, and the dispensing data.
- FIG. 8 is a flowchart showing a registration process of personal / medical history information by the data server 110.
- the personal / medical history information registration process performed by the data server 110 will be described below with reference to FIG.
- the communication unit 112 receives the dispensing pharmacy ID (hash value), the personal identification ID, the dispensing pharmacy user ID, the receipt linkage ID, and the dispensing data transmitted from the pharmacy system 400 and supplies them to the updating unit 113. (Step S111).
- the update unit 113 generates user drug history information including the dispensing pharmacy ID (hash value), personal identification ID, dispensing pharmacy user ID, receipt cooperation ID, dispensing data, and last update date supplied from the communication unit 112. Then, the generated user medication history information is added to the in-server database 111 (step S112). That is, the newly generated user medication history information is recorded in the server database 111. Thereby, for example, the user medicine history information shown in FIG. 6 is newly recorded.
- the updating unit 113 uses the user's dispensing data as it is as medication history data.
- the pharmacy system 400 transmits the dispensing pharmacy ID that identifies the pharmacy, the personal identification ID and dispensing user ID that identifies the user, and the dispensing data of the user to the data server 111, and Request registration.
- the data server 110 receives these pieces of information transmitted from the pharmacy system 400 to generate and register user drug history information.
- a personal identification ID, a reception linkage ID, and a dispensing pharmacy user ID are exchanged as information for specifying a user between the pharmacy system 400 and the data server 110 via the network 20.
- a personal identification ID, a reception linkage ID, and a dispensing pharmacy user ID are exchanged as information for specifying a user between the pharmacy system 400 and the data server 110 via the network 20.
- this information is seen by others, it is generally impossible to specify the individual user, and thus it is possible to prevent personal information from leaking. Security can be improved.
- a dispensing pharmacy ID for specifying a pharmacy is also exchanged between the in-pharmacy system 400 and the data server 110.
- This dispensing pharmacy ID is a hashed value, that is, a hash value. Therefore, it is difficult for others to identify the pharmacy from this hash value, which can improve security.
- the digitized dispensing data can be constructed in the data server 110 without specifying an individual.
- the dispensing data constructed in the data server 110 will not be complete.
- personal information is erroneously written, some information is not correctly classified, or classification itself is not performed.
- electronic medicine notebooks even if electronic medicine notebooks become widespread, it takes a long time to accumulate data.
- the data built in the health insurance union system 200 is checked by an examination / payment institution and / or health insurance union on the way, and if there is insufficient data, it is returned to the hospital or pharmacy, so it covers the individual drug history.
- the data is highly accurate. However, due to such check and return time, there is a delay of about two months from the prescription of the medicine until the dispensing data is generated in the health insurance association system 200.
- data constructed in the data server 110 and data constructed in the health insurance association system 200 are linked using the receipt linkage ID. Therefore, it is possible to cause the data server 110 to construct dispensing data with high accuracy without causing the data server 110 to retain personal information itself.
- FIG. 9 is an explanatory diagram showing an outline of the operation of the information processing system 1 according to the present embodiment.
- the personal identification ID registered in the IC card 20 is provided to the in-hospital system 300 or the pharmacy system 400.
- the in-hospital system 300 and the in-pharmacy system 400 transmit the dispensing pharmacy ID, the dispensing pharmacy user ID, the personal identification ID, the examination data, the drug history data, and the receipt linkage ID to the data center 100.
- the data center 100 constructs user medication history information from the transmitted data.
- the data center 100 does not hold information that directly identifies an individual, such as a name, date of birth, and address.
- the user can also use the in-hospital system 300 and the in-pharmacy system 400 to generate a receipt linkage ID for linking with the electronic receipt of the health insurance association 200, or original data for generating a receipt linkage ID (pass as a seed of encryption). Code etc.) is created and registered in the health insurance association 200 in advance.
- the health insurance association system 200 When the original data for generating the receipt linkage ID is registered, the health insurance association system 200 generates the receipt linkage ID from the original data.
- the health insurance association system 200 generates a one-way hashed character string consisting of the user's insurance card number, the user's date of birth, and the passcode using a hash function such as SHA-256 as a receipt linkage ID. And keep it inside.
- the hospital system 300 and the pharmacy system 400 execute a billing process for the insurance / public expenses to the examination payment organization 500.
- the name, date of birth, insurance card number, examination data and medical data are sent from the in-hospital system 300 or the pharmacy system 400 to the examination and payment institution 500.
- the examination / payment institution 500 checks the data and returns it to the hospital or pharmacy if there is any deficiency.
- the examination / payment institution 500 executes a claim processing for the insurance / public expenditure to the health insurance association system 200.
- the data center 100 transmits a medical history data inquiry to the health insurance association system 200 at a predetermined timing using the last update date and the receipt linkage ID, and the health insurance association system 200 responds to the inquiry,
- the receipt cooperation ID and drug history data are returned to the data center 100.
- the data center 100 updates the drug history data transmitted from the health insurance association system 200 using the receipt linkage ID as a key.
- FIG. 10 is a flowchart illustrating an example of a processing operation of the information processing system 1 according to an embodiment of the present disclosure.
- the flowchart shown in FIG. 10 shows an operation when registering drug history data from the pharmacy system 400 to the data center 100.
- step S121 When the user brings the IC card 20 to the pharmacy and brings the IC card 20 into contact with the reader / writer 430 (step S121), the processes shown in FIGS. 7 and 8 are executed in the pharmacy system 400 and the data server 110. Then, the personal / medical history information is inserted into the server database 111 of the data server 110 (step S122).
- the data server 110 sets the insurance card number, the receipt linkage ID, and the last update date as a set to the health insurance association system 200 for the receipt linkage ID.
- the medical history information of the user who has is inquired (step S123).
- the health insurance union system 200 acquires drug history information from a database or the like held inside using the receipt linkage ID as a key, and transmits the acquired drug history information to the data server 110 that is the inquiry source (step S124). .
- the data server 110 integrates the received drug history information into the in-server database 111 using the receipt cooperation ID as a key (step S125).
- the information processing system 1 allows the data center 100 to store information such as a name and an address that directly identifies an individual patient, It enables linkage with drug history information held in the health insurance union system 200.
- the health insurance association knows the passcode in advance or does not mediate the data server 110, and the health insurance from the user, hospital, or pharmacy. You can also ask the union directly for drug history information.
- FIG. 11 is an explanatory diagram showing an outline of the operation of the information processing system 1 according to the present embodiment.
- the operation outline shown in FIG. 11 is different from that shown in FIG. 9 and shows a case in which the user or a hospital / pharmacy directly inquires about the medical history information to the health insurance association without mediating the data server 110. It is.
- drug history information is directly inquired from the user, the hospital system 300, and the pharmacy system 400 to the health insurance association system 200, and the health insurance association system 200 transmits a result of the inquiry to the data server 110.
- An example is shown.
- FIG. 12 is a flowchart illustrating an example of a processing operation of the information processing system 1 according to an embodiment of the present disclosure.
- the flowchart shown in FIG. 12 shows an operation when registering drug history data from the pharmacy system 400 to the data center 100.
- step S131 When the user brings the IC card 20 to the pharmacy and brings the IC card 20 into contact with the reader / writer 430 (step S131), the processes shown in FIGS. 7 and 8 are executed in the pharmacy system 400 and the data server 110. Then, the personal / medicine history information is inserted into the in-server database 111 of the data server 110 (step S132).
- the user, the in-hospital system 300, and the in-pharmacy system 400 set the health insurance number and the last update date as a set.
- the receipt cooperation ID is calculated from the insurance card number, and the medicine history information of the user having the receipt cooperation ID is inquired (step S133).
- the health insurance union system 200 acquires drug history information from a database or the like held inside using the receipt linkage ID as a key, and transmits the acquired drug history information to the data server 110 of the inquiry source (step S134). .
- the data server 110 integrates the received drug history information into the in-server database 111 using the receipt cooperation ID as a key (step S135).
- the information processing system 1 does not cause the data center 100 to store information such as a name and an address that directly identifies an individual patient. It enables linkage with drug history information held in the health insurance union system 200. Further, since the receipt linkage ID is not used when inquiring from the user, the hospital system 300, or the pharmacy system 400, even if all communications from the user, the hospital system 300, and the pharmacy system 400 are wiretapped, , It cannot be associated with the receipt linkage ID, and it is impossible to acquire drug history information from the data server 110, and security can be improved.
- the trigger for starting transmission of drug history information from the health insurance association system 200 to the data server 110 is an inquiry from the data server 110, the user, the hospital system 300, or the pharmacy system 400.
- the medical history information may be automatically transmitted from the health insurance association system 200 to the data server 110 at the timing when the data is updated from the examination payment organization 500 to the health insurance association system 200.
- FIG. 13 is an explanatory diagram showing an outline of the operation of the information processing system 1 according to the present embodiment.
- the operation outline shown in FIG. 13 is different from those shown in FIGS. 9 and 11, and automatically from the health insurance association system 200 at the timing when the data is updated from the examination payment organization 500 to the health insurance association system 200.
- the case where medicine history information is transmitted to the data server 110 is shown.
- the health insurance association system is previously set from the user, the hospital system 300, and the pharmacy system 400.
- the receipt cooperation ID and the data serving as the basis of the receipt cooperation ID are registered.
- FIG. 14 is a flowchart illustrating an example of a processing operation of the information processing system 1 according to an embodiment of the present disclosure.
- the flowchart shown in FIG. 14 shows an operation when registering drug history data from the pharmacy system 400 to the data center 100.
- step S141 When the user brings the IC card 20 to the pharmacy and brings the IC card 20 into contact with the reader / writer 430 (step S141), the processing shown in FIGS. 7 and 8 is executed in the pharmacy system 400 and the data server 110. Then, the personal / medical history information is inserted into the in-server database 111 of the data server 110 (step S142).
- the health insurance association system 200 triggers the update.
- the medical history information is acquired from a database or the like held inside using the receipt linkage ID as a key, and the acquired medical history information is transmitted to the data server 110 as the inquiry source (step S144).
- the data server 110 integrates the received drug history information into the server database 111 using the receipt cooperation ID as a key (step S145).
- the information processing system 1 does not cause the data center 100 to store information such as a name and an address that directly identifies an individual patient. It enables linkage with drug history information held in the health insurance union system 200.
- the medical history information is automatically transmitted from the health insurance association system 200 to the data server 110 at the timing when the data is updated from the examination / payment institution 500 to the health insurance association system 200, there is no worry of wiretapping of data. System security can be improved.
- the data of the electronic medicine notebook that is excellent in immediacy but may be missing, and the electronic receipt that is more comprehensive but accurate in time, although there is a time delay.
- Data can be linked without performing communication including both information that can identify an individual and a medical history.
- the information processing system 1 can create drug history data that complements immediacy and completeness.
- the electronic medicine notebook from the day when the electronic medicine notebook is created, it can be linked with data before a predetermined period (for example, before two months ago) built in the health insurance association system 200. Accordingly, if the user has a large amount of information and uses the electronic medicine notebook for a predetermined period, all data after the receipt is digitized is collected in the data server 110. Of course, even if the electronic medicine notebook is not used, the data of the data server 110 is supplemented from the electronic receipt after a predetermined period.
- a predetermined period for example, before two months ago
- the timing of data linkage between the data server 110 and the health insurance association system 200 may be a timing at which the user touches the IC card 20 with the reader / writer and new drug history information is registered in the data server 110. It may be a timing when an inquiry is made from the user, the in-hospital system 300, or the pharmacy system 400, or may be a timing when data is updated from the examination payment organization 500 to the health insurance association system 200. In any case, data linkage between the data server 110 and the health insurance association system 200 can be performed securely and at an appropriate timing.
- each step in the processing executed by each device in the present specification does not necessarily have to be processed in time series in the order described as a sequence diagram or a flowchart.
- each step in the processing executed by each device may be processed in an order different from the order described as the flowchart, or may be processed in parallel.
- this technique can also take the following structures.
- a data holding unit that holds at least data for each individual without holding information that can identify a specific individual;
- a data registration unit that acquires at least the data from other systems that hold at least information that can identify a specific individual and data for each individual and registers the data in the data holding unit;
- the data registration unit is a server device that acquires data from the other system using a cooperation ID that cooperates with the other system and registers the data in the data holding unit.
- the data registration unit acquires the data regarding the health of each individual transmitted from the other system at a predetermined timing, and registers the data in the data holding unit using the cooperation ID, (2) Or the server apparatus as described in (3).
- the data holding unit has information on the last update date, and the data registration unit obtains data related to health for each individual after the last update date from the other system and registers the data in the data holding unit.
- the server device according to any one of (2) to (4).
- the step of registering in the data holding unit is a data linkage method in which data is acquired from the other system using a linkage ID linked with the other system and registered in the data holding unit.
- the step of registering in the data holding unit is a computer program that acquires data from the other system using a linkage ID that cooperates with the other system and registers the data in the data holding unit.
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- General Health & Medical Sciences (AREA)
- Public Health (AREA)
- Epidemiology (AREA)
- Primary Health Care (AREA)
- Chemical & Material Sciences (AREA)
- Bioinformatics & Cheminformatics (AREA)
- Medicinal Chemistry (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
Description
<1.本開示の一実施形態>
[システム構成例]
[データセンター構成例]
[病院内システム構成例]
[薬局内システム構成例]
[薬局内データベースの具体例]
[サーバ内データベースの具体例]
[ユーザ薬歴情報の登録処理例]
<2.まとめ>
[システム構成例]
まず、図面を参照しながら本開示の一実施形態にかかる情報処理システムの構成例を説明する。図1は、本開示の一実施形態にかかる情報処理システム1の構成例を示す説明図である。以下、図1を用いて本開示の一実施形態にかかる情報処理システム1の構成例について説明する。
図2は、本開示の一実施形態にかかる情報処理システム1に含まれるデータセンター100の構成例を示す説明図である。以下、図2を用いてデータセンター100の構成例について説明する。
図3は、本開示の一実施形態にかかる情報処理システム1に含まれる病院内システム300の構成例を示す説明図である。以下、図3を用いて病院内システム300の構成例について説明する。
図4は、本開示の一実施形態にかかる情報処理システム1に含まれる薬局内システム400の構成例を示す説明図である。以下、図4を用いて薬局内システム400の構成例について説明する。
図5は、薬局内システム400の薬局内データベース410に記録される個人/薬歴情報の例を示す説明図である。図5に示した例では、個人/薬歴情報には「調剤薬局ID」、「調剤薬局内ユーザID」、「レセプト連携ID」、「氏名」、「生年月日」、「住所」、「電話番号」、「保険証番号」、および「薬歴データ」が含まれている。
図6は、データサーバ110のサーバ内データベース111に記録されるユーザ薬歴情報の具体例を示す説明図である。図6に示した例では、各ユーザ薬歴情報には、「個人識別ID」、「調剤薬局ID」、「調剤薬局内ユーザID」、「レセプト連携ID」、「薬歴データ」、および「最終更新日」が含まれている。
図7は、薬局内システム400によるユーザ薬歴情報の登録処理例に示す流れ図である。以下、図7を用いて薬局内システム400によるユーザ薬歴情報の登録処理例について説明する。
以上説明したように本実施形態によれば、即時性に優れるが抜けのある可能性のある電子お薬手帳のデータと、時間的な遅れはあるがより網羅的で、精度が高い電子レセプトのデータとを、個人を特定できる情報と薬歴とを双方含んだ通信を行わなくとも連携させることが可能になる。これにより、本実施形態にかかる情報処理システム1は、即時性と網羅性を相互補完した薬歴データを作成できる。
(1)
特定の個人を識別することができる情報を保持せず、個人ごとのデータを少なくとも保持するデータ保持部と、
特定の個人を識別することができる情報及び個人ごとのデータを少なくとも保持する他のシステムから少なくとも該データを取得して前記データ保持部に登録するデータ登録部と、
を備え、
前記データ登録部は、前記他のシステムと連携する連携IDを用いて該他のシステムからデータを取得して前記データ保持部に登録する、サーバ装置。
(2)
前記個人ごとのデータは、健康に関するデータである、前記(1)に記載のサーバ装置。
(3)
前記データ登録部は、前記個人ごとの健康に関するデータが送信されてきたタイミングで、前記連携IDを用いて該他のシステムから健康に関するデータを取得して前記データ保持部に登録する、前記(2)に記載のサーバ装置。
(4)
前記データ登録部は、前記他のシステムから所定のタイミングで送信されてくる、前記個人ごとの健康に関するデータを取得して、前記連携IDを用いて前記データ保持部に登録する、前記(2)または(3)に記載のサーバ装置。
(5)
前記データ保持部は、最終更新日の情報を有し、前記データ登録部は、前記他のシステムから前記最終更新日以降の前記個人ごとの健康に関するデータを取得して前記データ保持部に登録する、前記(2)~(4)のいずれかに記載のサーバ装置。
(6)
前記連携IDは、一方向ハッシュ化によって生成される、前記(2)~(5)のいずれかに記載のサーバ装置。
(7)
前記他のシステムは、電子レセプトを用いたシステムである、前記(2)~(6)のいずれかに記載のサーバ装置。
(8)
特定の個人を識別することができる情報及び個人ごとのデータを少なくとも保持する他のシステムから、少なくとも該データを取得して、特定の個人を識別することができる情報を保持せず個人ごとのデータを少なくとも保持するデータ保持部に登録するステップを備え、
前記データ保持部に登録するステップは、前記他のシステムと連携する連携IDを用いて該他のシステムからデータを取得して前記データ保持部に登録する、データ連携方法。
(9)
特定の個人を識別することができる情報及び個人ごとのデータを少なくとも保持する他のシステムから、少なくとも該データを取得して、特定の個人を識別することができる情報を保持せず個人ごとのデータを少なくとも保持するデータ保持部に登録するステップをコンピュータに実行させ、
前記データ保持部に登録するステップは、前記他のシステムと連携する連携IDを用いて該他のシステムからデータを取得して前記データ保持部に登録する、コンピュータプログラム。
100 データセンター
110 データサーバ
111 サーバ内データベース
112 通信部
113 更新部
114 ユーザ検索部
115 薬歴検索部
120 情報処理サーバ
200 健康保険組合システム
300 病院内システム
400 薬局内システム
Claims (9)
- 特定の個人を識別することができる情報を保持せず、個人ごとのデータを少なくとも保持するデータ保持部と、
特定の個人を識別することができる情報及び個人ごとのデータを少なくとも保持する他のシステムから少なくとも該データを取得して前記データ保持部に登録するデータ登録部と、
を備え、
前記データ登録部は、前記他のシステムと連携する連携IDを用いて該他のシステムからデータを取得して前記データ保持部に登録する、サーバ装置。 - 前記個人ごとのデータは、健康に関するデータである、請求項1に記載のサーバ装置。
- 前記データ登録部は、前記個人ごとの健康に関するデータが送信されてきたタイミングで、前記連携IDを用いて該他のシステムから健康に関するデータを取得して前記データ保持部に登録する、請求項2に記載のサーバ装置。
- 前記データ登録部は、前記他のシステムから所定のタイミングで送信されてくる、前記個人ごとの健康に関するデータを取得して、前記連携IDを用いて前記データ保持部に登録する、請求項2に記載のサーバ装置。
- 前記データ保持部は、最終更新日の情報を有し、前記データ登録部は、前記他のシステムから前記最終更新日以降の前記個人ごとの健康に関するデータを取得して前記データ保持部に登録する、請求項2に記載のサーバ装置。
- 前記連携IDは、一方向ハッシュ化によって生成される、請求項2に記載のサーバ装置。
- 前記他のシステムは、電子レセプトを用いたシステムである、請求項2に記載のサーバ装置。
- 特定の個人を識別することができる情報及び個人ごとのデータを少なくとも保持する他のシステムから、少なくとも該データを取得して、特定の個人を識別することができる情報を保持せず個人ごとのデータを少なくとも保持するデータ保持部に登録するステップを備え、
前記データ保持部に登録するステップは、前記他のシステムと連携する連携IDを用いて該他のシステムからデータを取得して前記データ保持部に登録する、データ連携方法。 - 特定の個人を識別することができる情報及び個人ごとのデータを少なくとも保持する他のシステムから、少なくとも該データを取得して、特定の個人を識別することができる情報を保持せず個人ごとのデータを少なくとも保持するデータ保持部に登録するステップをコンピュータに実行させ、
前記データ保持部に登録するステップは、前記他のシステムと連携する連携IDを用いて該他のシステムからデータを取得して前記データ保持部に登録する、コンピュータプログラム。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/391,434 US20150051919A1 (en) | 2012-04-27 | 2013-03-21 | Server device, data linking method, and computer program |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012102281 | 2012-04-27 | ||
JP2012-102281 | 2012-04-27 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013161458A1 true WO2013161458A1 (ja) | 2013-10-31 |
Family
ID=49482795
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/058032 WO2013161458A1 (ja) | 2012-04-27 | 2013-03-21 | サーバ装置、データ連携方法およびコンピュータプログラム |
Country Status (3)
Country | Link |
---|---|
US (1) | US20150051919A1 (ja) |
JP (2) | JPWO2013161458A1 (ja) |
WO (1) | WO2013161458A1 (ja) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016161999A (ja) * | 2015-02-26 | 2016-09-05 | 日本メディカルビジネス株式会社 | 情報抽出装置、情報表示装置、情報提供システム、情報抽出方法、情報表示方法およびプログラム |
WO2017094538A1 (ja) * | 2015-12-03 | 2017-06-08 | ソニー株式会社 | Id取得端末装置および方法、情報処理装置および方法、並びにプログラム |
JPWO2019087671A1 (ja) * | 2017-10-31 | 2020-11-19 | 富士フイルム富山化学株式会社 | 情報提供サーバ、情報提供方法、および情報提供システム |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006067248A (ja) * | 2004-08-26 | 2006-03-09 | Sharp Corp | コンテンツ視聴装置、そのためのコンピュータプログラム、及び記録媒体 |
JP2007140647A (ja) * | 2005-11-15 | 2007-06-07 | Yamaguchi Univ | 臨床研究支援システム |
JP2009237975A (ja) * | 2008-03-27 | 2009-10-15 | Nec Corp | 緊急時の該当者検索システム、その方法及びプログラム |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6775670B2 (en) * | 1998-05-29 | 2004-08-10 | Luc Bessette | Method and apparatus for the management of data files |
WO2002019141A2 (en) * | 2000-08-30 | 2002-03-07 | Catalina Marketing International, Inc. | Biometric identification at the pharmacy, determining a medical treatment and selecting a promotion |
US20020120472A1 (en) * | 2000-12-22 | 2002-08-29 | Dvorak Carl D. | System and method for integration of health care records |
US20030037054A1 (en) * | 2001-08-09 | 2003-02-20 | International Business Machines Corporation | Method for controlling access to medical information |
US20030055824A1 (en) * | 2001-09-19 | 2003-03-20 | Andrea Califano | Distributed personalized genetic safe |
US7908155B2 (en) * | 2002-04-12 | 2011-03-15 | Becton, Dickinson And Company | System for collecting, storing, presenting and analyzing immunization data having remote stations in communication with a vaccine and disease database over a network |
US20030220817A1 (en) * | 2002-05-15 | 2003-11-27 | Steve Larsen | System and method of formulating appropriate subsets of information from a patient's computer-based medical record for release to various requesting entities |
US7921020B2 (en) * | 2003-01-13 | 2011-04-05 | Omnicare Inc. | Method for generating medical intelligence from patient-specific data |
US8620678B2 (en) * | 2003-01-31 | 2013-12-31 | Imd Soft Ltd. | Medical information query system |
US8090590B2 (en) * | 2003-03-10 | 2012-01-03 | Intuit Inc. | Electronic personal health record system |
US7519591B2 (en) * | 2003-03-12 | 2009-04-14 | Siemens Medical Solutions Usa, Inc. | Systems and methods for encryption-based de-identification of protected health information |
JP2005084903A (ja) * | 2003-09-08 | 2005-03-31 | Toshiba Solutions Corp | 電子文書管理システム |
US8185411B2 (en) * | 2004-02-17 | 2012-05-22 | International Business Machines Corporation | Method, system, and apparatus for patient controlled access of medical records |
US20050256740A1 (en) * | 2004-05-05 | 2005-11-17 | Kohan Mark E | Data record matching algorithms for longitudinal patient level databases |
US7827234B2 (en) * | 2005-01-10 | 2010-11-02 | International Business Machines Corporation | Privacy entitlement protocols for secure data exchange, collection, monitoring and/or alerting |
WO2006084362A1 (en) * | 2005-02-11 | 2006-08-17 | Hipaat Inc. | System and method for privacy managemen |
US7309001B2 (en) * | 2005-05-31 | 2007-12-18 | Catalina Marketing Corporation | System to provide specific messages to patients |
US20060293925A1 (en) * | 2005-06-22 | 2006-12-28 | Leonard Flom | System for storing medical records accessed using patient biometrics |
US20070192137A1 (en) * | 2006-02-01 | 2007-08-16 | Ombrellaro Mark P | Access control in an electronic medical record system |
US20070255704A1 (en) * | 2006-04-26 | 2007-11-01 | Baek Ock K | Method and system of de-identification of a record |
JP5238169B2 (ja) * | 2007-03-02 | 2013-07-17 | 株式会社東芝 | 医療情報管理システム |
WO2009006609A1 (en) * | 2007-07-03 | 2009-01-08 | Eingot Llc | Records access and management |
US20090254375A1 (en) * | 2008-04-08 | 2009-10-08 | The Quantum Group, Inc. | System and methods for automated healthcare patient record search, extraction, and creation |
-
2013
- 2013-03-21 JP JP2014512424A patent/JPWO2013161458A1/ja active Pending
- 2013-03-21 US US14/391,434 patent/US20150051919A1/en not_active Abandoned
- 2013-03-21 WO PCT/JP2013/058032 patent/WO2013161458A1/ja active Application Filing
-
2016
- 2016-10-03 JP JP2016195582A patent/JP6484863B2/ja active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2006067248A (ja) * | 2004-08-26 | 2006-03-09 | Sharp Corp | コンテンツ視聴装置、そのためのコンピュータプログラム、及び記録媒体 |
JP2007140647A (ja) * | 2005-11-15 | 2007-06-07 | Yamaguchi Univ | 臨床研究支援システム |
JP2009237975A (ja) * | 2008-03-27 | 2009-10-15 | Nec Corp | 緊急時の該当者検索システム、その方法及びプログラム |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2016161999A (ja) * | 2015-02-26 | 2016-09-05 | 日本メディカルビジネス株式会社 | 情報抽出装置、情報表示装置、情報提供システム、情報抽出方法、情報表示方法およびプログラム |
WO2017094538A1 (ja) * | 2015-12-03 | 2017-06-08 | ソニー株式会社 | Id取得端末装置および方法、情報処理装置および方法、並びにプログラム |
JPWO2017094538A1 (ja) * | 2015-12-03 | 2018-09-20 | ソニー株式会社 | Id取得端末装置および方法、情報処理装置および方法、並びにプログラム |
US11038885B2 (en) | 2015-12-03 | 2021-06-15 | Sony Corporation | ID acquisition terminal apparatus and method and information processing apparatus and method |
JPWO2019087671A1 (ja) * | 2017-10-31 | 2020-11-19 | 富士フイルム富山化学株式会社 | 情報提供サーバ、情報提供方法、および情報提供システム |
Also Published As
Publication number | Publication date |
---|---|
US20150051919A1 (en) | 2015-02-19 |
JP2016224995A (ja) | 2016-12-28 |
JP6484863B2 (ja) | 2019-03-20 |
JPWO2013161458A1 (ja) | 2015-12-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11393580B2 (en) | Systems and methods for determining and communicating a prescription benefit coverage denial to a prescriber | |
JP5967408B2 (ja) | 情報取得端末装置および情報取得方法、並びにプログラム | |
US8781861B2 (en) | Systems and methods for providing an inducement to purchase incident to a physician's prescription of medication | |
CA2884949C (en) | Systems and methods for verifying correlation of diagnosis and medication as part of qualifying program eligibility verification | |
KR20040053269A (ko) | 처방조치 시스템 및 방법 | |
US20240145049A1 (en) | System and Method to Facilitate Interoperability of Health Care Modules | |
US20200211686A1 (en) | Method for interfacing medical information between a medical information exchange and computing entities | |
JP6484863B2 (ja) | サーバ装置、データ連携方法およびコンピュータプログラム | |
US20110066446A1 (en) | Method, apparatus and computer program product for providing a distributed registration manager | |
US20140288956A1 (en) | Systems and Methods for Providing an Inducement of a Purchase in Conjunction with a Prescription | |
JP2012094064A (ja) | 処方判断システム | |
JP2008123457A (ja) | 医療機関用情報システム | |
JP5731345B2 (ja) | 情報処理システム、医療情報収集装置、医療情報収集方法、医療情報収集プログラム、申告情報収集装置、申告情報収集方法、申告情報収集プログラム、及び、患者側端末用プログラム | |
JP4558142B2 (ja) | 電子薬歴管理システム | |
US20180308567A1 (en) | System and method for storing and delivering healthcare informatics data | |
JP2014059922A (ja) | 薬剤の処方を確実に適切に行うためのシステム、サーバ装置、端末装置およびプログラム | |
JP2010146464A (ja) | 医療情報管理システム | |
JP6202152B2 (ja) | 情報取得端末装置および方法、情報管理装置および方法、並びにプログラム | |
KR20000058711A (ko) | 처방전 작성과 약국의 보험금 청구를 위한 인터넷 사이트 | |
US10297344B1 (en) | Systems and methods for establishing an individual's longitudinal medication history | |
TWI222354B (en) | Portable medical system | |
KR20120029759A (ko) | 전자처방전 운영 시스템, 전자처방전 서버, 약국 통신장치, 환자 통신장치 및 제어 방법 | |
JP2005242637A (ja) | 薬剤販売可否決定方法、プログラム及び装置 | |
JP2015146215A (ja) | 申告情報収集装置、申告情報収集方法、及び、申告情報収集プログラム |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13781480 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14391434 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 2014512424 Country of ref document: JP Kind code of ref document: A |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13781480 Country of ref document: EP Kind code of ref document: A1 |