US20160350485A1 - Method and apparatus for generating medical information of object - Google Patents

Method and apparatus for generating medical information of object Download PDF

Info

Publication number
US20160350485A1
US20160350485A1 US15/111,830 US201515111830A US2016350485A1 US 20160350485 A1 US20160350485 A1 US 20160350485A1 US 201515111830 A US201515111830 A US 201515111830A US 2016350485 A1 US2016350485 A1 US 2016350485A1
Authority
US
United States
Prior art keywords
filter
cloud
content
external
document
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
Application number
US15/111,830
Other languages
English (en)
Inventor
Seung Wook Choi
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
IRM Inc
Original Assignee
IRM Inc
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by IRM Inc filed Critical IRM Inc
Priority claimed from PCT/KR2015/001851 external-priority patent/WO2015137646A1/ko
Assigned to IRM INC. reassignment IRM INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CHOI, SEUNG WOOK
Publication of US20160350485A1 publication Critical patent/US20160350485A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • 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
    • G06F19/322—
    • 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
    • G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
    • G16H50/20—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems
    • G06F19/3437—
    • 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
    • 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
    • G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
    • G16H50/30—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for calculating health indices; for individual health risk assessment

Definitions

  • the present invention relates to a method and apparatus for generating medical information of an object, and in particular, to a method and apparatus for forming a filter that generates medical information of an object by performing a preset operation. Also, the present invention provides a method or apparatus for generating medical information of an object by using a workflow designed by using at least one filter that performs a preset operation.
  • Cloud computing refers to a computing environment based on the Internet or a network.
  • a program infrastructure may be built in a data server on the Internet and users may use on demand, through computers or mobile phones, programs stored in the data server.
  • users may use computing resources including intangible hardware and/or software, such as a cloud, through terminals or clients such as mobile phones.
  • the present invention provides a method and apparatus for generating medical information of an object. Also, the present invention provides a computer-readable recording medium having embodied thereon a program for executing the method on a computer.
  • Technical problems to be solved are not limited to the above technical problems, and there may be other technical problems.
  • a computer-readable recording medium has embodied thereon a program for executing the method on a computer.
  • An apparatus for generating information about a filter includes: a filter class setter configured to set at least one filter class corresponding to an operation for generating medical information of an object; a filter setter configured to set at least one filter included in the filter class and configured to perform the operation; and a filter condition setter configured to set at least one condition required to operate the filter.
  • a method of generating medical information of an object includes: receiving at least one first content from at least one from among external apparatuses connected to a cloud; selecting a first filter that performs an operation based on the first content from among filters respectively included in a plurality of filter classes; and performing a preset operation by using the first filter.
  • a computer-readable recording medium has embodied thereon a program for executing the method on a computer.
  • medical information of an object may be generated without a user's intervention. Also, since medical information of an object may be generated and provided based on an open platform, the medical information of the object may be provided without time and space constraints. Also, since a workflow is designed by using at least one filter that performs a preset operation, medical information of an object may be generated without a user's intervention.
  • FIG. 1 is a conceptual diagram illustrating a system for providing medical information, according to an embodiment of the present invention.
  • FIG. 2 is a diagram for explaining a system for providing medical information, according to an embodiment of the present invention.
  • FIG. 3 is a flowchart for explaining an operation of a system for providing medical information, according to an embodiment of the present invention.
  • FIG. 4 is a view illustrating a workflow according to an embodiment of the present invention.
  • FIG. 5 is a diagram for explaining an external filter, according to an embodiment of the present invention.
  • FIG. 7 is a diagram illustrating an apparatus for generating information about a filter, according to an embodiment of the present invention.
  • FIG. 8 is a flowchart illustrating a method of generating information about a filter, according to an embodiment of the present invention.
  • FIG. 9 is a diagram illustrating an apparatus for generating medical information of an object, according to an embodiment of the present invention.
  • FIG. 10 is a flowchart illustrating a method of generating medical information of an object, according to an embodiment of the present invention.
  • FIG. 1 is a conceptual diagram illustrating a system 100 for providing medical information according to an embodiment of the present invention.
  • the system 100 includes a cloud 110 and a user 130 .
  • the user 130 means an apparatus used by the user 130 and encompasses an external apparatus that may access the cloud 110 .
  • the cloud 110 may be a predetermined server to which one or more external apparatus may make access through wired/wireless communication.
  • the system 100 refers to a system that generates medical information of an object based on the cloud 110 and provides the medical information to the user 130 .
  • the object may be, but not limited to, a patient who is required to be diagnosed.
  • the system 100 may generate medical information of an object based on an open platform and may provide the medical information to the user 130 .
  • the system 100 includes a platform that provides various services 120 such as medical information search, storage, transmission, inquiry, or exchange based on the medical information standard such as Integrating the Healthcare Enterprise (IHE), Digital Imaging and Communications in Medicine (DICOM), or Health Level-7 (HL7) and the international standard such as Word Wide Web Consortium (W3C) or International Organization for Standardization (ISO).
  • IHE Integrating the Healthcare Enterprise
  • DIOM Digital Imaging and Communications in Medicine
  • HL7 Health Level-7
  • W3C Word Wide Web Consortium
  • ISO International Organization for Standardization
  • the services 120 provided by the system 100 may include a medical information providing or processing service, a tele-medicine service, a clinical decision supporting system service, a medical information storing or sharing service, a server-side computing service, and a social networking service.
  • the services 120 are not limited to the above services, and may be any service provided by the system 100 according to an embodiment of the present invention as long as a work may be done by a user by using the medical information due to the service.
  • a system 200 for providing medical information will now be explained with reference to FIG. 2 .
  • FIG. 2 is a diagram for explaining the system 200 according to an embodiment of the present invention.
  • FIG. 2 Services 210 provided by the system 200 , an external filter 220 , and an architecture 230 of a cloud are illustrated in FIG. 2 .
  • An infrastructure 2310 an internal filter 2320 , a data storage 2330 , a controller 2340 , a platform-level application programming interface (API) 2350 , a service-specific API 2360 , and a user interface 2370 are included in the architecture 230 .
  • a dataset handler 2341 , a workflow manager 2342 , a patient manager 2343 , a user manager 2344 , a group manager 2345 , and a condition manager 2346 are included in the controller 2340 .
  • a filter manager is further included in the controller 2340 .
  • Types of the services 210 are the same as those described with reference to FIG. 1 . Accordingly, a detailed explanation of the types of the services 210 will not be given.
  • the external filter 220 refers to a filter that operates outside the cloud.
  • the external filter 220 performs an operation outside a database of the cloud.
  • the external filter 220 may be included in at least one apparatus from among external apparatuses connected to the cloud.
  • information about the external filter 220 may be generated, set, changed, and deleted by the filter manager of the architecture 230 and may be transmitted to the external apparatus, or may be generated, set, changed, and deleted by the external apparatus.
  • the external filter 220 according to an embodiment of the present invention will be explained below in detail with reference to FIGS. 5 and 6 .
  • the architecture 230 of FIG. 2 is an architecture that may be constructed in the cloud 110 of FIG. 1 . Accordingly, it will be understood by one of ordinary skill in the art that general-purpose elements other than the elements illustrated in FIG. 2 may be further included.
  • the infrastructure 2310 , the data storage 2330 , the controller 2340 , the platform-level API 2350 , the service-specific API 2360 , and the user interface 2370 included in the architecture 230 of FIG. 2 may correspond to one or more processers.
  • Each processor may be an array of logic gates, or a combination of a general-purpose microprocessor and a memory storing a program that may be executed by the microprocessor. Also, it will be understood by one of ordinary skill in the art that the processor may be another type of hardware.
  • the data storage 2330 stores and manages all types of content that may be processed by the cloud.
  • the content used herein refers to any type of document including text, an image, or a video.
  • examples of the content may include all types of documents, such as images, waveforms, and measured values, which may be processed by general arithmetic units. Accordingly, content and a document in an embodiment of the present invention are described as the same concept.
  • one document may be included zero or more document sets DocSet.
  • a document may not be included in a document set or may be included in one or more document sets.
  • a specific document has to belong to one group.
  • the group used herein may refer to a group of a real organization such as a hospital or a department/division, or a virtual user set. The group will be explained below in detail.
  • An ID for identifying each document is assigned in the cloud.
  • An ID type related to a document and a definition thereof according to an embodiment of the present invention are shown in Table 1.
  • Filter UID Is an ID indicating a filter that generates the document.
  • Patient Id Is an ID indicating a patient related to the document.
  • Each of all documents according to an embodiment of the present invention has a unique ID (UID), and the UID guarantees uniqueness only in a specific group. Also, each of all documents has a unique UUID separate from the UID and guarantees uniqueness in all of the documents.
  • a document in the cloud according to an embodiment of the present invention corresponds to a document entry in an Integrating the Healthcare Enterprise (IHE) Cross Enterprise Document Sharing (XDS).
  • the dataset handler 2341 manages a document set.
  • the dataset handler 2341 generates, sets, changes, and deletes a document set.
  • the document set DocSet refers to a virtual set of real documents. Any processing in the cloud is performed in units of document sets. Also, a specific document set has to belong to one group. An ID for identifying each document set is assigned in the cloud. An ID type related to a document set and a definition thereof according to an embodiment of the present invention are shown in Table 2.
  • DocSet I is a unique ID of a document set, and is unique in a specific UID group that generates the document set.
  • DocSet I is a unique ID separate from the document set UID, and is UUID unique in all document sets. For example, there is one document set UID for a first document set whereas a document set UUID may vary whenever the first document set is transmitted (or processed).
  • DocSet Indicates a type of a document set, and is used to designate Class UID an input/output method of a filter.
  • Group UID Filter UID Indicates a filter that generates the document set.
  • Patient Id Indicates a patient related to the document set.
  • a document set in the cloud corresponds to a submission set in the IHE XDS.
  • a document set has to have one document set class DocSet Class.
  • the document set class used herein refers to a class of a document set.
  • the document set class is used to designate an input/output method of a filter, and is expressed with a unique document set class UID that is unique in the cloud.
  • the workflow manager 2342 manages a workflow that operates in the cloud.
  • the workflow manager 2342 generates, sets, changes, and deletes a workflow.
  • a workflow according to an embodiment of the present invention will be explained below in detail with reference to FIG. 4 .
  • the patient manager 2343 manages information about a patient.
  • the patient manager 2342 generates, sets, changes, and deletes patient information.
  • the patient refers to an owner of medical information or health information, and is different from a user that is another entity using the medical information.
  • the patient receives different patient numbers according to organizations (e.g., hospitals or governments). Accordingly, the patient in the cloud may be expressed with different patient numbers in a plurality of groups and the linking of the different patient numbers may indicate the same patient.
  • the user manager 2344 manages information about a user.
  • the user manager 2344 generates, sets, changes, and deletes user information.
  • the term ‘manage’ used herein includes actions of generating, changing, and deleting patient information.
  • the user refers to a user who uses services of the cloud and is different from the patient.
  • the user may be a medical staff member such as a doctor or a nurse, or may be a government official sometimes.
  • One user may belong to zero or more groups. In other words, the user may not belong to any group, or may belong to one or more groups. If the user belongs to one or more groups, the user may be given a group manager right. A right to search for and inquire about the afore-described document set may be given to an individual user.
  • a user according to an embodiment of the present invention may be authenticated by a method of the system 200 itself or may be authenticated by a service provider that provides other authentication services.
  • the group manager 2345 manages information about a group.
  • the group managers 2345 generates, sets, changes, and deletes group information.
  • the group refers to a set of users. According to a configuration, the group may refer to a group of a real organization such as a hospital or a department/division, or a virtual user set.
  • the group may be an independent group or may be a group under one higher group. Also, the group may include a plurality of users.
  • the group may give a manager right to manage the group to a specific user included in the group. In this case, the right to manage the group is inherited to sub-groups of the group. In other words, a manager of the specific group may also manage the sub-groups of the group.
  • a right to search for and inquire about a document set may be indirectly given through the group to which the user belongs. However, the right to search for and inquire about the document set is valid only in the designated group, and is not inherited to the sub-groups of the group.
  • the condition manager 2346 manages conditions set on the system 200 .
  • the condition manager 2346 generates, sets, changes, and deletes conditions.
  • the conditions may correspond to a document set condition DocSet rule and/or a filter condition.
  • the filter condition may be generated, set, changed, and deleted by the condition manager 2346 , or may be generated, set, changed, and deleted by the filter manager.
  • the document set condition refers to a condition used to automatically give a right to search for and inquire about a specific document set to a user.
  • the filter condition refers to a condition used to automatically perform an operation of a filter.
  • the internal filter 2320 or the external filter 220 may be included in the filter according to an embodiment of the present invention.
  • the internal filter 2320 performs an operation in the database of the cloud. In this case, information about the internal filter 2320 is generated, set, changed, and deleted by the filter manager of the architecture 230 .
  • a filter class, a filter condition, a filter queue, and a filter log related to the filter will now be explained in detail.
  • the filter class refers to a class of the filter, and an input/out method is expressed by using a document set class.
  • One filter class may correspond to a plurality of filters. That is, there may be various filters having the same input/output method and function.
  • An input and an output of the filter may be expressed with zero or more document set classes.
  • the filter may receive one document set and may output one document set, and may receive a plurality of documents sets and may generate a plurality of output document sets.
  • the filter may have an output function without having an input function or may have an input function without having an output function.
  • the internal filter 2320 refers to a filter that performs an operation in the database of the cloud, and may be a stored function of a database of the infrastructure 2310 .
  • the external filter 220 refers to a filter that performs an operation outside the database of the cloud and may operate by using the APIs 2350 and 2360 provided by the cloud.
  • the filter indicates an instance of the filter and indicates an actual instance of the filter expressed with a filter class. All filters having the same filter class UID may perform substantially the same function.
  • a default group and a default patient may be differently designated according to each filter.
  • the filter manger may automatically set a group of documents and a document set generated by the filter by designating a default group.
  • the filter manager may automatically set a patient of a document and a document set generated by the filter by designating a default patient.
  • the filter condition refers to at least one condition required to operate the filter. When the filter condition is satisfied, the filter automatically performs an operation. If a plurality of document sets are needed to operate the filter, a condition may be set according to each of the document sets.
  • a time when the filter performs an operation may be designated as follows.
  • an absolutely designed specific date and time e.g., Apr. 5, 2014, 03:00 P.M.
  • a predetermined period of time after the filter condition is satisfied e.g., 5 hours after the filter condition is satisfied
  • a predetermined period of time after the beginning (00:00 A.M.) of the day after the condition is satisfied e.g., assuming that the condition is satisfied on Apr. 5, 2014, 03:00 P.M., 5 hours after Apr. 6, 2014, 00:00 A.M.
  • the filter manager (or the condition manager 2346 ) registers the filter that is to perform an operation and necessary document sets in the filter queue and designates a time when the filter is to perform the operation. If the time when the filter is to perform the operation is not specified, the filter immediately performs the operation.
  • the filter queue refers to a wait queue for operating the filter.
  • the internal filter 23320 processes content of the filter queue at a designated time interval (e.g., 60 seconds).
  • the external filter 220 processes content of the filter queue according to filter procedure (FilterProc) module settings.
  • the filter log refers to a log about processing (action) of the internal filter 2320 .
  • the internal filter 2320 and the external filter 220 according to an embodiment of the present invention will be explained below in detail with reference to FIGS. 5 through 6 .
  • the user interface 2370 refers to a user interface for managing the cloud and searching for and inquiring about information.
  • the user interface 2370 may be a web-based interface.
  • the platform-level API 2350 refers to an API collection for directly interfacing between the cloud and external apparatuses.
  • the service-level API 2360 refers to an API collection based on the platform-level API 2350 for a specific service (e.g., a service A) from among the services 210 provided by the system 200 .
  • the infrastructure 2310 refers to an infrastructure for providing all of the afore-described services of the cloud.
  • the infrastructure 2310 may correspond to, but not limited to an Amazon Web Services cloud service.
  • the cloud having the architecture 230 may generate and provide medical information of an object (e.g., a patient) based on an open platform, and may provide the medical information of the object to a user without time and space constraints.
  • an object e.g., a patient
  • the cloud having the architecture 230 may generate and provide medical information of an object (e.g., a patient) based on an open platform, and may provide the medical information of the object to a user without time and space constraints.
  • FIG. 3 is a flowchart for explaining an operation of a system for providing medical information (referred to as the medical information providing system) according to an embodiment of the present invention.
  • an operation of the medical information providing system includes steps that are sequentially performed by the system 100 or 200 or the cloud 110 of FIGS. 1 and 2 . Accordingly, although omitted, the description of the medical information providing system or the cloud 110 of FIGS. 1 and 2 may apply to the operation of the medical information providing system of FIG. 3 .
  • each of the steps of FIG. 3 is performed by the ‘cloud 110 ’.
  • an entity that performs each of the steps of FIG. 3 may be any of the elements included in the architecture 230 of FIG. 2 .
  • step 310 the cloud 110 generates and sets group information.
  • the cloud 110 generates a group (hereinafter, referred to as a master group) that represents an organization that is to open a service, based on an external signal input from a user.
  • a master group represents an organization that is to open a service, based on an external signal input from a user.
  • Organizations such as real hospitals may be generated under the master group.
  • the cloud 110 may generate a group as shown in Table 3.
  • Radionet top group master group
  • SNUH primary child group medical institution
  • Radiology secondary child group department in medical institution
  • CMC primary child group medical institution
  • Cardiology secondary child group department in medical institution
  • GuroClinic primary child group medical institution
  • the cloud 110 may generate a master group Rradionet, and may generate real medical institutions such as Seoul National University Hospital (SNUH), Democratic Medical Center (CMC), and Guro Clinic as child groups under the master group Radionet. Also, after forming the real medical institutions as groups, the cloud 110 may register departments in the medical institutions as other child groups Radiology and Cardiology.
  • SNUH Seoul National University Hospital
  • CMC Catholic Medical Center
  • Guro Clinic child groups under the master group Radionet.
  • the cloud 110 may register departments in the medical institutions as other child groups Radiology and Cardiology.
  • a database table structure for storing group information is shown in Table 4.
  • Group Id Indicates an ID of a group, and sets assigning_authority_id that is one of three elements constituting a patient number to Group Id. It may be expressed by using, but not limited to, ISO OID. For example, when a medial institution code such as 82999 is given, it indicates a 999 th hospital in Korea (82). Group Id Indicates a type of the ID of the group, and sets Type assigning_authority_id_type that is one of three elements constituting the patient number to Group Id Type. When a group ID is registered by using ISO OID, ISO has to be designated. However, otherwise, self-determination may be used. For example, Group Id Type may be set to “BIS-CLOUD”.
  • step 320 the cloud 110 generates and sets user information.
  • the cloud 110 generates a user (hereinafter, referred to as a master manager) who is to manage the master group, based on an external signal input from the user.
  • the cloud 110 gives a right to manage the master group to the master manager.
  • the user may manage sub-groups of the group.
  • the master manager when the master manager has a right to manage a master group, it means that the master manager may generate a plurality of groups under the master group. Only a group manager may add a user or a patient to the group or child groups of the group.
  • a master manager bioadmin may manage both a group Radionet and child groups.
  • a group manager snuhadmin may manage a group SNUH and a group Radiology that is a child group of the group SNUH. If a separate manager is necessary for the group Radiology, a group manager snuhradioadmin may be additionally designated as shown in Table 6.
  • a user in the medical information providing system may belong to a plurality of groups.
  • the user when the user belongs to a specific group and is given a management right, the user becomes a manger of the group and, otherwise, becomes a general user.
  • the cloud 110 After a group manager is generated, the cloud 110 generates as many general users as needed and makes the general users belong to groups.
  • the user may have a plurality of authentication methods. For example, the user may log on through self authentication of the medical information providing system, or may log on by using other authentication accounts (e.g., a Google account).
  • other authentication accounts e.g., a Google account
  • a database table structure for storing user information is shown in Table 7.
  • a database table structure for setting a relationship between a group and a user is shown in Table 8.
  • step 330 the cloud 110 generates and sets patient information.
  • the cloud 110 may generate and set patient information, based on an external signal input from the user.
  • a patient may have attributes such as a patient number, a name, a sex, and a birthdate. From among the attributes, the patient number includes three parts patient_id_value, assigning_authority_id, and assigning_authority_id type. In this case, the parts assigning_authority_id and assigning_authority_id type correspond to the attributes Group Id and Group Id Type of the group, and patient_id_value indicates the patient number of the group. Accordingly, the patient in the medical information providing system according to an embodiment of the present invention belongs to only one group.
  • a database table structure for storing the patient information is shown in Table 9.
  • step 340 the cloud 110 designs a workflow based on an external signal input from a manager of the cloud 110 .
  • the workflow is the flow of an operation performed by at least one filter.
  • the medical information providing system according to an embodiment of the present invention generates medical information of an object (e.g., a patient) according to the workflow, and provides the medical information to a user.
  • An object e.g., a patient
  • a workflow will now be explained with reference to FIG. 4 .
  • FIG. 4 is a view illustrating a workflow 400 according to an embodiment of the present invention.
  • the workflow 400 designed by the cloud 110 is illustrated in FIG. 4 .
  • the workflow 400 is illustrated in FIG. 4 for convenience of explanation, the workflow 400 designed by the cloud 110 is not limited to that of FIG. 4 .
  • any workflow in which medical information of an object e.g., a patient
  • may be generated by using at least one filter belonging to at least one filter set or a single filter set and may be provided to a user may be included in the scope of the present invention without limitations.
  • a circular portion in the workflow 400 of FIG. 4 refers to a document set class DSC. At least one document may be included in one document set. Accordingly, it will be understood by one of ordinary skill in the art that although a specific document set class is described in each circular portion of FIG. 4 , the same applies to another document belonging to the document set.
  • the document set class, the document set, and the document are the same as those described with reference to FIG. 2 , and thus a detailed explanation thereof will not be given.
  • a rectangular portion in the workflow 400 of FIG. 4 refers to a filter class FC and a filter FU included in the filter class. At least one filter may be included in one filter class. Accordingly, it will be understood by one of ordinary skill in the art that although a specific filter class and a filter are described in each rectangular portion of FIG. 4 , the same applies to another filter included in the filter class.
  • the filter class and the filter are the same as those described with reference to FIG. 2 , and thus a detailed explanation thereof will not be given.
  • a filter 4.1 410 that is one instance of a filter class 3.1 generates one or more from among four document sets EKG 411 , Holter 412 , Event Recorder 413 , and DICOM 414 .
  • the filter 4.1 410 may be an external filter that generates a document set, or may be an internal filter that generates a document set by using a signal received from an external apparatus.
  • the document set EKG 411 expressed with a document set class 5.1 may be stored in the data storage 2330 .
  • a filter 4.2.1 420 that is one instance of a filter class 3.2.1 receives the document set Holter (document set class 5.2) 412 and outputs a document set Clinical Decision Supporting System (CDSS) Results (a document set class 5.2.1) 421 .
  • CDSS Clinical Decision Supporting System
  • a filter 4.2.2 450 that is one instance of a filter class 3.2.2 generates a new document set (a document set class 5.2.2) 451 by combining the document set Holter 412 with the document set CDSS Results 421 .
  • a filter 4.2 430 that is one instance of a filter class 3.2 combines the document set Event Recorder 413 that is expressed with a document set class 5.3.
  • a filter 4.4.1 440 that is one instance of a filter class 3.4.1 provides the document set DICOM 414 that is expressed with a document set class 5.4 to an external apparatus.
  • the external apparatus displays the document set DICOM 414 on a screen.
  • the displayed document set 441 may be checked by the cloud 110 .
  • the cloud 110 sets a document set class.
  • the cloud 110 sets a document set class that is needed to operate the workflow 400 that is designed in step 340 .
  • the cloud 110 assigns a UID to each document set and a filter and sets the UID in the medical information providing system.
  • the filter class 3.1 410 and the document set class 5.1 411 of FIG. 4 may be respectively expressed with UIDs such 1.2.410.200054.3.1 and 1.2.410.200054.5.1.
  • the setting of the document set class is completed when the UID and a name of the document set class are designated.
  • a database table structure for storing document set class information is shown in Table 11.
  • DocSet Class Indicates a UID of a document set class, and a unique UID UID is assigned to each document set class.
  • DocSet Class Indicates a type of the document set class and is used only Type for reference.
  • DocSet Class Indicates a name of the document set class. Name
  • step 360 the cloud 110 sets a filter class.
  • the cloud 110 sets a filter class that is needed to operate the workflow 400 designed in step 340 .
  • a database table structure for storing filter class information is shown in Table 13 and Table 14.
  • Filter Class UID Is a UID of a filter class, and a unique UID is assigned to each filter class.
  • Filter Class Name Indicates a name of the filter class.
  • Filter Class Type Indicates a type of the filter class and indicates an internal filter I or an external filter E.
  • Filter Proc Name Is set only in the internal filter and is a name of a database procedure.
  • Filter Proc Args Is set in the internal filter and is factors of the database procedure.
  • DocSet Type Indicates whether a designated document set is an input I or an output O of a filter.
  • DocSet Class Designates an input or output document set of the UID filter.
  • the cloud 110 sets an input document set and an output document set that may be processed by each filter class.
  • the cloud 110 may set a filter class as shown in Table 16.
  • step 370 the cloud 110 sets a filter.
  • the cloud 110 sets a filter that is needed to operate the workflow 400 designed in step 340 .
  • a database table structure for storing filter information is shown in Table 17.
  • Filter UID Indicates a UID of a filter and is a unique value for each filter.
  • Filter Class UID Indicates a type of the filter and sets a filter class UID.
  • Filter Name Indicates a filter name.
  • Filter Proc Args Re-defines factors of a database procedure that is used in an internal filter.
  • Default Group Indicates a group that is automatically set when there is no group information in a document set processed by the filter.
  • Default Patient Indicates a patient that is automatically set when there is no patient information in the document se processed by the filter.
  • the cloud 110 may set a filter as shown in Table 19.
  • step 380 the cloud 110 sets a filter condition.
  • the filter condition includes i) setting of a filter that is to perform an operation and ii) setting of an input condition for performing the operation of the filter.
  • Filter Rule Name Indicates a name of a filter rule.
  • Filter Selects a filter that is to perform an operation.
  • Scheduled Time Designates an absolute time when the filter is to perform the operation, and the filter performs the operation on the designed time. The designating of the absolute time is performed before a relative time is designated.
  • Scheduled Delay Designates the relative time when the filter is to perform the operation, and the filter performs the operation a designated period of time after a current time in a a) mode, or, a designated period of time after tomorrow 00:00 A.M. in a b) mode.
  • the filter performs the operation on February 5, 2014, 21:00 in the a) mode and the filter performs the operation on February 6, 2014, 3:00 in the b) mode.
  • the workflow 400 of FIG. 4 the workflow is needed to be set only for the document set Holter 412 and the document set DICOM 414 . This may be obtained when the cloud 110 sets as shown in Table 24.
  • a function FilterRule_apply( ) is automatically called.
  • the cloud 110 searches for a filter condition to determine whether there is a filter to be applied to the new document set and records a result on a filter queue. If an input condition of the filter condition includes only one document set, the filter condition is used as soon as the document set satisfying the condition is generated. However, when the input condition of the filter condition includes a plurality of document sets (that is, when the filter has to process a plurality of documents sets at one time), the filter condition is used when all of the document sets needed to perform an operation of the filter are prepared.
  • a filter 1.2.410.200054.4.2.1 performs an operation as soon as a document set for a document set class 1.2.410.200054.5.2 is prepared.
  • a filter 1.2.410.200054.5.2.2 performs an operation when all document sets for document set classes 1.2.410.200054.5.2 and 1.2.410.200054.5.2.1 are prepared.
  • a filter 1.2.410.200054.4.4.1 performs an operation when a document set for a document set class 1.2.410.200054.5.4 is prepared.
  • a filter queue is generated.
  • the filter queue is not set but is generated as a result of using the filter condition, and stores pieces of information about the filter that is to perform an operation and a result of the operation of the filter.
  • the filter queue includes i) storing of information about the filter that is to perform an operation and ii) storing of information about a document set that is to be input to the filter.
  • Table 25 a database table structure for storing information about a filter that is to perform an operation is shown in Table 25.
  • Filter Queue UUID Is a UUID of a filter queue, and is used to process a filter operation by using an XDS method.
  • Filter Designates a filter that is to perform an operation.
  • Filter Result Text Indicates a result of the operation of the filter.
  • Filter Result Code Indicates a result code of the operation of the filter.
  • Scheduled Time Indicates a time when the filter is to perform the operation.
  • Performed Time Indicates a time when the filter performs the operation.
  • Table 27 a database table structure for storing information about a document set that is to be input to a filter is shown in Table 27.
  • Filter Queue Input Is a UUID of a filter queue input, and is used to process a filter operation by using an XDS method.
  • Filter Queue Designates a filter queue.
  • DocSet Designates a document set.
  • FIG. 5 is a diagram for explaining an external filter 541 according to an embodiment of the present invention.
  • a cloud 510 and external apparatuses 520 , 530 , and 540 connected to the cloud 510 are illustrated in FIG. 5 .
  • the cloud 510 and the external apparatuses 520 , 530 , and 540 may be connected to each other through wired or wireless communication.
  • the cloud 510 and the external apparatuses 520 , 530 , and 540 may be connected through, but not limited to, an IHE XDS or Mobile-access to Health Document (MHD) standard protocol.
  • MHD Mobile-access to Health Document
  • An external apparatus may be any apparatus as long as it may communicate with another external apparatus or the cloud 510 .
  • each of the external apparatuses 520 , 530 , and 540 may correspond to, but not limited to, medical equipment, a PC, or a mobile terminal for obtaining diagnostic information of a patient.
  • the external filter 541 may be included in at least one of the external apparatuses 520 , 530 , and 540 .
  • the external filter 541 and the cloud 510 may transmit/receive an operation through a program FilterProc.
  • the program FilterProc searches for filter operations to be processed by the program FilterProc by using a designated filter UID, downloads input document sets, performs filter processing, configures generated resultant documents into a new document set, and uploads the new document set. Setting of the program FilterProc will be explained with reference to FIG. 6 .
  • a cloud 610 included in the system 600 and programs 620 and 630 respectively installed in external apparatuses are illustrated in FIG. 6 .
  • Each of the programs 620 and 630 may be any program as long as it may be connected to the cloud 610 through wired/wireless communication.
  • Main key values used when the programs 620 and 630 provided in external apparatuses communicate with the cloud 610 by using an XDS or MHD protocol are shown in Table 29.
  • XDS/MHD submission Set Key Description entryUUID Is a UUID of a document set, and has to be completely unique. When firs transmitted, a symbolic name, instead of a UUID, may be used.
  • contentTypeCode Is a code indicating content of the document set, and internally corresponds to a document set class UID.
  • patientId Indicates a patient number.
  • sourceId Indicates a source that generates the document set, and internally corresponds to a filter UID.
  • submissionTime Indicates a time when the document set is transmitted.
  • title is a title of the document set.
  • uniqueId Is a UID of the document set, and has to be unique in a group.
  • a document, a document set, and a folder are realized and a relationship therebetween is expressed by using objects Document Entry, submission Set, Folder, and Association.
  • a database table structure for storing the objects in the cloud 610 is shown in Table 31 through Table 36.
  • the external filters 650 and 660 perform an operation through five steps.
  • the five steps through which the external filters 650 and 660 perform the operation are as follows.
  • the operation that is to be performed by the external filters 650 and 660 is searched for.
  • the operation that is to be performed by the external filters 650 and 660 may be searched for by using an XDS Registry Stored Query method.
  • a stored query FindFilterJobs may change a filter operation into an association list as shown in Table 41.
  • a list of operations that are to be performed by the external filters 650 and 660 is prepared.
  • an association list of searched filter operations forms a a filter job list in a program FilterProc as shown in Table 42.
  • logLevel Indicates a log level and designates one of the following values.
  • DEBUG serverHost Is an address of a XDS/MHD server of a cloud.
  • serverPort Is a port number of the XDS/MHD server of the cloud.
  • workingDir Designates a working directory.
  • filenameFormat Designates a file name of documents that are to be downloaded and may use the following keyword. %uid: is replaced by a UID of a document. %dttm: is replaced by a time when the document is generated. %seq: is replaced by a serial number that is automatically assigned. retrieveSetCount Indicates a set count when documents are downloaded.
  • %inDocFile is replaced by a file name of an individual input document.
  • %inJobDir is replaced by an overall operation folder when two or more input document sets are needed for filter processing.
  • %inJobPathList is replaced by an overall path name list of all input document files included in an operation folder.
  • %inJobFileList is replaced by a file name list of the all input documents included in the operation folder.
  • %outDocFile is replaced by a name of an individual output document file.
  • mimeType I is an MIME type that is needed to upload a generated document. rename Determines whether documents having used in an operation are to be moved or deleted, and designates true to move the documents and false to delete the documents. A default value is false (delete). repeat Determines whether to repeat. A default value is false (no repetition). repeatInterval Designates a repetition interval. For example, 300 (seconds) may be designated as a repetition interval.
  • a program FilterProc generates an operation folder under a folder designated with a working directory workingDir as shown in Table 44.
  • the program FilterProc may designate that pieces of content of the operation folder are to be deleted later.
  • the external filters 650 and 660 transmit a result of the operation to the cloud 610 .
  • the external filters 650 and 660 transmit association information as shown in Table 45 before transmitting a document set that is a result of the operation to the cloud 610 .
  • Association_kind column value of an XDSAssociation table is determined according to an Association.slotValue.
  • the XDS server XDSServer stores attributes of the object Association in the database and finally calls a function FilterQueue_update( ) to record that the filter operation is completed.
  • An example is shown in Table 46.
  • the external filter HolterCDSS 650 that is one external filter provided in the cloud 610 downloads a radionet holter file from the cloud 610 and performs a program HolterExport.exe or Holter.exe to perform CDSS processing.
  • the external filter HolterCDSS 650 uploads again automatic diagnosis result files having a JPEG format generated as a result of the program to the cloud 650 .
  • the external filter HolterCDSS 650 is a batch file made based on the program FilterProc and includes, in detail, a FilterProc.jar module that is in charge of communicating with the cloud and a HolterExport.exe or Holter.exe module that is in charge of performing actual CDSS processing.
  • a configuration and setting of the external filter HolterCDSS 650 according an embodiment of the present invention are respectively shown in Table 47 and Table 48.
  • the external filter EventMerge 660 is one external filter provided in the cloud 610 , and downloads signal files Event Recorder stored in the cloud 610 , merges and changes the signal files Event Recorder, and transmits the merged signal files as an input to a program Holter.exe.
  • the external filter EventMerge 660 is a batch file made based on the program FilterProc, and includes, in detail, EventBuild.jar that is a preprocessor for merging the signal files Event Recorder and Holter.exe for processing actual holter information.
  • a query file as shown in the following has to be generated and transmitted as a factor.
  • GetSubmissionSetAndContents has to be designated as a query type and a UID of a document set docsetUID containing files Event Recorder to be merged has to be designated.
  • Such query files may be obtained by being downloaded from a document set list of a web browser 640 .
  • a configuration and setting of the external filter EventMerge 660 according to an embodiment of the present invention are respectively shown in Table 49 and Table 50.
  • EventMerge.conf ⁇ “FilterProc” : ⁇ “logLevel” : “INFO”, “serverHost” : “54.238.177.162”, “serverPort” : “8080”, “workingDir” : “D:/Temp”, “filenameFormat” : “%dttm.raw”, “retrieveSetCount” : “3”, “preprocessor” : “java -jar D:/OPHIES/lib/EventBuild.jar %inDocSetDir”, “processor” : “ ⁇ “C: ⁇ Program Files ⁇ RADIONET ⁇ Holter ⁇ Holter.exe ⁇ ” -evt %inDocSetDir”, “rename” : “false”, ⁇ ⁇
  • FIG. 7 is a diagram illustrating an apparatus 700 for generating information about a filter according to an embodiment of the present invention.
  • the apparatus 700 includes a filter class setter 710 , a filter setter 720 , and a filter condition setter 730 . Only elements related to the present embodiment are illustrated in the apparatus 700 of FIG. 7 . Accordingly, it will be understood by one of ordinary skill in the art that general-purpose elements other than the elements illustrated in FIG. 7 may be further included in the apparatus 700 .
  • the filter class setter 710 , the filter setter 720 , and the filter condition setter 730 of FIG. 7 may correspond to one or a plurality of processors.
  • Each processor may be an array of logic gates, or a combination of a general-purpose microprocessor and a memory storing a program that may be executed by the microprocessor. Also, it will be understood by one of ordinary skill in the art that the processor may be another type of hardware.
  • the apparatus 700 of FIG. 7 may be further included in the medical information providing system or the cloud of FIGS. 1, 2, 5, and 6 . Accordingly, although omitted, the description of the medical information providing system or the cloud of FIGS. 1, 2, 5, and 6 may apply to the apparatus 700 of FIG. 7 .
  • the filter class setter 710 sets at least one filter class corresponding to an operation for generating medical information of an object.
  • the object used herein may refer to, but not limited to, a patient.
  • the filter class refers to a class of a filter and an input/output method is expressed by using a document set class.
  • One filter class may correspond to a plurality of filters. That is, there may be various filters having the same input/output method and function.
  • the filter setter 720 sets at least one filter that is included in the filter class and performs an operation.
  • Types of the filter include an internal filter and an external filter.
  • the internal filter may refer to a filter that performs an operation in a database of the cloud and may be a stored function of a database of an infrastructure.
  • the external filter may refer to a filter that performs an operation outside the database of the cloud and may be realized by using an API provided by the cloud.
  • the filter indicates an instance of the filter and indicates an actual instance of the filter expressed with a filter class. All filters having the same filter class UID may perform substantially the same function.
  • An operation performed by the filter may correspond to any one from among an operation of converting at least one input content into at least one output content, an operation of storing content, an operation of providing content to another apparatus, and an operation of generating content.
  • the other apparatus to which the content is provided refers to an apparatus for using the content in various ways, for example, an apparatus for displaying the content.
  • the content used herein refers to any type of document including text, an image, or a video.
  • examples of the content may include all types of documents, such as images, waveforms, and measured values, which may be processed by general arithmetic units. Accordingly, content and a document in the description of FIGS. 1 through 6 are expressed as the same concept.
  • FIG. 8 is a flowchart illustrating a method of generating information about a filter (referred to as the filter information generating method) according to an embodiment of the present invention.
  • the filter information generating method includes steps that are sequentially performed by the medical information providing system, the cloud, or the apparatus 700 of FIGS. 1, 2, 5, 6, and 7 . Accordingly, although omitted, the description made with reference to FIGS. 1, 2, 5, 6, and 7 may apply to the filter information generating method of FIG. 8 .
  • a cloud sets at least one filter class corresponding to an operation for generating medical information of an object.
  • step 820 the cloud sets at least one filter that is included in the filter class and performs an operation.
  • step 830 the cloud sets at least one condition required to operate the filter.
  • FIG. 9 is a diagram illustrating an apparatus 900 for generating medical information of an object according to an embodiment of the present invention.
  • the interface unit 910 and the filter selector 920 included in the apparatus 900 of FIG. 9 may correspond to one or more processors.
  • Each processor may be an array of logic gates, or a combination of a general-purpose microprocessor and a memory storing a program that may be executed by the microprocessor. Also, it will be understood by one of ordinary skill in the art that the processor may be another type of hardware.
  • the apparatus 900 of FIG. 9 may be included in the medical information providing system or the cloud of FIGS. 1, 2, 5, and 6 . Accordingly, although omitted, the description of the medical information providing system or the cloud of FIGS. 1, 2, 5, and 6 may apply to the apparatus 900 of FIG. 7 .
  • the interface unit 910 receives at least one content from at least one from among external apparatuses connected to the cloud.
  • Content used herein refers to any type of document including text, an image, or a video.
  • examples of the content may include all types of documents, such as images, waveforms, and measured values, which may be processed by general arithmetic units. Accordingly, content and a document in the description of FIGS. 1 through 6 are expressed as the same concept.
  • the filter selector 920 selects a filter that performs a preset operation based on the content received by the interface unit 910 from among filters respectively included in a plurality of filter classes.
  • a filter class refers to a class of a filter, and an input/output method is expressed by using a document set class.
  • One filter class may correspond to a plurality of filters. That is, there may be various filters having the same input/output method and function.
  • Types of the filter include an internal filter and an external filter.
  • the internal filter may refer to a filter that performs an operation in a database of the cloud and may be a stored function of a database of an infrastructure.
  • the external filter may refer to a filter that performs an operation outside the database of the cloud and may be realized by using an API provided by the cloud.
  • the preset operation performed by the filter selected by the filter selector 920 refers to any one from among an operation of converting at least one input content into at least one output content, an operation of providing content to at least one from among apparatuses connected to the cloud, an operation of generating new content by combining different pieces of content, and an operation of storing content.
  • the apparatus to which the content is provided refers to an apparatus for using the content in various ways, for example, an apparatus for displaying the content.
  • the filter selector 920 may select a filter that performs an operation based on a result of the preset operation from among the filters respectively included in the plurality of filter classes. In other words, as shown in the workflow of FIG. 4 , the filter selector 920 may select another filter that performs another operation by using a result of the operation of the filter.
  • the time condition may correspond to any one from among a condition in which the filter performs the operation when information is input to the filter, a condition in which the filter performs the operation a predetermined period of time after information is input, and a condition in which the filter performs the operation a predetermined period of time after the beginning (00:00 A.M.) of the day after information is input.
  • the filter information generating object medical information generating method includes steps that are sequentially processed by the medical information providing system, the cloud, or the apparatus 900 of FIGS. 1, 2, 5, 6, and 9 . Accordingly, although omitted, the description made with reference to FIGS. 1, 2, 5, 6, and 9 may apply to the object medical information generating method of FIG. 10 .
  • a cloud receives at least one content from at least one from among external apparatuses connected to the cloud.
  • the cloud selects a filter that performs an operation based on received content from among filters respectively included in a plurality of filter classes.
  • step 1030 the selected filter performs a preset operation.
  • the afore-described method may be implemented as an executable program, and may be executed by a general-purpose digital computer that runs the program by using a computer-readable recording medium. Also, a structure of data used in the method may be recorded by using various units on a computer-readable recording medium. Examples of the computer-readable recording medium include storage media such as magnetic storage media (e.g., read-only memories (ROMs), random-access memories (RAMs), universal serial buses (USBs), floppy discs, or hard discs), optically readable media (e.g., compact disk-read only memories (CD-ROMs), or digital versatile disks (DVDs)), etc.
  • ROMs read-only memories
  • RAMs random-access memories
  • USBs universal serial buses
  • floppy discs or hard discs
  • optically readable media e.g., compact disk-read only memories (CD-ROMs), or digital versatile disks (DVDs)

Landscapes

  • Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Public Health (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Epidemiology (AREA)
  • Biomedical Technology (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Pathology (AREA)
  • Medical Treatment And Welfare Office Work (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
US15/111,830 2014-03-10 2015-02-26 Method and apparatus for generating medical information of object Abandoned US20160350485A1 (en)

Applications Claiming Priority (7)

Application Number Priority Date Filing Date Title
KR10-2014-0027953 2014-03-10
KR20140027953 2014-03-10
KR10-2014-0109954 2014-08-22
KR10-2014-0109953 2014-08-22
KR1020140109953A KR101633911B1 (ko) 2014-03-10 2014-08-22 대상체의 의료 정보를 생성하는 방법 및 장치.
KR1020140109954A KR102382313B1 (ko) 2014-03-10 2014-08-22 대상체의 의료 정보를 생성하는 방법 및 장치.
PCT/KR2015/001851 WO2015137646A1 (ko) 2014-03-10 2015-02-26 대상체의 의료 정보를 생성하는 방법 및 장치

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/001851 A-371-Of-International WO2015137646A1 (ko) 2014-03-10 2015-02-26 대상체의 의료 정보를 생성하는 방법 및 장치

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/308,513 Division US11901075B2 (en) 2014-03-10 2021-05-05 Method and apparatus for generating medical information of object

Publications (1)

Publication Number Publication Date
US20160350485A1 true US20160350485A1 (en) 2016-12-01

Family

ID=54244976

Family Applications (2)

Application Number Title Priority Date Filing Date
US15/111,830 Abandoned US20160350485A1 (en) 2014-03-10 2015-02-26 Method and apparatus for generating medical information of object
US17/308,513 Active 2036-08-03 US11901075B2 (en) 2014-03-10 2021-05-05 Method and apparatus for generating medical information of object

Family Applications After (1)

Application Number Title Priority Date Filing Date
US17/308,513 Active 2036-08-03 US11901075B2 (en) 2014-03-10 2021-05-05 Method and apparatus for generating medical information of object

Country Status (2)

Country Link
US (2) US20160350485A1 (ko)
KR (3) KR102382313B1 (ko)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019000771A1 (zh) * 2017-06-27 2019-01-03 苏州美天网络科技有限公司 一种基于app的病患住院管理系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140279807A1 (en) * 2013-03-14 2014-09-18 Siemens Aktiengesellschaft Rules-based management system and method for processing medical information
US9042617B1 (en) * 2009-09-28 2015-05-26 Dr Systems, Inc. Rules-based approach to rendering medical imaging data
US9251295B2 (en) * 2011-08-31 2016-02-02 International Business Machines Corporation Data filtering using filter icons
US9639615B1 (en) * 2012-06-28 2017-05-02 Open Text Corporation Systems and methods for health information messages archiving

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2001290890A (ja) * 2000-04-04 2001-10-19 Terumo Corp 医療情報検索システム及びその制御方法、記憶媒体
JP2002083058A (ja) 2000-09-06 2002-03-22 Yokogawa Electric Corp 広域医療情報システム
JP2004113730A (ja) 2002-09-25 2004-04-15 Terarikon Inc コンピュータ読影支援システム
JP2010267042A (ja) * 2009-05-14 2010-11-25 Konica Minolta Medical & Graphic Inc 医療データ管理システム
KR20110055921A (ko) * 2009-11-20 2011-05-26 어울림엘시스 주식회사 온라인상의 개인정보 보호 시스템 및 이 시스템을 이용한 개인정보 보호 방법
JP5758684B2 (ja) * 2011-04-21 2015-08-05 生活協同組合コープさっぽろ 患者情報提供サーバ、及び患者情報提供処理プログラム
KR101329346B1 (ko) * 2011-11-23 2013-12-19 건국대학교 산학협력단 의료용 단말기를 통한 의료정보 처리 시스템 및 그 방법
JP6075833B2 (ja) * 2012-08-09 2017-02-08 キヤノン株式会社 医用情報処理装置、医用情報処理方法及びプログラム
US10033702B2 (en) * 2015-08-05 2018-07-24 Intralinks, Inc. Systems and methods of secure data exchange

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9042617B1 (en) * 2009-09-28 2015-05-26 Dr Systems, Inc. Rules-based approach to rendering medical imaging data
US9251295B2 (en) * 2011-08-31 2016-02-02 International Business Machines Corporation Data filtering using filter icons
US9639615B1 (en) * 2012-06-28 2017-05-02 Open Text Corporation Systems and methods for health information messages archiving
US20140279807A1 (en) * 2013-03-14 2014-09-18 Siemens Aktiengesellschaft Rules-based management system and method for processing medical information

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019000771A1 (zh) * 2017-06-27 2019-01-03 苏州美天网络科技有限公司 一种基于app的病患住院管理系统

Also Published As

Publication number Publication date
KR102382313B1 (ko) 2022-04-04
KR101945993B1 (ko) 2019-02-08
KR20160034877A (ko) 2016-03-30
KR101633911B1 (ko) 2016-06-27
KR20150105900A (ko) 2015-09-18
US20210257098A1 (en) 2021-08-19
US11901075B2 (en) 2024-02-13
KR20150105899A (ko) 2015-09-18

Similar Documents

Publication Publication Date Title
US11087878B2 (en) Methods and systems for improving connections within a healthcare ecosystem
US9961156B2 (en) Healthcare semantic interoperability platform
US9961158B2 (en) System and methods of managing content in one or more networked repositories during a network downtime condition
US11410753B2 (en) System and methods of capturing medical imaging data using a mobile device
US20110153351A1 (en) Collaborative medical imaging web application
US11515016B2 (en) Rule-based low-latency delivery of healthcare data
US20160132645A1 (en) System and architecture for providing shared patient data notifications
US20060106648A1 (en) Intelligent patient context system for healthcare and other fields
GB2495824A (en) Managing the failover operations of a storage unit in a cluster of computers
US9826054B2 (en) System and methods of pre-fetching content in one or more repositories
US11901075B2 (en) Method and apparatus for generating medical information of object
US20120323601A1 (en) Distributed sharing of electronic medical records
US20230237116A1 (en) Web-based medical image viewer with web database
US11087862B2 (en) Clinical case creation and routing automation
US20160063077A1 (en) Data brokering system for fulfilling data requests to multiple data providers
CA2861754A1 (en) Data brokering system for fulfilling data requests to multiple data providers
US20210158938A1 (en) Enhanced Enterprise Image Reading with Search and Direct Streaming
US11243974B2 (en) System and methods for dynamically converting non-DICOM content to DICOM content
WO2024065061A1 (en) Healthcare record virtualization
Lee et al. Service Oriented Development of Information Visualization of the Electronic Health Records for Population Data Set
WO2014202795A2 (en) System and methods of managing content in one or more repositories
Yuan et al. An architecture for cross-hospital access to electrocardiogram data

Legal Events

Date Code Title Description
AS Assignment

Owner name: IRM INC., KOREA, REPUBLIC OF

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CHOI, SEUNG WOOK;REEL/FRAME:039163/0209

Effective date: 20160621

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE AFTER FINAL ACTION FORWARDED TO EXAMINER

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

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: ADVISORY ACTION MAILED

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: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

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