JP6398664B2 - Medical information linking system, method, and program - Google Patents

Description

  The present invention relates to a medical information linking system, a medical information linking method, and a medical information linking program.

  In medical institutions such as hospitals, clinics, care providers, and dispensing pharmacies, medical information such as medical examinations, examinations, and prescriptions may be managed as electronic information by a business system such as an electronic medical record system. In such a business system, a patient ID for identifying a patient and medical information about the patient are associated and managed.

  As a technique related to management of medical information, a system related to management when a medicine that is a source of an injection to be administered to a patient is accommodated in a tray for each patient based on a doctor's injection prescription information has been proposed. In this system, a medicine that is a source of an injection medicine is stored in a tray for each patient, and a matching label in which collation information that can be distinguished from drugs in other trays is printed in a bar code form is attached to each medicine. And the collation label of the medicine taken out from the tray for co-infusion based on the doctor's injection prescription information is read with a bar code reader before co-infusion. And after collating the read collation information with a doctor's injection prescription information automatically, mixed injection is performed according to the collation result.

  Further, there is a personal medical information management service (hereinafter referred to as “PHR service”) related to PHR (Personal Health Record), which is a record in which an individual stores medical information related to his / her health under self-management. The PHR service is provided by a web system, for example, and a user accesses the PHR service from a terminal such as a personal computer or a smartphone, and registers and manages information related to his / her health.

JP 2002-92165 A

  In order for PHR service users to efficiently register their personal medical information in the PHR service, it is necessary to associate the PHR service with a business system such as an electronic medical record system operating at each medical institution. It is.

  However, in the conventional technology, the patient ID and the medical information are linked in the business system of the medical institution. However, the medical information managed by the business system of the medical institution and the medical service managed by the PHR service are used. A technique for linking information is not disclosed.

  In addition, a user who uses the PHR service is not necessarily an expert regarding the operation of electronic information. Therefore, it is necessary to identify a medical institution to which medical information is to be associated from among a plurality of medical institutions, to identify the patient ID assigned to each medical institution, and to associate the identified information with the PHR service. Registering may not be an easy operation for the user.

  An object of the present invention is to link medical information managed by a medical institution and medical information managed by a personal medical information management service by a simple operation.

  As one aspect, a medical information associating system includes a medical institution information processing apparatus that manages medical information in a medical institution, a personal medical information processing apparatus that manages medical information by a personal medical information management service, and a medical information associating apparatus; including. The medical institution information processing apparatus includes a first request unit that requests the medical information association apparatus to assign a unique association number to identification information of the medical institution and patient identification information in the medical institution. In addition, the medical institution information processing apparatus outputs information representing the association number assigned by the medical information association apparatus to a medium that can be read by a terminal device of a user who uses the personal medical information management service. Is provided. The personal medical information processing apparatus includes a second request unit that requests association between medical information managed by the medical institution information processing apparatus and medical information managed by the personal medical information processing apparatus. The second request unit, in the user's terminal device, associates the association number acquired by reading from the medium, the identification information of the personal medical information management service, and the identification information of the user to the medical information association device. Send. The medical information linking device assigns a linking number to a request from the first request unit, and stores the identification information of the medical institution and the patient identification information in association with the linking number in the storage unit. A provision part is provided. Further, based on the request from the second request unit, the received identification information of the personal medical information management service and the user identification information are stored in the storage unit that matches the received association number. And a registration unit for registering in the storage unit.

  As one aspect, there is an effect that medical information managed by a medical institution and medical information managed by a personal medical information management service can be linked with a simple operation.

It is a functional block diagram which shows schematic structure of the medical information tied system which concerns on this embodiment. It is a figure which shows an example of a business system medical information table. It is a figure which shows an example of a patient information table. It is a figure which shows an example of the output of a two-dimensional code image. It is a figure which shows an example of a PHR medical information table. It is a figure which shows an example of a user information table. It is a figure which shows an example of a tied table. It is a figure which shows an example of an entry point table. It is a block diagram which shows schematic structure of the computer which functions as a medical information tied server. It is a block diagram which shows schematic structure of the computer which functions as a server for business systems. It is a block diagram which shows schematic structure of the computer which functions as a server for PHR services. It is a sequence diagram which shows an example of a series of processes in a medical information association system. It is a flowchart which shows an example of the business system side process. It is a flowchart which shows an example of a production | generation process. It is a figure which shows an example of a tied table. It is a flowchart which shows an example of a PHR service side process. Registration processing is executed (S50 in FIG. 12). It is a figure which shows an example of a tied table. It is a figure which shows an example of an entry point table. It is a flowchart which shows an example of a relay process. It is a figure which shows roughly an example of the medical information tied base provided by this embodiment. It is a figure which shows an example of a tied table.

  Hereinafter, an example of an embodiment according to the disclosed technology will be described in detail with reference to the drawings.

  As shown in FIG. 1, a medical information linking system 10 according to the present embodiment includes a medical information linking server 20, a plurality of business system servers 30, a plurality of PHR (Personal Health Record) service servers 40, and a plurality of servers. User terminal 50. The medical information association server 20, each of the plurality of business system servers 30, each of the plurality of PHR service servers 40, and each of the plurality of user terminals 50 are connected to each other via the network 15. The medical information association server 20 is an example of a medical information association device according to the disclosed technology. The business system server 30 is an example of a medical institution information processing apparatus according to the disclosed technology. The PHR service server 40 is an example of a personal medical information processing apparatus according to the disclosed technology.

  The business system server 30 operates, for example, in medical institutions such as hospitals, clinics, care providers, and dispensing pharmacies, and manages various medical information related to examinations, examinations, issuance of prescriptions, and the like performed in each medical institution. The business system server 30 is a server that operates as a business system such as an electronic medical record system, a care support system, or a dispensing receipt computer. In addition, the business system server 30 may be a server that operates as a regional cooperation system that collects and manages medical information in a plurality of medical institutions existing in a predetermined region.

  As illustrated in FIG. 1, the business system server 30 includes an issue request unit 31 and an output unit 32 as functional units related to the association between the business system and the PHR service. The issue request unit 31 is an example of a first request unit of the disclosed technology. The business system server 30 includes a business system medical information table 35 and a patient information table 36.

  First, each table of the business system server 30 will be described.

  The business system medical information table 35 stores a patient ID for identifying a patient and medical information about the patient identified by the patient ID in association with each other. FIG. 2 shows an example of the business system medical information table 35. In the example of the business system medical information table 35 in FIG. 2, information of “examination date”, “information type”, “document”, and “update date / time” is stored in association with the patient ID. “Examination date” is information such as the date on which a medical examination or examination is performed, the date on which a prescription is issued, and the like. “Information type” is information indicating the type of medical information such as medical examination, examination, and prescription. “Document” is document data indicating the contents of medical information. “Update date and time” is the date and time when each piece of medical information on the business system medical information table 35 is updated.

  The patient information table 36 stores a patient ID and attribute information of the patient identified by the patient ID in association with each other. FIG. 3 shows an example of the patient information table 36. In the example of the patient information table 36 in FIG. 3, information such as “name”, “date of birth”, “address”, and the like is stored as patient attribute information in association with the patient ID. The patient attribute information may include other attribute information such as sex and age.

  Next, each functional unit of the business system server 30 will be described.

  The issue request unit 31 requests the medical information linking server 20 to issue a two-dimensional code image representing the linking number used for linking the business system and the PHR service (details will be described later). Specifically, an operator such as a doctor of a medical institution instructs the business system server 30 operating in the medical institution to issue a two-dimensional code image. A request to issue a two-dimensional code image can be instructed by selecting a corresponding item from a business system menu provided by the business system server 30, for example.

  When the issuance request unit 31 accepts the issuance request for the two-dimensional code image, for example, the operator directly inputs the bar code or the like indicating the patient ID printed on the examination card or the like with a bar code reader. The patient ID of the target patient input by is acquired. Further, the issue request unit 31 stores a business system ID that is identification information of a business system (own system) and a medical institution ID that is identification information of a medical institution stored in a predetermined storage area of the business system server 30 in advance. To get. Further, the issue request unit 31 acquires predetermined attribute information from the patient information table 36 among the patient attribute information corresponding to the acquired patient ID. Here, a case where “birth date” is acquired as patient attribute information will be described. The issue request unit 31 generates an issue request including the acquired patient ID, business system ID, medical institution ID, and patient attribute information, and transmits the request to the medical information association server 20 via the network 15.

  When the output unit 32 receives the data of the two-dimensional code image returned in response to the request for issuing the two-dimensional code image, the output unit 32 uses the printer connected to the business system server 30 to convert the received two-dimensional code image to a paper medium. Control to print out. FIG. 4 shows an example of the output of a two-dimensional code image. FIG. 4 shows an example in which a two-dimensional code image 38 and a description 39 for associating the business system and the PHR service using the two-dimensional code image 38 are printed out on the paper medium 37.

  The PHR service server 40 is a server that provides a PHR service for managing PHR, which is medical information related to personal health such as a mother-child notebook and a medicine notebook. The PHR service server 40 can provide the PHR service to the user terminal 50 in the form of a web application or a mobile application, for example.

  As shown in FIG. 1, the PHR service server 40 includes an association request unit 41 as a functional unit related to association between a business system and a PHR service. The association request unit 41 is an example of a second request unit of the disclosed technology. The PHR service server 40 includes a PHR medical information table 45 and a user information table 46.

  First, each table included in the PHR service server 40 will be described.

  In the PHR medical information table 45, a user ID for identifying a user who uses the PHR service and medical information about the user identified by the user ID are stored in association with each other. FIG. 5 shows an example of the PHR medical information table 45. In the example of the PHR medical information table 45 in FIG. 5, information of “medical institution ID”, “examination date”, “information type”, and “document” is stored in association with the user ID. The “medical institution ID” stores a medical institution ID indicating a medical institution that is a management source of medical information. Information stored in the “examination date”, “information type”, and “document” is the same as that in the business system medical information table 35. The PHR medical information table 45 includes medical information directly input by the user from the user terminal 50 provided with the PHR service, and medical information acquired from the business system server 30 by associating a business system and a PHR service described later. Is memorized.

  The user information table 46 stores a user ID and user attribute information identified by the user ID in association with each other. FIG. 6 shows an example of the user information table 46. In the example of the user information table 46 in FIG. 6, information such as “name”, “date of birth”, “address”, and the like is stored as user attribute information in association with the user ID. The user attribute information may include other attribute information such as sex and age.

  Next, functional units of the PHR service server 40 will be described.

  The association request unit 41 associates the medical information associated with the medical information association server 20 with the medical information possessed by the business system server 30 and the medical information possessed by the PHR service server 40 in order to associate the business system with the PHR service. Request. Specifically, the association request unit 41 receives an association number and an expiration date (details will be described later) acquired from the user terminal 50 by reading a two-dimensional code image issued to the user from the user terminal 50. To do. The association request unit 41 acquires the user ID of the user who has logged in to the PHR service. Further, the association request unit 41 acquires a service ID that is identification information of a PHR service (own service) stored in advance in a predetermined storage area of the PHR service server 40. Further, the association request unit 41 acquires user attribute information corresponding to the acquired user ID from the user information table 46. The user attribute information to be acquired is predetermined attribute information, and the same attribute information included in the issue request transmitted from the issue request unit 31 of the business system server 30 to the medical information association server 20 is acquired. Set as follows. Therefore, “birth date” is acquired here as attribute information. The association request unit 41 generates an association request including the acquired association number, expiration date, user ID, service ID, and user attribute information, and transmits the association request to the medical information association server 20 via the network 15.

  The user terminal 50 is a terminal device that includes a display unit that displays an image, an input unit that inputs information, and a reading unit that reads a two-dimensional code image. As the user terminal 50, for example, a personal computer, a tablet terminal, a smartphone, or the like can be used.

  The medical information association server 20 functions as a medical information association base for realizing association between the business system and the PHR service. The medical information association server 20 associates a business system ID, a pair of a medical institution ID and a patient ID, and a pair of a service ID of the PHR service and a user ID in order to realize the association between the business system and the PHR service. wear. Thereby, the medical information associated with the patient ID in the business system is associated with the medical information associated with the user ID in the PHR service. The business system ID and the medical institution ID are examples of medical institution identification information of the disclosed technology. In this embodiment, since a business system that collects and manages medical information of a plurality of medical institutions, such as a regional cooperation system, is assumed, the business system ID and the medical institution ID are used to associate the medical information with the target. The medical institution which becomes becomes.

  As illustrated in FIG. 1, the medical information association server 20 includes a transmission / reception unit 21, a generation unit 22, a registration unit 23, and a relay unit 24 as functional units. The generating unit 22 is an example of a providing unit of the disclosed technology. The medical information linking server 20 includes a linking table 25 and an entry point table 26.

  First, each table that the medical information association server 20 has will be described.

  The association table 25 is associated with the unique association number assigned for each issuance request received from the business system server 30 and included in the association request received from the PHR service server 40 and the information included in the issuance request. Information is stored. FIG. 7 shows an example of the pegging table 25. In the example of the association table 25 in FIG. 7, the business system ID, medical institution ID, patient ID, and patient attribute information (here “birth date”) included in the issuance request are stored in association with the association number. ing. Further, a service ID, a user ID, and user attribute information (here “birth date”) included in the association request are stored in association with the association number. The association table 25 also stores the expiration date of the two-dimensional code image that is set when the association number is assigned. The expiration date of the two-dimensional code image is a time limit that allows the association request to be performed using the issued two-dimensional code image.

  The entry point table 26 stores entry points as information representing the position on the network 15 for each of the business system and the PHR service registered in the association table 25. The “entry point” is a URL indicating an access destination to the business system or the PHR service. FIG. 8 shows an example of the entry point table 26. In the example of the entry point table 26 in FIG. 8, information on “entry point” and “service type” is stored in association with the business system ID or the service ID. “Service type” is information indicating whether the access destination is a business system or a PHR service.

  Next, each functional unit of the medical information association server 20 will be described.

  The transmission / reception unit 21 transmits / receives information to / from each of the business system server 30 and the PHR service server 40. In addition, when receiving the issue request transmitted from the business system server 30, the transmission / reception unit 21 delivers the issue request to the generation unit 22. In addition, when the transmission / reception unit 21 receives the data of the two-dimensional code image generated by the generation unit 22 from the generation unit 22, the transmission / reception unit 21 returns the data to the business system server 30 that is the transmission source of the issue request. Further, when receiving the association request from the PHR service server 40, the transmission / reception unit 21 delivers the association request to the registration unit 23.

  When the generation unit 22 receives the issue request from the transmission / reception unit 21, the generation unit 22 refers to the association table 25 and assigns a unique association number to the received issue request. The generation unit 22 stores the business system ID, the medical institution ID, the patient ID, and the patient attribute information included in the issuance request in association with the assigned association number in the association table 25. In addition, the generation unit 22 sets a date after a predetermined period from the current time (for example, one week later, one month later, etc.) as the expiration date of the issued two-dimensional code image, and stores the date in the association table 25. Further, the generation unit 22 generates a two-dimensional code image representing the assigned association number and the set expiration date, and passes the generated two-dimensional code image to the transmission / reception unit 21.

  When the registration unit 23 receives the association request from the transmission / reception unit 21, the registration unit 23 checks the expiration date included in the association request. If the expiration date has not expired at this time, the registration unit 23 stores the attribute information of the user included in the association request in association with the association number matching the association number included in the association request in the association table 25. It is compared with the patient attribute information. When the attribute information matches, the registration unit 23 associates the service ID, the user ID, and the user attribute information included in the association request with the association number that matches the association number included in the association request. 25. As a result, the association information indicating the correspondence between the business system ID, the medical institution ID and patient ID pair, and the service ID and user ID pair is registered in the association table 25 using the association number as a key. become.

  Further, the registration unit 23 registers the entry point of the business system indicated by the business system ID and the entry point of the PHR service indicated by the service ID included in the registered association information in the entry point table 26. The entry point information can be extracted from, for example, the header information of the issuance request received from the business system server 30 and the association request received from the PHR service server 40.

  The relay unit 24 relays a search request for medical information and a return of a search result performed between the business system and the PHR service. Specifically, when a medical information search request including a service ID and a user ID is received from the PHR service, the business system ID and medical service associated with the received service ID and user ID are referenced with reference to the association table 25. An institution ID and a patient ID are specified. The relay unit 24 acquires an entry point corresponding to the specified business system ID from the entry point table 26 and relays a search request including the specified medical institution ID and patient ID from the association table 25. When the relay unit 24 receives a search result searched for in the business system as medical information corresponding to the patient ID from the business system server 30, the relay unit 24 relays the search result to the PHR service server 40 that is the search request source.

  When the relay unit 24 receives a search request for medical information including the business system ID, the medical institution ID, and the patient ID from the business system, the relay unit 24 refers to the association table 25. Then, the service ID and the user ID associated with the received business system ID, medical institution ID, and patient ID are specified. The relay unit 24 acquires an entry point corresponding to the identified service ID from the entry point table 26 and relays a search request including the identified user ID from the association table 25. When the relay unit 24 receives a search result searched by the PHR service as medical information corresponding to the user ID from the PHR service server 40, the relay unit 24 relays the search result to the business system server 30 that is the search request source.

  The medical information association server 20 can be realized by a computer 60 shown in FIG. 9, for example. The computer 60 includes a CPU 61, a memory 62 as a temporary storage area, and a nonvolatile storage unit 63. The computer 60 also includes an input / output interface (I / F) 64 to which an input / output device 68 such as a display device and an input device is connected. The computer 60 also includes a read / write (R / W) unit 65 that controls reading and writing of data with respect to the recording medium 69 and a network I / F 66 connected to the network 15 such as the Internet. The CPU 61, the memory 62, the storage unit 63, the input / output I / F 64, the R / W unit 65, and the network I / F 66 are connected to each other via a bus 67.

  The storage unit 63 can be realized by an HDD (Hard Disk Drive), an SSD (solid state drive), a flash memory, or the like. The storage unit 63 as a storage medium stores a medical information association program 70 for causing the computer 60 to function as the medical information association server 20. In addition, the storage unit 63 includes an association information storage area 75 in which information constituting the association table 25 is stored, and an entry point storage area 76 in which information constituting the entry point table 26 is stored. The CPU 61 reads the medical information association program 70 from the storage unit 63 and develops it in the memory 62, and sequentially executes the processes of the medical information association program 70. Further, the CPU 61 reads information from the association information storage area 75 and develops it in the memory 62 as the association table 25. Further, the CPU 61 reads information from the entry point storage area 76 and develops it as the entry point table 26 in the memory 62.

  The medical information association program 70 includes a transmission / reception process 71, a generation process 72, a registration process 73, and a relay process 74. The CPU 61 operates as the transmission / reception unit 21 illustrated in FIG. 1 by executing the transmission / reception process 71. The CPU 61 operates as the generation unit 22 illustrated in FIG. 1 by executing the generation process 72. The CPU 61 operates as the registration unit 23 illustrated in FIG. 1 by executing the registration process 73. Further, the CPU 61 operates as the relay unit 24 illustrated in FIG. 1 by executing the relay process 74. Accordingly, the computer 60 that has executed the medical information association program 70 functions as the medical information association server 20.

  The business system server 30 can be realized by a computer 80 shown in FIG. 10, for example. The computer 80 includes a CPU 81, a memory 82, a storage unit 83, an input / output I / F 84 to which an input / output device 88 is connected, and an R / R that controls reading and writing of data with respect to the recording medium 89. A W unit 85 and a network I / F 86 are provided.

  The storage unit 83 as a storage medium stores a business system side program 90 for causing the computer 80 to function as each functional unit related to the association in the business system server 30. In addition, the storage unit 83 includes a business system medical information storage area 95 in which information configuring the business system medical information table 35 is stored, and a patient information storage area 96 in which information configuring the patient information table 36 is stored. . The CPU 81 reads the business system side program 90 from the storage unit 83 and develops it in the memory 82, and sequentially executes the processes of the business system side program 90. Further, the CPU 81 reads information from the business system medical information storage area 95 and develops it in the memory 82 as a business system medical information table 35. Further, the CPU 81 reads information from the patient information storage area 96 and develops it in the memory 82 as a patient information table 36.

  The business system side program 90 includes an issue request process 91 and an output process 92. The CPU 81 operates as the issue request unit 31 illustrated in FIG. 1 by executing the issue request process 91. The CPU 81 operates as the output unit 32 shown in FIG. 1 by executing the output process 92. As a result, the computer 80 that has executed the business system side program 90 functions as each functional unit related to the association in the business system server 30.

  The PHR service server 40 can be realized by a computer 100 shown in FIG. 11, for example. The computer 100 includes a CPU 101, a memory 102, a storage unit 103, an input / output I / F 104 to which an input / output device 108 is connected, an R / W unit 105 that controls reading and writing of data with respect to a recording medium 109, and a network I / F 106. Is provided. The CPU 101, the memory 102, the storage unit 103, the input / output I / F 104, the R / W unit 105, and the network I / F 106 are connected to each other via a bus 107.

  The storage unit 103 as a storage medium stores a PHR service-side program 110 that causes the computer 100 to function as a functional unit related to association in the PHR service server 40. The storage unit 103 includes a PHR medical information storage area 115 in which information constituting the PHR medical information table 45 is stored, and a user information storage area 116 in which information constituting the user information table 46 is stored. The CPU 101 reads the PHR service side program 110 from the storage unit 103 and expands it in the memory 102, and sequentially executes the processes included in the PHR service side program 110. Further, the CPU 101 reads information from the PHR medical information storage area 115 and develops it in the memory 102 as a PHR medical information table 45. Further, the CPU 101 reads information from the user information storage area 116 and develops it in the memory 102 as a user information table 46.

  The PHR service side program 110 has an association request process 111. The CPU 101 operates as the association request unit 41 illustrated in FIG. 1 by executing the association request process 111. As a result, the computer 100 that has executed the PHR service-side program 110 functions as a functional unit related to the association in the PHR service server 40.

  Each of the medical information linking server 20, the business system server 30, and the PHR service server 40 can be realized by, for example, a semiconductor integrated circuit, more specifically, an ASIC (Application Specific Integrated Circuit) or the like.

  Next, the operation of the medical information linking system 10 according to the present embodiment will be described with reference to the sequence diagram shown in FIG.

  First, for example, a patient visits a medical institution, and reports to the doctor of the medical institution that he / she wishes to associate the business system in the medical institution with the PHR service used by the patient. A medical institution doctor or the like issues a two-dimensional code image to the business system server 30 operating in the medical institution by selecting a corresponding item from the business system menu provided by the business system server 30. Instruct the request. When an issue request is instructed to the business system server 30, the business system server 30 executes the business system side processing shown in FIG. 13 (S10-1 in FIG. 12).

  In step S11 of the business system side processing shown in FIG. 13, the issue request unit 31 receives the patient ID specified by input, the business system ID and the medical institution stored in advance in a predetermined storage area of the business system server 30. Get an ID. Further, the issue request unit 31 acquires predetermined attribute information (here, “birth date”) from the patient attribute information stored in the patient information table 36.

  Here, it is assumed that the patient “Taro Yamada” of the medical institution B desires the association. Further, it is assumed that the business system medical information table 35 included in the business system server 30 operating in the medical institution B is FIG. 2 and the patient information table 36 is FIG. Therefore, “A0019” (see FIG. 3) is designated as the patient ID of the patient who wishes to be associated. In addition, it is assumed that the medical institution ID “H0008” of the medical institution B and the business system ID “systemB.net” of the business system that manages the medical information of the medical institution B are stored in a predetermined storage area. In this case, the issue request unit 31 acquires the patient ID “A0019”, the business system ID “systemB.net”, the medical institution ID “H0008”, and the date of birth “1979/7/1” (see FIG. 3). .

  Next, in step S <b> 12, the issue request unit 31 generates an issue request including the acquired patient ID, business system ID, medical institution ID, and patient attribute information, and sends it to the medical information association server 20 via the network 15. Send.

  Next, in step S <b> 13, the output unit 32 determines whether two-dimensional code image data has been received from the business system server 30. If received, the process proceeds to step S14. If not received, the process waits until it is received.

  Here, processing in the medical information association server 20 that has received the issue request transmitted from the business system server 30 will be described. When the transmission / reception unit 21 of the medical information association server 20 receives the issue request transmitted from the business system server 30, the business system server 30 executes the generation process shown in FIG. 14 (S20 in FIG. 12).

  In step S21 of the generation process illustrated in FIG. 14, the transmission / reception unit 21 passes the received issue request to the generation unit 22. When the generation unit 22 receives the issue request from the transmission / reception unit 21, the generation unit 22 refers to the association table 25 and assigns a unique association number to the received issue request. Then, the generation unit 22 stores the business system ID, medical institution ID, patient ID, and patient attribute information included in the issuance request in the association table 25 in association with the assigned association number. In addition, the generation unit 22 sets a date after a predetermined period from the current time (for example, one week later, one month later, etc.) as the expiration date of the issued two-dimensional code image, and stores the date in the association table 25.

  For example, if the associating table 25 before numbering is in a state as shown in FIG. 7, the generating unit 22 assigns a number “R0004”, for example, to the issued issue request. . Then, the generation unit 22 associates the business system ID “systemB.net” and the medical institution ID “H0008” included in the issuance request with the assigned association number “R0004”, as indicated by the broken line portion in FIG. Store in the association table 25. Similarly, the generation unit 22 associates the patient ID “A0019”, the date of birth “1979/7/1”, and the set expiration date included in the issuance request with the assigned association number “R0004”. 25.

  Next, in step S <b> 22, the generation unit 22 generates a two-dimensional code image representing the assigned association number and the set expiration date, and transfers the data of the two-dimensional code image to the transmission / reception unit 21. Next, in step S23, the transmission / reception unit 21 returns the received two-dimensional code image data to the business system server 30 that issued the request, and ends the generation process.

  When the output unit 32 of the business system server 30 receives the returned two-dimensional code image as described above, an affirmative determination is made in step S13 of the business system side processing shown in FIG. 13, and the process proceeds to step S14. . In step S14, the output unit 32 controls the printer connected to the business system server 30 so that the received two-dimensional code image is printed on a paper medium, for example, as shown in FIG. The system side processing is terminated (S10-2 in FIG. 12).

  Next, a user using the PHR service logs in to the PHR service from the user terminal 50 using the user ID, and reads a two-dimensional code image issued by a medical institution visited by the user as a patient from the user terminal 50. (S30 in FIG. 12). The user terminal 50 acquires the association number and the expiration date represented by the read two-dimensional code image, and transmits them to the PHR service server 40. When the PHR service server 40 receives the association number and the expiration date transmitted from the user terminal 50, the PHR service side process shown in FIG. 16 is executed in the PHR service server 40 (S40-1 in FIG. 12). .

  In step S41 of the PHR service side process illustrated in FIG. 16, the association request unit 41 acquires the received association number and expiration date. Further, the association request unit 41 acquires the user ID of the user who has logged in to the PHR service. The association request unit 41 acquires a service ID stored in advance in a predetermined storage area of the PHR service server 40. Furthermore, the association request unit 41 acquires predetermined attribute information (here “birth date”) from the user attribute information stored in the user information table 46.

  Here, it is assumed that “Taro Yamada” described above associates the business system of medical institution B with the PHR service related to “medicine notebook” using the two-dimensional code image issued by medical institution B. Further, it is assumed that the PHR medical information table 45 included in the PHR service server 40 that provides the PHR service related to the “medicine notebook” is FIG. 5 and the user information table 46 is FIG. Therefore, “Taro Yamada” logs in to the PHR service related to “Medication Notebook” with the user ID “aaa@domoko.ne.jp” (see FIG. 6). Further, it is assumed that the service ID “drugnote.net” of the PHR service related to “medicine notebook” is stored in a predetermined storage area. In this case, the association request unit 41 acquires the association number “R0004” and the expiration date “2014/10/31” (see FIG. 15). In addition, the association request unit 41 acquires the user ID “aaa@domoko.ne.jp”, the service ID “drugnote.net”, and the date of birth “1979/7/1” (see FIG. 6).

  Next, in step S <b> 42, the association request unit 41 generates an association request including the acquired association number, expiration date, user ID, service ID, and user attribute information, and the medical information association server 20 via the network 15. Send to.

  Next, in step S43, the associating request unit 41 determines whether or not the associating result for the associating request is received from the medical information associating server 20. If received, the process proceeds to step S44. If not received, the process waits until it is received.

  Here, processing in the medical information linking server 20 that has received the linking request transmitted from the PHR service server 40 will be described. When the transmission / reception unit 21 of the medical information association server 20 receives the association request transmitted from the PHR service server 40, the registration process shown in FIG. 17 is executed in the medical information association server 20 (S50 in FIG. 12).

  In step S51 of the registration process illustrated in FIG. 17, the transmission / reception unit 21 passes the received association request to the registration unit 23. Then, the registration unit 23 confirms the expiration date included in the associating request, and determines whether or not the expiration date has passed. If not, the process proceeds to step S52. If it has elapsed, the two-dimensional code image has expired, that is, the association request cannot be permitted, and therefore the process proceeds to step S56 without registering the association information.

  In step S52, the registration unit 23 stores the user attribute information included in the association request and the patient attribute information stored in the association table 25 in association with the association number matching the association number included in the association request. Match. If the attribute information matches, the process proceeds to step S53. If the attribute information does not match, the identity between the patient to whom the two-dimensional code image is issued and the user using the PHR service is not secured. The process proceeds to step S56 without registering information.

  Here, the attribute information (“date of birth”) of the user included in the association request is “1979/7/1”. Further, as shown in FIG. 15, the patient attribute information (“date of birth”) stored in the association table 25 in association with the association number matching the association number “R0004” included in the association request is “ 1979/7/1 ". Accordingly, an affirmative determination is made in step S52.

  In step S53, the registration unit 23 stores the service ID, the user ID, and the user attribute information included in the association request in the association table 25, thereby registering the association information using the association number as a key in the association table 25. To do.

  For example, the registration unit 23 associates the service ID “drugnote” included in the association request with the association number “R0004” of the association table 25 that matches the association number included in the association request, as indicated by the broken line in FIG. .Net "is stored in the association table 25. Similarly, the registration unit 23 associates the user ID “aaa@domoko.ne.jp” and the date of birth “1979/7/1” included in the associating request with the associating number “R0004”. To remember. Accordingly, with the association number “R0004” as a key, association information indicating the correspondence between the medical institution B and the PHR service relating to the “medicine notebook” is registered in the association table 25 for “Taro Yamada”.

  Next, in step S54, the registration unit 23 stores the entry point of the business system indicated by the business system ID included in the association information registered in the association table 25 and the entry point of the PHR service indicated by the service ID. Register with. For example, the entry point is registered in the entry point table 26 in the state shown in FIG. 8 based on the association information as shown by the broken line portion in FIG. In the example of FIG. 8, the PHR service related to the “medicine notebook” indicated by the service ID “drugnote.net” has already been registered in the entry point table 26, and is not registered here again.

  Next, in step S55, the registration unit 23 notifies the transmission / reception unit 21 of the association result indicating that the registration of the association information is completed, and transmits the association result from the transmission / reception unit 21 to the PHR service server 40 that is the association request source. The registration process is terminated.

  On the other hand, in step S56, the registration unit 23 notifies the transmission / reception unit 21 of a connection result indicating that the connection information cannot be registered, and transmits the connection result from the transmission / reception unit 21 to the PHR service server 40 that is the connection request source, and registration processing Exit.

  When the linking result transmitted in step S55 or S56 is received by the linking request unit 41 of the PHR service server 40, an affirmative determination is made in step S43 of the PHR service side process shown in FIG. 16, and the process proceeds to step S44. To do. In step S44, the associating request unit 41 notifies the user terminal 50 of the accepted associating result, and ends the PHR service side processing (S40-2 in FIG. 12).

  Next, a case where medical information is searched between the business system and the PHR service based on the association information registered as described above will be described.

  First, a user who is a user of the PHR service logs in to the PHR service from the user terminal 50 and selects a corresponding item from the menu of the PHR service to instruct a search request for medical information in the business system. Thereby, a search request for medical information is transmitted from the user terminal 50 to the PHR service server 40 (S61 in FIG. 12).

  In the PHR service, the user ID of the logged-in user is acquired, and the acquired user ID and the service ID of the own service are included in the search request and transferred to the medical information association server 20 (S62 in FIG. 12).

  The medical information linking server 20 that has received the linking request from the PHR service executes the relay process shown in FIG. 20 (S70-1 in FIG. 12).

  In step S71 of the relay process illustrated in FIG. 20, the relay unit 24 refers to the association table 25 and identifies the business system ID, the medical institution ID, and the patient ID associated with the received service ID and user ID. . When there are a plurality of business system IDs and medical institution IDs associated with the user ID and the service ID, all are specified.

  Next, in step S72, the relay unit 24 acquires an entry point corresponding to the specified business system ID from the entry point table 26, and relays a search request including the specified medical institution ID and patient ID from the association table 25. .

  Next, in step S <b> 73, the relay unit 24 determines whether the search result for the search request is received from the business system server 30. If received, the process proceeds to step S74. If not received, the process waits until it is received.

  Here, processing in the business system server 30 that has received the search request relayed from the medical information association server 20 will be described. Upon receiving the search request, the business system server 30 acquires medical information from the business system medical information table 35 using the received patient ID as a key, and returns the medical information to the medical information association server 20 as a search result. If the corresponding medical information does not exist, a search result indicating that no medical information exists is notified to the medical information association server 20 (S81 in FIG. 12). The medical institution ID is the medical information about the target medical institution in the medical information of the business system when the medical information of a plurality of medical institutions is managed by one business system as in the regional cooperation system. Used to specify information.

  When the medical information association server 20 receives the search result from the business system server 30, an affirmative determination is made in step S73 of the relay process shown in FIG. 20, and the process proceeds to step S74. In step S74, the relay unit 24 relays the received search results to the search request source PHR service server 40, and the relay process ends. Note that when the association information corresponding to the PHR service of the search request source is not registered in the association table 25, a search result indicating that the association destination does not exist is notified (step S70-2 in FIG. 12).

  Here, the medical information association base provided by the medical information association server 20 will be described with a more specific example.

  For example, as shown in FIG. 21, a plurality of business systems such as a regional cooperation system A, a regional cooperation system B, an electronic medical record system C, an electronic medical record system D, a care support system E,. Suppose that Further, it is assumed that a plurality of PHR services such as a medicine notebook service, a mother and child notebook service, a health notebook service, a home medical care notebook service,. The regional cooperation system A is “systemA.net”, the regional cooperation system B is “systemB.net”, the electronic medical record system C is “karteC.com”, and the electronic medical record system D is “karteD.com”. Identified. The medicine notebook service is identified by the service ID of “drugnote.net”, the health notebook service is identified by “healthnote.com”, and the home care notebook service is identified by the service ID of “zaitakunote.com”.

  For example, it is assumed that the pegging table 25 at the current stage is in the state shown in FIG. The patient ID “A0028” is the patient ID of “Taro Yamada” at the medical institution with the medical institution ID “H0002”. Similarly, the patient ID “A0037” is the patient ID of “Taro Yamada” in the medical institution whose medical institution ID is “H0105”. In this case, the medical information of “Taro Yamada” indicates that the relationship indicated by the solid line arrow in FIG. 21 is associated. Therefore, when “Taro Yamada” makes a medical information search request from the medicine notebook service, the medical information of the regional cooperation system A associated with the association number “R0001” and the electronic information associated with “R0002”. Medical information of the medical chart system C can be acquired.

  From this state, as described in the above embodiment, it is assumed that the association information of the association number “R0004” is added and the association table 25 is in the state shown in FIG. In this case, it indicates that the pegging indicated by the broken line arrow in FIG. 21 has been added. In this state, when “Taro Yamada” makes a medical information search request from the medicine notebook service in the same manner as described above, in addition to the medical information of the regional cooperation system A and the electronic medical record system C, it is linked with “R0004”. Medical information of the obtained regional cooperation system B can be acquired.

  Note that the medical information acquired from the regional cooperation system is medical information of a medical institution indicated by the medical institution ID corresponding to the associated number among the medical information included in the regional cooperation system.

  Further, not only when the medical information search request is made from the PHR service side, it is also possible to make a search request from the business system side.

  Here, a case where a search request is made from the electronic medical chart system D will be described. For example, it is assumed that the associating information shown in the dashed line portion in FIG. 22 is registered in the associating table 25. This association information represents a relationship indicated by a one-dot broken line arrow in FIG. The medical institution ID of the medical institution that uses the electronic medical chart system D is “H0200”.

  In this state, it is assumed that medical information about the patient with the patient ID “A0001” is acquired from the PHR service from the electronic medical chart system D. The patient ID “A0001” is a patient ID in the medical institution of the medical institution ID “H0200” of “Ichiro Suzuki”. In this case, the electronic medical record system D transmits a search request including the business system ID “karteD.com”, the medical institution ID “H0200”, and the patient ID “A0001” to the medical information association server 20.

  In the medical information linking server 20, the linking information of the linking number “R0005” is retrieved from the linking table 25 using the business system ID “karteD.com”, the medical institution ID “H0200”, and the patient ID “A0001” as keys. . Then, based on the association information of the association number “R0005”, the home medical note service is identified as the PHR service of the association destination, and the medical information of “Ichiro Suzuki” is acquired from the home medical note service.

  As described above, according to the medical information association system according to the present embodiment, a unique association number is assigned to a pair of medical institution identification information (business system ID and medical institution ID) and patient identification information. Issue a two-dimensional code image to represent. In addition, a pair of identification information of a medical institution and identification information of a patient and a correlation number are stored in association with each other. Then, the PHR service transmits an association request including the association number acquired by reading the two-dimensional code image and a pair of the identification information of the PHR service and the identification information of the user. Accordingly, a pair of medical institution identification information and patient identification information and a pair of PHR service identification information and user identification information can be associated with each other using the association number as a key. Therefore, it is possible for a user to link medical information managed by a medical institution and medical information managed by a PHR service with a simple operation of simply reading a two-dimensional code image issued by the medical institution. .

  Further, by associating a pair of medical institution identification information and patient identification information with a pair of PHR service identification information and user identification information, a plurality of business systems can be associated with a plurality of PHR services. realizable.

  In addition, when associating a pair of medical institution identification information and patient identification information and a pair of PHR service identification information and user identification information with the association number as a key, patient attribute information in the medical institution The user attribute information in the PHR service is collated. Thereby, fraud such as impersonation can be prevented.

  In the above embodiment, the case where the date of birth is used as the attribute information has been described. However, other attribute information may be used, or a plurality of attribute information may be used in combination. When a plurality of attribute information is used, the effect of preventing fraud is further enhanced.

  Moreover, although the said embodiment demonstrated the case where a 2D code image was produced | generated with a medical information tied server, you may produce | generate a 2D code image with the server for business systems. In this case, the medical information linking server may return the numbered linking number and expiration date information to the business system server.

  In the above-described embodiment, the case where the code image representing the association number is a two-dimensional code image has been described. However, the code image may be any code image that can be easily read from the user terminal, for example, a one-dimensional code image. May be. Moreover, although the said embodiment demonstrated the case where the code image showing a tied number was printed out on a paper medium, it is not limited to this. As long as the code image is output in a state that can be easily read from the user terminal, any medium or output method may be output.

  Further, the information indicating the association number is not limited to output in the form of a code image. For example, the associating number may be printed on a paper medium as it is with numbers or symbols, and the associating number may be read from the user terminal by character recognition or the like.

  Further, the output of the information indicating the association number to the medium is not limited to the case of outputting to the paper medium as an image or a character. For example, data representing the association number itself, data obtained by encrypting the association number, or the like may be recorded on a USB memory or IC card, and the data recorded on the USB memory or IC card may be read at the user terminal. .

  In the above description, the medical information association program 70 is stored (installed) in the storage unit 63, the business system program 90 is stored in the storage unit 83, and the PHR service program 110 is stored in the storage unit 103 in advance. However, the present invention is not limited to this. It is also possible to provide the information recorded in a storage medium such as a CD-ROM, DVD-ROM, or USB memory.

  Regarding the above embodiment, the following additional notes are disclosed.

(Appendix 1)
A medical information linking system including a medical institution information processing apparatus that manages medical information in a medical institution, a personal medical information processing apparatus that manages medical information by a personal medical information management service, and a medical information linking apparatus,
The medical institution information processing apparatus includes:
A first requesting unit that requests the medical information associating device to give a unique association number to the identification information of the medical institution and the identification information of the patient in the medical institution;
An output unit that outputs information representing a pegging number assigned by the medical information pegging device to a medium that can be read by a terminal device of a user using the personal medical information management service;
The personal medical information processing apparatus includes:
In the user terminal device, the association number acquired by reading from the medium, the identification information of the personal medical information management service, and the identification information of the user are transmitted to the medical information association device, and the medical information A second requesting unit for requesting association between medical information managed by an institutional information processing apparatus and medical information managed by the personal medical information processing apparatus;
The medical information linking device is:
An assigning unit that assigns an association number to the request from the first request unit, and stores the identification information of the medical institution and the identification information of the patient in association with the association number;
Based on the request from the second request unit, the received identification information of the personal medical information management service and the user identification information correspond to the association number stored in the storage unit that matches the received association number. And a registration unit for registering in the storage unit.

(Appendix 2)
The assigning unit generates a one-dimensional or two-dimensional code image representing the assigned pegging number;
The medical information stringing system according to claim 1, wherein the output unit outputs the one-dimensional or two-dimensional code image generated by the adding unit to a paper medium.

