JP2002109371A - Information-providing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make changes, based on information retrieval request to information retrieved from an information retrieving device, according to the information retrieval request. SOLUTION: An mediating server 102 has a privacy protection processing 112 function for editing the retrieved information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention belongs to a technical field related to electronic commerce using the Internet or the like. Among them, it particularly belongs to the field of system technology for providing information on services and products, ordering and the like.

[0002]

2. Description of the Related Art In the field of electronic commerce, there is a system for acquiring information on goods such as services or goods via a network, and ordering or reserving appropriate goods from the information. In general, a consumer can acquire information on a product by requesting a search for a database (hereinafter, referred to as a DB) or a system having a file group that manages information on characteristics of the product. At this time, it is common to provide information that is characteristic of the product as a search condition. Product features include cases where a predetermined item and a candidate list of items are given, and cases where consumers freely set words.The former is a database search using SQL statements, etc.
In the latter case, techniques such as full-text search are often used.

Further, the system has a customer DB for managing personal information such as age, gender, purchase history, etc., and combines search conditions with personal information to provide or search for product information closest to the consumer's request. There are systems that can provide information on products that are closely related to products. For example, the system has a knowledge base of products that are likely to be searched for personal information. Based on the search conditions and the personal information in the customer DB, the product recommended by the knowledge base is proposed to the consumer with priority.

[0004]

On the other hand, in an area such as nursing care, local medical and nursing resources are managed so that nursing care and medical staff who grasp the condition of the care recipient can order an appropriate nursing care service. There are applications that use the system. Nursing and medical staff
This system is used to search for necessary nursing care services and make reservations for appropriate nursing care services. The difference between the system on the left and the system that provides general product information is that the user who searches for product information using the system is different from the consumer who actually receives the product (for nursing care, the service). is there.

[0005] In particular, when personal information is added as a search method, a privacy problem arises. It is problematic for a third party, such as a caregiver or a medical staff, to notify each company without permission of personal information before a service contract is made. Here, if an intermediary server is provided and the search is undertaken by one hand, personal information does not need to be passed to each company, but it is difficult to implement such as customizing search results based on each company's own customer DB It is.

[0006] The present invention is not limited to nursing care services, but can be applied to a case where a service beneficiary who receives a service and a person who searches for information on the service are different.

[0007]

In order to solve the above-mentioned problems, the present invention is to perform a change based on an information retrieval request to information retrieved from an information retrieval device in response to the information retrieval request. is there. For example, a predetermined item is provided from information for each service beneficiary including a plurality of items. In addition, service providers (or information searchers)
Alternatively, the item to be provided may be determined according to the service provision content, and the determined item may be transmitted to the information search source.

[0008]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described with reference to FIG. In the present embodiment, the service requester system 10
1. Assume a system configuration including an intermediate server 102 and a business server 103. Service requester system 101
May be used by medical and welfare staff such as care managers. The business server 103
Is considered to be used by care service providers such as hospitals, nursing homes, nursing homes, and helper stations. In FIG. 1, the service requester system 10
1. Although only one mediation server 102 and one business server 103 are described, at least a plurality of service requester systems and business servers may exist.

The mediation system 102 includes a privacy protection policy 116, a patient DB 113, and a service attribute DB1.
14. It has a service offer 115. The business server 103 includes a patient DB 121, a service attribute DB 12
2. It has a service offer 123. Note that the configuration may be such that only one of the mediation system 102 and the business server 103 has the patient DB.

FIG. 3 shows the data format of the patient DB, and each column is an attribute of personal information handled by this DB. Column 301 is a patient ID, column 302 is a patient name, column 303 is a date of birth, and column 3
04 is an infection (HIV). In FIG. 3, the attributes described on the left are used as an example, but other attributes may be included in the patient DB.

