CN1989504B - System and method for coupling patient data with executable guideline decision support systems - Google Patents
System and method for coupling patient data with executable guideline decision support systems Download PDFInfo
- Publication number
- CN1989504B CN1989504B CN200580025268XA CN200580025268A CN1989504B CN 1989504 B CN1989504 B CN 1989504B CN 200580025268X A CN200580025268X A CN 200580025268XA CN 200580025268 A CN200580025268 A CN 200580025268A CN 1989504 B CN1989504 B CN 1989504B
- Authority
- CN
- China
- Prior art keywords
- data
- data element
- back end
- relevant
- storage system
- 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.)
- Expired - Fee Related
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
- 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
-
- 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
- G16H70/00—ICT specially adapted for the handling or processing of medical references
- G16H70/20—ICT specially adapted for the handling or processing of medical references relating to practices or guidelines
-
- 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
Abstract
A system and method are provided for exchanging data between a local information storage system (26) storing first data elements associated with respective data, and an executable guideline decision support system (12) executable on at least one processor for storing a plurality of executable guidelines and executing the guidelines, including processing at least data associated with a second data element. The method includes the steps of generating a request to exchange data between the local information system and the decision support system (12); determining a first data element of the plurality of first data elements that corresponds to the second data element, and at least one interoperability parameter defining how the first and second data elements correspond; processing the data being exchanged in accordance with the determined at least one interoperability parameter; and transmitting the data being exchanged between the first and second data elements.
Description
The present invention relates generally to decision support system (DSS), especially relate to and use executable clinical guideline to assist to provide to the patient decision support system (DSS) of health care.
Existing evidence shows, can guide the validity that realizes improving care of patients by using the computer-implemented evidential executable clinical practice that combines with clinical workflow.This improvement can be included in point-of care the patient is provided the performance of specific suggestion.This can be carried out to guide and make the clinician can more easily obtain knowledge, and does not need the clinician to go for out specific knowledge.Many professional associations (such as ACP-AS IM, ACR, ACC etc.) have formulated the guide that is used for care of patients.Having developed decision support system (DSS) (DSS) combines with the execution that can carry out guide with the data relevant to patient and nursing thereof that will be stored in infosystem.
Yet decision support system (DSS) can not be widely used in point-of care, and this is due to decision support system (DSS) to a great extent and is used for not mating between the infosystem of store patient data.Solve and to a kind of method of not mating relevant problem to be, combining closely between DSS and local clinical information storage system is provided, this just causes being difficult to shared this DSS with other mechanisms.
Another kind method is the design medical logic module (MLM) relevant to DSS, for providing compatibility between DSS and local information storage system with shared information between them.This MLM provides a specific part, and the item that is wherein used by DSS is surrounded by other, is used for providing the mapping to the item that is used by local information storage system.These other be known as curling brace (curly brace).Mapping between this MLM item and local information storage system is that mechanism is specific, and needs a lot of customizations (custom tailoring).Thereby, prepare and use the task of this mapping to be commonly called " curling brace problem ".Set up the cost of DSS and to pay be very high, and it needs the time for customization of using local information storage system, this has hindered the purpose that shares DSS with many mechanisms.
Therefore, the present invention be directed to such problem, namely develop a kind of system and method, wherein DSS can be coupled to many infosystems and be configured in many mechanisms.
One aspect of the present invention is to provide a kind of system and method for swap data.This system comprises the local information storage system of a plurality of the first data elements that storage is relevant to each data that relate to a plurality of patients, and the guide the carried out decision support system (DSS) that can carry out at least one processor.This decision support system (DSS) comprises be used to storing a plurality of guideline storage system carried out of carrying out guide, and is used for carrying out the execution engine of this guide, and this guide comprises the processing data relevant to the second data element at least.
This decision support system (DSS) comprises the search module that can carry out at least one processor, be used for being created on the request of the data that between local information system, decision support system (DSS) and patient's knowledge base, exchange is relevant to the second data element.This patient's knowledge base can carry out to determine corresponding to the first data element in this a plurality of first data elements of this second data element on this at least one processor, and at least one interoperability parameter has defined how correspondence of this first and second data element.This patient's knowledge base can also carry out to process exchanged data according at least one interoperability parameter that should determine, to set up semantic mutual the using between this first and second data element.Provide coupling with the exchanged data of transmission between this first and second data element.
The method comprising the steps of: be created on the request of swap data between this local information system and decision support system (DSS), wherein these exchanged data are comprised in the data relevant to the second data element, and determine corresponding to the first data element in this a plurality of first data elements of this second data element and define how at least one interoperability parameter of correspondence of this first and second data element.The method also comprises step: process exchanged data according to this at least one interoperability parameter of determining, to set up the semantic use mutually between this first and second data element; The exchanged data of transmission between this first and second data element.
With reference to following listed accompanying drawing and detailed description of the present invention, these and other features of the present invention, aspect and advantage will become better understood:
Fig. 1 shows the block diagram that comprises an example system of the decision support system (DSS) that is coupled to local information storage system according to of the present invention.
Fig. 2 shows the process flow diagram in the operating period of system shown in Figure 1 implementation step, and wherein the data that obtain are retrieved in this decision support system (DSS) request from this local information back-up system; With
Fig. 3 shows the process flow diagram in the operating period of system shown in Figure 1 implementation step, and wherein this decision support system (DSS) is upgraded the data by the local information storage system storage.
The invention describes a kind ofly provides the decision support system (DSS) of clinical guidance for carrying out executable clinical guideline with the treatment the patient to the user.This decision support system (DSS) is coupled to the local information storage system that stores the data relevant to a plurality of patients and/or its treatment.This decision support system (DSS) need to be stored in data in this patient information storage system carrying out this guide, and this decision support system (DSS) need to be upgraded the data by the local information storage system storage.This decision support system (DSS) comprises patient's knowledge base, it makes by local information storage system canned data and the inquiry that is generated by this decision support system (DSS) or update semantics coupling, so that the semantic interoperability between this decision support system (DSS) and local information storage system to be provided.This semantic interoperability guarantees that this decision support system (DSS) and local information storage system have common understanding to a data of asking or exchanging and/or the implication of operation, with the wrong medical decision that prevents from misreading and finally causing.
Fig. 1 shows the preferred embodiment of an example system 10, and it has the decision support system (DSS) of the local information storage system of being coupled to, and is used for assisting to provide the decision support that keeps healthy for the patient.This system 10 comprises can carry out guide decision support system (DSS) (DSS) 12, and it comprises can carry out guideline storage system 14, DSS carries out engine 16, user interface (UI) 18, domain knowledge base (DKB) 22, patient's knowledge base (PKB) 24 and request module 30.This system 10 also comprises the local information storage system (LISS) 26 of the data that interface module 28 is relevant at least one patient and/or this at least one patient's treatment with storage.This execution engine 16 comprises request module 30, be used for generated query or request and search the correct data of the execution needed semanteme of guide with search PKB 24, perhaps determine to use the semantic correct mode of the data that are performed engine 16 processing, for example be used for upgrading LISS 26.
Term storage system refers to for storage and the system of visit information, for example one or more databases or storage vault, and wherein this storage system can be structuring or non-structured.DSS 12 is by with at least one processor and can being realized by at least one storage medium of this at least one processor access.The parts of this system 10 (for example this local information storage system 26, interface module 28 are connected with DSS and parts (for example evidence guideline storage system 14, DSS execution engine 16, user interface 18, domain knowledge base 22, patient's knowledge base 24 are connected with request module)) connect by wired or wireless connection 31, this connection 31 can be provided by one or more networks, for example LAN, WAN, Intranet, the Internet or its combination.
The all parts of system 10 can share the resource of this at least one processor and at least one storage medium, one or more in perhaps can special-purpose this resource.This at least one processor can comprise, such as personal computer, microprocessor, handheld computing device, server etc.This at least one storage medium can comprise, such as hard disk drive, CD-ROM, RAM, flash memory, volatile memory, nonvolatile memory etc.
LISS 26 preferably can select from a plurality of dissimilar LISS, wherein this DSS can with this dissimilar LISS in various LISS exchange messages.The data that these LISS 26 storages are relevant to a plurality of patients and treatment thereof, it can comprise patient information, laboratory result, image result etc., it preferably is stored as a plurality of the first data elements according at least a standard electronic medical records configuration.
This DSS 12 or its part may reside in server and/or can be by server access with on the storer of carrying out, and wherein this server can be by a plurality of computer access.For example, the user for example the clinician can operation element the station for example personal computer to use this DSS 12, wherein carry out this DSS 12 on server or workstation.Alternatively, this DSS can be positioned at one or more workstations or can the storer by its access on.And this DSS can embed or be connected to another system, such as management information system (such as hospital, sanatorium, laboratory etc.).Comprise about the exemplary application of this DSS and assist to carry out resource management, plan and/or quality assurance.
Guideline storage system 14 is stored a plurality of guides of carrying out.Be stored in guide in this guideline storage system 14 and be preferably evidentially, and develop according to expert of the art's experience and research.This guide is encoded by suitable coding techniques, such as ASBRU, GLIF, EON, GUIDE, PRODIGY and PROforma etc.This guideline storage system 14 is preferably searchable, to search specific guide or the most standard compliant guide, typically be the guide that provides clinical treatment to instruct at least one the environment of combination in optimum matching patient environment, user environment, care environments etc.
DSS 12 can access the guide of selecting from director information system 14.This guide can be selected by the instruction DSS 12 selected guides of access by the user, and/or this guide can by DSS 12 according to DSS 12 can with the data relevant to clinical setting select, such as the environment of patient's current state, medical history, nursing of providing up to now etc.Clinical practice can be used for submitting clinical context data to DSS 12, and perhaps user interface 18 can be used for allowing the user to input clinical context data.The copy of selected guide or its connection can be temporarily or permanent storage in teller work station for example, be stored in together with patient data in local information storage system 26, and/or be stored in by can carry out that guidance system 14 or DSS 12 provide and/or addressable work space in.The copy of this storage can customize individuality by some step of for example removing or skipping this guide, for example by realizing with the guide edit tool.
Each guide comprises at least one group of step, and every group comprises at least one step.Each step of this guide comprises various types of steps.A kind of step is the parts executable operations of indication user's (such as clinician, nurse, hospital administrators, technician etc.) or system 10.The example of this operation comprises: Information Monitoring, execution are tested, are provided treatment or jump to this guide or different another step of guiding.Another kind of step is to select step, is used for the prompting user and makes decision, for example the next step from determining to carry out from the selection of at least two steps.Another kind of step is state step, provides patient's current state, the entity (entity) relevant to the patient or patient's treatment or this implementation.Another kind of step is situation step (case step), wherein carries out at least one algorithm to make decision, and determines which step next step carries out.Information acquisition for example gathers from LISS 26, can carry out the term of execution of this various step.
Providing by guideline user interface 18 alternately between DSS 12 and user.This guide that is performed offers the user by guideline user interface 18.This guideline user interface 18 can generate demonstration, for example is used for being presented at screen hand-held or the upper computing equipment of table, and processes the input from input equipment pointing device and/or keyboard etc.This guideline user interface can generate graphic user interface (GUI), but is not limited to this.For example, this guideline user interface 18 can comprise the voice activation system that menu setecting and/or prompting are provided by audio message, for example uses by phone.User's response can provide by button and/or ARU, and can process this response with voice recognition technology.
The execution engine 16 of DSS 12 is carried out at least one guide carried out that is stored in guideline storage system 14.This at least one can carry out guide execution typically comprise access and process the data that are stored in domain knowledge base 22 and/or local information storage system 26.Yet, will cause the misunderstanding of data and wrong medical subsequently to determine by the data of DSS12 and LISS 26 uses and difference use or the explanation of term.This patient's knowledge base provides requestor (for example carry out engine 16) and the supplier (for example LISS 26) of semantic interoperability to guarantee information to have common understanding to the implication of requested date and service.Semantic interoperability means and highly relies on contextual semantic matches process, and can comprise that necessary compensation is with the requestor that guarantees this information and the compatibility between the supplier.Semantic matches is applied to definition of conception and explanation thereof.
The example of semantic difference is included in the difference of the aspects such as the use of degree of confidence, demographic conditions (such as sex, body weight, height, skin color, race), clinical condition, environmental baseline, reference point, term of numeral, unit, measuring technique and condition, measuring position, degree of error, information source (such as expert physician and computerized algorithm), value or diagnosis and scope.
PKB 24 and DKB 22 are the inhabitation information storage systems, preferably are configured to ontology (ontology).In each ontology, represent knowledge about the patient data field with declarative language.Can be called domain by the group objects that this declarative language represents.This ontology has defined one group of expression property term, and explanation and the good formal rule that uses that limits these terms is provided.The interface module 28 that is connected between PKB 24 and LISS 26 can use available specification to realize, for example HL7 Templates or Australian Archtypes specification.
PKB 24 stores the back end of preserving patient-related data, and the relation between this back end is with the attribute relevant to each back end.These data can configure according to standard medical data model (such as HL7, DICOM etc.).This relation for example semantic interlink has shown how this back end is correlated with, for example by cause-effect relationship, time relationship and/or Membership.This attribute comprises the context of describing these data and the information of semantic meaning, is used for limiting explanation and the use of these data, such as how obtaining these data, how representing these data etc.For example, this attribute can be described the characteristic about these data, such as the degree of confidence of use, unit, measuring technique and the condition of numeral, measuring accuracy, degree of error, information source (such as expert physician and computerized algorithm), value or diagnosis, demographic conditions, relevant clinical condition, environmental baseline, reference point, term and scope thereof etc.When and this attribute can comprise the LISS designator, is used to indicate back end corresponding to data element and/or which local information storage system of local information storage system.
DKB 22 stores the information irrelevant with particular patient, relates to the data of specified disease, medicine, treatment etc.This information can comprise for setting up semantic mutually with useful algorithm and/or equation, for example is used for defining relation and/or compensates between the incompatible use of information, such as the difference of compensating unit, reference point, environmental baseline etc.DKB 22 provides the semantic interlink between the information of being stored.For example, DKB 22 can comprise for maieutic territory, comprise element: FAC (AC) and EFW (EFW).Can provide semantic interlink to confirm and to obtain EFW with AC between AC and EFW.In another example, can be included in element femur length (FL) and menstrual age (MA) in same domain or another territory, for example orthopedic.Another kind of semantic interlink can provide between FL and MA element, so that FL is the function of MA.
With reference to Fig. 2, flow process Figure 200 of the system's of being presented at 10 steps that duration of work carries out is provided, wherein DSS 12 is from LISS 26 request msgs.In step 202, request module 30 generates the PKB inquiry, comprises for the request corresponding to the data that are performed specific second data element that engine 16 process of retrieval by LISS 26 storages, keeps simultaneously the semantic interoperability with this specific the second data element.The anticipatory data that will retrieve according to this request is the data that will exchange between LISS 26 and DSS 12.This PKB inquiry more particularly asks PKB 24 to search the information of searching this anticipatory data in one of first data element in being stored in LISS 26 about how, and determine how to use this data that find, keep simultaneously and carry out the semantic interoperability between engine 16.Preferably, PKB 24 knows the attribute of this second data element, and the semantic interoperability between the second data element that engine 16 processes is kept and be performed to this attribute.Otherwise this PKB inquiry can provide this attribute by reference DKB 22, because this attribute is set when the data element of this guide of definition.This PKB inquiry can ask to retrieve corresponding to more than first data element and/or more than the data of second data element, yet for the sake of clarity, below explanation only relates to retrieval corresponding to the situation of the data of first data element and second data element.
PKB 24 processes this PKB inquiry.In step 204, PKB 24 access are corresponding to the first back end of the second data element.In step 206, PKB 24 determines to relate to the first back end and second back end relevant to the first data element of being stored by LI SS 26.By processing and relevant this second back end that arranges of the first data element that at least one relation that the first back end is associated and inspection and LISS 26 store.Can determine by checking the LISS designator to the relevant of the first data element that LISS 26 stores, if be included in the back end of PKB 24.Otherwise, can consult list or LISS itself that these a plurality of the first data elements are provided.For example, when a plurality of possible back end relate to the first back end and the first data element of storing to LISS 26 when relevant, select the optimum data node as the second back end according to predetermined condition, such as selecting according to the user, simple relation, having for the most public attribute of first node etc.
In step 208, PKB 24 determines how corresponding at least one interoperability parameter is to define this first and second data element, and it is indicated by the relation between this first and second node.This interoperability parameter comprises following at least one in both: define at least one relation how this first and second data element is correlated with, and be used at least one group of at least one offset rule that how definition to compensate between the first and second data elements.
This at least one relation determines according to the relation that is configured between the first and second nodes, and can comprise the identifier that is used to identify focused data unit of institute by LISS 26.This offset rule is by relatively this first back end (corresponding to the second data element) and the second back end (corresponding to the first data element) are determined.This offset rule is determined like this, Attribute Relative by determining this first node is in the difference of the attribute of Section Point, and produce this rule of determining difference of compensation so that the semantic interoperability between this first and second data element to be provided, and/or provide the ability of obtaining information in data available from LISS 26.Preferably, this PKB inquiry is configured to the inquiry based on description logic.Preferably, request module 30 comprises at least one artificial intelligence module that represents this PKB inquiry for formulism.PKB 24 can consult DKB 22 or intelligent agent (intelligent agent) is used attribute mutually to determine this second back end and this.
This interoperability parameter can by temporarily or for good and all with at least one the storage of this second data element or first node in order to its use subsequently.The relation that should determine and offset rule or its access of determining can be provided according to design alternative by PKB 24 and DKB 22.If this interoperability parameter has been stored and is available, do not need so to determine again them, but obtain them from storer.
In step 210, PKB generates the LISS inquiry according at least one relationship interoperability parameter that should determine, is used for inquiry LISS 26 to obtain the data relevant to this first data element.This at least one relationship interoperability parameter is used for this first data element of location LISS.Interface module 28 is the understandable form of LISS 26 with this LISS query conversion.In step 212, LISS 26 is by providing result to respond this LISS inquiry to interface module 28, and wherein this result comprises the data relevant to this first data element.In step 214, interface module 28 further becomes the intelligible appropriate format of PKB 24 with this LISS query conversion.The result that interface module 28 will be changed is provided to PKB 24.
In step 216, receiving on the basis of this result, 24 pairs of these results of PKB are used determined offset rules compensating this data, so that this result data and the semantic mutual use of this second data element, thereby guarantee accurately to be processed by the execution engine 16 of DSS 12.In step 218, the data that PKB 24 should the mutual use of semanteme are provided to can carry out engine 16, this can carry out engine 16 can for the treatment of and/or upgrade this evidence guideline storage system 14.
With reference to Fig. 3, the process flow diagram 300 of the system that the is illustrated in 10 performed steps of duration of work is provided, wherein DSS 12 updates stored in the data in LISS 26.In step 302, PKB 24 is from carrying out engine 16 and receiving update requests so that with the data element the Data Update LISS 26 of the second data element, and these data are exchanged data.This update request can be asked corresponding to more than first data element and/or more than the renewal of second data element, yet for the sake of clarity, below explanation only relates to retrieval corresponding to the situation of the data of first data element and second data element.
In step 304, PKB 24 access are corresponding to the first back end of this second data element.In step 306, PKB 24 determines the second relevant to this first back end and relevant with the first data element of LISS 26 storages back end.In step 308, PKB 24 determines to describe how corresponding at least one interoperability parameter of this first and second data element, and it is indicated by the relation between this first and second node.If this interoperability parameter has been stored and is available, do not need so to determine them, but retrieve them from storer.
In step 310,24 pairs of market demand determined offset rules relevant to this second data element of PKB are used so that these data and this first data element are semantic mutually to compensate this data.In step 312, PKB generates the LISS update request according at least one relationship interoperability parameter that should determine, is used to indicate this offset data of LISS 26 use and upgrades this first data element.This at least one relationship interoperability parameter is used for this first data element and the corresponding element thereof of location LISS 26.Interface module 28 is converted to the understandable form of LISS 26 with this first data element of correct renewal according to the agreement that LISS 26 uses with this LISS update request.In step 314, LISS26 upgrades this first data element with this suitable offset data.
When exploitation DSS 12, preferably by preparing DSS 12 with the semantic convention of LISS 26 use with most.When exploitation PKB 24, do not need to copy fully its LISS that will use 26.Preferably, PKB 24 has knowledge according to the expection incompatibility between DSS 12 and various LISS 26.The whole content of PKB 24 must be enough large or data that expansion is processed to hold its, for example from the data of DSS 12 and be stored in LISS 26 corresponding to the data from the data of DSS 12.
Can predict, can develop PKB when being used.For example, the mutual with on the basis of problem of not success correction being detected, can ask user intervention.If the judgement user inputs successfully, the execution module 16 of system 10, PKB 24 and/or interface module 28 can utilize the scheme of advising to carry out suitable renewal (forever or provisionally) in order to using in the future.Alternatively, detecting on the basis of Similar Problems, can inquire about intelligent agent so that solution to be provided.If judge that the scheme that this intelligent agent is recommended is successfully, can come suitable update system 10 with it so.
It is also envisioned that, described above the renewal for example for system 10, can be uploaded in the server that is connected to a plurality of systems 10.This renewal can be downloaded in these a plurality of systems 10 and might run in the system 10 of similar interoperability problems.Uploading and downloading of this renewal can be automatically or supervised by each system of systems keeper.
Described embodiment of the present invention is exemplary and not restrictive, and does not attempt to represent each embodiment of the present invention.Can make various modifications and change and not break away from the spirit and scope of the present invention, as claims on letter and given on the meaning of equal value of admitting legally.
Claims (16)
1. the system of a swap data comprises:
Store the local information storage system (26) of a plurality of first data elements relevant to each data that relate to a plurality of patients;
The guide the carried out decision support system (DSS) (12) that can carry out at least one processor, comprise be used to storing a plurality of guideline storage system carried out (14) of carrying out guide, with the execution engine (16) that is used for carrying out this guide, carry out described guide and comprise at least the data relevant to the second data element are processed, this decision support system (DSS) (12) comprising:
The search module (30) that can carry out on this at least one processor is used for being created on the request of the data that between local information storage system (26) and decision support system (DSS) (12), exchange is relevant to the second data element; With
The patient's knowledge base (24) that can carry out on this at least one processor be used for to be determined these a plurality of first data elements corresponding to the first data element of this second data element and defines how corresponding at least one interoperability parameter of this first and second data element; Process this exchanged data relevant to the second data element with at least one interoperability parameter that is used for according to determining, use mutually with the semanteme of setting up between this first and second data element; With
Coupling (31) is used for the exchanged data relevant to the second data element of transmission between this first and second data element.
2. the system as claimed in claim 1, wherein this at least one interoperability parameter comprises with lower at least one: at least one is used for the relation how this first and second data element of definition is correlated with, and at least one group is used at least one offset rule how definition compensates between this first data element and corresponding the second data element.
3. system as claimed in claim 2, wherein:
This patient's knowledge base (24) can be carried out on this at least one processor, be used for a plurality of back end, at least one relation relevant to each back end of this a plurality of back end and at least one attribute of being correlated with this each node are stored or accessed, how each back end in described these a plurality of back end of at least one contextual definition relevant to each back end is correlated with other back end;
Access in these a plurality of back end the first back end corresponding to the second data element;
Determine by processing at least at least one relation relevant to this first back end the second back end that can be correlated with the data element of these a plurality of the first data elements, thus definite first data element corresponding with this second back end;
According to the relation that defines through at least one of storing or accessing between this first and second back end, determine at least one relation of this at least one interoperability parameter; With
According to determine at least one offset rule of this at least one interoperability parameter through at least one attribute relevant to this first and second back end of storage or access.
4. the system as claimed in claim 1, wherein this patient's knowledge base (24) is configured to ontology.
5. the system as claimed in claim 1, wherein this search module (30) disposes artificial intelligence to generate this request.
6. the system as claimed in claim 1, wherein this request is configured to the inquiry based on descriptive logic.
7. the system as claimed in claim 1, wherein this system also comprises interface module (28), is used for interfaces between patient's knowledge base (24) and local information storage system (26).
8. system as claimed in claim 3, wherein this system also comprises the domain knowledge base (22) that can carry out on this at least one processor, is used for storage and does not relate to these a plurality of patients and the information that relates at least one interoperability parameter relevant to each back end of these a plurality of back end; With
Wherein this patient's knowledge base (24) is accessed this domain knowledge base (22) to determine this at least one interoperability parameter.
9. system as claimed in claim 3, wherein:
This request is used for from this local information storage system (26) retrieve data with for the treatment of this second data element;
This patient's knowledge base (24) can also be carried out on this at least one processor, be used for generating the inquiry for local information storage system (26), from the exchanged data of the data retrieval relevant to this first data element, wherein at least one relation according to this at least one interoperability parameter generates this inquiry with request; Be used for receiving the swap data of this request; Be used for processing according to this at least one offset rule the swap data of this reception; Use this offset data to upgrade the data relevant to this second data element with being used for, to process this more new data by carrying out engine (16).
10. system as claimed in claim 2, wherein:
This request is used for upgrading with these exchanged data relevant to the second data element the data that local information storage system (26) is stored; With
This patient's knowledge base (24) can also be carried out on this at least one processor, is used for processing these exchanged data relevant to the second data element to compensate this exchanged data relevant with the second data element according to this at least one offset rule; Be used for generating update request to use exchanged Data Update first data element relevant to the second data element through compensation according at least one relation of this at least one interoperability parameter; Transmit this update request with being used for to this local information storage system (26).
11. the system as claimed in claim 1, wherein select this local information storage system (26) from have the dissimilar a plurality of local information storage system (26) that operate agreement, and this decision support system (DSS) (12) can set up semantic mutually with in case with this a plurality of local information storage system (26) swap data.
12. one kind is used for comprising step in the method that can carry out swap data between guide decision support system (DSS) and local information storage system (26):
Local information storage system (26) is provided, is used for storage a plurality of first data elements relevant to each data;
Provide to carry out and guide decision support system (DSS) (12), comprising:
Be provided for storing a plurality of guideline storage system carried out (14) of carrying out guide; With
Be provided for carrying out the execution engine (16) of at least one guide in these a plurality of guides, carry out described guide and comprise at least the data relevant to the second data element are processed;
Be created on the request of swap data between local information storage system and decision support system (DSS) (12), wherein these exchanged data are comprised in the data relevant to the second data element;
Determine corresponding to the first data element in this a plurality of first data elements of this second data element and define how at least one interoperability parameter of correspondence of this first and second data element;
Process this exchanged data relevant to the second data element according to this at least one interoperability parameter of determining, to set up the semantic use mutually between this first and second data element; With
These exchanged data of transmission between this first and second data element.
13. method as claimed in claim 12, wherein this at least one interoperability parameter comprises with lower at least one: at least one is used for the relation how this first and second data element of definition is correlated with, and at least one group is used at least one offset rule how definition compensates between this first data element and corresponding the second data element.
14. method as claimed in claim 13 determines that wherein the first data element also comprises step:
At least one relation that is associated to a plurality of back end, to each back end in these a plurality of back end and at least one attribute relevant with this each node are stored or are accessed, and how relevant with other back end each back end in described these a plurality of back end of at least one contextual definition relevant to each back end is;
Access in these a plurality of back end the first back end corresponding to the second data element;
Determine by processing at least at least one relation relevant to this first back end the second back end that can be correlated with the data element of these a plurality of the first data elements, thus definite first data element corresponding with this second back end;
According to the relation that defines through at least one of storing or accessing between this first and second back end, determine at least one relation of this at least one interoperability parameter; With
According to determine at least one offset rule of at least one group of this at least one interoperability parameter through at least one attribute relevant to this first and second back end of storage or access.
15. method as claimed in claim 14, wherein:
This step that generates request is used for from this local information storage system (26) retrieve data with for the treatment of this second data element; With
Should comprise step for the treatment of the step of these data:
Generation is for the inquiry of local information storage system (26), with the exchanged data of retrieval from the data relevant to this first data element, wherein
Generate this inquiry according at least one relation of this at least one interoperability parameter;
According to the swap data that receives in this inquiry at least one the offset rule processing response that compensates this swap data; Upgrade the data relevant to this second data element with this offset data of use, to process this more new data by carrying out engine (16).
16. method as claimed in claim 14, wherein:
The step of this generation request is used for upgrading with these exchanged data the data that local information storage system (26) is stored; With
Should comprise step for the treatment of the step of these data:
Process these exchanged data with these exchanged data of compensation according to this at least one offset rule;
Generate update request according at least one relation of this at least one interoperability parameter, to use exchanged Data Update first data element of this compensation; With
Transmit this update request to this local information storage system.
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US59107604P | 2004-07-26 | 2004-07-26 | |
| US60/591,076 | 2004-07-26 | ||
| PCT/IB2005/052447 WO2006013516A2 (en) | 2004-07-26 | 2005-07-21 | System and method for exchanging patient data with decision support systems for executable guideline |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1989504A CN1989504A (en) | 2007-06-27 |
| CN1989504B true CN1989504B (en) | 2013-06-19 |
Family
ID=35355951
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN200580025268XA Expired - Fee Related CN1989504B (en) | 2004-07-26 | 2005-07-21 | System and method for coupling patient data with executable guideline decision support systems |
Country Status (4)
| Country | Link |
|---|---|
| EP (1) | EP1774448A2 (en) |
| JP (1) | JP5475231B2 (en) |
| CN (1) | CN1989504B (en) |
| WO (1) | WO2006013516A2 (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8527293B2 (en) | 2007-03-30 | 2013-09-03 | General Electric Company | Method and system for supporting clinical decision-making |
| US20130117219A1 (en) * | 2011-11-03 | 2013-05-09 | Microsoft Corporation | Architecture for knowledge-based data quality solution |
| US20140358570A1 (en) * | 2013-06-04 | 2014-12-04 | Koninklijke Philips N.V. | Healthcare support system and method |
| US20190013093A1 (en) * | 2015-07-21 | 2019-01-10 | Arizona Board Of Regents On Behalf Of The University Of Arizona | Systems and methods for analyzing healthcare data |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH02267631A (en) * | 1989-04-07 | 1990-11-01 | Fujitsu Ltd | Processing system for generation of decision tree |
| JPH06168129A (en) * | 1992-11-30 | 1994-06-14 | Mitsubishi Electric Corp | Knowledge extracting device |
| JPH0773038A (en) * | 1993-09-06 | 1995-03-17 | Toshiba Corp | Knowledge expression converter |
| US6163781A (en) * | 1997-09-11 | 2000-12-19 | Physician Weblink Technology Services, Inc. | Object-to-relational data converter mapping attributes to object instance into relational tables |
| JP2003108377A (en) * | 2001-10-01 | 2003-04-11 | Seiko Epson Corp | Knowledge rule conversion apparatus, expert system, knowledge rule conversion program and construction method of expert system |
| JP4451037B2 (en) * | 2001-12-06 | 2010-04-14 | 株式会社ユニバーサルエンターテインメント | Information search system and information search method |
| US20040122787A1 (en) * | 2002-12-18 | 2004-06-24 | Avinash Gopal B. | Enhanced computer-assisted medical data processing system and method |
| CN1742275A (en) * | 2002-12-19 | 2006-03-01 | 皇家飞利浦电子股份有限公司 | Method and apparatus for selecting the operating parameters for a medical imaging system |
-
2005
- 2005-07-21 CN CN200580025268XA patent/CN1989504B/en not_active Expired - Fee Related
- 2005-07-21 WO PCT/IB2005/052447 patent/WO2006013516A2/en active Application Filing
- 2005-07-21 JP JP2007523215A patent/JP5475231B2/en not_active Expired - Fee Related
- 2005-07-21 EP EP05776290A patent/EP1774448A2/en not_active Ceased
Also Published As
| Publication number | Publication date |
|---|---|
| JP5475231B2 (en) | 2014-04-16 |
| JP2008507785A (en) | 2008-03-13 |
| WO2006013516A2 (en) | 2006-02-09 |
| WO2006013516A3 (en) | 2006-04-06 |
| CN1989504A (en) | 2007-06-27 |
| EP1774448A2 (en) | 2007-04-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20080097791A1 (en) | System and Method for Coupling Patient Data with Executable Guideline Decision Support System | |
| US6988088B1 (en) | Systems and methods for adaptive medical decision support | |
| US8121862B2 (en) | Medical support system | |
| Isern et al. | Ontology-driven execution of clinical guidelines | |
| RU2662205C2 (en) | Extension of clinical guidelines based on clinical expert recommendations | |
| US20090094063A1 (en) | Display and method for medical procedure selection | |
| JP2008522283A (en) | Manual therapy workflow management | |
| EP3675138B1 (en) | Medical imaging device control based on decision tree data structures | |
| EP2689361A1 (en) | Generating a report based on image data | |
| CN104781843B (en) | Clinical decision support | |
| CN102203784A (en) | Dynamic clinical worklist | |
| US20210104317A1 (en) | Systems and methods to configure, program, and personalize a medical device using a digital assistant | |
| US20140214451A1 (en) | Adaptive Medical Documentation System | |
| US8145506B2 (en) | Patient problem data structure and processing system | |
| CN1989504B (en) | System and method for coupling patient data with executable guideline decision support systems | |
| Giannoulis et al. | Designing and implementing a collaborative health knowledge system | |
| Schnurr et al. | Medicine 4.0—interplay of intelligent systems and medical experts | |
| JP2017033518A (en) | Device, method, system and program | |
| EP3659150B1 (en) | Device, system, and method for optimizing image acquisition workflows | |
| Michalowski et al. | MitPlan 2.0: enhanced support for multi-morbid patient management using planning | |
| Slotwiner | Electronic health records and cardiac implantable electronic devices: New paradigms and efficiencies | |
| US20210225467A1 (en) | Pathway information | |
| US20200051676A1 (en) | Device, system, and method for optimizing usage of prior studies | |
| WO2015031020A1 (en) | Systems and methods of generating patient notes with inherited preferences | |
| Silva et al. | Rule-based Clinical Decision Support System using the OpenEHR Standard |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20130619 Termination date: 20170721 |