JP2021103348A - Medical information system, medical information device, control method for medical information device, and control program - Google Patents

Abstract

To provide a medical information system and a medical information device seamlessly operating in linkage with a patient terminal, and a control method and program for the medical information system.SOLUTION: In a medical information system 1, an integrated infrastructure includes an integrated database for storing first patient data inputted from a patient terminal, and a management unit which, when the first patient data is registered in the integrated database, makes the first patient data opened to a plurality of medical information devices. The medical information devices comprise a business database for storing second patient data and medical records inputted from the staff of a medical institution, an acquisition unit for acquiring the first patient data made open by the integrated infrastructure and preserving it in the business database, an acceptance unit for accepting access from a patient terminal, and a name-based aggregation unit which, when the first patient data preserved in the business database relating to a patient concerned with access is not associated with medical records, associates the first patient data with the medical record that pertains to a specific patient selected by staff.SELECTED DRAWING: Figure 1

Description

The present invention relates to a medical information system for managing medical information such as medical records used in a medical institution, a medical information device, a control method and a control program of the medical information device.

There is a known mechanism or way of thinking (so-called PHR (Personal Health Record)) in which an IT system used in a medical institution is converted to a cloud and medical information stored in the cloud is returned to a patient for utilization (for example, Patent Document 1). ).

JP-A-2017-68479, paragraph 0004

However, the current situation is limited to cloud-based IT systems, and sufficient discussion has not yet been reached. For example, there is a problem in cooperation between medical business systems, such as the terminal (application) possessed by a patient and each business system such as medical care, dentistry, and pharmacy are not designed to be seamlessly linked.

Therefore, an object of the present invention is to seamlessly link a terminal (application) possessed by a patient with each business system such as medical care, dentistry, and dispensing.

In order to solve the above-mentioned problems, the first aspect of the present invention is
A medical information system including a plurality of medical information devices and an integrated platform interposed between each of the plurality of medical information devices and a patient terminal.
The integrated platform is
A first database that stores the first patient data input via the patient terminal for each patient, and
When the first patient data is registered in the first database, the management unit that publishes the first patient data to the plurality of medical information devices is included.
Each of the plurality of medical information devices
A second database that stores a second patient data and medical record entered through the staff of the medical institution for each patient,
An acquisition unit that acquires the first patient data published on the integrated platform and stores it in the second database, and
The reception section that accepts access from the patient terminal and
When the first patient data stored in the second database for the patient related to the access is not associated with the medical record, the staff selected the first patient data. Includes a name identification section that links the medical records for a particular patient,
To provide a medical information system characterized by.

For example, the first patient data and the second patient data may each include at least name, gender and date of birth.
The candidate presenting unit may select a patient having the second patient data that partially matches the first patient data in at least one of the name, the sex, and the date of birth as the candidate.

In the medical information system of the present invention having the above-described configuration, each of the plurality of medical information devices may further include a candidate presentation unit that displays a list of candidates so that the staff can select the specific patient. Good.

The second aspect of the present invention is
A medical information device that is accessed from a patient terminal via an integrated platform that includes a first database that stores a first patient data input via the patient terminal for each patient.
A second database that stores a second patient data and medical record entered through the staff of the medical institution for each patient,
An acquisition unit that acquires the first patient data registered and published on the integrated platform and stores it in the second database.
The reception section that accepts access from the patient terminal and
When the first patient data stored in the second database for the patient related to the access is not associated with the medical record, the staff selected the first patient data. The name identification section that links the medical records related to a specific patient,
Provide a medical information device characterized by including.

A third aspect of the present invention is
A plurality of medical information devices including a first database for storing first patient data input via the patient terminal for each patient, and a plurality of medical information devices.
An integrated platform that includes a second database that stores second patient data and medical records entered through the staff of a medical institution for each patient, intervening between each of the plurality of medical information devices and patient terminals. When,
For the medical information device in the medical information system including
The first patient data registered and published in the integrated platform is acquired and stored in the second database.
Accepting access from the patient terminal,
When the first patient data stored in the second database for the patient related to the access is not associated with the medical record, the staff selected the first patient data. Provided is a control method of a medical information system that executes a procedure of associating the medical record with respect to a specific patient.

A fourth aspect of the present invention is
A plurality of medical information devices including a first database for storing first patient data input via the patient terminal for each patient, and a plurality of medical information devices.
An integrated platform that includes a second database that stores second patient data and medical records entered through the staff of a medical institution for each patient, intervening between each of the plurality of medical information devices and patient terminals. When,
For the medical information device in the medical information system including
The first patient data registered and published in the integrated platform is acquired and stored in the second database.
Accepting access from the patient terminal,
When the first patient data stored in the second database for the patient related to the access is not associated with the medical record, the staff selected the first patient data. Provided is a control program for performing the procedure of associating the medical record with respect to a specific patient.

A fourth aspect of the present invention is
A plurality of medical information devices including a first database for storing first patient data input via the patient terminal for each patient, and a plurality of medical information devices.
Intervening between each of the plurality of medical information devices and the patient terminal, the second patient data and medical record input through the staff of the medical institution for each patient are stored, and registered and registered in the integrated platform. An integrated platform that includes a second database that acquires the published first patient data and stores it in the second database.
For the display device of the medical information device in the medical information system including
When the first patient data stored in the second database for the patient related to the access received from the patient terminal is not associated with the medical record, the first patient related to the patient related to the access. A list of patients related to the second patient data having a predetermined relationship with the data is displayed on the screen.
Medical information for executing a procedure of associating the medical record regarding a specific patient selected by the staff from the list with the first patient data stored in the second database for the patient related to the access. Provides a method of controlling the system.

According to the present invention, a terminal (application) possessed by a patient can be seamlessly linked with each business system such as medical care, dentistry, and dispensing. In addition, the system infrastructure that handles patient data can be cut out from each business system and operated, and two similar information, patient data input by the patient from the app and patient data input by the staff of the medical institution from the business system, are available. Can be managed appropriately.

It is a schematic diagram of the medical information system 1 which concerns on Embodiment 1. It is a block diagram which shows the physical structure of the computer 10 which constitutes the medical information system 1. It is a block diagram which shows the software structure of the integrated board 10. It is a block diagram which shows the software structure of the medical information apparatus 30. It is a figure which shows the outline of the patient data registration starting from (A) a patient and (B) a medical institution staff. It is a conceptual diagram of the integration of patient data in business DB 35. This is an example of a screen 40 for displaying a list of patient receptions in the medical information device 30 of the medical institution a. This is an example of an input screen 50 for accepting a patient whose medical record is not registered in the medical information device 30 of the medical institution a. This is an example of a screen 60 that displays a list of similar patients registered in the medical information device 30 of the medical institution a. It is the schematic of the medical information system 2 which concerns on Embodiment 2. It is a flow chart which shows an example of the cooperation procedure in the medical information system 2.

Hereinafter, typical embodiments of the present invention will be described in detail with reference to the drawings. However, the present invention is not limited to these drawings. In addition, since the drawings are for conceptually explaining the present invention, the dimensions, ratios, or numbers may be exaggerated or simplified as necessary for easy understanding.

1. 1. Overview of medical information system
1-1. Overall Configuration of Medical Information System The overall configuration of the medical information system 1 according to the present embodiment will be described.
As shown in FIG. 1A, the medical information system 1 includes an integrated platform 10 and a plurality of medical information devices 30, and is configured to be able to communicate with a plurality of patient terminals (apps) 70. Here, "medical care" is a concept including medical care, dentistry, and pharmacy, and may further include long-term care and the like. In addition, "medical information" broadly includes, for example, a PHR (Personal Health Record) relating to medical records (medical records), prescription / medication records, and the like. In this specification, the medical record refers to medical information excluding patient data described later.

The medical information device 30 is a business system that handles medical information, and is provided for each medical institution. The medical information device 30 may be a business system that handles a specific area such as medical care, dentistry, or pharmacy, or may be a complex business system that covers a plurality of areas or medical treatment in general. Further, the medical institution may have, for example, an individual clinic / hospital / pharmacy as one unit, or a plurality of clinics / hospitals / pharmacies belonging to the same management body as one unit. In this embodiment, a cloud-type business system is assumed as the medical information device 30, but the mounting method does not matter as long as it can be connected to the Internet. Details of the medical information device 30 will be described later.

The application 70 is an application that can be used by a patient operating a computer terminal (patient terminal) such as a personal computer, a smartphone, a tablet, or a wearable terminal. The patient can communicate with the medical institution and share medical information through the application 70.

The integrated platform 10 is a system platform that cross-sectionally manages patient data input from the application 70 and patient data handled by a plurality of medical information devices 30 connected to the integrated platform 10. The integrated platform 10 has management functions such as an authentication function, a data management function, and a payment function, and further has a linking function for linking patient data input from the application 70 with patient data input from a medical institution. It may be done (see the second embodiment described later). These functions will be described in detail later.

In the present embodiment, the application 70 and the integrated platform 10 are connected via an encrypted communication path. Protocols such as HTTPS and gRPC can be appropriately used for encrypted communication.
Further, the integrated platform 10 and each medical information device 30 are connected by an encrypted communication path. More specifically, from the viewpoint of security, fault tolerance, and asynchronous information linkage, as shown in FIG. 1 (B), information sharing from the integrated platform 10 to each medical information device 30 is published. By the subscribe-subscribe method, information sharing from each medical information device 30 to the integrated platform 10 is made by a request according to a protocol such as HTTPS.

1-2. Hardware Configuration of Medical Information Device, Patient Terminal, and Computer Constituting the Integrated Platform With reference to FIG. 2, the hardware configuration of the computer 100 constituting the medical information device 30, the patient terminal 70, and the integrated platform 10 will be described. As shown in the figure, the computer 100 includes a CPU (arithmetic unit) 101, a memory 102, a storage device 103, and a communication device 104, and may further include an input device 105 and an output device 106.

The CPU 101 reads various programs and data into the memory 102 and executes them to realize various functions as the integrated platform 10, the medical information device 30, and the patient terminal 70. The storage device 103 stores various data, databases, and programs, such as a hard disk drive, a solid state drive, and a flash memory.

The communication device 104 is an interface for connecting to a wired and wireless communication network, for example, an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone network, and wireless communication. It is a wireless communication device, a USB (Universal Serial Bus) connector for serial communication, an RS232C connector, and the like.

The input device 105 is, for example, a keyboard, a mouse, a touch panel, a button, a microphone, or the like for inputting data. In particular, the medical information device 30 and the computer 100 as the patient terminal 70 include the input device 105.

The output device 106 is, for example, a display, a printer, a speaker, or the like that outputs data, and in particular, the medical information device 30 and the computer 100 as the patient terminal 70 include a display.

2. The integrated infrastructure 10 will be described in detail with reference to the software configuration diagram 3 of the integrated infrastructure. As shown in the figure, the integrated infrastructure 10 includes each functional unit of the gateway (GW) 11, the authentication unit 12, the management unit 13, the payment unit 14, and the integrated database (DB) 15. These functional parts may be a single device, or may be separated for each function, for example.

The GW 11 receives access from the application 70 and controls access to the resources of the integrated platform 10 and each medical information device 30. Communication between the GW 11 and the application 70 is performed according to, for example, HTTP. The GW 11 may have a firewall function.

The authentication unit 12 authenticates and authorizes accounts, issues access tokens, and the like. Accounts are managed, for example, by telephone numbers or email addresses and passwords.

The management unit 13 manages basic patient information (patient information) included in the account. Here, the patient information includes patient data, and the patient data is data commonly held among the medical information devices 30, such as name, gender, and date of birth. However, the patient data individually required by the medical information device 30 shall be retained and managed by the medical information device 30. When the patient data is newly registered and the registered patient data is updated, the management unit 13 publishes the patient data to the medical information device 30.

The payment unit 14 performs payment processing for each medical information device 30 and manages the payment history.