(Appendix 3)
The medical information linking system according to supplementary note 1, wherein the output unit generates a one-dimensional or two-dimensional code image representing the linking number assigned by the adding unit, and outputs the code image to a paper medium.

(Appendix 4)
When the registration unit registers the received identification information of the personal medical information management service and the user identification information in the storage unit, the registration information of the patient in the medical institution and the personal medical information management service The medical information association system according to any one of supplementary notes 1 to 3, wherein the attribute information of the user is collated.

(Appendix 5)
When the assigning unit assigns the association number, any one of appendix 1 to appendix 4 that sets an expiration date for a period until a request is made by the second request unit using the association number. The medical information linking system described in the item.

(Appendix 6)
Based on the identification information of the medical institution and the identification information of the patient, the identification information of the personal medical information management service, and the identification information of the user stored in association with the storage unit via the association number The medical institution information processing apparatus relays a search request from the personal medical information processing apparatus to the medical institution information processing apparatus, and the medical institution information processing for the medical information in the personal medical information processing apparatus. The medical information stringing system according to any one of supplementary notes 1 to 5, further including a relay unit that relays a search request from the apparatus to the personal medical information processing apparatus.

(Appendix 7)
On the computer,
A unique pegging number is assigned to the identification information of the medical institution received from the medical institution information processing apparatus that manages the medical information in the medical institution and the patient identification information in the medical institution, and the identification information of the medical institution and the Store the patient identification information and the associated number in the storage unit in association with each other,
Information representing an association number output from a personal medical information processing apparatus that manages medical information by a personal medical information management service to a medium that can be read by a terminal device of a user who uses the personal medical information management service The association number acquired by reading from the terminal device of the personal information, the identification information of the personal medical information management service and the identification information of the user who uses the personal medical information management service are received and match the received correlation number In association with the association number stored in the storage unit, the received medical information management service identification information and the user identification information stored in the storage unit are associated with medical information. Method.