FIG. 4 shows the data format of the privacy protection policy.
Is a tag name, and a column 403 is a privacy attribute. Here, the community ID is ID information provided for identifying a target service domain, and a different privacy protection policy can be set for each service domain. As service domains in the present embodiment, visiting care, facility care, welfare equipment rental, and the like can be considered. The tag name corresponds to one of the attributes of the patient DB. The privacy attribute registers a protection level for each attribute. In the present embodiment, which attribute of the patient DB may be notified to the enterprise server 103 as the protection level is defined. The attribute value of the patient DB to which the privacy attribute is allowed allows the notification to the provider server 103. In addition, the attribute value of the patient DB for which the privacy attribute is not allowed is not allowed to be notified to the provider server 103. As a privacy attribute, a method of defining whether to notify or not according to the authority of the business server may be considered as an alternative. For example, when the authority of the business server is set to five levels, the attribute of the personal information for which 3 is registered as the privacy attribute is notified to the business server having the authority of 3 or more of the attribute shown on the left. It is possible to forgive.

FIG. 5 shows the data format of the service attribute DB. A column 501 is a community ID, a column 502 is a provider ID, a column 503 is a service ID, a column 504 is a tag name, and a column 505 is a value. The community ID is synonymous with the community ID in the privacy protection policy. The provider ID is ID information for identifying which service provider information. The service ID is
ID information for identifying a service. The tag name is
This is an attribute for defining the characteristics of the service.
05, the attribute value is registered. The tag name of the service attribute DB may include the tag name of the privacy protection policy.

FIG. 6 shows a data format of a service offer. It defines an estimate and an interface for the service identified by the service ID in the service attribute DB. Column 601 is a service ID, column 602 is a price, column 60
Reference numeral 4 denotes a business entity reference. The service ID is ID information for identifying a service in the service attribute DB, and the same ID as the service ID is included in the service ID in the service attribute DB. The price represents the provision price of this service. The service provider reference is an interface for communicating the service to the service service provider. For example, when TCP / IP is used as a communication protocol, it corresponds to an IP address and a port number. In the present embodiment, in the service reservation processing,
It is assumed that the service requester system 101 and the business server 103 perform communication.

Hereinafter, the processing flow of the present invention will be described with reference to FIG.

First, the service requester system 101
In the service request processing 104, a request profile in the data format shown in FIG. 2 is transmitted to the mediation server 102 as a service request message. The service request receiving process 106 of the mediation server 102 receives the service request message.

The request profile shown in FIG. 2 is defined by tag-value pairs. For example, “<” shown at 201 in FIG.
"Request source reference>" is a tag, and "01" indicated by 203
01: 8 "is the value. The “</ request source reference>” 202 is provided for identifying the end of the value character string.

The service reception processing 106 passes the received service request message to the personal information search processing 107 and the privacy protection processing 112.

The personal information search processing 107 will be described with reference to the flowchart of FIG.

Step 701: Extract the patient ID from the service request message. The patient ID is described in an area of a tag “<patient ID>” indicated by 204 in the request profile of FIG.

Step 702: Based on the patient ID, the patient D
The personal information is searched from B113. Since the patient ID is “1” in the request profile of FIG. 2, the patient DB of FIG.
About at least patient name: Taro Yamada, date of birth: 1940
/ 11/03, Infectious disease (HIV): positive, ... hit. Of course, if the personal information of the patient ID is not registered in the patient DB, no record is hit.

Step 703: The personal information retrieved in step 702 is passed to the matching processing 108 together with the service request message.

The matching process 108 will be described with reference to the flowchart of FIG.

Step 801: Search the service attribute DB 114 based on the service request message and personal information.
First, the service attribute DB 114 is searched based on the community ID described in the request profile which is a service request message. Hit record row
C (i) (i = 1 to k). The community ID is described in an area of a tag “<community ID>” indicated by 205 in the request profile of FIG. Since the community ID is “1” in the request profile of FIG. 2, at least “1,
1, 1, service name, visiting care "," 1, 1, 1, day of the week, Monday "," 1, 1, 1, time zone, 10:00 to 1
1:00 "," 1, 1, 1, infectious disease (HIV), positive "
Records are hit.