The integrated DB 15 corresponds to the first database. The data items stored in the integrated DB 15 are assumed to be as follows, but are not limited to these. Further, it is not necessary to store all the following items in the integrated DB 15.
-Account information-Minimum basic information necessary for patients to use App 70-Patient data (corresponding to the first patient data, including name, gender, date of birth, etc.)
-Authentication information-Information required to log in to App 70-Patient's phone number, e-mail address, etc.-Payment information-Information required to make payment from App 70 However, the above itemization has been changed as appropriate. For example, the patient data may include a telephone number or the like, or conversely, the gender or the like may be excluded from the patient data. Further, the integrated DB 15 may be a single database or may be divided into a plurality of databases.

3. 3. The medical information device 30 will be described in detail with reference to the software configuration diagram 4 of the medical information device. As shown in the figure, the medical information device 30 includes each functional unit of the acquisition unit 31, the reception unit 32, the candidate presentation unit 33, the name identification unit 34, and the business database (DB) 35. In addition, the medical information device 30 includes a management function (not shown) that manages the business DB 35, but description thereof will be omitted here. It should be noted that these functional units may be a single device, or may be separated for each function, for example.

The acquisition unit 31 asynchronously acquires the patient data published from the integrated platform 10 and stores it in the business DB 35. That is, the acquisition unit 31 functions as a subscriber.

The reception unit 32 receives access (for example, reservation for medical examination, dispensing, etc.) from the application 70 and stores it in the business DB 35. The received access is displayed on the display device of the medical information device 30 (see FIG. 7A).

The candidate presentation unit 33 searches the business DB 35, and the medical record is associated with the patient related to the received access (that is, the patient data or account related to the patient acquired by the acquisition unit 31 and registered in the business DB 35). Check if it is. When the medical record described later is not associated with the patient, the candidate presentation unit 33 selects the candidate for the patient from the business DB 35, and displays the medical information device 30 so that the staff of the medical institution can confirm or select the candidate. (See FIG. 7C). Here, the candidate is the patient data associated with the medical record (that is, the patient data or account in which the patient data is input by the staff of the medical institution), and has a predetermined relationship with the patient data of the patient related to the access. Have. Candidates are preferably extracted from valid (non-disabled) accounts. In addition, the relevance of data is evaluated here as a degree of similarity. For example, when any of the items of name, gender, and date of birth match (exact match or partial match), the relevance (similarity) is May be accepted.

The name identification unit 34 links the medical record of the candidate confirmed or selected by the staff of the medical institution to the patient data corresponding to the patient related to access, and invalidates (for example, deletes) the patient data of the confirmed or selected candidate. However, it will not be used in the future. As a result, the patient data derived from the patient and the patient data derived from the staff of the medical institution are named and unified into the patient data derived from the patient.

The business DB 35 corresponds to the second database. The following data items are assumed to be stored in the business DB 35, but the data items are not limited to these. Further, it is not necessary to store all the following items in the business DB 35.
-Patient data (corresponds to the second patient data, including name, gender, date of birth, etc.)
-Basic information required for medical examination-Insurance information, public expense information, etc.-Medical examination information-Information for managing medical examination results-In the case of medical care and dentistry, main complaints / findings, treatments / actions, etc.-In the case of dispensing Is drug history, medication guidance, etc.-Accounting information-Information for calculating the amount billed to the patient-Billed amount, breakdown, etc. Here, among the registered items of the business DB35, the items other than the patient data are the medical records described above. It may be included in. The business DB 35 may be a single database or may be divided into a plurality of databases.

4. Operation of Medical Information System Next, the operation of the medical information system 1 having the above-described configuration will be described for each case.

4-1. Registration of new patient data With reference to FIG. 5, the procedure for saving patient data via the application 70 (patient starting point) and via the medical information device 30 (staff starting point) will be described.

(A) Patient-origin patient data registration When a patient accesses the medical information system 1 from the application 70 for the first time, patient-origin patient data registration is performed.

Specifically, in step A1, the application 70 is input with its own patient information (patient data, etc.). In step A2, the application 70 transmits an HTTP request requesting patient registration to the integrated platform 10 based on the input patient information.