(Appendix 8)
The medical information linking method according to appendix 7, wherein the linking number is assigned, and a one-dimensional or two-dimensional code image representing the given linking number is generated and transmitted to the medical institution information processing apparatus.

(Appendix 9)
When registering the received identification information of the personal medical information management service and the user identification information in the storage unit, the patient attribute information in the medical institution and the user attribute information in the personal medical information management service The medical information linking method according to supplementary note 7 or supplementary note 8, wherein:

(Appendix 10)
Any one of appendix 7 to appendix 9 for setting an expiration date of processing for registering the received identification information of the personal medical information management service and the identification information of the user in the storage unit when assigning the association number The medical information linking method described in the item.

(Appendix 11)
In the computer,
Based on the identification information of the medical institution and the identification information of the patient, the identification information of the personal medical information management service, and the identification information of the user stored in association with the storage unit via the association number The medical institution information processing apparatus relays a search request from the personal medical information processing apparatus to the medical institution information processing apparatus, and the medical institution information processing for the medical information in the personal medical information processing apparatus. The medical information association method according to any one of appendix 7 to appendix 10, wherein a process further including relaying a search request from the apparatus to the personal medical information processing apparatus is executed.

(Appendix 12)
On the computer,
A unique pegging number is assigned to the identification information of the medical institution received from the medical institution information processing apparatus that manages the medical information in the medical institution and the patient identification information in the medical institution, and the identification information of the medical institution and the Store the patient identification information and the associated number in the storage unit in association with each other,
Information representing an association number output from a personal medical information processing apparatus that manages medical information by a personal medical information management service to a medium that can be read by a terminal device of a user who uses the personal medical information management service The association number acquired by reading from the terminal device of the personal information, the identification information of the personal medical information management service and the identification information of the user who uses the personal medical information management service are received and match the received correlation number Medical processing for executing processing including registering the received identification information of the personal medical information management service and the user identification information in the storage unit in association with the associated number stored in the storage unit Information association program.

