Source: http://www.google.com/patents/US20040138920?dq=6101531
Timestamp: 2015-08-01 03:48:55
Document Index: 735300544

Matched Legal Cases: ['art 201', 'art 202', 'art 202', 'art 201', 'art 202', 'art 202', 'art 202', 'art 201', 'art 202', 'art 201', 'art 202', 'art 202', 'art 202', 'art 201', 'art 201', 'art 202', 'art 201', 'art 202', 'art 202', 'art 201', 'art 201', 'art 202']

Patent US20040138920 - Medical equipment management apparatus which predicts future status of ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsA medical equipment management apparatus for managing a medical equipment provided in a medical facility connected to the apparatus through a network. The apparatus comprises a reception unit, a storage unit, a prediction unit, a determination unit, and an informing unit. The reception unit is configured...http://www.google.com/patents/US20040138920?utm_source=gb-gplus-sharePatent US20040138920 - Medical equipment management apparatus which predicts future status of medical equipmentAdvanced Patent SearchPublication numberUS20040138920 A1Publication typeApplicationApplication numberUS 10/686,705Publication dateJul 15, 2004Filing dateOct 17, 2003Priority dateOct 18, 2002Also published asCN1509688A, CN100518647C, US8489408Publication number10686705, 686705, US 2004/0138920 A1, US 2004/138920 A1, US 20040138920 A1, US 20040138920A1, US 2004138920 A1, US 2004138920A1, US-A1-20040138920, US-A1-2004138920, US2004/0138920A1, US2004/138920A1, US20040138920 A1, US20040138920A1, US2004138920 A1, US2004138920A1InventorsYuuji Sawanaga, Yoichi Takada, Satoshi IkedaOriginal AssigneeKabushiki Kaisha Toshiba, Toshiba Medical System CorporationExport CitationBiBTeX, EndNote, RefManPatent Citations (11), Non-Patent Citations (2), Referenced by (10), Classifications (7), Legal Events (1) External Links: USPTO, USPTO Assignment, EspacenetMedical equipment management apparatus which predicts future status of medical equipment
[0050] (First Embodiment) [0051]FIG. 1 is an illustration showing an exemplary overview of a medical system including a medical equipment management apparatus according to a first embodiment of the present invention. As shown in FIG. 1, hospitals A, B, and C are connected to a service center D through a network. Each of the hospitals A, B, and C includes one or more medical equipments such as the medical diagnosis apparatuses as described in the background of the invention. The service center D monitors the medical equipments provided in the hospitals A, B, and C. Further, a local maintenance provider E is connected to the network. The local maintenance provider E is provided in an area where the hospital A is located. If necessary, a CT manufacturer F may also be connected to the network. [0052] In hospital A, a CT apparatus 1 is provided as the medical equipment. Although only the CT apparatus 1 will be described herein as an example of the equipment, the medical equipment provided in the hospital A may alternatively be any other type of medical equipment including, but not limited to, an X-ray diagnosis apparatus, a magnetic resonance imaging apparatus, a nuclear medical imaging apparatus, an ultrasound diagnosis apparatus, and an endoscope apparatus. There may also be provided other medical equipment in the hospital A. The equipment to be monitored by a service center according to embodiments of the present invention is further not be limited to medical equipment. [0053] The CT apparatus 1 is connected to a service processor 2 which receives information regarding a status of the CT apparatus 1 or regarding each status of one or more parts included in the CT apparatus 1. Such information is hereinafter referred to as a parameter data. The service processor 2 provides the service center D with the parameter data through the network. [0054] The hospital A further includes PCs (personal computers) 3 to 5. The PC 3 is provided in a department of radiology in the hospital A and may be used by radiological technologists. The PC 4 is a PC which is usually used by a user in the hospital A. The ‘user’ may include a doctor, the radiological technologist, a system administrator, and other users. There is another PC 5 in the hospital A. The PC 5 may be provided, but not limited to, for example, in an administration department. The PC 5 may be provided in a department regarding management, operation, maintenance of the CT apparatus 1 in the hospital A. Further, the number of each PC 3 to 5 may be more than one. The PCs 3 to 5 can receive emails from the service center D and can allow the radiological technologist, the user, and the like to access to information provided in the Internet web site by the service center D, through a WWW (World Wide Web) browser. The information may be expectancy based on monitored parameter data of the CT apparatus 1 or information provided in response to a reference request. The reference request will be described in detail later. [0055] One example of the parameter data is amplification characteristic, such as a bias voltage level and an amplitude voltage level of an amplifier. The amplifier is, for example, used for amplifying electric signals which is converted from optical signals transmitted between a rotation part and a fixed part of a gantry of the CT apparatus 1. Such an example of the amplifier will be described in detail later. [0056] The hospitals B and C may include components similar to the hospital A. [0057] Any one or more of PCs, including the PCs 3 to 5, which are described in embodiments of the present invention, may alternatively be other types of computers. [0058] When it comes to the service center D, a medical equipment management apparatus 6 is provided for monitoring and managing information or a status of the CT apparatus 1 in the hospital A and other medical equipment which are provided in the hospitals A, B, and/or C. In addition, a maintenance service is directed or requested from the service center D to the local maintenance provider E. Details of the medical equipment management apparatus 6 will be described later. [0059] The local maintenance provider E provides hospitals including the hospital A in an area assigned to the local maintenance provider E with a maintenance service and any other necessary assistance locally. There is a PC 7 in the local maintenance provider E. The PC 7 is a maintenance personnel's PC or a PC which is used for managing information of the hospital A. [0060] Similar to the PCs 3 to 5, the PC 7 can also receive emails from the service center D and can allow its user to access to information provided in the Internet web site by the service center D, through a WWW browser. The information may be expectancy based on monitored parameter data of the CT apparatus 1 or information provided in response to a reference request. The reference request will be described in detail later. [0061] Further, medical equipment manufacturers may also be connected to the network. In the first embodiment of the present invention, the CT manufacturer F which has manufactured the CT apparatus 1 can be connected to one or more of the hospital A, the service center D, and the local maintenance provider E through the network so that CT engineers are given a chance to find and analyze technical problems, if occurred, as soon as possible. This leads to the CT engineers' early investigation of a solution to the problems based on the analysis. [0062] Next, a further detailed explanation will be made with respect to a relationship among the hospital A, the medical equipment management apparatus 6, and the local maintenance provider E. FIG. 2 is a block diagram showing a first exemplary configuration of the medical equipment management apparatus 6 in relationship to the hospital A and the local maintenance provider E according to the first embodiment of the present invention. [0063] The medical equipment management apparatus 6 provided in the service center 6 includes a reception unit 60, a storage unit 61, and a retrieval unit 62. The reception unit 60, as an FTP server, for example, receives parameter data from the hospital A. The storage unit 61, as a data mart, for example, stores the parameter data received by the reception unit 60. The retrieval unit 62 reads out (or retrieves) the parameter data stored in the storage unit 61 as prior data. [0064] In addition, the medical equipment management apparatus 6 includes a prediction unit 63, a determination unit 64, a graph preparation unit 65, and an embedding unit 66. The prediction unit 63 predicts expectancy of parameter data to be received in the future from the hospital A by calculation based on the prior parameter data read out by the retrieval unit 62. The determination unit 64 compares the expectancy to a predetermined threshold, and determines whether or not the expectancy exceeds the predetermined threshold. The determination unit 64 may also or alternatively determine (predict) a date when the expectancy will exceed (or be equal to) the predetermined threshold. Such a date is hereinafter referred to as a probable date. The graph preparation unit 65 prepares a graph showing the prior parameter data and the expectancy based on the prediction or based on the prediction and the determination. If necessary, the embedding unit 66 embeds the prepared graph in reports which are provided to the hospital A and/or the local maintenance provider E. [0065] Further, the medical equipment management apparatus 6 still includes an email unit 67. The email unit 67 transmits emails to the local maintenance provider E and the hospital A, if necessary, according to the determination by the determination unit 64. The emails may include an content based on the determination. [0066] Operations of the medical equipment management apparatus 6 configured as described above will be described below in relationship to operations in the hospital A and the local maintenance provider E. [0067] In the hospital A, specimens are examined by the CT apparatus 1. The service processor 2 receives parameter data from the CT apparatus 1 regularly, at any or given time, or in response to a predetermined trigger event. The service processor 2 then provides the reception unit 60 with the received parameter data regularly, at any or given time, or every time when the service processor 2 receives the parameter data from the CT apparatus 1. Further, the service processor 2 may alternatively provide the reception unit 60 with the parameter data in response to requests from the medical equipment management apparatus 6. Except for a case of providing every time when the service processor 2 receives the parameter data from the CT apparatus 1, the service processor 2 may provide all parameter data received from the CT apparatus 1 since the previous providing by the service processor 2. Alternatively, only a part or a latest of parameter data already received from the CT apparatus 1 may be provided to the reception unit 60. [0068] In any case, parameter data provided by the service processor 2 are received by the reception unit 60 through, for example, exclusive lines. The received parameter data are stored in the storage unit 61 and used for expectancy calculation in a later stage. Prior to the storage, the reception unit 60 sorts the received parameter data in accordance with parts or the like regarding the parameter data. The parameter data and the following parameter data to be received may be stored in tables each of which is provided for each part or the like of the CT apparatus 1. [0069] The reception unit 60 is not limited to on-line reception of the parameter data. For example, the service center D may regularly receive storage media storing parameter data from the hospital A directly or through the local maintenance provider E. The storage media may be placed in a readout system (the reception unit 60) by an operator, and the parameter data stored in the media may be received by the reception unit 60. [0070] Parameter data stored in the storage unit 61 are retrieved by the retrieval unit 62 regularly or at any or given time. The parameter data may be alternatively retrieved in response to reference requests from PCs 3-5, 7 and the like which will be described later. In the retrieval, the retrieval unit 62 may retrieve parameter data for all parts of the CT apparatus 1. Alternatively, the retrieval unit 62 may select one or more specific parts and retrieve parameter data only for such selected parts. [0071] Further, parameter data retrieved regarding each part of the CT apparatus 1 may be all parameter data of the part or may alternatively be specific parameter data obtained or received every predetermined interval. Still alternatively retrieved may be only latest parameter data at the instant of retrieval. [0072] The retrieved parameter data (prior data) are provided to the prediction unit 63. In the prediction unit 63, expectancy of parameter data to be received in the future is predicted by calculation based on the parameter data (prior data) retrieved from the storage unit 61. When all parameters stored in the storage unit 61 have been retrieved for the prediction, the expectancy will have a higher degree of accuracy. The future may be a time in a predetermined period, such as, for example, a week or a month, from the time of prediction. When the expectancy is predicted in response to reference requests, the future may be a time indicated in the requests, if indicated. [0073] When a transition of parameter data regarding a part of the CT apparatus 1, which was prepared in a previous prediction, is stored, a present prediction may be implemented based on the transition and newly received and retrieved parameter data. In this case, there may be a possibility that a predicted expectancy has a lower degree of accuracy, compared to a case using more or all received parameter data. However, it may also be possible to predict the expectancy more easily and more quickly. [0074] In some cases, a transition of parameter data regarding an old part, before being replaced with a current one, of the CT apparatus 1 may still be stored in the storage unit 61 or other unit. In such a case, the transition regarding the old part may be considered for predicting expectancy of parameter data regarding the current part. The transition may alternatively be used as correction data for correcting expectancy predicted based on received parameter data regarding the current part. [0075] A further possible way of prediction is applicable to the following case. It may not be so rare that a part which is similar to or has the same model number as what is used in the CT apparatus 1 is being used or was used in a CT apparatus or other type of apparatus provided in the hospital A or in other hospitals. If a transition of parameters regarding such a part is obtained in the service center D, such an obtained transition may be considered for predicting an expectancy of parameter data regarding the part used in the CT apparatus 1. The transition may alternatively be used as correction data for correcting an expectancy predicted based on received parameter data regarding the part used in the CT apparatus 1. [0076] It does not matter whether a prediction engine used in the prediction unit 63 is linear or nonlinear. A data mining technique is one exemplary technique for the prediction. In the data mining technique, there may be used, for example, a co-occurrence relation analysis technique (or a basket analysis), a classification technique (or a decision tree), and/or a neural network. In addition, an expectancy may be analogized by extracting pattern information from received parameter data. Another prediction may use differential information between a plurality of parameter data. [0077] Turning back to FIG. 2, when an expectancy has been obtained in a manner as described above, the expectancy is compared to a predetermined threshold and is determined whether or not the expectancy exceeds the predetermined threshold in the determination unit 64. The determination unit 64 holds thresholds corresponding to parameters, respectively. The threshold is a type of indicator for determining whether or not it shows that a part regarding parameter data deteriorates so as not to operate properly or is becoming unable to maintain its normal operation. Two thresholds may be set for one expectancy. One is an upper threshold showing an upper limitation for maintaining a part to operate properly. Another is a bottom threshold showing a bottom limitation for maintaining the same part to operate properly. [0078] In addition, whether or not there are two thresholds described above, a predetermined threshold can be dual. That is, for example, a standard level and a dangerous level can be set for each predetermined threshold. A dangerous threshold level indicates an emergency situation that it is nearly impossible for the part to properly operate, i.e., it is necessary to repair or replace the part immediately. Therefore, it requires an urgent contact with the local maintenance provider E. On the other hand, a standard threshold level may be set at a 70 percent of the dangerous threshold level, for example. The standard threshold level does not indicate an emergency situation as the dangerous threshold level, but it indicates maintenance service will be required in the near future. It may also be necessary to decide whether to wait for a next regular maintenance service or to ask for a maintenance service before the next regular maintenance service, in consideration of a time of the next regular maintenance service. [0079] The determination unit 64 also or alternatively determines a probable date when an expectancy exceeds the threshold (the standard threshold level or the dangerous threshold level) based on the prediction in the prediction unit 63 when the probable date is requested from one or more PCs 3-5, 7, and the like. [0080] Further, the graph preparation unit 65 prepares a graph showing parameter data stored in the storage unit 61 and a predicted expectancy. The prepared graph may reflect a determination result in the determination unit 64. Further, a function which becomes a base of the prediction in the prediction unit 63 may also be expressed in the graph. Instead of or in addition to the graph preparation, the graph preparation unit 65 may prepare a table including the parameter data and the predicted expectancy. [0081] The prepared graph is embedded or included in a report in the embedding unit 66. The report may be, for example, a so-called performance report including operation conditions of the CT apparatus 1. An alternative example of the report may be a so-called QA (quality assurance) report including qualities such as an image quality obtained regarding the CT apparatus 1. These reports are usually provided to the hospital A and/or the local maintenance provider E regularly, in the event of an emergency, and/or in response to requests. Therefore, the prepared graph (the predicted expectancy) can also be provided to the hospital A and/or the local maintenance provider E regularly, in the event of an emergency, and/or in response to requests. [0082] When an expectancy is determined to exceed the threshold (the standard threshold level or the dangerous threshold level) in the determination unit 64, the email unit 67 transmits email(s) to issue a notice of such an occurrence, the expectancy, the probable date, the graph, and/or the report. The expectancy, the probable date, the graph, and/or the report may be accessed by clicking a URL written in the email, and accordingly referred through the WWW browser. In addition, the email is transmitted to the PC 7 provided in the local maintenance provider E for the purpose of giving a notice of a request of a maintenance service. The email is also transmitted to the PC 4 and maybe also the PCs 3 and 5 in the hospital A for the purpose of giving a notice of letting the user recognize a current status of the CT apparatus 1 and immediate or near future's necessity of a maintenance service. The email to the hospital A may be a CC (carbon copy) of the email transmitted to the local maintenance provider E. [0083] When the email is received in the PC 7, the email can be displayed in a display 71 of the PC 7 and referred by maintenance personnel or the like. Accordingly, it becomes possible for the local maintenance provider E to study a time for a maintenance service based on the determination (i.e., information included in the received email). A study result may lead to an arrangement of repairs, parts replacement, and so on. Information to be written in and/or to be attached with the email may be different according to the determination of whether or not the expectancy exceeds the threshold (also whether the expectancy is between the standard threshold level and the dangerous threshold level or exceeds the dangerous threshold level). [0084] When the email is received in the PC 4, the email can be displayed in a display 41 of the PC 4 and referred to by the user. Accordingly, it becomes possible for the user to recognize the necessity of having a maintenance service on the CT apparatus 1 immediately or in the near future. Based on the information obtained through the email, the user can take actions in advance for operations without the CT apparatus 1 for a maintenance period. The email may also be transmitted to the PC 3 and 5. This makes it possible to let other hospital staff relating to operations of the CT apparatus 1 recognize the same, for example. Information to be written in and/or to be attached with the email may be the same as or be different from that for the PC 7 provided in the local maintenance provider E. [0085] By receiving the email, the hospital A can spontaneously contact the local maintenance provider E and discuss a maintenance service with maintenance personnel. [0086] Further, the PC 4 includes a keyboard 42 for various operations, such as, for example, input, designation, and request. The PC 7 also includes a keyboard 72 for various operations, such as, for example, input, designation, and request. [0087] (Second Embodiment) [0088] Another relationship among the hospital A, the medical equipment management apparatus 6, and the local maintenance provider E will be described with reference to FIG. 3. FIG. 3 is a block diagram showing a second exemplary configuration of the medical equipment management apparatus 6 in relationship to the hospital A and the local maintenance provider E according to a second embodiment of the present invention. [0089] In FIG. 3, components, which operate in a manner similar to the components shown in FIG. 2 are given the same reference numbers and are detailed explanations of their components are appropriately omitted. In addition, operations of the medical equipment management apparatus 6 are similar to those described in the first embodiment except for those described below. Therefore, detailed explanations of such operations similar to those in the first embodiment are omitted. [0090] The medical equipment management apparatus 6 further includes an expectancy request unit 68 and a prior data request unit 69. The expectancy request unit 68 requests plotting an expectancy in response to reference requests of the expectancy of parameter data from the hospital A. The prior data request unit 69 requests prior data (i.e., parameter data) towards a storage unit 611 in response to the requests from the expectancy request unit 68. [0091] When the user operates a keyboard 421 of the PC 4 so as to request an expectancy of parameter data regarding a specific part or the like of the CT apparatus 1, this request is sent to the expectancy request unit 68. One possible way of sending the request from the keyboard 421 may be inputs, selection, and/or button pressing in a web site of the service center D through a WWW browser. Another example may be using email instead of the WWW browser. The request may correspond to a probable date, instead of the expectancy. [0092] Such a request of the expectancy or the probable date may alternatively be made by a radiological technologist through the PC 3 or by other hospital staff in a department of administration or else through the PC 5. [0093] When the request from the PC 4 (3, or 5) is received by the expectancy request unit 68 through the network, the expectancy request unit 68 sends a request to the prior data request unit 69 according to a content of the request from the PC 4 (3, or 5). The request to the prior data request unit 69 may be a graph showing prior data (parameter data) and an expectancy. In another exemplary case, it may be an embedding of the graph into a report, such as, for example, a performance report and a QA report. [0094] The prior data request unit 69 requests the storage unit 611 parameter data necessary for the request from the expectancy request unit 68. The storage unit 611 provides the retrieval unit 62 with parameter data meeting the request from the prior data request unit 69. [0095] The parameter data provided to the retrieval unit 62 are used for calculations in the prediction unit 63 so as to predict an expectancy. In the prediction unit 63 and the determination unit 64, operations described before are implemented. The graph preparation unit 651 and the embedding unit 661 implement operations similar to those in FIG. 2. When the request from the hospital A regards a graph, the graph prepared in the graph preparation unit 651 is available in the PC 4 (3, or 5) which has made the request. In such a PC 4 (3, or 5), the graph can be referred in the display 411 (or the like). Also when the request from the hospital A corresponds to a report, the report embedded with the graph is available in the PC 4 (3, or 5) which has made the request. In such a PC 4 (3, or 5), the report can be referred in the display 411 (or the like). [0096] This reference may be realized through the WWW browser, by operating buttons or inputting necessary information. Alternatively, the reference may be made through email from the medical equipment management apparatus 6. If the email includes a URL for accessing to the graph or the report, the user or other hospital staff can refer to the graph or the report through the Internet web site by clicking the URL. If the email is attached with a file including the graph or the report, the user or other hospital staff can open the attached file and refer to the graph or the report. [0097] According to the second embodiment of the present invention, the user or other hospital staff can request information regarding an expectancy for himself or herself. Therefore, anytime he or she feels it necessary, even when he or she feels anxiety, he or she can obtain an expectancy, the graph, and/or the report to see a current situation without waiting for a notice by email from the medical equipment management apparatus 6. This leads to relief of anxiety. In addition, the hospital A can study or take appropriate actions for responding to the situation in advance of receiving the email, depending on a result of the reference. [0098] (Third Embodiment) [0099] Requests from the hospital A has been described in the second embodiment of the present invention. Such requests may also be made from the local maintenance provider E. [0100]FIG. 4 is a block diagram showing a third exemplary configuration of the medical equipment management apparatus 6 in relationship to the hospital A and the local maintenance provider E according to a third embodiment of the present invention. [0101] In FIG. 4, components, which operate in a manner similar to the components shown in FIG. 2 or 3 are given the same reference numbers and detailed explanations are appropriately omitted. In addition, operations of the medical equipment management apparatus 6 are similar to those described in the first or second embodiment except for those described below. Therefore, detailed explanations of such operations similar to those in the first or second embodiment are omitted. [0102] When the maintenance personnel or other staff in the local maintenance provider E operates a keyboard 722 of the PC 7 so as to request an expectancy of parameter data regarding a specific part or the like of the CT apparatus 1, this request is sent to the expectancy request unit 682. The request from the keyboard 722 may be made as in the case of the keyboard 421 described in the second embodiment. [0103] When the request from the PC 7 is received by the expectancy request unit 682 through the network, the expectancy request unit 682 sends a request to the prior data request unit 69 according to a content of the request from the PC 7. The request to the prior data request unit 69 may be as described in the second embodiment. Subsequently, the graph and/or the report are obtained as described in the second embodiment. [0104] When the request from the local maintenance provider E corresponds to a graph, the graph prepared in a graph preparation unit 652 is available in the PC 7 which has made the request. In such a PC 7, the graph can be referred in the display 712. Also when the request from the local maintenance provider E corresponds to a report, the report embedded with the graph by an embedding unit 662 is available in the PC 7 which has made the request. In such a PC 7, the report can be referred in a display 712. This reference may be realized in various manners as described in the second embodiment. [0105] According to the third embodiment of the present invention, the maintenance personnel or the other staff can request information regarding an expectancy for himself or herself. Therefore, anytime he or she feels it necessary, for example, when he or she wants to identify the situation of the CT apparatus 1 or to arrange parts in sufficient time, he or she can obtain an expectancy, the graph, and/or the report to see a current situation without waiting for a notice by email from an email unit 672 of the medical equipment management apparatus 6. In addition, the local maintenance provider E can coordinate schedules for maintenance personnel and/or arrange (or order) some parts for replacement in advance of receiving the email, depending on a result of the reference. [0106] (Fourth Embodiment) [0107] The above mentioned requests may also be made from inside the service center D. [0108]FIG. 5 is a block diagram showing a fourth exemplary configuration of the medical equipment management apparatus 6 in relationship to the hospital A and the local maintenance provider E according to a fourth embodiment of the present invention. [0109] In FIG. 5, components, which operate in a manner similar to the components shown in FIG. 2 or 3 are given the same reference numbers and detailed explanations are appropriately omitted. In addition, operations of the medical equipment management apparatus 6 are similar to those described in the first or second embodiment except for those described below. Therefore, detailed explanations of such operations similar to those in the first or second embodiment are omitted. [0110] When a person in the service center D, who has or may not have an access authority to the medical equipment management apparatus 6, operates a keyboard 602 of a PC 600 provided in the service center D so as to request an expectancy of parameter data regarding a specific part or the like of the CT apparatus 1, this request is sent to an expectancy request unit 683. The request from the keyboard 602 may be made as in the case of the keyboard 421 described in the second embodiment. [0111] When the request from the PC 600 is received by the expectancy request unit 683 through the network, the expectancy request unit 683 sends a request to the prior data request unit 69 according to a content of the request from the PC 600. The request to the prior data request unit 69 may be as described in the second embodiment. Subsequently, the graph and/or the report are obtained as described in the second embodiment. [0112] When the request from inside the service center D corresponds to a graph, the graph prepared in a graph preparation unit 653 is available in the PC 600 which has made the request. In such a PC 600, the graph can be referred in a display 601. Also when the request from inside the service center D regards a report, the report embedded with the graph by an embedding unit 663 is available in the PC 600 which has made the request. In such a PC 600, the report can be referred in the display 601. This reference may be realized in various manners as described in the second embodiment. [0113] According to the fourth embodiment of the present invention, the person in the service center D can request information regarding expectancy for himself or herself. Therefore, it makes it possible to accommodate various matters in the service center D, if any. [0114] (Fifth Embodiment) [0115] Further, the above mentioned requests may also be made from the CT manufacturer F. [0116]FIG. 6 is a block diagram showing a fifth exemplary configuration of the medical equipment management apparatus 6 in relationship to the hospital A and the local maintenance provider E according to a fifth embodiment of the present invention. [0117] In FIG. 6, components, which operate in a manner similar to the components shown in FIG. 2 or 3 are given the same reference numbers and detailed explanations are appropriately omitted. In addition, operations of the medical equipment management apparatus 6 are similar to those described in the first or second embodiment except for those described below. Therefore, detailed explanations of such operations similar to those in the first or second embodiment are omitted herein. [0118] When a person in the CT manufacturer F, who has or may not have an access authority to the medical equipment management apparatus 6, operates a keyboard 802 of a PC 800 provided in the CT manufacturer F so as to request an expectancy of parameter data regarding a specific part or the like of the CT apparatus 1, this request is sent to an expectancy request unit 684. The request from the keyboard 802 may be made as in the case of the keyboard 421 described in the second embodiment. [0119] When the request from the PC 800 is received by the expectancy request unit 684 through the network, the expectancy request unit 684 sends a request to the prior data request unit 69 according to a content of the request from the PC 800. The request to the prior data request unit 69 may be as described in the second embodiment. Subsequently, the graph and/or the report are obtained as described in the second embodiment. [0120] When the request from the CT manufacturer F corresponds to a graph, the graph prepared in a graph preparation unit 654 is available in the PC 800 which has made the request. In such a PC 800, the graph can be referred in a display 801. Also when the request from the CT manufacturer F regards a report, the report embedded with the graph by an embedding unit 664 is available in the PC 800 which has made the request. In such a PC 800, the report can be referred in the display 801. This reference may be realized in various manners as described in the second embodiment. [0121] According to the fifth embodiment of the present invention, the person in the CT manufacturer F can request information regarding an expectancy for himself or herself. Therefore, if necessary, he or she can see, for example, whether the CT apparatus 1 manufactured by the CT manufacturer F is operating properly or the CT apparatus 1 is showing any abnormality (any possibility of abnormality). Accordingly, the CT manufacturer F can determine abnormality signs at an early stage, which may not be discovered by other manufacturers who do not manufacture the CT apparatus 1. This improves the credibility of the CT manufacturer F. [0122] (Sixth Embodiment) [0123] In the first to fifth embodiments of the present invention, the requests from PCs have corresponded to a graph or a report. The requests are not limited to those, but also applied to other information, such as, for example, only an expectancy. [0124] Turning now to FIG. 7, which is a block diagram showing a sixth exemplary configuration of the medical equipment management apparatus 6 in relationship to the hospital A and the local maintenance provider E according to a sixth embodiment of the present invention. [0125] In FIG. 7, components, which operate in a manner similar to the components shown in FIG. 2 or 3 are given the same reference numbers and detailed explanations are appropriately omitted. In addition, operations of the medical equipment management apparatus 6 are similar to those described in the first or second embodiment except for those described below. Therefore, detailed explanations of such operations similar to those in the first or second embodiment are omitted herein. [0126] When the user in the hospital A operates a keyboard 425 of the PC 4 so as to request an expectancy of parameter data regarding a specific part or the like of the CT apparatus 1, this request is sent to an expectancy request unit 685. The request from the keyboard 425 may be made as in the case of the keyboard 421 described in the second embodiment. [0127] When the request from the PC 4 is received by the expectancy request unit 685 through the network, the expectancy request unit 685 sends a request to the prior data request unit 69 according to a content of the request from the PC 4. The request towards the prior data request unit 69 may be as described in the second embodiment. Subsequently, the expectancy is obtained as described in the second embodiment. [0128] The expectancy predicted in a prediction unit 635 is available in the PC 4 which has made the request. In such a PC 4, the expectancy can be referred in a display 415. This reference may be realized in various manners as described in the second embodiment. A PC which makes the requests is not limited to the PC 4, but may also be other PCs, such as, for example, the PCs 3, 5, 7, 600, and 800. [0129] According to the sixth embodiment of the present invention, it is advantageous for the medical system or, particularly, the PCs, for example, when it is enough to know only an expectancy or when it is preferable to avoid displaying a large size of data for reference. [0130] (Seventh Embodiment) [0131] Instead of the expectancy, the requests may also be applied to a result of the determination based on the expectancy and the predetermined threshold. [0132]FIG. 8 is a block diagram showing a seventh exemplary configuration of the medical equipment management apparatus 6 in relationship to the hospital A and the local maintenance provider E according to a seventh embodiment of the present invention. [0133] In FIG. 8, components which operate in a manner similar to the components shown in FIG. 2 or 3 are given the same reference numbers and detailed explanations are appropriately omitted. In addition, operations of the medical equipment management apparatus 6 are similar to those described in the first or second embodiment except for those described below. Therefore, detailed explanations of such operations similar to those in the first or second embodiment are omitted herein. [0134] When the user in the hospital A operates a keyboard 426 of the PC 4 so as to request a result of determination of an expectancy of parameter data regarding a specific part or the like of the CT apparatus 1, this request is sent to an expectancy request unit 686. The request from the keyboard 426 may be made as in the case of the keyboard 421 described in the second embodiment. [0135] When the request from the PC 4 is received by the expectancy request unit 686 through the network, the expectancy request unit 686 sends a request to the prior data request unit 69 according to a content of the request from the PC 4. The request to the prior data request unit 69 may be as described in the second embodiment. Subsequently, a level of the expectancy is determined in a determination unit 646 as described in the second embodiment. [0136] The result of the determination is available in the PC 4 which has made the request. In such a PC 4, the result of the determination can be referred in a display 416. In the reference, for example, a message indicating that the expectancy exceeds the threshold (there is abnormality; an early maintenance is required; there is no problem; and the like) is available when there is only one threshold. When there are two or more thresholds, it is possible to determine which range the expectancy belongs to. In addition or alternatively, a message, such as, for example, that an urgent maintenance is required; a maintenance is required within a predetermined period; a maintenance is not required for the time being; and the like, is available according to which range the expectancy belongs to. [0137] This reference may be realized in various manners as described in the second embodiment. A PC which makes the requests is not limited to the PC 4, but may also be other PCs, such as, for example, the PCs 3, 5, 7, 600, and 800. [0138] According to the seventh embodiment of the present invention, it is advantageous for the medical system or, particularly, the PCs, for example, when it is enough to know only a result of the determination or an emergency level, or when it is preferable to avoid displaying a large size of data for reference. [0139] <Operation Flow>
[0140] Operation flows will be described each of which is from a parameter data reception to an expectancy reference. Each of the flows may be applied to, but are not limited to, the medical equipment management apparatus 6 with one or more of the configurations described in the first to seventh embodiments of the present invention. In the embodiments below, however, flowcharts are described based on the medical equipment management apparatus 6 in relationship to the hospital A and the local maintenance provider E shown in FIG. 3, as an example. [0141] (Eighth Embodiment) [0142]FIG. 9 is a flowchart showing a first exemplary operation of the medical equipment management apparatus 6 according to an eighth embodiment of the present invention. As shown in FIG. 9, parameter data provided from the service processor 2 connected to the CT apparatus 1 are received by the reception unit 60 (step 901). The received parameter data are stored in the storage unit 611 (step 902). [0143] The stored parameter data are retrieved (or read out) by the retrieval unit 62 every predetermined time. The retrieval may also be implemented for every part included in the CT apparatus 1. In step 903, it is determined whether or not it is time to retrieve the stored parameter data. As long as it is not such a time (step 903 NO) and there is no reference request (step 907 NO), the reception in step 901 and the storage in step 902 are repeated in the event that parameter data are provided from the service processor 2. [0144] In response to the retrieval in the retrieval unit 62, an expectancy of parameter data to be received in the future is predicted by calculation based on the retrieved parameter data in the prediction unit 63 (step 904). The predicted expectancy is compared to a predetermined threshold in the determination unit 64 (step 905). When the expectancy is determined to exceed the predetermined threshold (greater than the upper threshold, if predetermined, or lower than the bottom threshold, if predetermined), an email for informing such a determination is transmitted to the PC 7 provided in the local maintenance provider E (and maybe to the PC 4 provided in the hospital A) by the email unit 671 (step 906). A graph and/or a report may be included in the email as described before. [0145] After the email transmission, it is determined if there is a request corresponding to an expectancy or the like (step 907). The same is also determined in step 907 when the expectancy does not exceed the predetermined threshold in step 905. Further, the same is also determined in step 907 when it is not determined to be a time to retrieve the stored parameter data in step 903. [0146] When it is determined that there is a reference request, the graph preparation unit 651 prepares a graph which compares the parameter data and the expectancy to the predetermined threshold (step 908). The prepared graph may be embedded in a report as described before. The prepared graph is referred to through the WWW browser or the report and displayed in the PC 4 (step 909). [0147] Further, the above described steps are repeated. In addition, the steps 901 to 902 belong to a reception processing, and the steps 903 to 906 belong to an alarm transmission processing. The steps 907 to 909 belong to a graph presentation processing. Any one or more of the above three processes may be implemented simultaneously or in parallel in the medical equipment management apparatus 6. [0148] In step 903, the retrieval time is not limited to every predetermined time period, but can be variously set as described before. For example, the retrieval may be implemented every time parameter data is received from the service processor 2, every time the medical equipment management apparatus 6 is powered on, any time set by the user, any combination of those, or any preferable timing. [0149] Next, FIG. 10 is an exemplary graph referred to in step 909. In FIG. 10, parameter data are plotted in black triangles as prior data from January to July. In addition, an expectancy is plotted in a white triangle as parameter data predicted to be received in August. Further, FIG. 10 includes an upper threshold and a bottom threshold. The upper threshold includes a standard level and a dangerous level. Similarly, the bottom threshold includes a standard level and a dangerous level. Since the expectancy for August exceeds the standard level of the upper threshold, an email is transmitted by the email unit 671. Still further, the graph shows a linear function which was obtained based on the parameter data and has become a base of the prediction. [0150] (Ninth Embodiment) [0151] In the eighth embodiment, the expectancy was predicted every predetermined period or so described before regardless of reference requests from the PC 4. However, the expectancy may be predicted in response to reference requests from the PC 4. [0152] Next, FIG. 11 is a flowchart showing a second exemplary operation of the medical equipment management apparatus 6 according to a ninth embodiment of the present invention. As shown in FIG. 11, parameter data provided from the service processor 2 connected to the CT apparatus 1 are received by the reception unit 60 (step 1101). The received parameter data are stored in the storage unit 611 (step 1102). [0153] It is determined if there is a request for referring to an expectancy or the like (step 1103). When there is no reference request (step 1103 NO), the reception in step 1101 and the storage in step 1102 are repeated in the event that parameter data are provided from the service processor 2. [0154] When it is determined that there is the reference request, the stored parameter data regarding a part of the CT apparatus 1 are retrieved (or read out) by the retrieval unit 62 according to the reference request. In response to the retrieval in the retrieval unit 62, an expectancy of parameter data to be received in the future is predicted by calculation based on the retrieved parameter data in the prediction unit 63 (step 1104). The predicted expectancy is compared to a predetermined threshold in the determination unit 64 (step 1105). When the expectancy is determined to exceed the predetermined threshold (greater than the upper threshold, if predetermined, or lower than the bottom threshold, if predetermined), an email for informing such a determination is transmitted to the PC 7 provided in the local maintenance provider E (and maybe to the PC 4 provided in the hospital A) by the email unit 671 (step 1106). A graph and/or a report may be included in the email as described before. [0155] After the email transmission, the graph preparation unit 651 prepares a graph which compares the parameter data and the expectancy to the predetermined threshold (step 1107). The prepared graph may be embedded in a report as described before. The graph is also prepared when the expectancy does not exceed the predetermined threshold in step 1105. The prepared graph is referred to through the WWW browser or the report and displayed in the PC 4 (step 1108). [0156] The above described steps are repeated. [0157] In the eighth and ninth embodiments, even if it is not a case by the email transmission or the reference request, the expectancy and/or the graph may be referred to by a person who receives the report regularly, in the event of an emergency, and/or in response to requests, as long as the report is embedded with expectancy or the graph. [0158] (First Modification) [0159] When there are dual threshold levels as shown in FIG. 10, such as the standard level and the dangerous level, flowcharts shown in FIGS. 9 and 11 may be modified to transmit emails to different addresses according to a relationship between expectancy and threshold levels, respectively. [0160]FIG. 12A is a flowchart showing a first example modifying a part of the flowchart shown in FIG. 9. Similarly, FIG. 12B is a flowchart showing a first example modifying a part of the flowchart shown in FIG. 11. In both FIGS. 12A and 12B, an expectancy is first compared to the dangerous level when the expectancy is compared to the predetermined threshold (step 1201). [0161] When the expectancy is determined to exceed the dangerous level (greater than the dangerous level of the upper threshold, if predetermined, or lower than the dangerous level of the bottom threshold, if predetermined), an email for informing such a determination is transmitted to a first group of addresses (or a first address) by the email unit 671 (step 1202). The first group of addresses may include the PC 7 provided in the local maintenance provider E and the PC 4 in the hospital A. [0162] When the expectancy is not determined to exceed the dangerous level in step 1201, the expectancy is then compared to the standard level (step 1203). When the expectancy is determined to exceed the standard level (greater than the standard level of the upper threshold, if predetermined, or lower than the standard level of the bottom threshold, if predetermined), an email for informing such a determination is transmitted to a second group of addresses (or a second address) by the email unit 671 (step 1204). The second group of addresses may include only the PC 7. Alternatively, the second group of addresses may be the same as the first group of addresses. [0163] Instead of the comparisons described above, the expectancy may first be compared to the standard level. Further, instead of transmitting emails to different group of addresses, contents of emails may be differentiated according to the comparisons. For example, when the expectancy is determined to exceed the dangerous level in step 1201, an email including a first message is transmitted to both the PC 7 and the PC 4 by the email unit 671. The first message is, for example, for asking the maintenance personnel to go to the hospital A to implement inspection and a maintenance service. Similarly, when the expectancy is determined to exceed the standard level in step 1203, an email including a second message is transmitted to both the PC 7 and the PC 4 by the email unit 671. The second message is, for example, for suggesting it is not necessary for immediate maintenance if a next regular maintenance service is scheduled within a month, but, otherwise, asking the maintenance personnel to implement inspection and a maintenance service within two months. [0164] (Second Modification) [0165] The flowcharts shown in FIGS. 9 and 11 may be modified to prepare and provide a graph showing a probable date according to the reference request from the PC 4. [0166]FIG. 13A is a flowchart showing a second example modifying a part of the flowchart shown in FIG. 9. Similarly, FIG. 13B is a flowchart showing a second example modifying a part of the flowchart shown in FIG. 11. In both FIGS. 13A and 13B, when there was the reference request, it is determined whether the reference request corresponds an expectancy or probable date (step 1301). [0167] When the reference request is determined to correspond to the expectancy, the graph preparation unit 651 prepares a graph showing the expectancy based on the reference request (e.g., a requested part of the CT apparatus 1) (step 1302). The prepared graph may be, for example, as shown in FIG. 10. Further, the prepared graph may be embedded in a report as described before. The prepared graph is provided (presented) for reference through the WWW browser or the report and displayed in the PC 4 (step 1303). [0168] On the other hand, when the reference request is determined to correspond to the probable date, the probable date is determined by calculation based on the parameter data and the expectancy in the determination unit 64 (step 1304). The graph preparation unit 651 prepares a graph showing the probable date based on the reference request (step 1305). The prepared graph may be, for example, as shown in FIG. 14. In FIG. 14, the probable date is July 11. The prepared graph may be embedded in a report as described before, and the prepared graph is provided (presented) for reference through the WWW browser or the report and displayed in the PC 4 (step 1306). [0169] When there are two or more threshold levels of the predetermined threshold, the user may designate which level the probable date should correspond to in the reference request. Alternatively, probable dates corresponding to respective threshold levels may be shown in a graph whether a specific threshold level is indicated in the reference request or not. [0170] (Third Modification) [0171] As described in the second modification, when both the expectancy request and the probable date request are acceptable, minimum information, such as an expectancy and a probable date, may be provided (presented) for reference, instead of the graph. [0172] Next, FIG. 15A is a flowchart showing a third example modifying a part of the flowchart shown in FIG. 9. Similarly, FIG. 15B is a flowchart showing a third example modifying a part of the flowchart shown in FIG. 11. In both FIGS. 15A and 15B, when there was the reference request, it is determined whether the reference request corresponds to an expectancy or probable date (step 1501). [0173] When the reference request is determined to correspond to the expectancy, the expectancy based on the reference request (e.g., a requested part of the CT apparatus 1) is provided (presented) for reference through the WWW browser or a report, if embedded, and displayed in the PC 4 (step 1502). [0174] On the other hand, when the reference request is determined to correspond to the probable date, the probable date is determined by calculation based on the parameter data and the expectancy in the determination unit 64 (step 1503). The probable date based on the reference request (e.g., a requested part of the CT apparatus 1) is provided (presented) for reference through the WWW browser or a report, if embedded, and displayed in the PC 4 (step 1504). [0175] When there are two or more threshold levels of the predetermined threshold, the user may designate which level the probable date should correspond to in the reference request. Alternatively, probable dates corresponding to respective threshold levels may be provided whether or not a specific threshold level is indicated in the reference request. [0176] (Tenth Embodiment) [0177] As described in the embodiments of the present invention, an email is transmitted to the local maintenance provider E when an expectancy exceeds the predetermined threshold. Such an email transmission may be controlled in accordance with a contract made between the hospital A and the CT manufacturer F or the local maintenance provider E. [0178] Turning now to FIG. 16, which is a table showing an exemplary relationship between types of contracts and email transmission rules including what is instructed in the email according to a tenth embodiment of the present invention. [0179] In FIG. 16, the maintenance necessity is categorized into four levels including three abnormality levels and a normal level regarding operations of the CT apparatus 1. The three abnormality levels are ‘high’, ‘medium’, and ‘low’. Contract 1 aims at reducing as many risks as possible which causes affections against operations of the CT apparatus 1, such as, for example, CT examinations. An amount of the contract 1 is high. Even when the abnormality level is low, an email is transmitted to the local maintenance provider E so as to give a notice of the current situation. In contrast, contract 2 has some risk. When the abnormality level is low, no email is transmitted to the local maintenance provider E. An amount of the contract 2 is, however, reasonable. [0180] Under the condition in the table shown in FIG. 16, operations of the medical equipment management apparatus 6 will be described with reference to FIG. 17. FIG. 17 is a flowchart showing a fourth example modifying a part of the flowchart shown in FIG. 9 according to a tenth embodiment of the present invention. There is no figure showing an example modifying a part of the flowchart shown in FIG. 11 according to the tenth embodiment of the present invention. However, a flowchart similar to that shown in FIG. 17 is also applied as a modification of a part of the flowchart shown in FIG. 11. [0181] In the tenth embodiment, the table shown in FIG. 17 is stored, for example, in the determination unit 64. After an expectancy is predicted, the expectancy is first compared to a high threshold level corresponding to the abnormality level ‘high’ (step 1701). [0182] When the expectancy is determined to exceed the high threshold level, an email having a first content is transmitted to at least the PC 7 provided in the local maintenance provider E by the email unit 671 (step 1702). The first content may be a message instructing an urgent replacement of a part of the CT apparatus 1 regarding the expectancy. This email is transmitted whether it is the contract 1 or 2. [0183] When the expectancy is determined not to exceed the high threshold level in step 1701, the expectancy is then compared to a medium threshold level corresponding to the abnormality level ‘medium’ (step 1703). When the expectancy is determined to exceed the medium threshold level, an email having a second content is transmitted to at least the PC 7 by the email unit 671 (step 1704). The second content may be a message instructing a replacement of a part of the CT apparatus 1 regarding the expectancy in the next regular maintenance service. This email is transmitted whether it is the contract 1 or 2. [0184] When the expectancy is determined not to exceed the medium threshold level in step 1703, a type of contract is determined (step 1705). When the type of contract is determined to be the contract 1, the expectancy is further compared to a low threshold level corresponding to the abnormality level ‘low’ (step 1706). When the expectancy is determined to exceed the low threshold level, an email having the second content is transmitted to at least the PC 7 by the email unit 671 (step 1704). When the type of contract is determined not to be the contract 1 (i.e., determined to be a contract B) in step 1705, no email is transmitted. [0185] A CC (carbon copy) of the email to the PC 7 may be transmitted to the PC 4 and/or others. This lets the user and/or other hospital staff know that the same email is transmitted to the local maintenance provider E. Further, the user and/or other hospital staff can see the current situation of the CT apparatus 1 and take necessary actions and preparations for the situation. Instead of the CC, an email with an original message may be transmitted to the PC 4 and/or others. [0186] (Fourth Modification) [0187]FIG. 18 is a flowchart showing a first example modifying a part of the flowchart shown in FIG. 18. In the flowchart shown in FIG. 17, the email having the second content is transmitted when the expectancy is determined to exceed the low threshold level in step 1706. As shown in FIG. 18, however, with such a determination, an email having a third content may be transmitted by the email unit 671, instead of the email having the second content (step 1801). The third content is different from the first and second contents. A flowchart similar to that shown in FIG. 18 is also applied as a modification of a part of the flowchart shown in FIG. 11. [0188] Despite the flowcharts in FIG. 17 or 18, a type of contract may be determined first. After the determination, an expectancy predicted may be compared to predetermined threshold levels in accordance with a flowchart regarding the determined contract. [0189] According to the tenth embodiment and the fourth modification, the hospital A can choose a contract type according to a cost effectiveness and operations although there may be some risk as described above in a lower amount of contract. The contract type may be changeable by the hospital A, for example, through the WWW browser over the Internet web site. [0190] (Eleventh Embodiment) [0191] The CT apparatus 1 will now be described with reference to FIGS. 19 to 22. The CT apparatus 1 according to an eleventh embodiment of the present invention has an urgent response feature of managing the CT apparatus 1 to operate properly for the time being in case of abnormality occurrence. FIG. 19 is an illustration showing an exemplary overview of the CT apparatus 1 according to the eleventh embodiment of the present invention. [0192] As shown in FIG. 19, the CT apparatus 1 includes a gantry 191, a specimen couch 192, and a console unit 193. The gantry 191 has an opening 194 where radiography is implemented. The specimen couch 192 is placed in front of the gantry 191, and has a table 195 where a specimen lies. The gantry 191 and the specimen couch 192 are controlled from the console unit 193. Further, a height of the specimen couch 192 is adjusted, if necessary, by operations in the console unit 193. The table 195 is slid towards and away from the gantry 191 by operations in the console unit 193. Therefore, the specimen lying on the table 195 is inserted into the opening 194 in the radiography. The console unit 193 controls components of the CT apparatus 1 systematically. Further, the console unit 193 has an input device 196 and a monitor 197. The input device 196 is, for example, equipped with a keyboard and/or a pointing device, such as a mouse, a trackball, a joystick, and/or the like. The console unit 193 accommodates a control unit which will be described later. [0193] Next, FIG. 20 is a schematic diagram showing further exemplary details of the CT apparatus 1 according to the eleventh embodiment of the present invention. [0194] As shown, the gantry 191 includes a fixed part 201 and a rotation part 202. The rotation part 202 is supported by the fixed part 201 and is allowed to rotate around the specimen inserted in the opening 194. The rotation part 202 is provided with an X-ray tube 203 and an X-ray detector 204 opposing the X-ray tube 203. Therefore, the specimen lying on the table 195 is placed between the X-ray tube 203 and the X-ray detector 204 in the opening 194. An X-ray radiated from the X-ray tube 203 is an X-ray beam in a conical form. The radiated X-ray is collimated by a slit (or a collimator) provided nearby the X-ray tube 203 so as to be formed in a desired size. The collimated sectorial X-ray is exposed to the specimen. Also, the X-ray transmitted through the specimen (an X-ray resulting from the X-ray radiation) is detected by the X-ray detector 204. The X-ray detector 204 has a plurality of detecting elements aligned in a one-dimensional form. Further, the X-ray detector 204 may alternatively have a plurality of detecting elements arrayed in a two-dimensional form. [0195] The X-ray tube 203 and the X-ray detector 204 are fixed on the rotation part 202 and so continuously rotated around the specimen. The rotation part 202 is driven by a rotation driving unit 205 based on control signals supplied from a control unit 206. In addition, the specimen couch 192 also includes a couch control unit 207 controlling, for example, the table 195 based on couch control signals supplied from the control unit 206. The couch control unit 207 controls the table 195 to move to a predetermined slice position by a predetermined distance intermittently or to move over a predetermined scan range continuously. [0196] The X-ray tube 203 is connected to a high voltage generator 208. The high voltage generator 208 determines an X-ray tube current, an X-ray tube voltage, and the like to be supplied to the X-ray tube 203 on the basis of X-ray control signals supplied from the control unit 206. Accordingly, the X-ray tube 203 radiates the X-ray at predetermined timings. [0197] The X-ray detector 204 is connected to a data acquisition system (hereinafter referred to as a DAS) 209. Further, the DAS 209 acquires projection data reflecting an X-ray transmission factor of each X-ray pulse obtained from the X-ray detector 204 on the basis of data acquisition control signals supplied from the control unit 206. The DAS 209 includes an integrator and an analog to digital converter (hereinafter referred to as an A/D converter) although the integrator and the A/D converter are not shown in FIG. 20. The integrator temporally integrates signals output from each detecting element of the X-ray detector 204, and the A/D converter converts signals output from the integrator into digital signals. [0198] In the CT apparatus 1 configured as described above, data transmitted between the fixed part 201 and the rotation part 202 are amplified by amplifying units provided in a data transmission system. The data transmission system includes transmission systems and reception systems. Further, one of the reception systems is provided in the fixed part 201. The reception system includes an amplifying unit for amplifying detection data signals transmitted from a transmission system provided in the rotation part 202. Another reception system is provided in the rotation part 202 and includes another amplifying unit for amplifying control signals for controlling, for example, the X-ray tube 203 and the rotation part 202, which are transmitted from a transmission system provided in the fixed part 201. In addition, the transmission between the fixed part 201 and the rotation part 202 is, for example, made in an optical signal form according to the eleventh embodiment of the present invention. [0199]FIG. 21 is a block diagram showing an exemplary configuration of the amplifying unit provided in the fixed part 201 or the rotation part 202 according to the eleventh embodiment of the present invention. As shown, the amplifying unit includes a photo receiving unit 210, a clock generator 220, a bias voltage control unit 230, and an amplitude voltage control unit 240. [0200] The photo receiving unit 210 includes a photoelectric conversion device 211, a preamplifier 212, and a limiting amplifier 213. The photoelectric conversion device 211 includes a photodiode, for example. The photoelectric conversion device 211 receives optical signals transmitted from an electric-photo conversion device, such as a laser diode, for converting electric signals into optical signals. The photoelectric conversion device 211 then converts the received optical signals into electric signals. Further, the converted electric signals may be transmitted at a speed of 500 Mbps, for example. Since the electric signals output from the photoelectric conversion device 211 are very weak, the preamplifier 212 amplifies such weak signals. The limiting amplifier 213 further amplifies signals amplified by the preamplifier 212 so as to obtain signals with a predetermined amplitude. [0201] The clock generator 220 generates clock signals synchronized with clock signals included in the optical signals received by the photoelectric conversion device 211. The generated clock signals are used for synchronizing operation timings of correction units which will be described later with the optical signals. [0202] The bias voltage control unit 230 includes a bias voltage level monitor 231, a bias level correction section 232, and an alarm device 233. The bias voltage level monitor 231 monitors a bias voltage level of the preamplifier 212. In addition, the bias level correction section 232 applies a positive feedback to a bias circuit of the preamplifier 212 when the monitored bias voltage level is lower than a predetermined bias threshold. Accordingly, the bias voltage level is kept to be a normal operation level. Also when the monitored bias voltage level is lower than the predetermined bias threshold, the alarm device 233 generates warning signals for an audible alarm, a warning light, a warning display, and/or the like. [0203] Similar to the bias voltage control unit 230, the amplitude voltage control unit 240 includes an amplitude voltage level monitor 241, an amplitude level correction section 242, and an alarm device 243. The amplitude voltage level monitor 241 monitors an amplitude voltage level of an input of the limiting amplifier 213. Also, the amplitude level correction section 242 applies a positive feedback to the input of the limiting amplifier 213 when the monitored amplitude voltage level is lower than a predetermined amplitude threshold. Accordingly, the amplitude voltage level of the input of the limiting amplifier 213 is kept to be a normal operation level. Also, when the monitored amplitude voltage level is lower than the predetermined amplitude threshold, the alarm device 243 generates warning signals for an audible alarm, a warning display, and/or the like. [0204] Exemplary basic operations of the photo receiving unit 210 are as follows. The photoelectric conversion device 211 receives optical signals transmitted from the electric-photo conversion device. When the electric-photo conversion device is provided in the transmission system of the rotation part 202, the photoelectric conversion device 211 is in the reception system of the fixed part 201. On the other hand, when the electric-photo conversion device is provided in the transmission system of the fixed part 201, the photoelectric conversion device 211 is in the reception system of the rotation part 202. [0205] The received optical signals are then converted to electric signals in the photoelectric conversion device 211. The converted electric signals are amplified in the preamplifier 212, and the amplified electric signals are further amplified in the limiting amplifier 213 so as to have a predetermined level. The signals amplified in the limiting amplifier 213 are provided to the following units. [0206] The preamplifier 212 and the limiting amplifier 213 will deteriorate after being used a period of time so that they cannot keep their normal characteristics or normal operations. When such deterioration occurs, the above described correction is useful so as to keep a predetermined amplifying level of the preamplifier 212 and/or a predetermined amplifying level of the limiting amplifier 213, for the time being, as a result of the monitoring. Simultaneously, when such deterioration occurs, the user of the CT apparatus 1, such as a radiological technologist, is informed of the deterioration by the alarm device 233 (243). With the above described correction, a current examination being performed by the CT apparatus 1 will be completed without any problem. This functions as a first aid until a proper fix is implemented in a maintenance service. [0207] Next, detailed operations of the CT apparatus 1 will be described with reference to FIG. 22. FIG. 22 is a flowchart showing a exemplary operation of the CT apparatus 1 according to the eleventh embodiment of the present invention. [0208] As described above, optical signals transmitted from the electric-photo conversion device or the like are received by the photoelectric conversion device 211. The received optical signals are converted into electric signals in the photoelectric conversion device 211 (step 2201). Further, the converted signals are provided to and amplified by the preamplifier 212 (step 2202). A bias voltage level of the preamplifier 212 is constantly monitored by the bias voltage level monitor 231, and the monitored bias voltage level is compared to a predetermined bias threshold (step 2203). When the monitored bias voltage level is lower than the predetermined bias threshold as a result of the comparison in step 2203, the bias level correction section 232 applies a positive feedback to a bias circuit of the preamplifier 212 so that the bias voltage level is kept at a normal operation level (step 2204). Also when the monitored bias voltage level is lower than the predetermined bias threshold, the alarm device 233 generates the warning signals (step 2205). [0209] When the monitored bias voltage level is equal to or greater than the predetermined bias threshold, the bias voltage level correction is not made by the bias level correction section 232. By repeating the above correction when it is needed, subsequent converted signals may be amplified by the preamplifier 212 with a bias voltage level equal to or greater than the predetermined bias threshold. [0210] The signals amplified by the preamplifier 212 are provided to and amplified by the limiting amplifier 213 (step 2206). An amplitude voltage level of an input of the limiting amplifier 213 is constantly monitored by the amplitude voltage level monitor 241, and the monitored amplitude voltage level is compared to a predetermined amplitude threshold (step 2207). [0211] When the monitored amplitude voltage level is lower than the predetermined amplitude threshold as a result of the comparison in step 2207, the amplitude level correction section 242 applies a positive feedback to the input of the limiting amplifier 213 so that the amplitude voltage level is kept at a normal operation level (step 2208). Also when the monitored amplitude voltage level is lower than the predetermined amplitude threshold, the alarm device 243 generates the warning signals (step 2209). [0212] When the monitored amplitude voltage level is equal to or greater than the predetermined amplitude threshold, the amplitude voltage level correction is not made by the amplitude level correction section 242. By repeating the above correction when it is needed, subsequent signals amplified in the preamplifier 212 may be amplified by the limiting amplifier 213 with an amplitude voltage level equal to or greater than the predetermined amplitude threshold. This results in providing the following units with signals having a predetermined level. [0213] In the above operations, the signals converted by the photoelectric conversion device 211 are synchronized with predetermined clock signals. Therefore, it is necessary to synchronize a timing of signals to be corrected by the bias level correction section 232 and a timing of signals to be corrected by the amplitude level correction section 242 with the predetermined clock signals. Since transmitted signals include their clock signals, the clock generator 220 generates clock signals synchronized with the clock signals included in the optical signals received by the photoelectric conversion device 211. The generated clock signals are supplied to the bias level correction section 232 and the amplitude level correction section 242 so as to synchronize their operations timings. [0214] According to the eleventh embodiment of the present invention, it is possible to know, at an early stage, about deterioration of characteristics of active devices due to aging. The active devices are, for example, devices included in the amplifying unit, such as the preamplifier 212 and the limiting amplifier 213. Since an alarm is issued when a characteristic has become below a predetermined threshold, it is possible to request the maintenance personnel in the local maintenance provider E to implement necessary actions, such as replacing or fixing the device, immediately. From another point of view, until such necessary actions, the CT apparatus 1 may be able to maintain a normal performance as a first aid since the bias voltage level and/or the amplitude voltage level are kept to be normal operation levels by the bias voltage control unit 230 and/or the amplitude voltage control unit 240. Therefore, at least a current radiography can be completed even if the deterioration occurs during the radiography. The specimen can also avoid unnecessary X-ray exposure which would be caused by reradiography. [0215] When there is two or more amplifying units, an alarm device included in each of the units may have an LED (light emitting diode) and the LED may be lit when a monitored voltage level is lower than a predetermined threshold. This may make it easier for the maintenance personnel to identify which unit to fix. All of the LEDs may be centralized in the console unit 193 in a distinguishable manner so that the maintenance personnel can identify which unit to fix more quickly (at a glance). Such identification leads to identifying what is wrong or what needs to be done. [0216] The features described above may also be applied to other types of units than the amplifying units. In addition, the amplifying units and/or the other types of units are not limited to a part of the CT apparatus 1, but may also be a part of other types of equipment including, but not limited to, medical equipment, such as an X-ray diagnosis apparatus, a magnetic resonance imaging apparatus, a nuclear medical imaging apparatus, an ultrasound diagnosis apparatus, an endoscope apparatus, and the like. Further, signals to be amplified or processed in another manner are not limited to signals converted from optical signals, but may also be signals converted from a pressure, such as, for example, a hydraulic pressure and a wind pressure. Further, the signals may also be based on vibration. The signals are also not limited to what are transmitted in a non-contact manner, but are also applied to a physically connected transmission. [0217] In addition, if there is an enough space for mounting a backup device for, for example, the preamplifier 212 and the limiting amplifier 213, such a backup device may be replaced with a currently-used device when the characteristic of the currently-used device deteriorates and has become below a predetermined threshold. This mounting may also be applied when a cost increase is allowed. The device may also be rendered normally operative in this replacement. [0218] (Twelfth Embodiment) [0219] Although the CT apparatus 1 described in the eleventh embodiment has a feature of trying to maintain a normal operation for itself, a better operation of the CT apparatus 1 may be realized under the management of the medical equipment management apparatus 6. A relationship between the CT apparatus 1 described in the eleventh embodiment and the medical equipment management apparatus 6 will be described with reference to FIG. 23. [0220]FIG. 23 is a flowchart showing a relationship between an operation flow of the CT apparatus 1 and an operation of the medical equipment management apparatus 6 according to a twelfth embodiment of the present invention. [0221] In FIG. 23, steps 2301 and 2302 correspond to the steps 2201 and 2202 in FIG. 22. Also steps 2304 to 2307 correspond to the steps 2203 to 2206 in FIG. 22. Further, steps 2309 to 2311 correspond to the steps 2207 to 2209 in FIG. 22. Still further, steps 2321 to 2329 correspond to the steps 901 to 909 in FIG. 9. Therefore, a detailed explanations of these steps is omitted. [0222] In the CT apparatus 1, a bias voltage level of the preamplifier 212 is constantly monitored by the bias voltage level monitor 231. The monitored bias voltage level is provided to the medical equipment management apparatus 6 through the service processor 2 regularly, at any given time, or in response to a predetermined trigger event, such as requests from the medical equipment management apparatus 6 (step 2303). While provided to the medical equipment management apparatus 6, the monitored bias voltage level is also compared to a predetermined bias threshold in step 2304. [0223] In the medical equipment management apparatus 6, the bias voltage level provided from the CT apparatus 1 is received as parameter data by the reception unit 60. Such a reception is repeated in accordance with the timing provided by the service processor 2. As a result of the repeated reception, an expectancy regarding the bias voltage level of the preamplifier 212 is predicted by calculation based on the received bias voltage levels (i.e., parameter data) in step 2324. The predicted expectancy is compared to a predetermined bias expectancy threshold in step 2325. [0224] The predetermined bias expectancy threshold may be, but does not have to be, identical to the predetermined bias threshold. This depends on each value to be set as each of the predetermined thresholds. [0225] Regarding an amplitude voltage level of the limiting amplifier 213 in the CT apparatus 1, it is constantly monitored by the amplitude voltage level monitor 241. The monitored amplitude voltage level is provided to the medical equipment management apparatus 6 through the service processor 2 regularly, at any given time, or in response to a predetermined trigger event, such as, for example, requests from the medical equipment management apparatus 6 (step 2308). While provided to the medical equipment management apparatus 6, the monitored amplitude voltage level is also compared to a predetermined amplitude threshold in step 2309. [0226] In the medical equipment management apparatus 6, the amplitude voltage level provided from the CT apparatus 1 is also received as parameter data by the reception unit 60. Such a reception is repeated in accordance with the timing provided by the service processor 2. As a result of the repeated reception, an expectancy regarding the amplitude voltage level of the limiting amplifier 213 is predicted by calculation based on the received amplitude voltage levels (i.e., parameter data) in step 2324. The predicted expectancy is compared to a predetermined amplitude expectancy threshold in step 2325. [0227] The predetermined amplitude expectancy threshold may be, but does not have to be, identical to the predetermined amplitude threshold. This depends on each value to be set as each of the predetermined thresholds. [0228] In the medical equipment management apparatus 6, signals amplified by the limiting amplifier 213 are processed in the following units or sections (step 2312). The alarm devices 233 and 243 may not be provided or may not have to generate the warning signals in steps 2306 and 2311 if emails are transmitted to the PC 3 provided in the department of radiology in the hospital A. Further, the correction operations in steps 2304 to 2305 and/or steps 2309 to 2310 may be repeated so as to maintain a normal operation of the CT apparatus 1 even if the deterioration occurs in the preamplifier 212 and/or the limiting amplifier 213. The correction operations may continue until the maintenance service is implemented on the preamplifier 212 and/or the limiting amplifier 213 according to the email or a result of the reference request. [0229] In the embodiments of the present invention, the medical equipment management apparatus 1 may have a random access memory (RAM), which can receive and store computer programs and applications as computer readable instructions in a temporary and/or non-volatile state. The medical equipment management apparatus may further have a hard disk drive as part of the units for reading from and writing to a hard disk, a magnetic disk drive for reading from and writing to a magnetic disk, and/or an optical disk drive for reading from and writing to an optical disk (such as a CD, CDR, CD-RW, DVD, or other optical device). Those skilled in the art will appreciate that one or more of such memory, drives, and their respective media are examples of a computer program product for storing computer readable instructions, which when executed, may implement an embodiment of the present invention. [0230] Accordingly, a medical equipment management apparatus which does not incorporate features of embodiments of the present invention can benefit the features as long as the medical equipment management apparatus is equipped with a feature of receiving and storing parameter data regarding a medical equipment as well as a feature of reading and performing a computer readable program. [0231] Further, in the embodiments of the present invention described above, the probable date is only provided in response to the reference request. However, such a probable date may also be included in the email. The email may be transmitted when the probable date is within a predetermined period from a date of the determination. The email may also be transmitted in accordance with a relationship between the expectancy on the probable date and the predetermined threshold (which threshold level of the predetermined threshold). [0232] For example, when the probable date represents a date when the expectancy becomes identical to the dangerous level of the predetermined threshold, an email including a message with information of the probable date may be transmitted to the PC 7 provided in the local maintenance provider E. The message may instruct the maintenance personnel to go to the hospital A and implement a maintenance service by one month prior to the probable date. Also when the probable date represents a date when the expectancy becomes identical to the standard level of the predetermined threshold, an email including a message with information of the probable date may be transmitted to the PC 7 provided in the local maintenance provider E. The message may instruct the maintenance personnel to implement a maintenance service in the next regular maintenance if the maintenance is scheduled by the probable date and, otherwise, to implement a maintenance service by two months prior to the probable date. [0233] On the occasion of the expectancy prediction, there is a possibility that a parameter data has already shown a value greater than the predetermined threshold. Particularly, when a parameter data exceeds than the dangerous level, it is determined that a trouble has already occurred. It is conceivable to transmit an email instructing the maintenance personnel to go to the hospital A and fix the trouble within two hours, for example. Similarly, when a parameter data does not exceed the dangerous level but the standard level, it is determined to be a dangerous situation. It is conceivable to transmit an email instructing the maintenance personnel to go to the hospital A and fix the trouble within a few days, for example. [0234] The embodiments of the present invention described above are examples described only for making it easier to understand the present invention, and are not described for the limitation of the present invention. Consequently, each component and element disclosed in the embodiments of the present invention may be redesigned or modified to its equivalent within a scope of the present invention. Furthermore, any possible combination of such components and elements may be included in a scope of the present invention as long as an advantage similar to those obtained according to the above disclosure in the embodiments of the present invention is obtained. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5680025 *Oct 7, 1994Oct 21, 1997Csi Technology, Inc.Proactive motor monitoring for avoiding premature failures and for fault recognitionUS5706411 *Nov 9, 1992Jan 6, 1998Microsoft CorporationPrinter status user interface and methods relating theretoUS5786994 *Nov 23, 1994Jul 28, 1998Imation Corp.Performance monitoring system and method for a laser medical imagerUS5874960 *Jul 5, 1995Feb 23, 1999Microsoft CorporationMethod and system for sharing applications between computer systemsUS6212256 *Nov 25, 1998Apr 3, 2001Ge Medical Global Technology Company, LlcX-ray tube replacement management systemUS6381557 *Nov 25, 1998Apr 30, 2002Ge Medical Systems Global Technology Company, LlcMedical imaging system service evaluation method and apparatusUS6735549 *Mar 28, 2001May 11, 2004Westinghouse Electric Co. LlcPredictive maintenance display systemUS6799154 *May 25, 2000Sep 28, 2004General Electric ComapnySystem and method for predicting the timing of future service events of a productUS6832199 *Nov 26, 1999Dec 14, 2004Ge Medical Technology Services, Inc.Method and apparatus for retrieving service task lists from remotely located medical diagnostic systems and inputting such data into specific locations on a tableUS6970804 *Dec 17, 2002Nov 29, 2005Xerox CorporationAutomated self-learning diagnostic systemUS7032132 *Jun 6, 2002Apr 18, 2006Kabushiki Kaisha ToshibaReproduction test service apparatus for medical systems, maintenance support information management apparatus, X-ray CT system, and maintenance service center apparatus* Cited by examinerNon-Patent CitationsReference1 *Lie, An Algorithm for Preventive Maintenance Policy, 1986, Reliability, IEEE Transactions on, Volume: 35, Issue: 1, Page(s): 71- 752 *Ricq, Study of CdTe and CdZnTe detectors for X-ray computed tomography, Nuclear Instruments and Methods in Physics Research Section A: Accelerators,Spectrometers,Detectors and Associated Equipment Volume 458, Issues 1-2, 1 February 2001, Pages 534-543* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS6912481 *Mar 14, 2003Jun 28, 2005Ge Medical Systems, Inc.Medical equipment predictive maintenance method and apparatusUS6976954 *Jun 28, 2002Dec 20, 2005Pentax CorporationEndoscope systemUS7451002 *Jan 6, 2006Nov 11, 2008Ge Medical Systems Global Technology Company, LlcAutomated generation of transfer functions based upon machine dataUS7828794 *Aug 25, 2005Nov 9, 2010Covidien AgHandheld electrosurgical apparatus for controlling operating room equipmentUS8121856 *Jun 27, 2006Feb 21, 2012Hill-Rom Services, Inc.Remote access to healthcare device diagnostic informationUS8260867Mar 23, 2006Sep 4, 2012Shimadzu CorporationData management system for an analyzing apparatusUS8351566Dec 8, 2009Jan 8, 2013Kabushiki Kaisha ToshibaPET deviceUS8483461 *Sep 21, 2009Jul 9, 2013Koninklijke Philips Electronics N.V.Diagnostic imaging system and methodUS20040181368 *Mar 14, 2003Sep 16, 2004Breunissen John R.Medical equipment predictive maintenance method and apparatusUS20110166440 *Sep 21, 2009Jul 7, 2011Koninklijke Philips Electronics N.V.Diagnostic imaging system and method* Cited by examinerClassifications U.S. Classification705/2, 702/182International ClassificationG06Q10/00Cooperative ClassificationG06Q50/22, G06Q10/06European ClassificationG06Q10/06, G06Q50/22Legal EventsDateCodeEventDescriptionMar 30, 2004ASAssignmentOwner name: KABUSHIKI KAISHA TOSHIBA, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SAWANAGA, YUUJI;TAKADA, YOICHI;IKEDA, SATOSHI;REEL/FRAME:015157/0443Effective date: 20040109Owner name: TOSHIBA MEDICAL SYSTEMS CORPORATION, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SAWANAGA, YUUJI;TAKADA, YOICHI;IKEDA, SATOSHI;REEL/FRAME:015157/0443Effective date: 20040109RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services