Upon receiving the patient registration request, the integrated platform 10 (management unit 13) generates, for example, an account P-app in step A3, and stores the patient information of the patient in the integrated DB 15. Next, in step A4, the integrated platform 10 (authentication unit 12) returns an authentication key to the application 70. After that, the application 70 authenticates to the integrated platform 10 (authentication unit 12) based on the issued authentication key.

In step A5, the integrated platform 10 (for example, the management unit 13) asynchronously publishes (publishes) patient data (account P-app) to the medical information device 30 connected to the integrated platform 10. In step A6, the medical information device 30 acquires (subscribes) the published patient data at an arbitrary timing and stores it in the business DB 35.

In this way, the patient data is registered in the integrated DB 15 and the business DB 35 from the patient starting point. Initially, medical records and the like are not linked to the patient data (account P-app) registered in the business DB 35 from the patient origin. Even when the patient changes his / her own patient data that has been registered, the change registration is performed according to the above steps.

(B) Staff-based patient data registration When a patient first visits a medical institution (for example, at the first visit), staff-based patient data registration is performed.

That is, in step B1, the staff of the medical institution inputs the basic patient information of the patient to the medical information device 30. The patient information referred to here includes the same type of patient data as the patient data stored in the integrated DB 15, and other data may be the same as or different from the patient information stored in the integrated DB 15. You may.

Then, in step B2, the medical information device 30 generates, for example, an account P, and stores the patient information of the patient input by the staff in the business DB 35.

In this way, the patient data (account P) of the patient is registered in the business DB 35 starting from the staff of the medical institution. Therefore, the medical record is associated with the valid (not invalidated) patient data registered in the business DB 35 from the staff of the medical institution.

4-2. Name identification of patient data The management method of patient data will be described with reference to FIG.

As described above, the patient data (account P-app) of the patient input via the application 70 (patient origin) is asynchronously published by the integrated platform 10 after being saved in the integrated DB 15, and is connected to the integrated platform 10. It can be acquired by all medical information devices 30 (acquisition unit 31) and is stored in each business DB 35. On the other hand, the patient data (account P) input via the medical information device 30 (starting from the staff) is also stored in the business DB 35. That is, in the business DB 35, two systems of patient data such as patient data originating from the patient and patient data originating from the staff are recorded as separate accounts P and P-app. However, there is a difference between these two systems of patient data, for example, that the staff-origin patient data is associated with a medical record, but the patient-origin patient data is not associated with a medical record.

In order to eliminate the coexistence state of such two systems of patient data (accounts), both are named and unified. Here, the patient data originating from the patient and the patient data originating from the staff in the business DB 35 are named by the operation of the staff of the medical institution. In the present embodiment, in order to realize accurate and reliable name identification, the staff visually confirms that items such as name, gender, and date of birth match, and then performs name identification.

A specific example of the name identification procedure will be described with reference to FIGS. 7A to 7C. As a premise, it is assumed that the patient data (account P-app) originating from the patient and the patient data (account P) originating from the staff are already registered in the business DB 35. Here, a medical appointment is given as an example of access from the patient terminal (application) 70 to the medical information device 30, but it goes without saying that the access is not limited to this.

The medical information device 30 (reception unit 32) of a certain medical institution a accepts a medical examination appointment by patient A via the application 70. Since this consultation appointment is made using patient data (account P-app) originating from the patient, the medical information device 30 does not register patient information as a business system in this account P-app (linkage). There is no medical record given). Therefore, on the reception list screen 40 of the terminal of the medical institution a, the reservation status 41 of the patient A including, for example, the display of “not registered medical record” appears (FIG. 7A).

When the staff of the medical institution a selects the "reception" button 42, the terminal of the medical institution a displays the patient information (for example, patient data such as the patient's name, gender, and date of birth input fields 51 to 54) on the business system. A screen 50 prompting the input or confirmation of (including) is displayed in a pop-up (FIG. 7B). When the staff inputs or confirms the patient information and selects the "Next" button 55, a list screen 60 of similar patients is displayed as a candidate for the patient A (FIG. 7C). By displaying the candidates in a list, the work load on the staff is reduced and work mistakes are reduced.

On the similar patient list screen 60, a list 61 of patients in the business system (patient data originating from the staff; account P) having data similar to the patient data originating from the application is displayed. Only valid accounts P need to be displayed in the list. Then, the staff of the medical institution a selects a patient who is determined to be the same as the patient A from the list 61, so that the name identification is performed. That is, the medical record associated with the account P in the business DB35 corresponding to the patient data originating from the staff is replaced with the patient data originating from the application (account P-app), and the patient data originating from the staff is supported. The account P in the business DB 35 to be executed is invalidated (deleted, etc.).

Alternatively, if there is no patient in the list 61 that can be determined to be the same as patient A (including the case where the candidate is not listed in the list 61), the staff selects the "new registration" button 62 and creates a new medical record. I do.

4-3. Usage procedure after account integration When the name identification of patient data originating from the application and staff is completed as described above, for example, when the application 70 accesses the medical information device 30 of the medical institution a for medical appointment.
-Patient A accesses (user authentication) the medical information system 1 (integrated platform 10) via the application 70.
-Patient A makes an appointment with medical institution a via the app 70, and makes an appointment for medical examination, etc.
-The medical information device 30 of the medical institution a accepts the reservation of the patient A (app 70), and accepts the reservation.
-If applicable, the payment will be made via the medical information system 1 (integrated platform 10) after the medical examination.
At this stage, in the business DB 35, the account used by the patient A (application 70) in the reservation is associated with the medical record. In the case of other access, the process may be performed in the same procedure as described above.

As described above, in the medical information system 1, the terminal (application 70) possessed by the patient and each business system such as medical care, dentistry, and dispensing are seamlessly linked via the integrated platform 10. That is, from the patient's point of view, it is convenient because it is possible to access a plurality of medical institutions via the application 70 simply by preparing one account via the application 70.

In addition, the medical information system 1 distinguishes between the patient's own data (patient-derived information) input by the patient and the patient's data (medical institution-derived information) input by the medical institution by executing name identification. Can be managed. That is, since the patient-derived information is stored in the integrated DB 15 and is not stored only in the business DB 35, whether or not the data is stored in the integrated DB 15 determines whether or not the data is patient-derived information. It is easy to judge. In other words, each DB stores the data in both the integrated DB 15 and the business DB 35 in relation to each other, thereby clarifying whether the data originates from the patient or the medical staff. Such handling can not only clarify the division of responsibilities for data management, but also respond to the demand for strict information management.

Therefore, in the medical information system 1, the system infrastructure (authentication, payment, PHR management, etc.) that handles patient data can be cut out from each business system and operated, and the patient data input by the patient from the application and the staff of the medical institution can be operated. It is possible to appropriately manage two similar information, that is, patient data input from a business system. In particular, two similar pieces of information can be appropriately managed from the viewpoint of the method of realizing data matching and the viewpoint of data handling while ensuring the security level of both the patient and the medical institution. Therefore, it is expected that both the cloud computing of medical sites and the return of information to patients will be realized, which will contribute to the reduction of medical expenses, which will continue to increase in the future.

5. Embodiment 2
The information linkage in the medical information system 2 and the medical information system 2 according to the second embodiment will be described with reference to FIGS. 8 and 9.

The medical information system 2 also includes an integrated infrastructure 10 and a plurality of medical information devices 30. However, in the second embodiment, in addition to the above-mentioned GW11, authentication unit 12, management unit 13, settlement unit 14, and integrated DB 15, the integrated infrastructure 10 includes an authentication code acquisition unit 16, a cooperation token acquisition unit 17, and a cooperation token. It has a tying portion 18. Further, the medical information device 30 includes an authentication code generation unit 36, an authentication code linking unit 37, and a cooperation token generation unit 38 in addition to the acquisition unit 31 and the reception unit 32, but has a name identification function, that is, a candidate presentation unit 33. And it is not necessary to have the name identification unit 34. Hereinafter, the newly added functional parts will be described in association with the cooperation procedure.

To give an overview of information linkage in the medical information system 2, information linkage consists of three major flows.
(1) Acquisition of authentication code (request for cooperation from patient A to medical institution a)
(2) Linking the authentication code with the user (agreement from medical institution a)
(3) Implementation of authentication processing and acquisition of access token for cooperation (confirmation of intention of patient A and implementation of cooperation)
Each flow will be described in detail below.

(1) Acquisition of authentication code Patient A uses the application 70 to request the medical information device 30 (authentication code acquisition unit 16) of the medical institution a to pay out the authentication code for linking the application (step C1). .. The authentication code acquisition unit 16 is implemented as, for example, an API (Application Programming Interface) that acquires an authentication code from the medical information device 30 based on the application operation of the patient A.

The authentication code acquisition unit 16 requests the authentication code generation unit 36 of the medical information device 30 to pay out the authentication code (step C2). The authentication code generation unit 36 issues an authentication code having an expiration date unique to the application, which is valid only between the application 70 and the medical information device 30 (step C3). At the same time, the authentication code generation unit 36 stores the authentication code payout result in a database (for example, business DB 35).

The authentication code acquisition unit 16 of the integrated platform 10 transmits the authentication code received from the medical information device 30 to the application 70 (step C4). The authentication code issued in this way is displayed on the screen of the application 70. Here, the authentication code unique to the application may be expressed by a character string sufficient to ensure uniqueness or a barcode such as a QR code (registered trademark), but is not limited thereto.

(2) Linking the authentication code with the user Patient A presents the authentication code received in the application 70 to the staff of the medical institution a. The staff of the medical institution a confirms the authentication code recorded in the medical information device 30, performs identity verification, and then associates (associates) the authentication code with the patient A recorded in the medical information device 30. ) Instruct. The authentication code linking unit 37 executes the linking of the authentication code according to the staff operation (step D1). Such staff operation also has significance as the consent or permission of the medical institution a for the cooperative processing.