(Appendix 13)
The medical information linking program according to appendix 12, wherein the linking number is assigned, and a one-dimensional or two-dimensional code image representing the given linking number is generated and transmitted to the medical institution information processing apparatus.

(Appendix 14)
When registering the received identification information of the personal medical information management service and the user identification information in the storage unit, the patient attribute information in the medical institution and the user attribute information in the personal medical information management service Supplementary note 12 or Supplementary note 13, the medical information linking program according to claim 13.

(Appendix 15)
Any one of appendix 12 to appendix 14, which sets an expiration date of the process of registering the received identification information of the personal medical information management service and the identification information of the user in the storage unit when assigning the association number Medical information linking program described in the section.

(Appendix 16)
In the computer,
Based on the identification information of the medical institution and the identification information of the patient, the identification information of the personal medical information management service, and the identification information of the user stored in association with the storage unit via the association number The medical institution information processing apparatus relays a search request from the personal medical information processing apparatus to the medical institution information processing apparatus, and the medical institution information processing for the medical information in the personal medical information processing apparatus. The medical information association program according to any one of appendix 12 to appendix 15, for executing processing further including relaying a search request from the apparatus to the personal medical information processing apparatus.

(Appendix 17)
A unique pegging number is assigned to the identification information of the medical institution received from the medical institution information processing apparatus that manages the medical information in the medical institution and the patient identification information in the medical institution, and the identification information of the medical institution and the An assigning unit that associates and stores the patient identification information and the associated number in the storage unit;
Information representing an association number output from a personal medical information processing apparatus that manages medical information by a personal medical information management service to a medium that can be read by a terminal device of a user who uses the personal medical information management service The association number acquired by reading from the terminal device of the personal information, the identification information of the personal medical information management service and the identification information of the user who uses the personal medical information management service are received and match the received correlation number A registration unit that registers the received identification information of the personal medical information management service and the identification information of the user in the storage unit in association with the association number stored in the storage unit;
Medical information linking device including:

(Appendix 18)
On the computer,
A unique pegging number is assigned to the identification information of the medical institution received from the medical institution information processing apparatus that manages the medical information in the medical institution and the patient identification information in the medical institution, and the identification information of the medical institution and the Store the patient identification information and the associated number in the storage unit in association with each other,
Information representing an association number output from a personal medical information processing apparatus that manages medical information by a personal medical information management service to a medium that can be read by a terminal device of a user who uses the personal medical information management service The association number acquired by reading from the terminal device of the personal information, the identification information of the personal medical information management service and the identification information of the user who uses the personal medical information management service are received and match the received correlation number Medical processing for executing processing including registering the received identification information of the personal medical information management service and the user identification information in the storage unit in association with the associated number stored in the storage unit A storage medium that stores an information association program.

10 Medical Information Linking System 15 Network 20 Medical Information Linking Server 21 Transmission / Reception Unit 22 Generation Unit 23 Registration Unit 24 Relay Unit 25 Linking Table 26 Entry Point Table 30 Business System Server 31 Issuance Request Unit 32 Output Unit 35 Business System Medical Information Table 36 Patient information table 37 Paper medium 38 Two-dimensional code image 40 PHR service server 41 Association request unit 45 PHR medical information table 46 User information table 50 User terminals 60, 80, 100 Computers 61, 81, 101 CPU
62, 82, 102 Memory 63, 83, 103 Storage unit 70 Medical information linking program 90 Business system side program 110 Service side program