Next, the records having the same service ID are collected from the hit records. S (j) = {C ( _ij )} ( _j = 1 to _m , _ij = 1 to
n _j , n ₁ + n ₂ +... + n _m = k). Here, the service ID of each record which is an element of each S (j) is the same. In the case of the above example, since the service IDs are all "1", they are put together. Then, the tag other than the community ID and the request source reference is extracted from the tag described in the request profile which is the service request message, and the corresponding value is extracted. Similarly, personal information search processing 107
The tag name is extracted from the personal information obtained by and the corresponding value is extracted. Summarizing the above, <Tag (i), Va
lue (i)> (i = 1 to p).

In the case of the request profile shown in FIG. 2, at least "service name", "day of the week", and "time zone" are extracted as tags. The values correspond to visiting care, Monday, and 10:00 to 11:00. Therefore, <service name, visiting care>, <day of the week, Monday>, <time zone, 10: 00-1
1:00>. Similarly, for personal information, patient name:
Taro Yamada, Date of Birth: November 03, 1940, Infectious Disease (HIV):
Positive, ... was hit, so <patient name, Taro Yamada>, <birth date, 11/31/1940>, <infection (HIV), positive>.

Next, <Tag (i), Value (i)> (i = 1 to p)
Is present in the tag name and value of each record that is an element of each S (j). Then, <Tag (i), Value
(i) Select S (j) that satisfies all of (i = 1 to p) and includes a record.

The above, <service name, visiting care>, <day of the week,
Monday>, <time zone, 10: 00-11: 00>, <patient name, Taro Yamada
>, <Birth date, 11/03/1940>, <Infectious disease (HIV), positive
About> ｛“1,1,1, service name, nursing care”, “1,1,1, day, day, Monday”, “1,1,1,
Time zone, 10: 00-11: 00 "," 1, 1, 1, infectious disease (HI
V), Positive "｝
There is no infectious disease (HIV), but for the other tags, there is one record that matches both the tag name and the value. Therefore, ｛“1, 1, 1, service name, visiting care”, “1, 1, 1, day of the week, Monday”, “1, 1, 1,.
Time zone, 10: 00-11: 00 "," 1, 1, 1, infectious disease (HI
V), positive "} is the record to be selected.

Step 802: If no S (j) is hit in step 801, the matching process 10
8 and the next service offer transmission processing 109 is not executed. S that hits in step 801
If (j) exists, the process proceeds to step 803.

Step 803: The service ID of the record included in each S (j) hit in step 801 is passed to the service offer transmission process 109. the above,
｛“1, 1, 1, service name, home care”, “1, 1,
1, 1, day, Monday "," 1, 1, 1, time zone, 10: 00-1
1:00 "," 1, 1, 1, infectious disease (HIV), positive "{}, the service ID 1 is passed to the service offer transmission process 109.

Next, the service offer transmission processing 109 will be described. In the service offer transmission process 109, a service offer is searched from the service offer 115 based on each service ID passed from the matching process. For example, in the example of the above s, since 1 is passed as the service ID from the service offer transmission processing 109, in the case of the service offer of FIG.
0, 0000: 9, ... ".

Each hit service offer is transmitted to the service offer receiving process 105. The service offer receiving process 105 of the service requester system 101 includes:
It is specified by the request source reference of the service request message.

As described above, the service reception processing 106
Passes the received service request message to the personal information search processing 107 and the privacy protection processing 112. Hereinafter, the flow after the privacy protection processing 112 will be described. First, the privacy protection processing 112 will be described with reference to FIG.

Step 901: service reception processing 106
Retrieves the patient ID from the service request message passed by This process is the same as step 701 of the personal information search process 107.

Step 902: Retrieve personal information from the patient DB based on the patient ID. This processing is the same as step 702 of the personal information search processing 107. Since the patient ID is “1” in the request profile of FIG. 2, at least the patient ID: 1, the patient name: Taro Yamada, the date of birth: November 03, 1940, the infectious disease (HI
V): Positive, ... hits.

Step 903: A privacy protection policy is searched from the privacy protection policy 116 based on the community ID described in the request profile which is a service request message. It is assumed that the hit record string is P (i) (i = 1 to k). Community ID is
In the request profile of FIG. 2, the tag "<"
Community ID> ”.

For example, since the community ID is “1” in the request profile of FIG. 2, at least “1, patient ID, OK” is set in the privacy protection policy of FIG.
"1, patient name, unacceptable", "1, birth date, acceptable" and "1, infectious disease (HIV), acceptable" are hit.