Then, the authentication code linking unit 37 notifies the staff of the medical institution a by displaying, for example, on the display of the medical information device 30, that the above association has been completed (step D2). The staff then notifies patient A of the completion of the association. At the same time, the authentication code linking unit 37 may notify the application 70 of the completion of the association.

(3) Implementation of authentication processing and acquisition of access token for cooperation Patient A performs cooperation processing using the authentication code after the work of (2) above. Such patient manipulation also has significance as the final confirmation or consent of patient A for the coordinated processing. Specifically, the application 70 calls the cooperation API in the integrated platform 10, that is, the cooperation token acquisition unit 17 based on the operation of the patient A (step E1).

The cooperation token acquisition unit 17 calls the cooperation API in the medical information device 30, that is, the cooperation token generation unit 38 (step E2). The request of the integration platform 10 includes the authentication code of patient A.

The cooperation token generation unit 38 extracts the user (patient) corresponding to the received authentication code (step E3), and pays a unique access token (cooperation access token) for accessing the patient information of the extracted user. Put out (step E4). When the integration platform 10 (cooperation token acquisition unit 17) receives the cooperation access token, the cooperation token linking unit 18 links the patient information (ID information) of patient A on the integration platform 10 with the cooperation access token. Attach (step E5).

When the linking work is completed, the linking token linking unit 18 notifies the application 70 of the completion of the linking process (step E6). By displaying such a notification in the application 70, for example, the patient A can know the completion of the cooperative processing.

As described above, in the second embodiment, the patient A issues a cooperation request with the medical information device 30 via the application 70, and after the cooperation permission by the staff of the medical institution a, the integrated platform 10 and the medical information device 30 are connected. The association is recorded on the integrated platform 10. That is, in order to link the information of patient A with the information of medical institution a, the consent of both patient A and medical institution a is required. The existing standardized authentication cooperation technology is used for issuing the authentication code, access permission, and access token, and in the integrated platform 10, patient data and access token are linked on the premise of the authentication cooperation technology. It has the advantage of being easy to link with existing systems.

Although the typical embodiments of the present invention have been described above, the present invention is not limited to these, and various design changes are possible, and these are also included in the present invention. For example, the medical information system may include a medical information device having a name identification function and a medical information device not having a name identification function, and the integrated platform is a service (function) according to the characteristics of the medical information device. ) Can be provided.

