Hash tag search system

Abstract

To flexibly control the hash tag of a tagged candidate.SOLUTION: A hash tag search system is sorted into one of multiple large groups, and has a recording management terminal operated in a business establishment sorted into one of multiple small groups included in a large group, and a recording management server connected to the recording management terminal. The recording management terminal transmits a search string that a searched hash tag should include, and a business establishment code showing a large group and a small group of an own business establishment that is a business establishment to be searched to the recording management server (step 72). A storage management server creates a search request including instructions for searching a large group tag that includes a search string and is common to a business establishment that belongs to the same large group as a large group into which the own business establishment is sorted, a small group tag common to a business establishment that belongs to the same small group as a small group into which an own business establishment is sorted, and a business establishment individual tag of an own business establishment (step 82).SELECTED DRAWING: Figure 16

Description

Technical Field

[0001] This invention relates to a hashtag search system.

Background Art

[0002] In social networking services (SNS), hashtags are used to categorize (group) posted articles so that specific posted articles can be easily retrieved from a large number of posted articles (see Patent Document 1 for telegram search using hashtags).

[0003] A hashtag generally consists of a hash symbol "#" followed by a keyword, and is tagged (assigned, associated) to a posted article (character data, image data, etc.) by the poster. By tagging a posted article with a hashtag, even if the posted article is image information rather than character information, it is possible to easily retrieve posted articles having a specific hashtag (keyword) from a large number of posted articles. For example, if a posted article is tagged with "#travel", by searching for the posted article using the hashtag "#travel" as a search tag, even if the posted article is image information that does not contain the character "travel", the posted article can be hit.

[0004] When tagging a posted article with a hashtag, a plurality of hashtags that have been used in the past are often listed as tagging candidates, and a hashtag to be tagged to the posted article is often selected from the displayed tagging candidates. This is because even if the hashtag (its keyword) is slightly different, it is treated as a different hashtag. For example, "#delicious" and "#so delicious" are treated as different hashtags. When "#delicious" is used as a search hashtag, posted articles tagged with "#delicious" will be hit in the search, but posted articles tagged with "#so delicious" but not with "#delicious" will not be hit.

[0005] To ensure that all the posted articles tagged with "#delicious" and those tagged with "#so delicious" are hit without omission, i.e., all the posted articles with the same topic are covered, the hash tags listed as tagging candidates should be unified to either "#delicious" or "#so delicious" (preventing either one from being displayed as a tagging candidate). However, for example, within a small group, it may be more convenient to categorize posted articles using hash tags of unique keywords.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] An object of the present invention is to enable flexible search (publication) control of hash tags that are candidates for tagging information used in a hierarchically structured business office.

[0008] The present invention provides a hash tag search system. The hash tag search system searches for hash tags (their candidates) suitable for tagging from among a plurality of pre-prepared hash tags. The hash tags hit by the search by the hash tag search system can be used to be listed as tagging candidates.

[0009] The hash tag search system according to the present invention is operated in a client device that is classified into any one of a plurality of major classifications and further classified into any one of a plurality of minor classifications included in the major classification, and a server device that is network-connected to the client device. The system searches for hash tags of tagging candidates from a plurality of hash tags stored in a database device according to a search request created by the server device. The client device includes means for transmitting to the server device a search string that should be included in the hash tag to be hit by the search, as well as the major classification and minor classification of the client's own business office where the search is to be performed. The server device includes a search request creation means for creating the search request given to the database device. Each of the plurality of hash tags to be searched stored in the database device is leveled into any one of a major classification tag commonly used by business offices belonging to a specific major classification, a minor classification tag commonly used by business offices belonging to a specific minor classification, and an office-specific tag used individually for each office. The search request created by the search request creation means of the server device includes the search string transmitted from the client device, and commands to search for a major classification tag commonly used by business offices belonging to the same specific major classification as the major classification in which the client's own business office is classified, a minor classification tag commonly used by business offices belonging to the same specific minor classification as the minor classification in which the client's own business office is classified, and the office-specific tag of the client's own business office.

[0010] The present invention is a hash tag search system targeting business offices with a two-stage structure of major classification and minor classification. That is, each business office (which may also be referred to as a "facility") is classified into any one of a plurality of major classifications. The major classification includes a plurality of minor classifications, and the business office is also classified into any one of the minor classifications.

[0011] "The "own office" typically refers to the office to which the staff member belongs who is attempting to tag any information with a hash tag using a client device. The office where the staff member is located (working), or the office where the client device operated by the staff member is installed, may be regarded as the own office. Of course, the own office may be specified regardless of the staff member's affiliation, workplace, or the installation location of the client device. In any case, when searching for the hash tag to be tagged, a single office (the office of the search subject) for which the search is to be conducted is specified, and this office is the "own office". The own office is identified in the server device by transmitting the major classification and minor classification of the own office from the client device to the server device. In addition to the data representing the major classification and minor classification, data for identifying the own office may be further transmitted from the client device to the server device. For example, when a staff member logs in to the system, the office to which the staff member belongs may be identified from the login code, and the identified office may be treated as the own office."

[0012] The hash tags to be searched are classified into one of a major classification tag commonly used by offices belonging to a specific major classification, a minor classification tag commonly used by offices belonging to a specific minor classification, and an office-specific tag used individually for each office. When storing the hash tag in the database device, it is set which of the three levels the hash tag is to be. Of course, a change in level may be accepted at any timing after the storage of the hash tag."

[0013] According to the present invention, a hash tag including a search string, which is an office-specific tag individually (uniquely) used in its own business office, and further, a subcategory tag commonly used by business offices belonging to the same specific subcategory in which the own business office is classified, and a major category tag commonly used by business offices belonging to the same specific major category in which the own business office is classified are hit. Not only the office-specific tag uniquely used for each business office, but also the common tags of the subcategory and major category in which the own business office is classified are hit. By the hash tags (major category tags) common to a plurality of business offices belonging to the major category and the hash tags (subcategory tags) common to a plurality of business offices belonging to the subcategory, the same hash tag is likely to be selected in a plurality of business offices within the major category and within the subcategory for the same topic. Since the hash tag (office-specific tag) uniquely used for each business office is also hit, a hash tag suitable for the topic specific to the business office can be selected.

[0014] In one embodiment, the above business office is a business office that provides services for the elderly or the disabled, the above major category is a corporate classification that classifies the above business office by the operating corporation, and the above subcategory is a service type classification that classifies the above business office by the service type provided by the above business office. A hash tag commonly used throughout the entire corporation to which the business office (own business office) performing the search belongs, and a hash tag commonly used throughout a plurality of business offices that provide the same service type as the service type provided by the business office (own business office) performing the search can be hit as tagging candidates together with the office-specific tag.

[0015] Preferably, at least some of the plurality of the above-mentioned business offices are classified into any one of one or more groups that group the business offices from a perspective different from the above classification, and at least a part of the above-mentioned business office individual tags among the plurality of hash tags to be searched stored in the above-mentioned database device are group common tags commonly used within the group, and the above search request further includes an instruction to search for the above group common tags commonly used within the same group as the above own business office. The business offices are grouped from a perspective different from the hierarchical structure, and it is a mode of using common tags for each group. The group common tag is specified, for example, by associating a flag indicating that it is a group common tag with the business office individual tag. For grouping, for example, the geographical conditions of the business office (such as whether it is located in eastern Japan or western Japan) can be used. In this case, when a hash tag of a tagging candidate is searched in a business office located in the eastern Japan group, other business office individual tags of business offices located in the eastern Japan group, for which a flag indicating that it is a group common tag is set, are further hit.

[0016] In one embodiment, the above server device is provided with means for eliminating the duplication when there are a plurality of the same hash tags among the hash tags of the tagging candidates hit by the search in the above database device. The hash tags to be searched are classified into any one of a general classification tag commonly used by business offices belonging to a specific general classification, a sub-classification tag commonly used by business offices belonging to a specific sub-classification, and a business office individual tag individually used for each business office, but the same hash tag may be included at different levels. By eliminating the duplication in this case, it is possible to prevent the search result from including two or more identical hash tags.

[0017] Preferably, the server device includes a tagging candidate hash tag transmitting means for transmitting to the client device the hash tags of the tagging candidates hit by the search in the database device, and the client device includes a display means for selectively displaying the received tagging candidate hash tags. The tagging candidate hash tags that are selectively displayed are controlled according to the levels set for each of the above-described hash tags.

[0018] The present invention provides not only a hash tag search system for business establishments having a two-stage structure of major classification and minor classification, but also a hash tag search system for business establishments having a three-stage structure of major classification, middle classification, and minor classification.

[0019] The hash tag search system according to the second invention is operated in a business office classified into any one of a plurality of major classifications, further classified into any one of a plurality of medium classifications included in the major classification, and further classified into any one of a plurality of minor classifications included in the medium classification. The system includes a client device and a server device network-connected to the client device. According to a search request created by the server device, it searches for a hash tag of a tagging candidate from a plurality of hash tags stored in a database device. The client device includes means for transmitting to the server device a search string that should include a hash tag to be hit by the search, as well as the major classification, medium classification, and minor classification of the client's own business office where the search is to be performed. The server device includes a search request creation means for creating the search request given to the database device. Each of the plurality of hash tags to be searched stored in the database device is leveled into any one of a major classification tag commonly used by business offices belonging to a specific major classification, a medium classification tag commonly used by business offices belonging to a specific medium classification, a minor classification tag commonly used by business offices belonging to a specific minor classification, and a business office individual tag individually used for each business office. The search request created by the search request creation means of the server device includes the search string transmitted from the client device, and a major classification tag commonly used by business offices belonging to the same specific major classification as the major classification in which the client's own business office performing the search is classified, a medium classification tag commonly used by business offices belonging to the same specific medium classification as the medium classification in which the client's own business office is classified, a minor classification tag commonly used by business offices belonging to the same specific minor classification as the minor classification in which the client's own business office is classified, and an instruction to search for the business office individual tag of the client's own business office.

Brief Description of the Drawings

[0020]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Example

[0021] Figure 1 is a block diagram showing the hardware configuration of a care content input system.

[0022] The care content input system includes a record management server 1, a database server 2, and a record management terminal 3. The database server 2 is connected to databases (office master 11, staff master 12, hash tag master 13, user master 21, record / form master 22, record table 23) storing various data required for the operation of the care content input system. Other databases can also be connected to the database server 2 as needed.

[0023] The record management terminal 3 is used for inputting various care (support) contents provided by the staff (employees, etc.) of a care facility (nursing facility) (hereinafter simply referred to as "facility") to the users (typically the elderly or disabled) of the facility, and recording (storing) the input care contents (care records). The care records are used for considerations of care plans for the users of the facility, utilization for high-quality care services and care management, improvement of the qualifications of the facility staff, information sharing, etc. The care content input system is commonly used in multiple facilities and is operated by the staff of each of the multiple facilities. Therefore, a plurality of record management terminals 3 operated by a plurality of staff are used for inputting care contents (care records).

[0024] As described above, there are multiple facilities, and generally, a plurality of users (the elderly or disabled) belong to each of them. Care (support) for each of the multiple users in the multiple facilities is carried out daily, and records are taken daily. The care (support) contents to be recorded include a number of items (care items) such as the vital data of the users (body temperature, blood pressure, percutaneous arterial oxygen saturation, etc.), diet content (amount of food intake), oral care, height, weight, exercise, visitors, recreation content, etc. The care (support) contents implemented for each user or measured for each user are input and recorded (stored) in the care content input system. The care (support) contents recorded in the care content input system include not only the contents related to the daily care of the users but also the personal records of the users themselves (such as the above-mentioned body temperature, height, weight, etc.), reported matters, etc.

[0025] The record management server 1 is connected to the record management terminal 3 via a network (Internet, etc.). In the record management server 1, the care (support) contents that have been and should be provided for each user of the facility are managed (record management, schedule management).

[0026] FIG. 2 is a block diagram showing the hardware configuration of the record management terminal 3. FIG. 3 shows a record form (health management record form F1) for inputting (recording) care (support) details. FIG. 4 shows a form (accident report form F2) for inputting (recording) accident reports. A plurality of types of record forms and forms such as those shown in FIGS. 3 and 4 are prepared in advance, and care (support) details and the like are input into input items defined in advance for each of the record forms and forms.

[0027] Referring to FIG. 2, the record management terminal 3 includes a CPU 30B that comprehensively controls the overall operation of the record management terminal 3, a RAM 30C that temporarily stores data and programs, a storage (SSD, HDD, etc.) 30D that stores an operating system, various application programs, etc., an input device (keyboard, etc.) 30E for inputting characters, numbers, etc., a communication device 30F for transmitting and receiving data through a network, a microphone 30G for inputting sound (voice), a speaker 30H for outputting sound, a camera 30I for imaging a subject image, and a display device 30J for displaying record forms / forms, etc. These are connected to a data bus 30A. A portable computer device capable of network connection can be used as the record management terminal 3.

[0028] The record management server 1 and the database server 2 are also computers equipped with a CPU, RAM, storage, communication device, etc. However, unlike the record management terminal 3, since these servers 1 and 2 are not computer devices directly operated by the office staff, input devices such as keyboards, display devices, microphones, speakers, and cameras are not necessarily required.

[0029] Hash tags can be attached (assigned, associated) to various data input and recorded using a care content input system. Figure 3 schematically shows a state where a hash tag 65 with a keyword (hash tag name) of "slightly elevated normal body temperature" is attached to a health management record form F1 created on a specific day for a specific user. Figure 4 schematically shows a state where a hash tag 66 with a keyword (hash tag name) of "dementia care" is attached to an accident report form F2 reporting the details of an accident that occurred at a certain workplace.

[0030] By attaching hash tags to each (not necessarily all) of the care (support) contents input and recorded daily for each of many users at many workplaces, it becomes easier to search for record forms and form sheets with common keywords (hash tag names) at a later date. For example, when searching for a health management record form (which may be limited to that of a specific user) with a hash tag of "#slightly elevated normal body temperature", the health management record forms with the hash tag of "#slightly elevated normal body temperature" among a large number of health management record forms will be hit. Since the pulse is recorded in the health management record form (Figure 3), for example, the correlation between the slightly elevated body temperature and the pulse can be analyzed at a later date. If a hash tag of "#matters to be shared with Dr. ○○" is attached to the record forms and form sheets in which the information to be conveyed to the user's attending physician is recorded, the record forms and form sheets with the hash tag of "#matters to be shared with Dr. ○○" can be searched from among a large number of record forms and form sheets, and the record forms and form sheets hit by the search can be collected and handed over to Dr. ○○. By using hash tags in this way, in addition to the types of record forms, types of form sheets, dates, users, etc., the record forms and form sheets can be grouped from a completely different perspective, and it is possible to easily find forms with common features (topics) from among a large number of record forms and form sheets.

[0031] Figure 5 shows a recording editor window displayed on the display screen of the display device 30J of the recording management terminal 3, which is used when inputting care details into a recording form using the recording management terminal 3. The recording editor window 61 has a form display column 61A in its left range, where various recording forms are displayed, and data can be input into the input items prepared in advance in the displayed recording forms. Figure 5 shows the recording editor window 61 in which the above-mentioned health management recording form F1 (Figure 3) is displayed in the form display column 61A.

[0032] In the right range of the recording editor window 61, a recording form selection column 61B, a hashtag display column 61C, a hashtag candidate search column 61D, and a hashtag candidate display column 61E are arranged and displayed vertically.

[0033] In the recording form selection column 61B, the names (recording form names) of a plurality of types of recording forms prepared in advance are displayed. When a specific recording form name is selected (clicked) in the recording form selection column 61B, the recording form having that recording form name is displayed in the left form display column 61A.

[0034] The hashtag display column 61C shows the hashtags tagged to the recording form displayed in the form display column 61A. Figure 5 shows a state where two hashtags, "#Normal" and "#Dementia Care", are tagged to a specific recording form F1 displayed in the form display column 61A.

[0035] If the business office staff are completely entrusted with the hash tags (keywords, hash tag names) to be tagged on the record form F1, it may cause problems in form search using hash tags. For example, both the hash tag "#Matters to be Shared with Doctor ○○" and the hash tag "#Matters Shared with Doctor ○○" are considered to be tagged on record forms or document forms that record information to be conveyed to Doctor ○○. However, since the keywords (hash tag names) do not exactly match, they will be treated as different hash tags. This may cause search omissions during form search using hash tags. Therefore, the tagging of hash tags is performed by selecting one of the hash tag candidates that can be tagged in advance.

[0036] The taggable hash tag candidates are listed and displayed in the hash tag candidate display column 61E. To avoid listing a large number of hash tag candidates, a hash tag candidate search column 61D is provided, and only the hash tag candidates that contain the string entered in the hash tag candidate search column 61D are displayed in the hash tag candidate display column 61E.

[0037] As will be described later, the hash tag candidates listed and displayed in the hash tag candidate display column 61E also conform to the publicly available levels set in advance for each hash tag (keyword, hash tag name). In this embodiment, five levels (five types) of publicly available levels are set for each hash tag, and the publicly available levels can be used to control the hash tag candidates listed and displayed in the hash tag candidate display column 61E. The details of the publicly available levels set for each hash tag (keyword, hash tag name) and the details of the control process for the list display of the hash tag candidate display column 61E using the publicly available levels will be described later.

[0038] Figure 6 shows that one of the three (published) hash tags (# body temperature slightly above normal) displayed in the hash tag candidate display column 61E of the record editor window 61 shown in Figure 5 is selected, and the selected hash tag "# body temperature slightly above normal" is newly tagged to a specific record form F1 displayed in the form display column 61A. The health management record form F1 displayed in the form display column 61A will be hit in a form search using the hash tag "# body temperature slightly above normal" when it is tagged with the hash tag "# body temperature slightly above normal".

[0039] For the form (see Figure 4), similar to the record form, data can be input using an editor window (not shown) and hash tags can be tagged.

[0040] Figures 7 to 11 respectively show the contents of the databases connected to the database server 2, namely the user master 21, the record / form master 22, the record table 23, the office master 11, the staff master 12, and the hash tag master 13.

[0041] Referring to Figure 7, the user master 21 includes data such as a "corporation code" for identifying the corporation operating the office, an "office code" for identifying the office operated by the corporation specified by the corporation code, a "user code" for identifying the user who uses the office, the name, gender, date of birth, etc. of the user specified by the user code. The corporation code, office code, user code, name, gender, date of birth, etc. are associated with each other and stored in the user master 21. The office to which a specific user belongs can be grasped by the user master 21.

[0042] Figure 13 explains the "office code" included in the user master 21.

[0043] As described above, the "business office code" is a code for identifying business offices operated by a corporation, and a single business office is specified by the business office code. The business office code includes, in addition to the code unique to each business office, a code representing the "service classification" and "service type" of the business office specified by the unique code. Specifically, the business office code is composed of seven digits, with the first digit representing the service classification, the second and third digits representing the service type, and the fourth to seventh digits representing the unique code of the business office, respectively.

[0044] The "service classification" indicates whether the business office specified by the unique code of the business office is a business office providing "services for the elderly" or a business office providing "services for the disabled". "1" represents that the business office provides services for the elderly, and "2" represents that the business office provides services for the disabled.

[0045] The second and third digits representing the "service type" represent the types of services provided by the business office specified by the unique code of the business office. For example, "15" means that the business office specified by the unique code of the business office provides the service type of "day care nursing", and "51" means that the business office provides the service type of "nursing and welfare facility services", respectively.

[0046] As will be described later, the "business office code" is used for setting the public level of the above-mentioned hash tags.

[0047] Referring to FIG. 8, the record / form master 22 includes the above-described corporate code, a "form code" for identifying various record forms and document forms, a "form name" of the record form and the document form, "form data" representing the layout of the record form and the document form, and the like. When a specific form name is selected using the record form selection column 61B of the record editor window 61 (FIG. 5) displayed on the display screen of the record management terminal 3, the form code specified by the selected form name is given to the database server 2 through the network. The database server 2 reads out the form data corresponding to the form code from the record / form master 22, and the record management server 1 that has received this transmits the form data to the record management terminal 3. The selected specific record form is displayed in the form display column 61A of the record editor window 61 of the record management terminal 3.

[0048] Referring to FIG. 9, in addition to the above-described corporate code, office code, user code, and form code, the record table 23 includes a "recording date and time" representing the date and time when the record was made, a "form record content" representing the actual content of the record such as numerical values and characters entered in the form, a "hash tag" tagged to the record form and the document form, and the like. In the record table 23, care (support) records for each user, which are performed daily using the record management terminal 3, are stored, and hash tags tagged to the forms used for the records are also stored. In the search for a record form or a document form using a hash tag, this record table 23 is searched.

[0049] Figure 10 shows the business office master 11. The business office master 11 includes, in addition to the corporate code and the business office code, the "business office name" of the business office specified by the business office code, the "group name" representing the name of each group that groups a plurality of business offices, and the like. The group specified by the group name classifies a plurality of business offices belonging to one corporation into several groups. For example, a plurality of business offices belonging to a certain region are grouped into one group according to the region where the business office exists. The business office master 11 shown in Figure 10 shows that among the plurality of business offices belonging to the corporation specified by the corporate code "210151", two business offices, "Tokuyo Suruga" and "Tokuyo Atami", belong to the "Suruga Group", and among the plurality of business offices belonging to the corporation specified by the corporate code "334011", "Day Suruga" belongs to the "East Japan Group" and "Day Fukuoka" belongs to the "West Japan Group". This "group" is also used for setting the public level of the above-mentioned hash tags, and the details will be described later.

[0050] Referring to Figure 11, the staff master 12 includes a "staff code" for identifying the staff of the nursing facility, a "usage PWD" which is the password when the staff uses the nursing care content input system, the name of the staff, the corporate code of the corporation to which the business office where the staff works belongs, the business office code, and the like.

[0051] Figure 12 shows the hash tag master 13. The hash tag master 13 includes, in addition to the corporate code, a "public level code", a "group designation flag", and a "hash tag" (hash tag name). In the hash tag candidate display column 61E of the record editor window 61 (Figure 5), the hash tags narrowed down as described later are displayed from among the hash tags registered in the hash tag master 13.

[0052] The "public level code" and "group designation flag" included in the hash tag master 13 are used to control the public level of the hash tags to be displayed in the above-described hash tag candidate display column 61E. In this embodiment, each of the hash tags has one of five levels (five types) of public levels set for each hash tag, and is published (listed) according to the public level, that is, it is determined whether to be listed or not listed in the hash tag candidate display column 61E.

[0053] FIG. 14 schematically shows the five levels (five types) of public levels set in advance for each of the hash tags and the hierarchical structure of each office. FIG. 15 shows an example of the explanation of the five-level public level of the hash tags and the public level code.

[0054] Referring to FIG. 14, in the schematic diagram shown in FIG. 14, each office is represented by a rectangular figure. Here, assume that each of corporations A, B, and C is a corporation engaged in the nursing care business, and each operates a plurality of offices. In FIG. 14, for the sake of convenience, corporation A is shown in detail, and the details of corporations B and C are omitted.

[0055] Company A operates 12 offices. Among the 12 offices, 7 offices provide "elderly services" (service classification "1"), and the remaining 5 offices provide "services for the disabled" (service classification "2"). Among the 7 offices that provide "elderly services", 5 offices provide the service type "day care nursing" (service type "15"), and 2 offices provide the service type "nursing home services" (service type "51"). Among the 5 offices that provide "services for the disabled", 4 offices provide the service type "life care" (service type "22"), and 1 office provides the service type "short-term admission" (service type "24"). Also, each office belongs to either Group α or Group β, or does not belong to any group. In the rectangular figure representing the office, a white rectangle represents an office belonging to Group α, a black rectangle represents an office belonging to Group β, and a hatched rectangle represents an office that does not belong to any group. That is, each office is classified into one of the major classifications of "company classification", and is further classified into one of the multiple medium classifications of "service classification" included in the major classification of company classification, and is further classified into one of the multiple minor classifications of "service type classification" included in the medium classification of service classification.

[0056] Referring to FIG. 15, the hash tag has one of the following five public levels and is classified into five types.

[0057] (A) Company tag (major classification tag) It is a hash tag listed in the hash tag candidate display column 61E as a tagging candidate in all offices belonging to a certain company. Conversely, in offices belonging to different companies, it is not listed in the hash tag candidate display column 61E. The public level code of the company tag is set to a code with all 7 digits being "0" (for example, refer to the 14th hash tag "normal body temperature" from the top of the hash tag master 13 shown in FIG. 12).

[0058] (B) Classification common tag (medium classification tag) It is a hashtag listed in the hashtag candidate display column 61E as a tagging candidate at other business offices with the same service classification. Conversely, it is not listed in the hashtag candidate display column 61E at business offices with different service classifications. For the public level code of the classification common tag, a 7-digit code with the lower 6 digits of the business office code all set to "0" is set (for example, refer to the hashtag "Large food intake" in Fig. 12).

[0059] (C) Classification and type common tags (sub-classification tags) It is a hashtag listed in the hashtag candidate display column 61E as a tagging candidate at other business offices with the same service classification and service type. Conversely, it is not listed in the hashtag candidate display column 61E at business offices with the same service classification but different service types. For the public level code of the classification and type common tag, a 7-digit code with the lower 4 digits of the business office code set to "0" is set (for example, refer to the hashtag "Slightly elevated normal body temperature" in Fig. 12).

[0060] (D) Business office individual tags It is a hashtag individually listed in the hashtag candidate display column 61E as a tagging candidate for each business office. Conversely, it is not listed in the hashtag candidate display column 61E at other business offices. For the public level code of the business office individual tag, the above-mentioned business office code is set as it is (for example, refer to the hashtag "In a bad mood when waking up" in Fig. 12).

[0061] (E) Group common tags In the grouping according to a perspective different from the above-described service classification and service type (for example, geographical scope), it is the above-described individual office tag of other offices belonging to the same group, and the "group designation flag" in the hash tag master 13 (FIG. 12) is set to on, so that it is a hash tag listed in the hash tag candidate display column 61E as a tagging candidate. Conversely, in offices belonging to different groups, it is not listed in the hash tag candidate display column 61E, and even if it is an individual office tag of other offices belonging to the same group, a hash tag with the "group designation flag" set to off is not listed. In the hash tag master 13 shown in FIG. 12, in the public level code of the group common tag, the office code is set as it is, and the group designation flag is set to on (True). The off of the group designation flag is indicated by "False". In the hash tag master 13 shown in FIG. 12, "small meal amount" and "large meal amount" are group common tags.

[0062] Referring to FIG. 14, since the "individual office tag" is a hash tag listed (publicized) in a specific office, it is listed when tagging a record form or a form in a specific office, and is not listed in other offices belonging to the same corporation, for example. It is appropriate to use the "individual office tag" for keywords used only in a specific office.

[0063] Since the "classification and type common tag" is a hash tag listed in offices with the same service classification and the same service type, it is appropriate to use the "classification and type common tag" for keywords commonly used among offices engaged in the same service type.

[0064] Since the "classification common tag" is a hash tag listed in offices with the same service classification, it is appropriate to use the "classification common tag" for keywords commonly used in all offices providing elderly services or all offices providing disabled services, regardless of the service type.

[0065] Since the "corporate tag" is a hash tag listed at all offices belonging to the same corporation, it is appropriate to use the "corporate tag" for keywords commonly used across the entire corporation.

[0066] The "group common tag" is a hash tag that can be commonly used regardless of service classification or service type, for example, by region (if the group is defined by region). For example, the hash tag "#Matters to be Shared with Doctor ○○" is usually assumed to be for doctors who have a hospital or the like near the location of the office, rather than doctors who have a hospital or the like far from the location of the office (doctors who can rush to the office immediately if contacted), so it is convenient to use it as a group common tag.

[0067] FIG. 16 is a flowchart showing the respective processes of the recording management terminal 3, the recording management server 1, and the database server 2 in the hash tag disclosure process (list display process) using the disclosure levels set for each of the above-described hash tags. In the description of the flowchart of FIG. 16, the recording editor window 61 shown in FIG. 5 is appropriately referred to.

[0068] When attempting to tag a hash tag to a record form or form, the keyword or a part thereof (referred to as a hash tag search string) to be used for the hash tag to be tagged is input into the hash tag candidate search field 61D (step 71). Here, it is assumed that "normal body temperature" is input as the hash tag search string.

[0069] As will be described later, the hash tag search string input to the hash tag candidate search field 61D in step 71 is used for the search process of hash tag candidates from among a number of hash tags stored in the hash tag master 13 (FIG. 12). When a string with an extremely small number of characters (short string) or a string with an extremely large number of characters (long string) is input to the hash tag candidate search field 61D, a string of an appropriate length (for example, about 3 to 10 characters) may be obtained.

[0070] The input hash tag search string and the business office code are transmitted from the record management terminal 3 to the record management server 1 (step 72). The business office code to be transmitted is typically the business office code of the business office to which the staff member who operates the record management terminal 3 and inputs the care record belongs. Hereinafter, the business office specified by the business office code transmitted in step 72 is referred to as the "own business office". Since the business office code includes a service classification code and a service type code in addition to the individual business office code (FIG. 13), the record management server 1 can transmit the major classification (corporate classification), medium classification (service classification), and minor classification (service type) of the own business office according to the business office code.

[0071] When the login process using the staff code and the usage PWD is performed when starting the use of the care content input system, by referring to the staff master 12 (FIG. 11) in the record management server 1 during the login process, the business office code of the business office to which the logged-in staff belongs can be specified, and the business office code can be transmitted from the record management server 1 to the record management terminal 3 in advance at the time of login, and this can be used as the business office code transmitted in step 72 described above. Instead of the business office code, the staff code input during the login process may be transmitted. Also in this case, the business office code can be specified by referring to the staff master 12 (FIG. 11) in the record management server 1.

[0072] The record management server 1 that has received the hashtag search string and the office code sends the office code to the database server 2 and requests the office codes of other offices belonging to the same group as its own office specified by the above office code (step 81). The database server 2 accesses the office master 11 (Figure 10) and sends the office codes of the other offices to the record management server 1 (step 91). Referring to Figure 10, for example, if its own office is "Tokuyo Suruga" with the office code "150001", the office code "150002" of "Tokuyo Atami", which is another office belonging to the same group, is sent from the database server 2 to the record management server 1.

[0073] The record management server 1 creates the following search formula and sends it to the database server 2 (step 82).

[0074] "Hashtag that matches the received hashtag search string at the beginning" AND (("Corporate tag" OR "Classification common tag of the same service classification as its own office" OR "Classification and type common tag of the same service classification and service type as its own office" OR "Office individual tag of its own office" OR "Office individual tag of other offices belonging to the same group as its own office with the group designation flag being 'True'"))

[0075] "Other offices belonging to the same group as its own office" are the offices specified by the office codes obtained through the processes of steps 81 and 91.

[0076] The database server 2 that has received the search formula accesses the hashtag master 13, searches for hashtags that match the search formula, and sends the hashtags found by the search to the record management server 1 (step 92).

[0077] In the hash tag master 13, there may be cases where exactly the same hash tags are registered with different public level codes (refer to the 14th and 18th "normal body temperature" from the top in Fig. 12). For this reason, the record management server 1 performs a process of eliminating such duplicates when there are multiple identical hash tags among the received hash tags. The hash tags that are found by the search and have duplicates eliminated are transmitted from the record management server 1 to the record management terminal 3 (step 83).

[0078] At the record management terminal 3, the received hash tags are listed and displayed in the hash tag candidate display column 61E (step 73, Fig. 5).

Explanation of symbols

[0079] 1 Record management server (server device) 2 Database server (database device) 3 Record management terminal (client device) 11 Office master 12 Staff master 13 Hash tag master 21 User master 22 Record / form master 23 Record table F1, F2 Record editor window

Claims

1. A system comprising a client device operated at a business establishment classified into any one of a plurality of major classifications and further classified into any one of a plurality of minor classifications included in the major classification, and a server device network-connected to the client device, which searches for hash tags as tagging candidates from a plurality of hash tags stored in a database device according to a search request created by the server device, wherein the client device includes means for transmitting to the server device a search string that should be included in the hash tags to be hit by the search, and the major classification and minor classification of the client's own business establishment where the search is to be performed, the server device includes search request creation means for creating the search request to be given to the database device, each of the plurality of hash tags to be searched stored in the database device is a major classification tag commonly used by business establishments belonging to a specific major classification, a minor classification tag commonly used by business establishments belonging to a specific minor classification, and a business establishment individual tag individually used for each business establishment, and is hierarchically divided into any one of them, the search request created by the search request creation means of the server device includes the search string transmitted from the client device, and includes an instruction to search for a major classification tag commonly used by business establishments belonging to the same specific major classification as the major classification in which the client's own business establishment is classified, a minor classification tag commonly used by business establishments belonging to the same specific minor classification as the minor classification in which the client's own business establishment is classified, and the business establishment individual tag of the client's own business establishment, a hash tag search system.

2. A system comprising a client device operated at a business establishment classified into any one of a plurality of major classifications, further classified into any one of a plurality of medium classifications included in the major classification, and further classified into any one of a plurality of minor classifications included in the medium classification, and a server device network-connected to the client device, which searches for hash tags as tagging candidates from a plurality of hash tags stored in a database device according to a search request created by the server device, wherein the client device includes means for transmitting to the server device a search string that should be included in the hash tags to be hit by the search, and the major classification, medium classification and minor classification of the client's own business establishment where the search is to be performed, The server device includes a search request creation means for creating the search request given to the database device, each of the plurality of hash tags to be searched stored in the database device is a major classification tag commonly used by business offices belonging to a specific major classification, a medium classification tag commonly used by business offices belonging to a specific medium classification, a minor classification tag commonly used by business offices belonging to a specific minor classification, and a business office individual tag individually used for each business office, and is classified into any one of them, the search request created by the search request creation means of the server device includes the search string transmitted from the client device, and includes an instruction to search for a major classification tag commonly used by business offices belonging to the same specific major classification as the major classification in which the own business office to execute the search is classified, a medium classification tag commonly used by business offices belonging to the same specific medium classification as the medium classification in which the own business office is classified, a minor classification tag commonly used by business offices belonging to the same specific minor classification as the minor classification in which the own business office is classified, and the business office individual tag of the own business office. A hash tag search system.

3. At least some of the plurality of business offices are classified into any one of one or more groups that group business offices from a different perspective from the above classification, at least a part of the business office individual tags among the plurality of hash tags to be searched stored in the database device are group common tags commonly used within the group, the search request further includes an instruction to search for the group common tag commonly used within the same group as the own business office. The hash tag search system according to claim 1 or 2.

4. The server device is provided with means for eliminating the duplication when there are a plurality of the same hash tags among the tagged candidate hash tags hit by the search in the database device. The hash tag search system according to claim 1 or 2.

5. The server device is provided with tagged candidate hash tag transmission means for transmitting the tagged candidate hash tags hit by the search in the database device to the client device, the client device is provided with display means for selectively displaying the received tagged candidate hash tags. The hash tag search system according to claim 1 or 2.

6. The establishment is an establishment that provides services for the elderly or the disabled, The major classification is a corporate classification that classifies the establishment by the operating corporation, The minor classification is a service type classification that classifies the establishment according to the service types provided by the establishment, The hash tag search system according to claim 1.

7. The establishment is an establishment that provides services for the elderly or the disabled, The major classification is a corporate classification that classifies the establishment by the operating corporation, The middle classification classifies whether the establishment is an establishment that provides services for the elderly or an establishment that provides services for the disabled, The minor classification is a service type classification that classifies the establishment according to the service types provided by the establishment, The hash tag search system according to claim 2.

Images