Step 904: For the privacy protection processing policy P (i) (i = 1 to k) hit in step 903, the privacy attribute of the tag name included in each P (i) is checked. In the above example, “1, patient ID, OK”
Since "1, patient name, unacceptable", "1, birth date, acceptable" and "1, infectious disease (HIV), unacceptable", at least the tag name, patient ID, patient name, birth date, infectious disease ( HIV)
Are checked one after another.

Step 905: If the privacy attribute of the tag checked in step 904 is acceptable, the flow jumps to step 908. If not, go to the next step 906.

Step 906: For the personal information hit in step 901, in step 905, delete the tag name that cannot be used and the corresponding value.

Step 907: Proceed to the next tag.

Step 908: If there is no tag to be checked, proceed to the next step 909. If there is a tag to be checked, the process returns to step 904.

Step 909: The service request message and the personal information processed in steps 904 to 908 are passed to the personal information combining process 111.

The flow from step 904 to step 908 will be described with a specific example. In the above example, the privacy protection processing policy is “1, patient ID, OK”, “1, patient name, NO”, “1, date of birth, OK”, “1, infectious disease (HI
V), impossibility ", the patient ID, patient name, date of birth, and privacy attributes for infectious disease (HIV) are checked one after another at least as tag names.

In step 901, patient ID: 1, patient name: Taro Yamada, date of birth: November 03, 1940, infectious disease (HI
V): Positive, ... is hit, patient name: Taro Yamada, then infectious disease (HIV): positive is deleted. Eventually, patient ID: 1, date of birth: November 03, 1940, ... remain.

Next, the personal information combining process 111 will be described. In this processing, the service request message and the personal information processed in the privacy protection processing 112 are combined into the format specified in FIG. Between the tag 1001 <service request> and the end </ service request>, a tag 1002 <personal information> indicating the end </ personal information> is provided as a personal information section. </ Request profile> indicating the end from tag 1003 <request profile>
Is provided. The message generated in this process is passed to the service request distribution process 110. Then, in the service request distribution process 110, the message processed in the personal information combining process 111 is transmitted to a predetermined service request reception process 117 of the business server 103. In the present embodiment, the message is delivered only to the provider server 103, but an operation of delivering the message to a plurality of provider servers is also conceivable.

The service request receiving process 117 passes the received message to the personal information searching process 118. The personal information search processing 118 is almost the same processing as the personal information search processing 107 of the mediation server 102, but will be described again here. First, the patient ID is extracted from the received message. The patient ID is described in the area of the tag “<Patient ID>” indicated by 1004 in the service request message of FIG. Based on this patient ID, personal information is retrieved from the patient DB 121. Since the patient ID is "1" in the service request message of FIG. 10, at least the patient name: Taro Yamada, date of birth: 1940/1 in the patient DB of FIG.
1/03, infectious disease (HIV): positive, number of uses: 10 ... hit. Of course, if the personal information of the patient ID is not registered in the patient DB, no record is hit. Here, the patient DB of the company server 103 has the data format of FIG. 11, and an attribute of “number of uses” in a column 1105 is added to the patient DB 113 of the mediation server 102.

The searched personal information is passed to matching processing 119 together with the received message. The matching process 119 is also performed by the matching process 108 of the mediation server 102.
The difference from the service attribute DB 122 is that the process first uses not only the personal information retrieved from the patient DB 121 but also the personal information of the received message. In the case of the above example, the personal information of the received message is patient ID: 1, date of birth: November 03, 1940, ..., and the personal information retrieved from the patient DB 121 is patient name: Taro Yamada. ,Birthday:
03/03/1940, Infectious disease (HIV): positive, number of uses: 10
... Therefore, as personal information, patient name: Taro Yamada, date of birth: November 03, 1940, infectious disease (HIV): positive, number of uses: 10...