1 ... Medical information system,
10 ... Integrated platform,
11 ... Gateway (GW),
12 ... Certification Department,
13 ... Account Management Department,
14 ... Payment department,
15 ... Integrated database (DB),
30 ... Medical information device,
31 ... Acquisition department,
32 ... Reception department,
33 ... Candidate presentation section,
34 ... Name identification department,
35 ... Business database (DB),
70 ... Patient terminal (app).

Claims (7)

A medical information system including a plurality of medical information devices and an integrated platform interposed between each of the plurality of medical information devices and a patient terminal.
The integrated platform is
A first database that stores the first patient data input via the patient terminal for each patient, and
When the first patient data is registered in the first database, the management unit that publishes the first patient data to the plurality of medical information devices is included.
Each of the plurality of medical information devices
A second database that stores a second patient data and medical record entered through the staff of the medical institution for each patient,
An acquisition unit that acquires the first patient data published on the integrated platform and stores it in the second database, and
The reception section that accepts access from the patient terminal and
When the first patient data stored in the second database for the patient related to the access is not associated with the medical record, the staff selected the first patient data. Includes a name identification section that links the medical records for a particular patient,
A medical information system featuring. Each of the plurality of medical information devices further includes a candidate presentation unit that displays a list of candidates so that the staff can select the specific patient.
The medical information system according to claim 1. The first patient data and the second patient data each include at least name, gender and date of birth.
The candidate presentation unit selects a patient having the second patient data that partially matches the first patient data in at least one of the name, the sex, and the date of birth as the candidate.
2. The medical information system according to claim 2. A medical information device that is accessed from a patient terminal via an integrated platform that includes a first database that stores a first patient data input via the patient terminal for each patient.
A second database that stores a second patient data and medical record entered through the staff of the medical institution for each patient,
An acquisition unit that acquires the first patient data registered and published on the integrated platform and stores it in the second database.
The reception section that accepts access from the patient terminal and
When the first patient data stored in the second database for the patient related to the access is not associated with the medical record, the staff selected the first patient data. The name identification section that links the medical records related to a specific patient,
A medical information device characterized by including. A plurality of medical information devices including a first database for storing first patient data input via the patient terminal for each patient, and a plurality of medical information devices.
An integrated platform that includes a second database that stores second patient data and medical records entered through the staff of a medical institution for each patient, intervening between each of the plurality of medical information devices and patient terminals. When,
For the medical information device in the medical information system including
The first patient data registered and published in the integrated platform is acquired and stored in the second database.
Accepting access from the patient terminal,
When the first patient data stored in the second database for the patient related to the access is not associated with the medical record, the staff selected the first patient data. A method of controlling a medical information system that executes a procedure of associating the medical record with respect to a specific patient. A plurality of medical information devices including a first database for storing first patient data input via the patient terminal for each patient, and a plurality of medical information devices.
An integrated platform that includes a second database that stores second patient data and medical records entered through the staff of a medical institution for each patient, intervening between each of the plurality of medical information devices and patient terminals. When,
For the medical information device in the medical information system including
The first patient data registered and published in the integrated platform is acquired and stored in the second database.
Accepting access from the patient terminal,
When the first patient data stored in the second database for the patient related to the access is not associated with the medical record, the staff selected the first patient data. A control program for performing the procedure of associating the medical record for a specific patient. A plurality of medical information devices including a first database for storing first patient data input via the patient terminal for each patient, and a plurality of medical information devices.
Intervening between each of the plurality of medical information devices and the patient terminal, the second patient data and medical record input through the staff of the medical institution for each patient are stored, and registered and registered in the integrated platform. An integrated platform that includes a second database that acquires the published first patient data and stores it in the second database.
For the display device of the medical information device in the medical information system including
When the first patient data stored in the second database for the patient related to the access received from the patient terminal is not associated with the medical record, the first patient related to the patient related to the access. A list of patients related to the second patient data having a predetermined relationship with the data is displayed on the screen.
Medical information for executing a procedure of associating the medical record regarding a specific patient selected by the staff from the list with the first patient data stored in the second database for the patient related to the access. How to control the system.

Images