Claims (8)

A medical information linking system including a medical institution information processing apparatus that manages medical information in a medical institution, a personal medical information processing apparatus that manages medical information by a personal medical information management service, and a medical information linking apparatus,
The medical institution information processing apparatus includes:
A first requesting unit that requests the medical information associating device to give a unique association number to the identification information of the medical institution and the identification information of the patient in the medical institution;
An output unit that outputs information representing a pegging number assigned by the medical information pegging device to a medium that can be read by a terminal device of a user using the personal medical information management service;
The personal medical information processing apparatus includes:
In the user terminal device, the association number acquired by reading from the medium, the identification information of the personal medical information management service, and the identification information of the user are transmitted to the medical information association device, and the medical information A second requesting unit for requesting association between medical information managed by an institutional information processing apparatus and medical information managed by the personal medical information processing apparatus;
The medical information linking device is:
An assigning unit that assigns an association number to the request from the first request unit, and stores the identification information of the medical institution and the identification information of the patient in association with the association number;
Based on the request from the second request unit, the received identification information of the personal medical information management service and the user identification information correspond to the association number stored in the storage unit that matches the received association number. And a registration unit for registering in the storage unit. The assigning unit generates a one-dimensional or two-dimensional code image representing the assigned pegging number;
The medical information stringing system according to claim 1, wherein the output unit outputs the one-dimensional or two-dimensional code image generated by the adding unit to a paper medium.   The medical information linking system according to claim 1, wherein the output unit generates a one-dimensional or two-dimensional code image representing a linking number assigned by the assigning unit and outputs the code image to a paper medium.   When the registration unit registers the received identification information of the personal medical information management service and the user identification information in the storage unit, the registration information of the patient in the medical institution and the personal medical information management service The medical information linking system according to any one of claims 1 to 3, wherein the attribute information of the user is collated.   The said grant part sets any expiration date with respect to the period until the request by the said 2nd request part using the said correlation number is performed, when giving the said correlation number. The medical information linking system according to claim 1.   Based on the identification information of the medical institution and the identification information of the patient, the identification information of the personal medical information management service, and the identification information of the user stored in association with the storage unit via the association number The medical institution information processing apparatus relays a search request from the personal medical information processing apparatus to the medical institution information processing apparatus, and the medical institution information processing for the medical information in the personal medical information processing apparatus. The medical information linking system according to any one of claims 1 to 5, further comprising a relay unit that relays a search request from the device to the personal medical information processing device. On the computer,
A unique pegging number is assigned to the identification information of the medical institution received from the medical institution information processing apparatus that manages the medical information in the medical institution and the patient identification information in the medical institution, and the identification information of the medical institution and the Store the patient identification information and the associated number in the storage unit in association with each other,
Information representing an association number output from a personal medical information processing apparatus that manages medical information by a personal medical information management service to a medium that can be read by a terminal device of a user who uses the personal medical information management service The association number acquired by reading from the terminal device of the personal information, the identification information of the personal medical information management service and the identification information of the user who uses the personal medical information management service are received and match the received correlation number In association with the association number stored in the storage unit, the received medical information management service identification information and the user identification information stored in the storage unit are associated with medical information. Method. On the computer,
A unique pegging number is assigned to the identification information of the medical institution received from the medical institution information processing apparatus that manages the medical information in the medical institution and the patient identification information in the medical institution, and the identification information of the medical institution and the Store the patient identification information and the associated number in the storage unit in association with each other,
Information representing an association number output from a personal medical information processing apparatus that manages medical information by a personal medical information management service to a medium that can be read by a terminal device of a user who uses the personal medical information management service The association number acquired by reading from the terminal device of the personal information, the identification information of the personal medical information management service and the identification information of the user who uses the personal medical information management service are received and match the received correlation number Medical processing for executing processing including registering the received identification information of the personal medical information management service and the user identification information in the storage unit in association with the associated number stored in the storage unit Information association program.

Images