In the above example, as a result of the matching processing 119, at least {1, 1, 1, service name, home visit, "1, 1, 1, day of the week, Monday", "1, 1, 1,.
Time zone, 10: 00-11: 00 "," 1, 1, 1, infectious disease (HI
V), positive "," 1, 1, 1, number of uses, 5 (>) "｝
Records are hit. This is a service whose service ID is 1. "1, 1, 1, number of uses, 5 (>)"
Indicates that the number of uses of personal information is 5 or more. Match that the patient uses the service 10 times.

In the message from the mediation server, the privacy protection processing 112 causes the patient name and infectious disease (HI
V) has been deleted. However, in this embodiment, the patient has already used the service ten times. For this reason,
The nursing care service operator that operates the operator server 103
Personal information subject to privacy protection was independently collected. Therefore, in this case, it is possible to perform matching processing using personal information to be protected.

The service ID of the service hit in the matching process 119 is the service offer transmission process 120
Cross over. The service offer transmission processing 120 is the same as the service offer transmission processing 109. In the service offer transmission process 120, the service offer 11 based on each service ID passed from the matching process 108
5 to search for a service offer. For example, in the above example, the service I
Since 1 is passed as D, "1, 60000, 0000: 9, ..." is hit in the case of the service offer in FIG.

Each hit service offer is transmitted to the service offer receiving process 105. The service offer receiving process 105 of the service requester system 101 includes:
It is specified by the request source reference of the service request message.

This is the end of the description of the flow in this embodiment with reference to FIG.

In the above embodiment, the mediation server 102
, The information on the patient name and the infectious disease (HIV) was deleted. However, since the patient had used the service in the past, the nursing care service operator operating the operator server 103 independently collected privacy-protected personal information.
The matching process based on the patient name and infectious disease (HIV) deleted in the privacy protection process 112 was performed. However, when the patient has not received the service of the nursing care service provider in the past, personal information cannot be captured, which is normal. In this case, there is no hit record in the personal information search processing 118 in the business server 103. Therefore, the business server 103 performs the matching process only with the personal information included in the message transmitted in the service request distribution process 110 of the mediation server 102. However, privacy protection processing 11
Since the matching process for the patient name and the infectious disease (HIV) deleted in step 2 is performed by the mediation server 102, there is no problem. In other words, for services that handle tag names of personal information that are not possible under the privacy policy,
The service provider who wants to perform the matching process registers the service attribute and the service offer in the mediation server.

Further, as a result of the matching processing in the mediation server 102, at least “1,65,000, 0000: 9,.
Was returned. On the other hand, as a result of the matching process of the business server 103, "1, 60000, 0000: 9, ..." was returned. This depends on how many times the patient has used the service
This means that service prices are discounted and provided for patients who use the service multiple times.

Next, a process of registering service attributes and services from the service server 103 to the service attribute DB 114 and the service offer 115 in the mediation server 102 will be described.

First, when registering the service attribute and the service, the user profile DB1 is stored in the mediation server.
412 and a profile DB 1413 are provided. here,
The privacy protection policy 1414, service attribute DB 1415 and service offer 1416 in FIG.
These are the same as the privacy protection policy 116, service attribute DB 114, and service offer 115 of FIG. FIG. 16 shows a data format of the user profile DB 1412.
02 is a user name, and a password is set in a column 1603. FIG. 17 shows the data format of the profile DB 1413. A column 1701 is a community ID, and a column 1
In 702, a tag name is set. That is, a set of tag names is defined for each community unit.

Hereinafter, the service attribute and service registration processing will be described with reference to FIG.

First, the user of the business server performs a log-in process to the mediation server. User is User I
When D and the password are input, the login processing 1401 transmits the user ID and the password to the authentication processing 1402 of the mediation server. In the authentication process 1402, it is checked whether the received user ID and password exist in the user profile DB 1412. If the received user ID and password do not exist in the user profile DB 1412, the authentication processing has failed, and the process does not proceed to the subsequent profile search processing 1403. For example, “00001” as the user ID and “ABC1101” as the password
Is entered, the user profile D in FIG.
B1412 is a record to which the user name “Jiro Tanaka” is applicable and the authentication is successful.
Proceed to 403.

In the profile search processing 1403, a tag set for the community ID input by the user is searched from the profile DB 1413. For example, when “1” is input as the community ID, FIG.
In the case of the profile DB 7, at least “service name”, “day of the week”, “time zone”, “availability”, “infection (HI
V) ".

Next, in a privacy protection policy search process 1404, the privacy protection policy for the community ID input by the user in the profile search process 1403 is searched from the privacy protection policy 1414. This processing is the same as step 903 of the privacy protection processing 112. For example, Community I
When D is “1”, the privacy protection policy of FIG. 4 indicates that at least “1, patient ID, acceptable”, “1, patient name, invalid”, “1, date of birth, acceptable”, “1, infectious disease” (HI
V), OK ".

Here, in the service editing processing 1405,
Construct the message specified in FIG. The message includes a service profile section between the tag 1501 <service> and </ service> indicating the end, as a service profile section, and a </ service profile> indicating the end from the tag 1502 <service profile> as a service offer section. , </ Service offer> indicating the end from the tag 1503 <service offer>. Here, the section of the service profile is information registered in the service attribute DB. On the other hand, in the service offer section, the tag constituting the service profile section is “provider ID”.
In addition to the “community ID”, a tag set obtained in the profile search processing 1403 is used. Therefore, at least "provider ID""community I
D "" Service name "" Day of the week "" Time zone "" Availability "
"Infectious disease (HIV)" is included. Here, the service attribute to be registered in the mediation server handles the tag name of the personal information that is not allowed in the privacy protection policy. Therefore, a tag name whose privacy attribute is not allowed is handled in the privacy protection policy searched in the privacy protection policy search processing 1404. In the above example, “patient name” and “infection (HIV)” correspond to each other. In FIG. 15, “infection (HIV)” is set.

The service offer section is a service content for the service attribute defined in the service profile section. In FIG. 15, a price and a reference pointer are defined.

Next, the message edited by the service editing processing 1405 is sent to the service transmission processing 1406.

The service transmission processing 1406 transmits the passed message to the service registration processing 1407 of the mediation server. The service registration process 1407 passes the received message to the service attribute registration process 1408. In the service attribute registration process 1408, the service attribute section of the message in FIG. 15, that is, the information of the area between <service profile> and </ service profile> is registered in the service attribute DB 1415. The data format of the service attribute DB 1415 is shown in FIG.
For the community ID of 01, the value between <community ID> and </ community ID> in FIG. 15 is set, and for the provider ID of column 502, the value between <provider ID> and </ provider ID> in FIG. The value is set. The service ID in the column 503 is a serial number.
The service attribute registration processing 1408 sets a number obtained by adding one to the largest number of the service ID recorded in B. In the column 505, which is the tag name and its value in the column 504, a tag excluding the community ID and the provider ID in the service profile section and its value are set. For example, in the case of the message of FIG. 15, at least the tags of “service name”, “day of the week”, “time zone”, and “infection (HIV)”
Monday, 10: 00-11: 00, positive is the service attribute DB 141
Set to 5.

Here, the service ID assigned by the service attribute registration process 1408 is registered in the service offer registration process 1409 along with the message.

Subsequently, service offer registration processing 140
9, the information of the service offer section of the message of FIG.
Register at 16. The data format of the service offer 1416 is shown in FIG. 6, but the service ID passed from the service attribute registration processing 1408 is set in the service ID in the column 601. The price in column 602 includes <price> and <//
The value between <price> and the value between <reference pointer> and <reference pointer> are set for the company reference in column 603. For example, in the case of the message shown in FIG.
00: 9 is set in 00 and the company reference.

In the result return process 1410, a service attribute registration process 1408 and a service offer registration process 1409
Is successful, the result receiving process 14 of the business server
Then, "normal end" is transmitted to the client 11. On the other hand, service attribute registration processing 1408 and service offer registration processing 14
If any one of the steps 09 fails, an “error” is transmitted.

Next, the service attribute and service registration processing in the mediation server will be described with reference to FIG. The login processing 1801 is the same as the login processing 1401 in FIG. The authentication processing 1802 is the same as the login processing 1402 in FIG. Profile search processing 1803
Is the same as the profile search processing 1403 in FIG. The service editing process 1804 is the same as the service editing process 1405 in FIG. Service attribute registration processing 1
805 is the same as the service attribute registration processing 1408 in FIG. The service offer registration processing 1806 corresponds to FIG.
This is the same as the service offer registration processing 1409 of FIG.

The user profile DB 1807 and the user profile DB 1412 in FIG. 14 are the same. The profile DB 1808 and the profile DB 1413 in FIG. 14 are the same. The service attribute DB 1809 is the same as the service attribute DB 122 of FIG. The service offer 1810 is the same as the service offer 123 in FIG.

[0070]

According to the present invention, since the mediation server edits information which is not desired to be made to be confidential, privacy can be protected.

[Brief description of the drawings]

FIG. 1 is a system configuration diagram according to an embodiment of the present invention.

FIG. 2 is a view for explaining a data structure in the embodiment of the present invention.

FIG. 3 is a diagram illustrating a DB according to an embodiment of the present invention.

FIG. 4 is a view for explaining a DB in the embodiment of the present invention.

FIG. 5 is a diagram illustrating a DB according to the embodiment of the present invention.

FIG. 6 is a diagram illustrating a DB according to the embodiment of the present invention.

FIG. 7 is a view for explaining a processing flow in the embodiment of the present invention.

FIG. 8 is a view for explaining a processing flow in the embodiment of the present invention. .

FIG. 9 is a view for explaining a processing flow in the embodiment of the present invention. .

FIG. 10 is a view for explaining a data structure in the embodiment of the present invention.

FIG. 11 is a view for explaining a DB in the embodiment of the present invention.

FIG. 12 is a view for explaining a DB according to the embodiment of the present invention.

FIG. 13 is a view for explaining a DB according to the embodiment of the present invention.

FIG. 14 is a system configuration diagram in the embodiment of the present invention.

FIG. 15 is a view for explaining a data structure in the embodiment of the present invention.

FIG. 16 is a view for explaining a DB in the embodiment of the present invention.

FIG. 17 is a view for explaining a DB in the embodiment of the present invention.

FIG. 18 is a system configuration diagram in the embodiment of the present invention.

[Explanation of symbols]

101: service request system, 102: mediation server,
103: business server, 104: service request processing, 1
05: service offer reception processing, 106: service request reception processing, 107: personal information search processing, 108: matching processing, 109: service offer transmission processing, 11
0: service request distribution processing, 111: personal information search processing, 112: privacy protection processing, 113: patient D
B, 114: service attribute DB, 115: service offer, 116: privacy protection policy, 117: service request reception processing, 118: personal information search processing, 11
9: matching process, 120: service content transmission process,
121: patient DB, 122: service attribute DB, 12
3: Service offer

──────────────────────────────────────────────────の Continued on the front page (51) Int.Cl. ⁷ Identification symbol FI Theme coat ゛ (Reference) G06F 17/30 170 G06F 17/30 170Z 340 340A (72) Inventor Koichi Sano 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture Address F-term in Hitachi, Ltd. System Development Laboratory (Reference) 5B049 AA06 BB41 CC01 FF01 GG00 5B075 KK54 ND20 PQ02 PR03 QP01 UU08 UU26

Claims (19)

[Claims] 1. An information providing apparatus connected via a network to an information search apparatus for performing input for searching for information for providing a service by a service provider, wherein the information search apparatus receives the information from the information search apparatus via the network. Means for receiving an information search request that is transmitted and includes service specifying information for specifying a service to be provided and service beneficiary information for specifying a service beneficiary to receive the service; and the service beneficiary according to the information search request. Means for retrieving information comprising a plurality of items relating to the service relating to the service beneficiary specified by the information; means for deciding an item which can be provided among a plurality of items constituting the retrieved information; And transmitting information on the determined item among the retrieved information via An information providing device comprising: 2. The information providing apparatus according to claim 1, further comprising a table indicating whether the information can be provided for each item of the information, wherein the determining unit uses the table to determine each item of the information. An information providing apparatus, which determines whether an item can be provided, and determines to provide the item determined to be available. 3. The information providing apparatus according to claim 2, wherein the table indicates whether each of the items can be provided according to a type of service to be provided, and the determining unit includes the service specifying information and the service specifying information. An information providing apparatus, wherein an item to be provided is determined based on the table. 4. The information providing apparatus according to claim 2, wherein the table further indicates whether each of the items can be provided according to a service provider, and the determination unit includes the service provider information. And an information providing apparatus for performing information to be provided based on the table. 5. The information providing apparatus according to claim 4, wherein when the table indicates whether each of the items can be provided according to a service provider according to a service provider, the determining unit includes: An information providing apparatus, characterized in that both the service provider information and the service specifying information determine items that can be provided in the table as available to the information search apparatus. 6. The information providing apparatus according to claim 1, wherein the transmitting unit deletes an item determined to be unavailable and transmits the searched information via the network. An information providing device, comprising: 7. The information providing apparatus according to claim 1, wherein the information storage device stores the information for each of the service beneficiaries, and the information processing device stores the information for each of the service beneficiaries. An information providing apparatus, further comprising at least one of means for connecting via the network. 8. The information providing device according to claim 1, wherein the information providing device is connected to the information processing device via the network, and the transmitting unit determines the information to be transmitted. Transmitting information about the selected item to the information processing apparatus. 9. An information providing method in an information providing apparatus connected via a network with an information searching apparatus for inputting a service provider for searching for information for providing a service, wherein the service provider provides the information via the network An information search request transmitted from the information search device and including service specifying information for specifying a service to be provided and service beneficiary information for specifying a service beneficiary to receive the service is received, and the service is provided in accordance with the information search request. Searching for information comprising a plurality of items relating to the service relating to the service beneficiary specified by the beneficiary information; determining an available item from among a plurality of items constituting the searched information; and Transmitting the item determined to be provided among the searched information. Characteristic information provision method. 10. The information providing method according to claim 9, wherein the information providing apparatus further includes a table indicating whether each item of the information can be provided, and the searched information is used by using the table. An information providing method for determining whether each of the items can be provided. 11. The information providing method according to claim 10, wherein the table indicates whether each of the items can be provided in accordance with a type of service to be provided, and based on the service specifying information and the table,
Determining whether each item of the retrieved information can be provided; 12. The information providing method according to claim 10, wherein the table further indicates whether each of the items can be provided according to a service provider, and is based on the service provider information and the table. Determining whether each item of the retrieved information can be provided. 13. The information providing method according to claim 12, wherein the table indicates whether each of the items can be provided according to the type of service according to the service provider. For both of the service identification information, an item indicated as available in the table,
An information providing method characterized by determining that the information can be provided. 14. The information providing method according to claim 9, further comprising transmitting, via the network, information obtained by deleting an item determined to be unavailable from the searched information. Characteristic information provision method. 15. The information providing method according to claim 9, wherein the searching is performed by a storage device storing the information of the information providing device for each of the service beneficiaries and the information providing device. An information providing method, wherein the information is retrieved from at least one of an information processing device that is connected to the connection unit that is provided via the network and that stores the information for each of the service beneficiaries. 16. The information providing method according to claim 9, wherein the information providing device is connected to the information processing device via the network, and the information on the determined item is stored in the information providing device. And transmitting the information to an information processing apparatus. 17. An information providing device connected via a network to an information search device requesting information search, a means for receiving an information search request transmitted from the information search device via the network, Means for searching for information corresponding to the information search request; means for making a change to the searched information based on the information search request; and making the change to the information search device via the network. Means for transmitting selected information. 18. An information providing method according to claim 17, wherein said change means deletes at least a part of items constituting the searched information. 19. A service requester device requesting execution of a service, and a business device used by a business operator executing the service are connected via a network, from the service requester device to the business operator device. A service intermediation device that mediates the service request of the above, wherein the service request information transmitted from the service requester device via the network and specifies service contents to be executed and a service beneficiary that specifies a service beneficiary who receives the service Means for receiving a service request including user information, means for searching for information related to the service specified by the service specifying information and related to the service beneficiary specified by the service beneficiary information, and the searched information To select an item that can be presented to the business operator device from a plurality of items constituting And presenting information related to the selected item, contents of a service specified by the service specifying information, and a service beneficiary specified by the service beneficiary information to the business entity device via the network. A service mediation device, comprising: