US20210073417A1 - Case storage system - Google Patents
Case storage system Download PDFInfo
- Publication number
- US20210073417A1 US20210073417A1 US16/743,277 US202016743277A US2021073417A1 US 20210073417 A1 US20210073417 A1 US 20210073417A1 US 202016743277 A US202016743277 A US 202016743277A US 2021073417 A1 US2021073417 A1 US 2021073417A1
- Authority
- US
- United States
- Prior art keywords
- case
- terminal device
- data
- server device
- upload
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
- G06F21/6254—Protecting personal data, e.g. for financial or medical purposes by anonymising data, e.g. decorrelating personal data from the owner's identification
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H10/00—ICT specially adapted for the handling or processing of patient-related medical or healthcare data
- G16H10/60—ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H30/00—ICT specially adapted for the handling or processing of medical images
- G16H30/20—ICT specially adapted for the handling or processing of medical images for handling medical images, e.g. DICOM, HL7 or PACS
Definitions
- the present invention relates to a system for storing case data.
- case data is shared among many persons, for example, in the case where the case data is stored in a server device on the Internet for a research purpose and shared, not only data required for case research but also information on personal privacy are transmitted and stored.
- the case data is transmitted in the server device or the like after the information on the privacy is deleted at the time of the transmission. In this way, the case data can be transmitted and stored while the privacy is protected.
- Patent Document 1 it is required to prepare in advance a special function to delete a privacy item for a terminal device on the transmission side. Thus, there is a problem that the safe transmission cannot be achieved by the terminal device without such a function.
- the privacy item has to be deleted by the server device or the like on a reception side. While such a method has an advantage that the case data can be transmitted from any type of the terminal device, there is a problem that the privacy item is contained in the transmitted data, which develops a risk.
- the present invention solves a problem as described above and therefore has a purpose of providing a system capable of transmitting/storing case data to/in a server device from any type of a terminal device without a risk of leakage of a privacy item.
- a case storage system is a case storage system including a case server device and a terminal device.
- the case server device includes: upload preparation means that receives a request for an upload command related page from the terminal device and transmits said upload command related page and a mask processing program to said terminal device; case transmission means that receives a case request from the terminal device and transmits masked case data recorded in a recording section to said terminal device; and recording means that records the transmitted masked case data in the recording section.
- the terminal device includes: upload command related page request means that transmits the upload command related page request to the case server device; display means that receives and displays the upload command related page request, which is transmitted from the case server device in response to the upload command related page request, on a display section, and displays the masked case data, which is transmitted from the case server device in response to the case request, on the display section; mask processing program recording means that receives the mask processing program, which is transmitted from the case server device in response to the upload command related page request, and records the mask processing program at least temporarily in the recording section; and case data transmission means that transmits the masked case data, in which specified privacy information in the case data is masked by the mask processing program, to the case server device when receiving upload command input for uploading the case data to the case server device on the basis of the upload command related page.
- the mask processing program is not transmitted until uploading is actually commanded. Therefore, it is possible to eliminate wasteful transmission processing.
- masking is performed by deleting an item itself, deleting a content of the data, or replacing the content of the data with a masking character.
- masking is performed by at least masking the item such as a patient's name, birth date, medical facility information, or primary doctor information among the items of the case data.
- the case data is DICOM data.
- the case storage server includes: upload preparation means that receives a request for an upload command related page from a terminal device and transmits said upload command related page and a mask processing program to said terminal device; and recording means that records the transmitted masked case data in a recording section.
- steps S 60 , S 61 correspond to the “upload preparation means”.
- step S 53 corresponds to the “case transmission means”.
- step S 62 corresponds to the “recording means”.
- step S 10 corresponds to the “upload command related page request means”.
- step S 6 corresponds to the “display means”.
- step S 12 corresponds to the “mask processing program recording means”.
- step S 16 corresponds to the “case data transmission means”.
- the “upload command related page” is a concept that includes not only a page provided with an upload command button but also a page having a direct or indirect link to the upload command button among pages recorded in the case server device.
- the “program” is a concept that includes not only a program that can directly be executed by a CPU but also a program in a source format, a program subjected to compression processing, an encrypted program, and the like.
- FIG. 1 is a functional configuration diagram of a case storage system according to an aspect of the present invention.
- FIG. 2 is a system configuration diagram of the case storage system.
- FIG. 3 illustrates a hardware configuration of a case server device.
- FIG. 4 illustrates a hardware configuration of a terminal device.
- FIG. 5 illustrates a flowchart of case browsing processing.
- FIGS. 6A-6C illustrate examples of a display screen on the terminal device in the case browsing processing.
- FIG. 7A illustrates a data example of a case DB 44 .
- FIG. 7B illustrates a data example of the case DB 44 .
- FIG. 8 is a flowchart of case registration processing.
- FIG. 9A illustrates an example of DICOM data.
- FIG. 9B is an example of the masked DICOM data.
- FIG. 10 is an example of a case registration screen.
- FIG. 1 is a functional configuration diagram of a case storage system according to an aspect of the present invention. Processing is executed as follows when a case is browsed from a terminal device T. Case request means 11 in the terminal device T transmits a case request to a server device S. Case transmission means 4 in the server device S receives the case request and transmits masked case data 10 recorded in a recording section 2 . Display means 12 in the terminal device T displays the received masked case data 10 on a display section 14 . In this way, of the cases stored in the server device S, the requested case can be displayed on the terminal device T.
- Processing is executed as follows when case data is uploaded from the terminal device T.
- Upload command related page request means 16 in the terminal device T transmits a request for an upload-related page to the server device S.
- Upload preparation means 6 in the server device S receives this request and transmits the upload-related page to the terminal device T.
- the display means 12 in the terminal device T displays the received upload-related page on the display section 14 .
- the upload preparation means 6 When receiving the request for the upload-related page, the upload preparation means 6 transmits a mask processing program 24 to the terminal device T.
- Mask processing program recording means 18 in the terminal device T temporarily records the received mask processing program 24 in a recording section 22 .
- Case data transmission means 20 masks privacy information in case data, which is recorded in the recording section 22 , using the above mask processing program 24 , and transmits the case data to the server device S.
- the masked case data is transmitted to the server device S even when an operator on the terminal device T side is unconscious of masking.
- Recording means S in the server device S records the received masked case data in the recording section 2 . In this way, even when a special program is not prepared on the terminal device T side in advance, it is possible to communicate and store the case data containing a masked privacy item.
- FIG. 2 illustrates a system configuration of the case storage system.
- Terminal devices T 1 , T 2 . . . Tn are connected to the case server device S via the Internet.
- the terminal devices T 1 , T 2 . . . Tn are PCs used by doctors at many different hospitals and the like.
- the cases stored in the case server device S can be browsed from each of the terminal devices T 1 , T 2 . . . Tn.
- DICOM data can be uploaded as the case data to the server device S from each of the terminal devices T 1 , T 2 . . . Tn.
- FIG. 3 illustrates a hardware configuration of the case server device S.
- Memory 32 a hard disk 34 , a DVD-RCM drive 36 , and a communication circuit 38 are connected to a CPU 30 .
- the communication circuit 38 is used to connect to the Internet.
- an operating system 40 In the hard disk 34 , an operating system 40 , a case server program 42 , and a case DB 44 are recorded.
- the case server program 42 fulfills its function in cooperation with the operating system 40 .
- These programs are recorded in a DVD-ROM 46 and are installed in the hard disk 34 via the DVD-ROM drive 36 .
- FIG. 4 illustrates a hardware configuration of the terminal device T.
- Memory 52 a keyboard/mouse 54 , a display 55 , a hard disk 56 , a DVD-ROM drive 58 , and a communication circuit 60 are connected to a CPU 50 .
- the memory 52 is a temporary storage section that functions as a work area of the CPU 50 .
- the communication circuit 60 is used to connect to the Internet.
- an operating system 62 and a terminal program 64 are recorded in the hard disk 56 .
- the terminal program 64 fulfills its function in cooperation with the operating system 62 .
- These programs are recorded in a DVD-ROM 66 and are installed in the hard disk 56 via the DVD-ROM drive 58 .
- FIG. 5 illustrates a flowchart of case browsing processing.
- a user the doctor or the like who operates the terminal device T operates the keyboard/mouse 54 of the terminal device T to input a command to access the case server device S.
- a predetermined user ID and a predetermined password are also input.
- the CPU 50 in the terminal device T accesses the case server device S (step S 1 ).
- the case server device S performs personal authentication on the basis of the transmitted user ID and the transmitted password (step S 51 ). If a result of the authentication is not OK, later processing is not executed, and the case browsing processing is terminated.
- the CPU 30 in the case server device S transmits an initial screen to the terminal device T (step S 52 ).
- the terminal device T displays this initial screen on the display 55 (step S 2 ).
- An example of the initial screen is illustrated in FIG. 6A . Menus such as case browsing and case registration are displayed.
- the terminal device T transmits a request for a case browsing screen to the server device S (step S 3 ).
- the case server device S extracts a disease name and the like from the case DB 44 recorded in the hard disk 34 , generates and transmits a case browsing screen (step S 53 ).
- non-volatile memory such as an SSD or the like may be used as an auxiliary storage device.
- FIG. 7A illustrates an example of the case DB 44 .
- the disease name, a date, the hospital, age, an examination type, an examination image, and the like are recorded in association with a case ID.
- Each of the data in this case DB 44 is basically in a DICOM data format.
- the case server device S extracts the disease name, the date, and the like from this case DB 44 so as to generate the case browsing screen on which the plural cases are listed.
- the case ID is associated with each of the cases on the case browsing screen to be transmitted
- the terminal device T displays the case browsing screen on the display 55 (step S 4 ).
- FIG. 6B illustrates the case browsing screen.
- the plural cases are displayed as a list. Although not illustrated, the cases may be searched by the disease name, an area, or the like and displayed on the list.
- the operator of the terminal device T operates the keyboard/mouse 54 to select the case, browsing of which is desired, from this case list.
- the terminal device T transmits the case request with the linked case ID to the case server device S (step S 5 ).
- the case server device S acquires the case data from the case DB 44 on the basis of the case ID contained in this case request, and transmits the case data to the terminal device T (step S 54 ).
- the terminal device T receives this case data and displays the case data on the display 55 (step S 6 ). In this way, as illustrated in FIG. 6C , the examination image and the like can be browsed on the terminal device T.
- FIG. 8 is a flowchart of case data registration processing.
- the case data (the DICOM data) that is a registration target recorded in a DVD-RoM 68 or the like is prepared in the terminal device T.
- FIG. 9A illustrates an example of the case data (the DICOM data) .
- This DICOM data is data that is output from examination equipment such as PET or SPECT.
- the output data from such examination equipment is recorded in the DVD-ROM 68 and is installed in the terminal device T.
- the output data may be transmitted from the examination equipment to the terminal device T via a LAN network or the like.
- privacy items such as a patient's name are contained in the DICOM data.
- the terminal device T is in a state where the initial screen in FIG. 6A is displayed.
- the terminal device T transmits a case registration screen request to the case server device S (step S 10 ).
- the case server device S receives this request and transmits a case registration screen to the terminal device T (step S 60 ).
- this case registration screen is displayed on the display 55 (step S 11 ).
- a file name enter area 80 in which a file name of a file to be uploaded is entered, and an upload button 82 used for uploading are provided.
- the case server device S transmits the case registration screen in step S 60 and also transmits the mask processing program (step S 61 ).
- the flowchart in FIG. 8 is illustrated such that the case registration screen and the mask processing program are separately transmitted.
- the case registration screen is transmitted in HTML (or XML)
- the mask processing program is transmitted as JavaScript® contained in the HTML at the same time. Needless to say, the case registration screen and the mask processing program may be transmitted separately.
- the terminal device T that has received the mask processing program temporarily stores this mask processing program in the memory 52 (step S 12 ).
- the operator of the terminal device T operates the keyboard/mouse 54 and enters the file name of the file to be uploaded in the file name enter area 80 on the case registration screen in FIG. 10 .
- the file may be selected by a pull-down menu or the like.
- the case data that is recorded in the DVD-ROM 68 installed in the DVD-ROM drive 58 is entered as the file to be uploaded.
- the terminal device T imports a part of the case data (the DICOM data in FIG. 9 ) as the target from the DVD-ROM 68 into the memory 52 (step S 14 ). Due to a large volume of the case data, it is difficult to import the entire case data into the memory 52 at once. Thus, the case data is partially imported just as described.
- the terminal device T starts the mask processing program, which is temporarily stored in the memory 52 , and executes mask processing of the privacy item in the case data (the DICOM data) by the mask processing program.
- the mask processing is executed with the patient's name being the privacy item.
- the recorded data is replaced with masking characters (for example, blank characters). Accordingly, even after the mask processing, data size (file size) is not changed and thus does not cause a problem for a processing program in which the change in the data size is determined as an error.
- the mask processing is executed by replacement with the masking characters.
- the mask processing may be executed by (deleting) the privacy item itself (that is, a tag) .
- the data may be deleted (for example, NULL is inserted) while the privacy item remains.
- the terminal device T transmits the masked case data to the case server device S (step S 16 ).
- the terminal device T repeatedly executes the processing in above steps S 14 to S 16 for all the items in the case data (step S 17 ).
- the masked case data (the masked DICOM data) as illustrated in FIG. 9B is transmitted from the terminal, device T to the case server device S.
- the case server device 5 that has received the masked case data (the masked DICOM data) adds the case ID to the masked case data (the masked DICOM data) and adds the masked case data with the case ID (the masked DICOM data) to the case DB 44 (step S 62 ).
- FIG. 7B illustrates the case DB 44 to which the new case data is added.
- the case data that has undergone the mask processing is transmitted and registered even when a special program for masking is prepared on the terminal device T side.
- the “patient's name” is the masking target.
- at least one of birth date, medical facility information, and primary doctor information may be set as the masking target.
- the masking target items may be determined as default in the mask processing program. Then, at the time of uploading from the terminal device T, the operator may be able to select to add (delete) the items to be masked.
- the mask processing program is temporarily stored.
- the mask processing program is deleted during transition to another processing, shut-down, or the like. That is, when the operator walks away from the case registration screen and returns to the case registration screen thereafter, the mask processing program is downloaded again.
- the downloaded mask processing program may be recorded in the hard disk or the like.
- it may be determined whether the mask processing program is already downloaded and recorded. Then, in the case where the mask processing program is already recorded, the mask processing program may not be downloaded again.
- the mask processing program is transmitted from the case server device at the same time.
- the mask processing program may be transmitted when the case server device is accessed.
- the mask processing program may be transmitted.
- the case DB 44 is recorded in the case server device.
- the case DB 44 may be recorded in another server device.
- the privacy item in which the privacy information is contained is deleted.
- a content of the privacy item may be encrypted and transmitted to the case server device S.
- a decryption key is recorded in the hard disk 34 on the terminal device T side by processing of the mask processing program 24 . In this way, even when the case data is lost in the terminal device T, this is downloaded from the case server device S and can be recovered by the decryption key.
- the DICOM data is used as the case data.
- the same can be applied to the case data in another format.
- the system is built for a purpose of browsing the stored case data.
- a system that stores the case data can also be applied for a purpose (downloading or the like) other than browsing.
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Theoretical Computer Science (AREA)
- Bioethics (AREA)
- Public Health (AREA)
- Primary Health Care (AREA)
- Epidemiology (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Nuclear Medicine, Radiotherapy & Molecular Imaging (AREA)
- Radiology & Medical Imaging (AREA)
- Medical Treatment And Welfare Office Work (AREA)
- Storage Device Security (AREA)
Abstract
Description
- The present invention relates to a system for storing case data.
- In the case where case data is shared among many persons, for example, in the case where the case data is stored in a server device on the Internet for a research purpose and shared, not only data required for case research but also information on personal privacy are transmitted and stored.
- In order to prevent this, for example, in JP-A-2005-184731, the case data is transmitted in the server device or the like after the information on the privacy is deleted at the time of the transmission. In this way, the case data can be transmitted and stored while the privacy is protected.
- However, in the related art as disclosed in
Patent Document 1, it is required to prepare in advance a special function to delete a privacy item for a terminal device on the transmission side. Thus, there is a problem that the safe transmission cannot be achieved by the terminal device without such a function. - In the case where the terminal device that cannot delete the privacy item is used, the privacy item has to be deleted by the server device or the like on a reception side. While such a method has an advantage that the case data can be transmitted from any type of the terminal device, there is a problem that the privacy item is contained in the transmitted data, which develops a risk.
- The present invention solves a problem as described above and therefore has a purpose of providing a system capable of transmitting/storing case data to/in a server device from any type of a terminal device without a risk of leakage of a privacy item.
- Characteristics of the present invention that can independently be applied will be listed below.
- (1) to (5) A case storage system according to the present invention is a case storage system including a case server device and a terminal device.
- The case server device includes: upload preparation means that receives a request for an upload command related page from the terminal device and transmits said upload command related page and a mask processing program to said terminal device; case transmission means that receives a case request from the terminal device and transmits masked case data recorded in a recording section to said terminal device; and recording means that records the transmitted masked case data in the recording section.
- The terminal device includes: upload command related page request means that transmits the upload command related page request to the case server device; display means that receives and displays the upload command related page request, which is transmitted from the case server device in response to the upload command related page request, on a display section, and displays the masked case data, which is transmitted from the case server device in response to the case request, on the display section; mask processing program recording means that receives the mask processing program, which is transmitted from the case server device in response to the upload command related page request, and records the mask processing program at least temporarily in the recording section; and case data transmission means that transmits the masked case data, in which specified privacy information in the case data is masked by the mask processing program, to the case server device when receiving upload command input for uploading the case data to the case server device on the basis of the upload command related page.
- Thus, even when special software is not prepared on the terminal device side in advance, it is possible to mask the privacy information, and upload/store the case data to/in the case server device.
- (6) In the case storage system according to the present invention,
-
- instead of receiving the upload command related page request, the upload preparation means acquires that the upload command is entered in the terminal device, and transmits the mask processing program.
- Thus, the mask processing program is not transmitted until uploading is actually commanded. Therefore, it is possible to eliminate wasteful transmission processing.
- (7) In the case storage system according to the present invention, masking is performed by deleting an item itself, deleting a content of the data, or replacing the content of the data with a masking character.
- Thus, it is possible to upload by preventing leakage of a privacy item.
- (8) In the case storage system according to the present invention, masking is performed by at least masking the item such as a patient's name, birth date, medical facility information, or primary doctor information among the items of the case data.
- Thus, it is possible to prevent leakage of the patient's name.
- (9) In the case storage system according to the present invention, the case data is DICOM data.
- Thus, it is possible to upload the DICOM data while preventing the leakage of the privacy item.
- (10) (11) The case storage server according to the present invention includes: upload preparation means that receives a request for an upload command related page from a terminal device and transmits said upload command related page and a mask processing program to said terminal device; and recording means that records the transmitted masked case data in a recording section.
- Thus, even when the special software is not prepared on the terminal device side in advance, it is possible to mask the privacy information, and upload/store the case data to/in the case server device.
- In an embodiment, steps S60, S61 correspond to the “upload preparation means”.
- In the embodiment, step S53 corresponds to the “case transmission means”.
- In the embodiment, step S62 corresponds to the “recording means”.
- In the embodiment, step S10 corresponds to the “upload command related page request means”.
- In the embodiment, step S6 corresponds to the “display means”.
- In the embodiment, step S12 corresponds to the “mask processing program recording means”.
- In the embodiment, step S16 corresponds to the “case data transmission means”.
- The “upload command related page” is a concept that includes not only a page provided with an upload command button but also a page having a direct or indirect link to the upload command button among pages recorded in the case server device.
- The “program” is a concept that includes not only a program that can directly be executed by a CPU but also a program in a source format, a program subjected to compression processing, an encrypted program, and the like.
- The features of the present invention can be described broadly as set forth above. The structures and characteristics of the present invention will be apparent from the following detailed description of the present invention together with those features, effects, and drawings.
-
FIG. 1 is a functional configuration diagram of a case storage system according to an aspect of the present invention. -
FIG. 2 is a system configuration diagram of the case storage system. -
FIG. 3 illustrates a hardware configuration of a case server device. -
FIG. 4 illustrates a hardware configuration of a terminal device. -
FIG. 5 illustrates a flowchart of case browsing processing. -
FIGS. 6A-6C illustrate examples of a display screen on the terminal device in the case browsing processing. -
FIG. 7A illustrates a data example of acase DB 44. -
FIG. 7B illustrates a data example of thecase DB 44. -
FIG. 8 is a flowchart of case registration processing. -
FIG. 9A illustrates an example of DICOM data. -
FIG. 9B is an example of the masked DICOM data. -
FIG. 10 is an example of a case registration screen. -
FIG. 1 is a functional configuration diagram of a case storage system according to an aspect of the present invention. Processing is executed as follows when a case is browsed from a terminal device T. Case request means 11 in the terminal device T transmits a case request to a server device S. Case transmission means 4 in the server device S receives the case request and transmits maskedcase data 10 recorded in arecording section 2. Display means 12 in the terminal device T displays the received maskedcase data 10 on adisplay section 14. In this way, of the cases stored in the server device S, the requested case can be displayed on the terminal device T. - Processing is executed as follows when case data is uploaded from the terminal device T. Upload command related page request means 16 in the terminal device T transmits a request for an upload-related page to the server device S. Upload preparation means 6 in the server device S receives this request and transmits the upload-related page to the terminal device T. The display means 12 in the terminal device T displays the received upload-related page on the
display section 14. - When receiving the request for the upload-related page, the upload preparation means 6 transmits a
mask processing program 24 to the terminal device T. Mask processing program recording means 18 in the terminal device T temporarily records the receivedmask processing program 24 in arecording section 22. - Case data transmission means 20 masks privacy information in case data, which is recorded in the
recording section 22, using the abovemask processing program 24, and transmits the case data to the server device S. Thus, the masked case data is transmitted to the server device S even when an operator on the terminal device T side is unconscious of masking. - Recording means S in the server device S records the received masked case data in the
recording section 2. In this way, even when a special program is not prepared on the terminal device T side in advance, it is possible to communicate and store the case data containing a masked privacy item. -
FIG. 2 illustrates a system configuration of the case storage system. Terminal devices T1, T2 . . . Tn are connected to the case server device S via the Internet. For example, the terminal devices T1, T2 . . . Tn are PCs used by doctors at many different hospitals and the like. The cases stored in the case server device S can be browsed from each of the terminal devices T1, T2 . . . Tn. - In addition, DICOM data can be uploaded as the case data to the server device S from each of the terminal devices T1, T2 . . . Tn.
-
FIG. 3 illustrates a hardware configuration of the case serverdevice S. Memory 32, ahard disk 34, a DVD-RCM drive 36, and acommunication circuit 38 are connected to aCPU 30. Thecommunication circuit 38 is used to connect to the Internet. - In the
hard disk 34, anoperating system 40, acase server program 42, and acase DB 44 are recorded. Thecase server program 42 fulfills its function in cooperation with theoperating system 40. These programs are recorded in a DVD-ROM 46 and are installed in thehard disk 34 via the DVD-ROM drive 36. -
FIG. 4 illustrates a hardware configuration of the terminaldevice T. Memory 52, a keyboard/mouse 54, adisplay 55, ahard disk 56, a DVD-ROM drive 58, and acommunication circuit 60 are connected to aCPU 50. Thememory 52 is a temporary storage section that functions as a work area of theCPU 50. Thecommunication circuit 60 is used to connect to the Internet. - In the
hard disk 56, anoperating system 62 and aterminal program 64 are recorded. Theterminal program 64 fulfills its function in cooperation with theoperating system 62. These programs are recorded in a DVD-ROM 66 and are installed in thehard disk 56 via the DVD-ROM drive 58. -
FIG. 5 illustrates a flowchart of case browsing processing. A user (the doctor or the like) who operates the terminal device T operates the keyboard/mouse 54 of the terminal device T to input a command to access the case server device S. At this time, a predetermined user ID and a predetermined password are also input. - In response to this, the
CPU 50 in the terminal device T (hereafter may simply be described as the terminal device T) accesses the case server device S (step S1). - The case server device S performs personal authentication on the basis of the transmitted user ID and the transmitted password (step S51). If a result of the authentication is not OK, later processing is not executed, and the case browsing processing is terminated.
- If the result of the authentication is OK, the
CPU 30 in the case server device S transmits an initial screen to the terminal device T (step S52). The terminal device T displays this initial screen on the display 55 (step S2). An example of the initial screen is illustrated inFIG. 6A . Menus such as case browsing and case registration are displayed. - When the operator of the terminal device T selects the case browsing, the terminal device T transmits a request for a case browsing screen to the server device S (step S3). In response to this, the case server device S extracts a disease name and the like from the
case DB 44 recorded in thehard disk 34, generates and transmits a case browsing screen (step S53). Note that, instead of thehard disk 34, non-volatile memory (such as an SSD) or the like may be used as an auxiliary storage device. -
FIG. 7A illustrates an example of thecase DB 44. The disease name, a date, the hospital, age, an examination type, an examination image, and the like are recorded in association with a case ID. Each of the data in thiscase DB 44 is basically in a DICOM data format. The case server device S extracts the disease name, the date, and the like from thiscase DB 44 so as to generate the case browsing screen on which the plural cases are listed. The case ID is associated with each of the cases on the case browsing screen to be transmitted - In response to this, the terminal device T displays the case browsing screen on the display 55 (step S4).
FIG. 6B illustrates the case browsing screen. The plural cases are displayed as a list. Although not illustrated, the cases may be searched by the disease name, an area, or the like and displayed on the list. - The operator of the terminal device T operates the keyboard/
mouse 54 to select the case, browsing of which is desired, from this case list. In response to this, the terminal device T transmits the case request with the linked case ID to the case server device S (step S5). The case server device S acquires the case data from thecase DB 44 on the basis of the case ID contained in this case request, and transmits the case data to the terminal device T (step S54). - The terminal device T receives this case data and displays the case data on the display 55 (step S6). In this way, as illustrated in
FIG. 6C , the examination image and the like can be browsed on the terminal device T. -
FIG. 8 is a flowchart of case data registration processing. When the case data is registered in thecase DB 44 of the server device S, the case data (the DICOM data) that is a registration target recorded in a DVD-RoM 68 or the like is prepared in the terminal device T. -
FIG. 9A illustrates an example of the case data (the DICOM data) . This DICOM data is data that is output from examination equipment such as PET or SPECT. Here, the output data from such examination equipment is recorded in the DVD-ROM 68 and is installed in the terminal device T. However, the output data may be transmitted from the examination equipment to the terminal device T via a LAN network or the like. - As illustrated in
FIG. 9A , privacy items such as a patient's name are contained in the DICOM data. - Referring back to
FIG. 8 , it is assumed that the terminal device T is in a state where the initial screen inFIG. 6A is displayed. Here, when the operator of the terminal device T selects the case registration, the terminal device T transmits a case registration screen request to the case server device S (step S10). The case server device S receives this request and transmits a case registration screen to the terminal device T (step S60). In the terminal device T, this case registration screen is displayed on the display 55 (step S11). - An example of the case registration screen is illustrated in
FIG. 10 . A filename enter area 80, in which a file name of a file to be uploaded is entered, and an uploadbutton 82 used for uploading are provided. - The case server device S transmits the case registration screen in step S60 and also transmits the mask processing program (step S61). The flowchart in
FIG. 8 is illustrated such that the case registration screen and the mask processing program are separately transmitted. However, in this embodiment, the case registration screen is transmitted in HTML (or XML), and the mask processing program is transmitted as JavaScript® contained in the HTML at the same time. Needless to say, the case registration screen and the mask processing program may be transmitted separately. - The terminal device T that has received the mask processing program temporarily stores this mask processing program in the memory 52 (step S12).
- The operator of the terminal device T operates the keyboard/
mouse 54 and enters the file name of the file to be uploaded in the filename enter area 80 on the case registration screen inFIG. 10 . Note that the file may be selected by a pull-down menu or the like. Here, the case data that is recorded in the DVD-ROM 68 installed in the DVD-ROM drive 58 is entered as the file to be uploaded. - Next, when the operator of the terminal device T clicks the upload
button 82, the terminal device T imports a part of the case data (the DICOM data inFIG. 9 ) as the target from the DVD-ROM 68 into the memory 52 (step S14). Due to a large volume of the case data, it is difficult to import the entire case data into thememory 52 at once. Thus, the case data is partially imported just as described. - Next, the terminal device T starts the mask processing program, which is temporarily stored in the
memory 52, and executes mask processing of the privacy item in the case data (the DICOM data) by the mask processing program. In this embodiment, the mask processing is executed with the patient's name being the privacy item. - In this embodiment, while the privacy item in the DICOM data remains, the recorded data is replaced with masking characters (for example, blank characters). Accordingly, even after the mask processing, data size (file size) is not changed and thus does not cause a problem for a processing program in which the change in the data size is determined as an error.
- In the above, the mask processing is executed by replacement with the masking characters. However, the mask processing may be executed by (deleting) the privacy item itself (that is, a tag) . Alternatively, the data may be deleted (for example, NULL is inserted) while the privacy item remains.
- Next, the terminal device T transmits the masked case data to the case server device S (step S16).
- The terminal device T repeatedly executes the processing in above steps S14 to S16 for all the items in the case data (step S17).
- As it has been described so far, the masked case data (the masked DICOM data) as illustrated in
FIG. 9B is transmitted from the terminal, device T to the case server device S. - The case server device 5 that has received the masked case data (the masked DICOM data) adds the case ID to the masked case data (the masked DICOM data) and adds the masked case data with the case ID (the masked DICOM data) to the case DB 44 (step S62).
FIG. 7B illustrates thecase DB 44 to which the new case data is added. - In this way, in regard to the case data, the case data that has undergone the mask processing is transmitted and registered even when a special program for masking is prepared on the terminal device T side.
- (1) In the above embodiment, the “patient's name” is the masking target. However, instead of this, or in addition to this, at least one of birth date, medical facility information, and primary doctor information may be set as the masking target. In addition, the masking target items may be determined as default in the mask processing program. Then, at the time of uploading from the terminal device T, the operator may be able to select to add (delete) the items to be masked.
- (2) In the above embodiment, the mask processing program is temporarily stored. Thus, the mask processing program is deleted during transition to another processing, shut-down, or the like. That is, when the operator walks away from the case registration screen and returns to the case registration screen thereafter, the mask processing program is downloaded again.
- However, in the terminal device T, the downloaded mask processing program may be recorded in the hard disk or the like. In this case, on the case registration screen, it may be determined whether the mask processing program is already downloaded and recorded. Then, in the case where the mask processing program is already recorded, the mask processing program may not be downloaded again.
- (3) In the above embodiment, when the case registration screen is transmitted, the mask processing program is transmitted from the case server device at the same time.
- However, the mask processing program may be transmitted when the case server device is accessed.
- Alternatively, when the case server device S detects that the upload
button 82 inFIG. 10 is clicked in the terminal device T, the mask processing program may be transmitted. - (4) In the above embodiment, the
case DB 44 is recorded in the case server device. However, thecase DB 44 may be recorded in another server device. - (5) In the above embodiment, as a mask processing method, the privacy item in which the privacy information is contained is deleted. However, a content of the privacy item may be encrypted and transmitted to the case server device S. In this case, a decryption key is recorded in the
hard disk 34 on the terminal device T side by processing of themask processing program 24. In this way, even when the case data is lost in the terminal device T, this is downloaded from the case server device S and can be recovered by the decryption key. - (6) In the above embodiment, the DICOM data is used as the case data. However, the same can be applied to the case data in another format.
- (7) In the above embodiment, the system is built for a purpose of browsing the stored case data. However, a system that stores the case data can also be applied for a purpose (downloading or the like) other than browsing.
- A general description of the present invention as well as preferred embodiments of the invention has been set forth above. It is to be expressly understood, however, the terms described above are for purpose of illustration only and are not intended as definitions of the limits of the invention. Those skilled in the art to which the present invention pertains will recognize and be able to practice other variations in the system, device, and methods described which fall within the teachings of this invention. Accordingly, all such modifications are deemed to be within the scope of the invention.
Claims (8)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2019164082A JP6903107B2 (en) | 2019-09-10 | 2019-09-10 | Case accumulation system |
JP2019-164082 | 2019-09-10 |
Publications (1)
Publication Number | Publication Date |
---|---|
US20210073417A1 true US20210073417A1 (en) | 2021-03-11 |
Family
ID=74851213
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/743,277 Abandoned US20210073417A1 (en) | 2019-09-10 | 2020-01-15 | Case storage system |
Country Status (3)
Country | Link |
---|---|
US (1) | US20210073417A1 (en) |
JP (1) | JP6903107B2 (en) |
CN (1) | CN112562802A (en) |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007249770A (en) * | 2006-03-17 | 2007-09-27 | Nec Corp | Personal information hiding service system |
US20120070045A1 (en) * | 2009-12-17 | 2012-03-22 | Gregory Vesper | Global medical imaging repository |
US10629311B2 (en) * | 2010-07-30 | 2020-04-21 | Fawzi Shaya | System, method and apparatus for real-time access to networked radiology data |
US8553965B2 (en) * | 2012-02-14 | 2013-10-08 | TerraRecon, Inc. | Cloud-based medical image processing system with anonymous data upload and download |
US20140109239A1 (en) * | 2012-03-30 | 2014-04-17 | Alexander Calhoun Flint | Collaborative cloud-based sharing of medical imaging studies with or without automated removal of protected health information |
JP6209962B2 (en) * | 2013-12-11 | 2017-10-11 | 富士ゼロックス株式会社 | Information processing apparatus and information processing program |
US10289868B2 (en) * | 2014-11-27 | 2019-05-14 | Siemens Aktiengesellschaft | Transmitting medical datasets |
US20180082020A1 (en) * | 2016-09-22 | 2018-03-22 | Laxmikantha Elachithaya Rajagopal | Method and device for securing medical record |
GB201617507D0 (en) * | 2016-10-14 | 2016-11-30 | Axial3D Limited | Axial3D UK |
-
2019
- 2019-09-10 JP JP2019164082A patent/JP6903107B2/en active Active
-
2020
- 2020-01-09 CN CN202010021232.0A patent/CN112562802A/en active Pending
- 2020-01-15 US US16/743,277 patent/US20210073417A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
JP2021043606A (en) | 2021-03-18 |
CN112562802A (en) | 2021-03-26 |
JP6903107B2 (en) | 2021-07-14 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7405838B2 (en) | Information processing apparatus, information processing method and print systems | |
US7849099B2 (en) | Document management method and apparatus thereof | |
US20130111353A1 (en) | Medical coordination system | |
JP4347264B2 (en) | Document management system | |
JP2009512960A (en) | Managing relationships between resources stored in the repository | |
WO2021199278A1 (en) | Method for providing electronic medical record for animal patient | |
WO2016157128A1 (en) | Method for capturing layered screen content | |
JP6095919B2 (en) | Electronic medical record screening result output device, electronic medical record screening result output method, and electronic medical record screening result output program | |
US6920482B1 (en) | Information processing apparatus, system and method | |
US20110179094A1 (en) | Method, apparatus and computer program product for providing documentation and/or annotation capabilities for volumetric data | |
US7606922B2 (en) | Information processing server, information processing system, information processing method and storage medium storing information processing program | |
US20210073417A1 (en) | Case storage system | |
JP6023520B2 (en) | Electronic medical record screening system, electronic medical record screening apparatus, electronic medical record screening method, and electronic medical record screening program | |
US20170076255A1 (en) | Medical care support system, server device and computer readable storage medium storing program | |
JP5393242B2 (en) | Data providing method and intermediate server device | |
JP2011118626A (en) | Information processing system, file management server, control method, and program | |
US10033739B2 (en) | Clinical-path management server and clinical-path management system | |
JP2006260232A (en) | Medical information processing system | |
KR101945993B1 (en) | Method and apparatus for generating medical information of object | |
JP6959501B2 (en) | Work management program, work management device and work management method | |
US20230128299A1 (en) | Cloud server, computer readable medium, and cloud system | |
WO2024089910A1 (en) | Information processing method, information processing program, information processing system | |
JP6867585B2 (en) | Work management program, work management device and work management method | |
US20230266980A1 (en) | Method for providing remote security service and server performing the same | |
US20220067305A1 (en) | Document management apparatus, document management system, and non-transitory computer readable medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: HEART ORGANIZATION CO., LTD., JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SUGAWARA, TOSHIKO;KANEUCHI, TETSUYA;REEL/FRAME:051522/0328 Effective date: 20191129 |
|
AS | Assignment |
Owner name: HEART ORGANIZATION CO., LTD., JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SUGAWARA, TOSHIKO;KANEUCHI, TETSUYA;REEL/FRAME:051721/0198 Effective date: 20191129 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |