Method and system for clinical data exchange framework
Through the communication between the clinical data access system and multiple remote clinical data databases and the use of data modeling templates, the complexity of clinical data exchange between heterogeneous systems is solved, efficient and economical data exchange is achieved, and maintenance costs are reduced.
Patent Information
- Application Number
- CN202380034611.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-20
- Filing Date
- 2023-04-11
- Publication Date
- 2024-11-26
AI Technical Summary
Existing healthcare information technology (IT) standards and supplier-specific solutions are difficult to achieve efficient and economical clinical data exchange across heterogeneous electronic health record systems, resulting in software complexity and high maintenance costs.
Adopt clinical data access system, which communicates with multiple remote clinical data databases, supports multiple access protocols, and recognizes and instantiates protocol-specific network sockets through link information and data modeling template registers to realize cross-heterogeneous systems. Clinical data exchange and application of data transformation and semantic translation.
It realizes efficient and economical clinical data exchange across heterogeneous electronic health record systems, reduces software complexity and maintenance costs, and improves the flexibility and scalability of data exchange.
Smart Images

Figure CN119032356A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to methods and systems for accessing and exchanging clinical data using a clinical data access system. Background Art
[0002] Electronic clinical data in healthcare scenarios has become the norm. Therefore, in electronic health record systems, most clinical information is digitized. However, there is no single standardized format for health records, and there are many different types and formats of electronic health record systems. For example, many electronic health record systems use the Fast Healthcare Interoperability Resources (FHIR) format created by the International Health Level Seven (HL7) Healthcare Standards Organization to store and transmit medical data. FHIR is a standard that describes the data format and elements (i.e., resources) and APIs for exchanging electronic health records. However, there are many other common formats for the organization, storage, and communication of clinical data, such as the Comprehensive Clinical Document Architecture (C-CDA).
[0003] There are many existing healthcare information technology (IT) standards and vendor-specific solutions that are designed to facilitate the exchange of clinical data across heterogeneous systems. However, these standards and proprietary solutions are generally not interoperable. In order for healthcare applications to interact with heterogeneous systems that support different protocols (such as HL7 and FHIR), the software modules used to handle data exchange must be re-implemented for each protocol, resulting in unnecessarily complex software solutions with high development and maintenance costs. Summary of the invention
[0004] Therefore, there is a continuing need in the art for methods and systems that can enable efficient and economical exchange of clinical data across heterogeneous electronic health record systems.
[0005] The present disclosure relates to innovative methods and systems for accessing clinical data using a clinical data access system. The clinical data access system communicates with multiple remote clinical data databases, the multiple remote clinical data databases including two or more different access protocols, and thus need to exchange clinical data across heterogeneous electronic health record systems. The clinical data access system also includes link information, including: (i) information about each of the one or more remote clinical data databases associated with each of the one or more objects, such as location and access protocol; and, (ii) an identifier for the one or more objects, the identifier being used to look up in the one or more remote clinical data databases. The system also includes a data modeling template register, which includes multiple data modeling templates of the clinical data access system for accessing each of the multiple remote clinical data databases, wherein the data modeling template includes at least an identification of the access protocol for the respective remote clinical data database, and a format of the clinical data stored in the respective remote clinical data database. The clinical data access system receives an access request for clinical data about one or more objects via a user interface of the clinical data access system, wherein the requested clinical data is stored in one or more of the remote clinical data databases. The clinical data access system obtains the link information, which also identifies one or more of the multiple remote clinical data databases that include the requested clinical data. The system obtains one or more data modeling templates via a data modeling template register, and the one or more data modeling templates specify protocol-specific data fields to be retrieved from the one or more remote clinical data databases. Once the remote clinical data database is identified, the clinical data access system instantiates a protocol-specific network socket for the identified remote clinical data database using the identified link information. The clinical data access system can now retrieve clinical data about the one or more objects from the remote clinical data database via the instantiated protocol-specific network socket. The system applies any data conversion required for the retrieved clinical data. The retrieved clinical data about the one or more objects can then be provided in response to a user request via any mechanism for sharing or providing clinical data.
[0006] In general, in one aspect, a method for accessing clinical data using a clinical data access system is provided. The clinical data access system communicates with multiple remote clinical data databases, and the multiple remote clinical data databases include two or more different access protocols. The method includes: (i) receiving an access request for clinical data about one or more objects via a user interface or client application of the clinical data access system, wherein the clinical data is stored in one or more of the remote clinical data databases; (ii) obtaining link information for the one or more objects via a link information register or via a client application, wherein the link information includes: (1) information about each of the one or more remote clinical data databases associated with each of the one or more objects, such as location and access protocol; and, (2) an identifier for the one or more objects, the identifier being used to look up in the one or more remote clinical data databases; (iii) obtaining a remote clinical data database for a remote clinical data database via a data modeling template register. (iv) instantiating a protocol-specific network socket for an identified remote clinical data database among the multiple remote clinical data databases using the link information specifying the one or more remote clinical data databases associated with the one or more objects; (v) retrieving clinical data about the one or more objects from an identified remote clinical data database among the multiple remote clinical data databases via the instantiated protocol-specific network socket; and (vi) providing the retrieved clinical data about the one or more objects.
[0007] According to an embodiment, the method also includes the following steps: via the data handler and orchestrator of the clinical data access system, using information from the one or more data modeling templates: applying data preprocessing, such as data conversion and semantic translation, to the retrieved clinical data; and, packaging the retrieved clinical data into a desired output data structure.
[0008] According to an embodiment, the method also includes: using the link information for a second remote clinical data database identified among the multiple remote clinical data databases, instantiating a second protocol-specific network socket for a second remote clinical data database identified among the multiple remote clinical data databases; retrieving clinical data about the one or more objects from the second remote clinical data database identified among the multiple remote clinical data databases via the instantiated second protocol-specific network socket; and merging and encapsulating the clinical data retrieved from a remote clinical data database identified among the multiple remote clinical data databases and a second remote clinical data database identified among the multiple remote clinical data databases.
[0009] According to an embodiment, the user browses and selects link information via the user interface or the client application for accessing one or more remote clinical data databases including the clinical data of the one or more subjects among the plurality of remote clinical data databases.
[0010] According to an embodiment, the method also includes the following steps: defining or modifying link information via the user interface or the definition or modification tool to add link information for a new clinical data database or updated link information for an existing clinical data database, the link information comprising at least: (i) information about each of the one or more remote clinical data databases associated with each of the one or more objects, such as location and access protocol; and, (ii) an identifier for the one or more objects, the identifier being used for searching in the one or more remote clinical data databases.
[0011] According to an embodiment, the method further comprises: defining or modifying a data modeling template for the clinical data access system via the definition or modification tool or user interface. According to an embodiment, defining a data modeling template for the clinical data access system comprises: identifying one or more protocol-specific data fields to be retrieved or updated; specifying data preprocessing to be applied to the retrieved data; and specifying how the retrieved data fields are to be organized and packaged in the output data structure and how a data formatting language is to be utilized.
[0012] According to an embodiment, an instantiated protocol-specific network socket generates a request to query or update the clinical data in one of the multiple remote clinical data databases identified, and wherein the instantiated protocol-specific network socket uses a message format of a specified access protocol to parse a received response to the query.
[0013] According to an embodiment, the linking information further comprises access and / or authentication credentials or encryption / decryption keys for one or more of the plurality of remote clinical data databases.
[0014] According to an embodiment, the system also includes a gateway service that handles dynamic data update requests by: listening to and receiving event-triggered push messages from the remote clinical data database, processing the received data using the data socket and data handler, storing the updates locally and sending them to the client application periodically or upon request.
[0015] According to another embodiment, a system for accessing clinical data is provided. The clinical data access system communicates with multiple remote clinical data databases, the multiple remote clinical data databases include two or more different access protocols, and also include clinical data stored about one or more objects, the system includes: a user interface; and a processor, which is configured to: (i) receive access requests for clinical data about one or more objects via the user interface system or a client application, wherein the clinical data is stored in one or more of the multiple remote clinical data databases; (ii) obtain link information for the one or more objects via a link information register or via the client application, wherein the link information includes: (1) information about each of the one or more remote clinical data databases associated with each of the one or more objects, such as location and access protocol; and (2) identifiers for the one or more objects, the An identifier is used to look up in the one or more remote clinical data databases; (iii) obtaining one or more data modeling templates via a data modeling template register using a template or template group identifier from a user interface or a remote client application, or directly via a remote client application, the data modeling template specifying protocol-specific data fields to be retrieved from the one or more remote clinical data databases; (iv) using the link information specifying the one or more remote clinical data databases associated with the one or more objects, instantiating a protocol-specific network socket for an identified remote clinical data database among the multiple remote clinical data databases; (v) retrieving clinical data about the one or more objects from an identified remote clinical data database among the multiple remote clinical data databases via the instantiated protocol-specific network socket; and (vi) providing the retrieved clinical data about the one or more objects.
[0016] According to an embodiment, the processor is also configured to: instantiate a second protocol-specific network socket for a second remote clinical data database identified among the multiple remote clinical data databases using the link information for the second remote clinical data database identified among the multiple remote clinical data databases; retrieve clinical data about the one or more objects from the second remote clinical data database identified among the multiple remote clinical data databases via the instantiated second protocol-specific network socket; and merge and encapsulate the clinical data retrieved from a remote clinical data database identified among the multiple remote clinical data databases and a second remote clinical data database identified among the multiple remote clinical data databases.
[0017] According to an embodiment, the user browses and selects link information via a user interface or a client application for accessing one or more remote clinical data databases including the clinical data of the one or more subjects among the plurality of remote clinical data databases.
[0018] According to an embodiment, the processor utilizes an instantiated protocol-specific network socket to generate a request to query or update the clinical data in a remote clinical data database identified among the multiple remote clinical data databases, and parses the received response to the query using a message format of a specified access protocol.
[0019] According to an embodiment, the linking information further comprises access and / or authentication credentials or encryption / decryption keys for one or more of the plurality of remote clinical data databases.
[0020] It should be recognized that all combinations of the foregoing concepts and the additional concepts discussed in more detail below (as long as these concepts are not mutually inconsistent) are expected to be part of the innovative subject matter disclosed herein. In particular, it is expected that all combinations of the claimed subject matter appearing at the end of this disclosure are part of the innovative subject matter disclosed herein. It should also be recognized that the terms explicitly adopted herein (which may also appear in any disclosure incorporated by reference) should be given the meaning most consistent with the specific concepts disclosed herein.
[0021] These and other aspects of the various embodiments will be apparent from and elucidated with reference to the embodiment(s) described hereinafter. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] In the drawings, the same reference numerals generally refer to the same parts in different views. The drawings illustrate features and ways of implementing various embodiments and should not be interpreted as limiting other possible embodiments falling within the scope of the claims. Moreover, the drawings are not necessarily drawn to scale, but generally focus on illustrating the principles of various embodiments.
[0023] Figure 1 is a flow chart of a method for accessing clinical data using a clinical data access system according to an embodiment.
[0024] Figure 2 is a schematic representation of a clinical data access system according to an embodiment.
[0025] Figure 3 is a flow chart of a method for creating or modifying link information or a data modeling template using a clinical data access system according to an embodiment.
[0026] Figure 4 is a schematic representation of a clinical data access system according to an embodiment. DETAILED DESCRIPTION
[0027] The present disclosure describes various embodiments of a clinical data exchange framework having a unified interface for data access, providing protocol-specific data access and processing instructions specified in external templates. More generally, the applicant has recognized and appreciated that it would be beneficial to provide a method and system for achieving efficient and economical clinical data exchange across heterogeneous electronic health record systems. The clinical data access system includes or communicates with multiple remote clinical data databases, the multiple remote clinical data databases including two or more different access protocols, and thus requires the exchange of clinical data across heterogeneous electronic health record systems. The clinical data access system also includes link information including: (i) information about each of the one or more remote clinical data databases associated with each of one or more objects, such as location and access protocol; and, (ii) an identifier for the one or more objects, the identifier being used to look up in the one or more remote clinical data databases. The system also includes a data modeling template register, which includes multiple data modeling templates of the clinical data access system for accessing each of the multiple remote clinical data databases, wherein the data modeling template includes at least an identification of the access protocol for the respective remote clinical data database, and a format of the clinical data stored in the respective remote clinical data database. The clinical data access system receives, via a user interface of the clinical data access system, an access request for clinical data about one or more objects, wherein the requested clinical data is stored in one or more of the remote clinical data databases. The clinical data access system obtains link information, which also identifies one or more of the multiple remote clinical data databases including the requested clinical data. The system obtains one or more data modeling templates via a data modeling template register, which specifies protocol-specific data fields to be retrieved from one or more remote clinical data databases. Once the remote clinical data database is identified, the clinical data access system instantiates a protocol-specific network socket for the identified remote clinical data database using the identified link information. The clinical data access system can now retrieve clinical data about the one or more objects from the remote clinical data database via the instantiated protocol-specific network socket. The system applies any data conversion required for the retrieved clinical data. The retrieved clinical data about one or more objects can then be provided in response to a user request via any mechanism for sharing or providing clinical data.
[0028] In certain embodiments, researchers and / or healthcare professionals can utilize the clinical data access system to retrieve and share clinical information about an object or patient. A persistent challenge for exchanging clinical information about an object or patient between heterogeneous health record systems is that clinical data is stored in these systems in different formats. The methods and systems described herein or otherwise contemplated provide a clinical data exchange framework with a unified interface for data access. This is achieved by allowing protocol-specific data access and processing instructions to be specified in external templates. In order to access a data set specified for an application via each protocol, a template can be defined for each protocol, each protocol using the appropriate resource naming of the protocol, a local data structure for storing clinical data to be processed by the application, and the mapping required between the external resource and the local data structure and any additional processing (e.g., data type conversion and semantic translation) to specify the data to be accessed. In order to communicate with an external resource library that supports a known protocol, a template designed for the protocol is loaded, and the system can communicate using the template information. Therefore, the methods and systems described herein or otherwise contemplated are extremely beneficial in applications for exchanging clinical information about an object or patient between heterogeneous health record systems.
[0029] In just one possible non-limiting embodiment, the clinical data exchange framework can be integrated with the MPEG-G standard for genomic data storage and management. Adapting MPEG-G to mature technologies in the healthcare IT ecosystem can reduce implementation costs and support a more diverse range of software systems. Seamless exchange of clinical and genomic data is a key component of precision medicine informatics solutions.
[0030] According to embodiments, the systems and methods described herein or otherwise contemplated may, in some non-limiting implementations, be implemented as elements of a commercial product of medical data, e.g. HealthSuite and IntelliBridge (available from Royal Philips of the Netherlands), or as elements of any other commercial product or any suitable system for efficient clinical data exchange.
[0031] refer to Figure 1 , in one embodiment, is a flow chart of a method 100 for accessing clinical data. The method may be performed by a clinical data access system. The method described in connection with the accompanying drawings is provided only as an example and should be understood not to limit the scope of the present disclosure. The clinical data access system may be any of the systems described or otherwise contemplated herein. The clinical data access system may be a single system or a plurality of different systems.
[0032] At step 110 of the method, a clinical data access system 200 is provided. Figure 2 , the system includes one or more of a processor 220, a memory 230, a user interface 240, a communication interface 250, and a storage device 260 interconnected via one or more system buses 210. It will be understood that in some aspects, Figure 2 The present invention constitutes an abstract concept, and the actual organization of the components of the system 200 may be different and more complex than illustrated. In addition, the clinical data access system 200 can be any system described or otherwise contemplated herein. Other elements or components of the system 200 are disclosed and / or contemplated elsewhere in this article.
[0033] According to an embodiment, the clinical data access system 200 includes or communicates with multiple remote clinical data databases 270, and the multiple remote clinical data databases 270 include two or more different access protocols. For example, the remote clinical data database 270 can be a component of a data sharing system or a collaborative network or queue for clinical data or research. Requesting and retrieving clinical data from a remote clinical data database requires a database-specific access protocol. However, given that the remote clinical data database is a component of a heterogeneous health record system, different database-specific access protocols exist within the multiple remote clinical data databases 270. Therefore, in order to share or retrieve data from a remote clinical data database, the clinical data access system must identify and utilize access protocols specific to the remote clinical data database.
[0034] According to an embodiment, an access protocol (also referred to as a data exchange protocol) is an interface specification that identifies the content of the exchanged data and how to implement and manage the data exchange. As just one example, Fast Healthcare Interoperability Resources (FHIR) is a data exchange protocol that describes clinical data formats and elements ("resources") and application programming interfaces (APIs), such as a RESTful protocol based on HTTP (i.e., an API that utilizes Representational State Transfer (REST)) for exchanging clinical data such as electronic health records. Using FHIR, clinical data such as medical health records are stored or represented in JSON, XML, or RDF format. The clinical data (which is formatted in JSON, XML, or RDF format) can be shared or communicated using an API such as a RESTful protocol, where HTTP methods are used to access data or resources in a network application. Other examples of access protocols include HL7, Phenopackets, C-CDA, and others.
[0035] One benefit of the methods and systems described or otherwise contemplated herein is that once the clinical data access system 200 identifies the access protocol utilized by any remote clinical data database or otherwise provides the system with an access protocol utilized by any remote clinical data database, the system can interact with the remote clinical data database. Thus, to communicate with a remote clinical data database, the clinical data access system 200 can first identify the access protocol utilized by the database. To facilitate this identification, the clinical data access system 200 includes a link information register 262. Although the link information register is in Figure 2 2 is shown as a component of the system's storage device 260, but it should be appreciated that the link information register may be a remote register in wired and / or wireless communication with the system 200.
[0036] According to an embodiment, the link information register includes information used by the clinical data access system to retrieve clinical data from one or more remote clinical data databases. In order to achieve this function, the link information register includes identification of clinical data stored in some or all of the multiple remote clinical data databases. In other words, the link information register includes information about clinical data stored in the remote clinical data database or a link to clinical data stored in the remote clinical data database. The identification of clinical data can be information stored in a database table or any other link format or mechanism.
[0037] As just one example, the link information register may include or communicate with a database of local data entities, such as samples in a variable call file or a gene expression file, and may also include or communicate with link information identifying in which of a plurality of remote clinical data databases 270 additional clinical data about the local data entity may be found. The link information may also be stored as metadata in a local file, such as in MPEG-G format (Moving Picture Experts Group-Genomics format for compression, storage, transmission and processing of genomic data), or any other format. Thus, according to an embodiment, the link information register includes an identification of the local data entity for which information may be retrieved (e.g., a sample ID), and a corresponding matching ID in (one or more) remote clinical data databases, either in plain text or in cipher text for increased security.
[0038] It is worth noting that the database identification information may be contained or found elsewhere. According to one non-limiting example, the researcher or healthcare professional may already know the target remote clinical data database in which the desired information may be found and may therefore identify the database.
[0039] According to an embodiment, the link information register also includes information required to facilitate communication between the clinical data access system 200 and multiple remote clinical data databases 270. For each remote clinical data database, the link information register may include a table or other mechanism for identifying the following: (i) the data exchange protocol utilized by the database; (ii) the format of the exchanged data; and (iii) any access credentials and / or keys used for encryption and / or decryption of the exchanged data. As a non-limiting example only, to access remote clinical data database X, the link information register may identify the data exchange protocol utilized by database X (FHIR), the format of the exchanged data from database X (XML), and the access credentials (login and password information) of database X. Therefore, according to an embodiment, the link information includes access / authentication credentials and encryption / decryption keys for each of one or more of the multiple remote clinical data databases.
[0040] According to an embodiment, the clinical data access system 200 includes a client application 280 or communicates with a client application 280. The client application can be any application that can utilize information within the system 200 and / or managed by the system 200. The client application (which can be a local or remote client application) optionally includes a user interface, such as the user interface 240 or a remote client application user interface. For example, a user can access the clinical data access system 200 via the user interface to enter an access request for clinical data about one or more objects. The client application 280 may also include link information for one or more objects, wherein the link information may include: (i) information about a remote clinical data database associated with each of the one or more objects, such as a location and access protocol; and, (ii) an identifier for one or more objects, the identifier being used to find in the remote clinical data database. The client application 280 may also include one or more data modeling templates that specify protocol-specific data fields to be retrieved from the remote clinical data database.
[0041] Link Information Register Example
[0042] The following is provided as a non-limiting example of data fields specified for link information. In this non-limiting example, XML format is utilized. Note that the scope of the core data component is not limited to the data elements described in this example, and the naming, organization, and format of the data elements need not be strictly followed. The proposed data elements may be expanded or omitted as needed for a specific application case.
[0043] As described herein or otherwise contemplated, clinical data link information specifies a list of available external data sources, their properties and applicable data modeling templates, and which samples' clinical data they contain. According to an embodiment, clinical data link information consists of two main complex data elements: DataSource and Sample.
[0044] According to an embodiment, DataSources is a collection of DataSource elements, each DataSource element containing the following elements: (i) ID, a unique identifier of the data source; (ii) Name, a name of the data source; (iii) URL, a URL or other identifier of the location of the data source; (iv) Protocol, a data exchange protocol used by the data source, such as HL7 and FHIR; (v) AvailableTemplates, a collection of one or more Template elements, each Template element specifies the ID of an existing template in the register that can be used with the data source.
[0045] According to an embodiment, Samples is a collection of Sample elements, each Sample element containing the following elements: (i) ID, a sample identifier; (ii) AvailableDataSources, a collection of DataSource elements, each DataSource element specifies the data source ID containing the clinical data of the sample; (iii) Metadata, a complex structure that specifies external data field values associated with the sample that can be used for querying. According to an embodiment, it has an attribute IsEncrypted, which, if set to true, indicates that all associated field values are ciphertext. Otherwise, they are plaintext. It is a collection of one or more Field elements, each Field element having an Id attribute that specifies the external data field for querying and the unique field value of the sample. And (iv) IsEncrypted, an encrypted identifier. If IsEncrypted is true, the Metadata value should be encrypted. If IsEncrypted is false, the Metadata value is not encrypted.
[0046] Referring to Table 1, in one embodiment, is a non-limiting example of clinical data linkage information.
[0047] Table 1: Example clinical data link information specified in XML format
[0048]
[0049]
[0050] According to an embodiment, the clinical data access system 200 includes a template register 263, also referred to as a data modeling template register. Figure 2 2 is shown as part of the storage device 260 in the system, but it should be appreciated that the template registers can be remote registers in wired and / or wireless communication with the system 200.
[0051] According to an embodiment, the clinical data link information in the link information register specifies a data modeling template from the data modeling template register 263 that is applicable to a specific remote clinical data database.
[0052] According to an embodiment, the data modeling template in the register includes at least an identification of an access protocol for the respective remote clinical data database, and a format of clinical data stored in the respective remote clinical data database. According to an embodiment, the data modeling template is defined for a specific clinical data exchange protocol and is therefore applicable to a clinical data database that supports the protocol. Therefore, the data modeling template may include one or more of the following: (i) a specified protocol; (ii) external data resources / fields to be extracted / updated; (iii) any required data conversion or semantic translation process between external and local data sources; (iv) a local data structure mapped to the external data resource / field; (v) a local data format (e.g., XML, JSON, or delimited table format and other examples); and / or (vi) a unique template ID and a template group ID, so that the same template group ID can be assigned to templates of different protocols but sharing the same local data structure and serving the same purpose.
[0053] As a non-limiting example only, to access a remote clinical data database X, the link information register may identify the data exchange protocol (FHIR) used by the database (X), the format (XML) of the exchanged data from database X, and the access credentials (login and password information) for database X.
[0054] As just one non-limiting example, the link information register may identify from the data modeling template register that data modeling template A is used to access database X. Thus, data modeling template A will include the data exchange protocol (FHIR) used by database X. Data modeling template A may also include identification of one or more data resources or fields from remote database X (which data resources or fields are to be extracted or updated via communications from the system), and identification of the local data format (XML in this context) of the sample ID in the clinical data access system, and instructions for converting or translating data from the format in the remote database X into the XML format of the clinical data access system.
[0055] Data Modeling Template Examples
[0056] The following is provided as a non-limiting example of data fields specified for a data modeling template. In this non-limiting example, XML format is utilized. Note that the scope of the core data components is not limited to the data elements described in this example, and the naming, organization, and format of the data elements need not be strictly followed. The proposed data elements may be expanded or omitted depending on the needs of a specific application case.
[0057] As described herein or otherwise contemplated, a data modeling template specifies its designated data exchange protocol, data resources / fields to be extracted from an external data repository, instructions for data mapping and processing, and output data structure and format. According to a non-limiting embodiment, a data modeling template may include the following elements: (i) ID, a unique identifier of the template; (ii) GroupId, an ID of its template group, where templates belonging to the same group should share the same local data structure and serve the same purpose; (iii) Name, the name of the template; (iv) Protocol, a clinical data exchange protocol, such as FHIR, HL7, Phenopackets, etc.; and (v) Method, an HTTP communication method operation type, such as 'Get' 'Post', etc. The HTTP communication method may be a standard communication method used in the art.
[0058] According to an embodiment, the data modeling template may additionally include a Request element. The Request element is a complex type data structure used to specify an external data field that can be used for querying and filtering. According to an embodiment, the Request element may include the following sub-elements: (i) RequestField, an "Id" attribute that specifies a unique identifier of an external data field that can be used for querying using the template; and, (ii) FilteredBy, an "Id" attribute that specifies a unique identifier of an external data field that can be used to filter the results.
[0059] According to an embodiment, the data modeling template may additionally include a Response element. The Response element is a complex type data structure used to specify a query response data structure, a mapping from an external data resource / field, and required data type conversion and translation. According to an embodiment, the Response element may include one or more ResponseField elements with the following attributes: (i) Id, the ID of the data field in the response data structure; (ii) Source, the ID of the external data resource / field whose data is mapped to the response data field; (iii) SourceDataType, the original data type of the external data field; (iv) TargetDataType, the target data type of the response data field, if it is different from the source data type, data type conversion should be applied; (v) SourceCodingSystem, the original coding system used by the external data field, such as LOINC or SNOMED; and (vi) TargetCodingSystem, the target coding system used by the response data field, if it is different from the source coding system, semantic translation should be applied.
[0060] Referring to Table 2, in one embodiment, is a non-limiting example of a data modeling template.
[0061] Table 2: Example data modeling template specified in XML format
[0062]
[0063]
[0064] Back to Figure 1 In the method 100 of the present invention, at step 120 of the method, a clinical data access system receives a request to access clinical data about one or more subjects or to access information about one or more samples of the one or more subjects. For example, the clinical data can be a medical health record or can be any clinical data used by researchers or healthcare professionals, including but not limited to laboratory results, demographics, genomic information, or any other type of medical, research or other analysis or measurement of a sample or subject.
[0065] According to an embodiment, a request to access clinical data can be received at a clinical data access system via a user interface 240 of the system. Alternatively, a remote system query or command can be made from a wired and / or wireless communication with the clinical data access system. According to an embodiment, a request to access clinical data can be received at a clinical data access system via a user interface of a clinical application 280. Some or all of the clinical data access systems can be cloud-based systems. Therefore, users such as clinicians, researchers, or healthcare professionals can access commands or query user interfaces via a network portal or application.
[0066] According to an embodiment, the request for clinical data includes an identification of a subject or sample, and more information about the subject or sample will be requested and optionally obtained from a remote database. For example, a clinician can request any additional information about subject Y from one or more remote databases. As another example, a researcher can request gene expression data from database X to supplement local sequencing data for one or more subject samples.
[0067] According to another embodiment, the request or command is a push from one or more of the remote clinical data databases. For example, the remote clinical data database may receive new information, such as clinical data or analytical data for a patient or sample, and be programmed or directed to share the new information with the clinical data access system. Thus, the remote clinical data database may send a push to the system to initiate communication with the client application(s) requesting dynamic updates from the database.
[0068] At step 130 of the method, the clinical data access system 200 obtains link information for one or more objects via a link information register 262 or directly via a client application 280, wherein the link information includes: (i) information about a remote clinical data database associated with each of the one or more objects, such as a location and access protocol, and (ii) an identifier for the one or more objects, the identifier being used to search in the remote clinical data database. According to an embodiment, a user browses and selects link information in the link information register or in a remote client via a user interface 240 of the system or via a client application 280 to access one or more remote clinical data databases including clinical data of a desired object in a plurality of remote clinical data databases.
[0069] According to an embodiment, the clinical data access system includes an orchestrator 264 that facilitates the identification function. For example, the orchestrator 264 can be a module of the clinical data access system, which therefore means that the orchestrator can be a packaged functional hardware unit designed to be used with other components, and / or a portion of a program that performs a specific function in the related functions.
[0070] At step 140 of the method, the system obtains one or more data modeling templates specifying protocol-specific data fields to be retrieved from a remote clinical data database via the data modeling template register 253 using a template or template group identifier from the user interface 240 or directly via a client application.
[0071] According to an embodiment, the orchestrator is a local orchestrator or a remote orchestrator in wired and / or wireless communication with the link information register 262 and the template register 263. Upon receiving a query or command from a user or other system or a push for data sharing from a remote database, the orchestrator identifies one or more remote clinical data databases including clinical data among a plurality of remote clinical data databases using the link information register, and link information and a data modeling template for each of the one or more identified remote clinical data databases.
[0072] According to an embodiment, the orchestrator parses the link information of the remote database from the link information register, including the identification of the data modeling template for the remote database. The orchestrator loads the appropriate (one or more) data modeling templates for the protocol definition of the identified (one or more) remote databases.
[0073] At step 150 of the method, the orchestrator instantiates a protocol-specific network socket using link information specifying a remote clinical data database associated with one or more objects to handle communications with the identified remote clinical data database. According to an embodiment, a network socket is a software structure for a networking architecture as defined by an application programming interface (API) specific to the system and / or remote database. The protocol-specific network socket may be an Internet socket, or may be any other suitable socket for implementing communications between a clinical data access system and a remote database. According to an embodiment, the instantiated protocol-specific network socket is created for communication and terminates when the communication is completed or when any other termination programming is implemented (including but not limited to connection failure, timing, or any other trigger).
[0074] At step 160 of the method, the system communicates with the remote clinical data database using the instantiated protocol-specific network socket to access, request, retrieve, or otherwise obtain target clinical data from the remote database. According to an embodiment, link information for the database from a link information register and data modeling information from a data modeling template specific to the database are used by the orchestrator to obtain the requested information.
[0075] According to an embodiment, a protocol-specific network socket applies a specified protocol specification (e.g., FHIR and many other protocol specifications) to generate messages, such as query, update, or event-triggered push requests, which are sent to an external data repository of a selected data modeling template, and parse response messages from the external data repository.
[0076] According to an embodiment, an instantiated protocol-specific network socket generates a request to query and / or update clinical data in a remote clinical data database identified among multiple remote clinical data databases, and the instantiated protocol-specific network socket uses the message format of the specified access protocol to parse the received response to the query.
[0077] At optional step 170 of the method, the clinical data access system applies any required or identified data conversion, translation, mapping, semantic translation and / or encapsulation / extraction to the clinical data received from the remote database according to the instructions defined in the data modeling template. Therefore, the clinical data access system may include a data handler 265 that applies the required data conversion and semantic translation to the results received via the data socket as specified in the template and merges them with the local data entities of the same object or sample at the clinical data access system. For example, the data handler 265 can be a module of the clinical data access system, which therefore means that the data handler can be a packaged functional hardware unit designed to be used with other components and / or a part of a program that performs specific functions in related functions. According to an embodiment, the orchestrator 264 can direct or control the data handler to perform one or more of its functions.
[0078] The retrieved clinical data may be provided in any format in which the data is retrieved from the remote clinical data database. However, at an optional step 180 of the method, the clinical data access system 200 packages the retrieved clinical data into a desired output data structure before providing the retrieved clinical data via a user interface. The desired output data structure may be predetermined or preprogrammed, or the desired output data structure may be defined or otherwise determined by a user via a user interface of the system and / or by a client application 280. For example, the retrieved clinical data may be packaged as a report for a user. There may be many formats for the packaged clinical data, including a display of the clinical data.
[0079] At step 190 of the method, the clinical data access system provides or otherwise stores or processes the received clinical data. According to one embodiment, the clinical data access system provides the received clinical data to a clinician, researcher, or healthcare professional via a user interface of the system. According to an embodiment, the system can display the report on a display of the system. Alternatively, the report can be transmitted to another device via wired and / or wireless communication. For example, the system can transmit the report to a mobile phone, a computer, a laptop, a wearable device, and / or any other device configured to allow display and / or otherwise transmit the report.
[0080] According to an embodiment, the clinical data access system writes the received clinical data to a local database or file. For example, the clinical data access system can store the received clinical data in a file or database of the clinical data access system or another system in MPEG-G format. According to an embodiment, the clinical data access system provides the received clinical data to another application of the clinical data access system or an application of another system that will utilize the data. According to yet another embodiment, the clinical data access system performs two or more of these functions.
[0081] refer to Figure 3 , in one embodiment, is a method 300 for defining or modifying link information in a link information register 262 or a client application 280 and / or defining or modifying a data modeling template in a data modeling template register 263 .
[0082] According to an embodiment, at step 310 of the method, a link information interface, such as a user interface 240 or another interface tool, is provided or otherwise accessed by a user. A user such as a clinician, researcher, healthcare professional, or programmer may access the link information interface to define link information. As described herein or otherwise contemplated, the link information in the link information register 262 of the clinical data access system 200 includes information used by the clinical data access system to retrieve clinical data from one or more remote clinical data databases. The link information may also include an identification (e.g., a sample ID) of a local data entity for which information may be retrieved, and a corresponding matching ID in (one or more) remote clinical data databases, either in plain text or in ciphertext to increase security. According to an embodiment, the link information register also includes information required to facilitate communication between the clinical data access system 200 and multiple remote clinical data databases 270. For each remote clinical data database, the link information register may include a table or other mechanism for identifying the following: (i) a data exchange protocol used by the database; (ii) a format for exchanged data; and (iii) any access credentials and / or keys for encryption and / or decryption of exchanged data.
[0083] Thus, the user can define any of these elements of link information in the link information register 262 and / or the client application 280. For example, at step 312 of the method, the user defines the link information. This can include entering information into predefined fields, or otherwise entering or uploading information that populates one or more fields of link information in the link information register. As just one example, the user can provide a sample ID for a local data entity, and a corresponding matching ID for a sample in a remote clinical data database. As another example, the user can identify a data exchange protocol used by a remote clinical data database, and a data format used by a remote clinical data database. This information can be manually entered or uploaded using a standard method for providing data or data sets.
[0084] At optional step 314 of the method, the user may modify any of these elements of the link information in the link information register 262. This may include modifying existing information about a remote clinical data database, or adding new information about a database. The user may provide the information manually, or may upload the information using standard methods for modifying data or data sets. For example, modifying the link information may include uploading link information for an existing clinical data database and / or adding link information for a new clinical data database.
[0085] At step 330 of the method, the link information defined for the remote clinical data database and / or the modified information for the remote clinical data database is stored in the link information register 262 of the clinical data access system, where it can be accessed in the future.
[0086] According to an embodiment, at step 320 of the method, a data modeling template interface is provided, for example, via the user interface 240, or otherwise accessed by a user. A user, such as a clinician, a researcher, a healthcare professional, or a programmer, may access the data modeling template interface to define data modeling templates for the data modeling template register 263. As described herein or otherwise contemplated, the modeling templates in the data modeling template register 262 of the clinical data access system 200 include at least an identification of an access protocol for a respective remote clinical data database, and a format of clinical data stored in the respective remote clinical data database, as well as other possible information as described herein or otherwise contemplated. Thus, a data modeling template may include one or more of the following: (i) a specified protocol; (ii) external data resources / fields to be extracted / updated; (iii) any required data conversion or semantic translation process between the external data source and the local data source; (iv) a local data structure mapped to the external data resource / field; (v) a local data format (e.g., XML, JSON, or a defined tabular format and other paradigms); and / or (vi) a unique template ID and a template group ID, so that templates of different protocols but sharing the same local data structure and serving the same purpose can be assigned the same template group ID.
[0087] Thus, a user can define any of these elements of a data modeling template. For example, at step 322 of the method, a user defines one or more data fields of a data modeling template, such as a new template. This can include entering information into predefined fields, or otherwise entering or uploading information that populates one or more fields of model template information. As just one example, a user can define a specified protocol for a remote clinical data database, as well as the data conversions required to convert data from the clinical database to a format used or required by a clinical data access system. This information can be entered manually or uploaded using standard methods for providing data or data sets.
[0088] According to an embodiment, a new data modeling template in a register of a clinical data access system is thus defined including: (i) identifying protocol-specific data fields to be retrieved or updated; (ii) specifying data preprocessing (e.g., data conversion or semantic translation) that needs to be applied to the retrieved data; and (iii) specifying how the retrieved data fields should be organized and packaged in an output data structure, and how to use a data formatting language, such as XML or JSON.
[0089] At optional step 324 of the method, the user may modify any of these elements of the data modeling template in the data modeling template register 263. This may include modifying existing information about the remote clinical data database, or adding new information about the database. The user may provide the information manually, or may upload the information using standard methods for modifying data or data sets.
[0090] At step 330 of the method, the new data modeling template and / or the modified data modeling template is stored in the data modeling template register 263 of the clinical data access system, where it can be accessed in the future.
[0091] refer to Figure 4 , in one embodiment, is a schematic representation 400 of a clinical data access system and method, including different functional components and their relationships. According to a non-limiting example, the schematic representation also illustrates how the framework can be integrated with an MPEG-G server, hospital systems, and applications that require clinical data as input. Note that link information can be stored directly within the MPEG-G dataset as metadata or link attributes, rather than in a separate register, to indicate the availability of additional clinical data in external repositories and devices for specific sample access. By making the link information an inherent part of the MPEG-G dataset, it is ensured that clinical data exploration is always supported and will not be lost during file transfers or system migrations. Although Figure 4 The application of MPEG-G is provided as an example, but it will be appreciated that many other applications and examples are possible.
[0092] exist Figure 4 In the present invention, hospital system 400 (which can be one hospital "hospital system 1" or multiple hospitals "hospital system 1" ... "hospital system N") includes two components: (i) a backend EHR / HIS / LIS system 412, which communicates with some proprietary protocol, and (ii) a clinical data server 414, which interacts with the backend system and connects it to the external environment. According to an embodiment, if the EHR / HIS / LIS system can communicate directly with external applications using a commonly accepted data exchange protocol, the clinical data server can be omitted.
[0093] According to an embodiment, the clinical data server provides the following functionality: (i) translates and reformats query / update / response messages between internal and external protocols; (ii) performs message validation and discards any invalid messages; (iii) keeps track of any active dynamic update requests from external clients and, in response to receiving messages triggered by relevant events from backend systems, publishes push updates (e.g., FHIR bundles) to the corresponding data exchange gateway; and (iv) validates and authorizes data access requests as needed.
[0094] Reference again Figure 4 The clinical data access system includes an orchestrator 264 that communicates with a link information register 262 including link information and communicates with a data modeling template register 263 including a plurality of data modeling templates. Figure 3 As described, a user may define or modify a data modeling template. Thus, the system may include a component or module for interfacing with a data modeling template, such as a data modeling template builder 420, to enable building a new template or modifying an existing template.
[0095] Also in Figure 4 In the present invention, a user 430 can interact with the clinical data access system via a user interface, for example, the user interface can be a link information browser and / or query builder 440. The link information browser and / or query builder 440 allows the user to find or otherwise identify clinical data that can be retrieved, and to identify or select link information required to retrieve the clinical data.
[0096] The system may also include or communicate with another application 460 that utilizes clinical data retrieved from one or more remote databases 410. Similarly, the system may also include or communicate with an MPEG-G server 470 when used for this specific application.
[0097] refer to Figure 4, according to an embodiment, available link information can be extracted from a register or a data set. A user 430 can browse the link information in the link information register 262, including the availability of clinical information in one or more remote clinical data databases 410 for a specific sample, and the available data modeling templates in the template register 263. The user can select one or more samples for clinical data retrieval and the data modeling template to be applied. According to an embodiment, the orchestrator parses the link information associated with the selected sample and instantiates one or more protocol-specific network sockets 450 using the dispatched link and template information for handling communications with an external resource library. The network socket 450 generates a query message based on the protocol of the target server and uses the relevant link and template information, and parses the query response message received from the external resource library. According to an embodiment, the orchestrator uses the data handler to apply any required data conversion and semantic translation as specified in the template to the results from the data socket and merges them together. The merged results are presented to the user and / or stored in the data set.
[0098] Application Examples
[0099] The following non-limiting examples are provided merely to illustrate several applications or embodiments of the methods described herein or otherwise contemplated, and therefore do not limit the scope of the present application or the claims.
[0100] Example 1 - Exploring External Clinical Data Available for Datasets
[0101] In this example, a user explores a dataset of gene expression in an MPEG-G file that contains link information for specific samples together with additional clinical data, which can be retrieved from one or more remote clinical data databases. The samples of the dataset are patients undergoing clinical trials that are used to determine whether there is a set of genes that can predict the treatment response three months after the first dose of the drug is given based on its expression level measured before treatment. Three months have passed since the gene expression data was generated, and now the user wants to collect the latest clinical observations, including heart rate and blood pressure. The user finds that one or more of the samples have clinical data available in one or more remote clinical data databases, and there are applicable data modeling templates for retrieving the required clinical data. The user then selects all samples and data modeling templates, specifies that the query results should be stored as attributes associated with the samples of the dataset, and submits the query. Within a few minutes, the query response is received from one or more remote clinical data databases. The system automatically performs data parsing, conversion, translation, merging and formatting according to the protocol of the database and the information in the selected data modeling template. This achieves the generation of the required clinical data for all samples, which are then stored in the dataset as sample attributes using the MPEG-G codec. The data exchange framework makes the latest and accurate clinical data readily available, alleviating the burden of finding, downloading and preparing the required clinical data, thereby allowing users to focus on analysis.
[0102] Example 2 - Implementing live updates from external clinical data repositories to local datasets
[0103] In this example, the principal investigator (PI) of a clinical study has an MPEG-G dataset that contains link information for accessing additional clinical data of samples in one or more remote clinical data databases. There are hundreds of samples in the dataset, and the PI wants to monitor dynamic trends and statistics of certain health data of all samples every day for three months without manually retrieving and updating the database every day. Using the clinical data access system, the PI can submit a dynamic update request with link information, patient ID, and desired data modeling template. The gateway then deposits the dynamic update request to one or more remote clinical data databases, and when new observation data is added for the patient being monitored, the remote clinical data database sends an event-triggered data push request to the gateway. The clinical data access system collects the push updates, then regularly processes and merges the new data, and writes them to the dataset using the MPEG-G codec.
[0104] For example, according to an embodiment, the system includes a gateway service that handles dynamic data update requests by: listening to and receiving event-triggered push messages from a remote clinical data database, processing the received data using a data socket and a data handler, storing the updates locally and sending them to a client application periodically or upon request.
[0105] Example 3 - Easy integration of real-time clinical data into healthcare applications
[0106] In this example, software architects at a health technology company are looking for an easy solution to incorporate live clinical data of patients from multiple remote clinical data databases using different data exchange standards and vendor-specific solutions into their clinical decision support system. The user decides to use the clinical data access system to handle the extraction and preprocessing of clinical data. The software developer in the team selects the data exchange protocol that needs to be handled. In response, the tool displays a list of available data resources for the selected protocol. After that, the software developer selects the data fields required by the specific software module and specifies the field name, organization and format (e.g., JSON) of the output data structure, together with the mapping with the external data field and the required data type conversion and translation process. After clicking the "Build" button, a data modeling template is generated. Using the generated template and using appropriate link information and patient ID, the system can immediately retrieve the patient's clinical data and output them in a format that can be directly used by the software module. In this way, the problem of integrating live clinical data into a software solution is simplified to simply defining a protocol-specific data modeling template and coupling it to a software module that uses the extracted clinical data in a predefined format.
[0107] refer to Figure 2 , is a schematic representation of a clinical data access system 200, according to an embodiment. The system 200 may be any of the systems described herein or otherwise contemplated, and may include any of the components described herein or otherwise contemplated. It will be understood that Figure 2 The system 200 is an abstract concept in some respects, and the actual organization of the components of the system 200 may be different and more complex than that shown.
[0108] According to an embodiment, the system 200 includes a processor 220, which is capable of running instructions stored in the memory 230 or the storage device 260, or otherwise processing data, for example, to perform one or more steps of the method. The processor 220 can be formed by one or more modules. The processor 220 can take any suitable form, including but not limited to a microprocessor, a microcontroller, multiple microcontrollers, a circuit, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a single processor, or multiple processors.
[0109] Memory 230 may take any suitable form, including non-volatile memory and / or RAM. Memory 230 may include various memories, such as L1, L2 or L3 cache or system memory. Thus, memory 230 may include static random access memory (SRAM), dynamic RAM (DRAM), flash memory, read-only memory (ROM), or other similar memory devices. The memory may store an operating system, etc. RAM is used by the processor for temporary storage of data. According to an embodiment, the operating system may include code that controls the operation of one or more components of system 200 when run by the processor. It is apparent that in embodiments where the processor implements one or more of the functions described herein in hardware, the software corresponding to such functions described in other embodiments may be omitted.
[0110] The user interface 240 may include one or more devices for implementing communication with a user. The user interface may be any device or system that allows transmission and / or reception of information, and may include a display, a mouse, and / or a keyboard for receiving user commands. In certain embodiments, the user interface 240 may include a command line interface or a graphical user interface that may be presented to a remote terminal via a communication interface 250. The user interface may be located together with one or more other components of the system, or may be remote from the system and communicate with the system via a wired and / or wireless communication network.
[0111] The communication interface 250 may include one or more devices for implementing communication with other hardware devices. For example, the communication interface 250 may include a network interface card (NIC) configured to communicate according to an Ethernet protocol. Additionally, the communication interface 250 may implement a TCP / IP stack for communicating according to TCP / IP. Various alternative or additional hardware or configurations of the communication interface 250 will be apparent.
[0112] The storage device 260 may include one or more machine-readable storage media, such as a read-only memory (ROM), a random access memory (RAM), a magnetic disk storage medium, an optical storage medium, a flash memory device, or a similar storage medium. In various embodiments, the storage device 260 may store instructions executed by the processor 220 or data that the processor 220 may operate on. For example, the storage device 260 may store an operating system 261 for controlling various operations of the system 200.
[0113] It will be apparent that various information described as being stored in storage device 260 may additionally or alternatively be stored in memory 230. In this regard, memory 230 may also be viewed as constituting a storage device, and storage device 260 may be viewed as a memory. Various other devices will be apparent. Additionally, both memory 230 and storage device 260 may be viewed as non-transitory machine-readable media. As used herein, the term non-transitory will be understood to exclude temporary signals, but rather to include all forms of storage devices, including both volatile and non-volatile memories.
[0114] Although system 200 is shown as including one of each described component, in various embodiments, various components may be repeated. For example, processor 220 may include multiple microprocessors that are configured to independently run the methods described herein or are configured to perform the steps or subroutines of the methods described herein, so that multiple processors collaborate to implement the functions described herein. In addition, when one or more components of system 200 are implemented in a cloud computing system, various hardware components may belong to different physical systems. For example, processor 220 may include a first processor in a first server, and include a second processor in a second server. Many other variations and configurations are also possible.
[0115] The system may include, or communicate with, a plurality of remote clinical data databases 270, the plurality of remote clinical data databases including two or more different access protocols. For example, the remote clinical data database 270 may be a component of a data sharing system or a collaborative network or a queue for clinical data or research. Requesting and retrieving clinical data from a remote clinical data database requires a database-specific access protocol. However, given that the remote clinical data database is a component of a heterogeneous health record system, different database-specific access protocols exist within the plurality of remote clinical data databases 270. Therefore, in order to share or retrieve data from a remote clinical data database, the clinical data access system must identify and utilize an access protocol specific to the remote clinical data database.
[0116] The system may include or communicate with a client application 280. A client application may be any application that utilizes information within and / or managed by the system 200. The client application (which may be a local or remote client application) may optionally include a user interface, such as the user interface 240 or a remote client application user interface.
[0117] According to an embodiment, the storage device 260 of the system 200 may store one or more algorithms, modules and / or instructions to perform one or more functions or steps of the methods described herein or otherwise contemplated. For example, the system may include, among other instructions or data, a link information register 262, a data modeling template register 263, an orchestrator 264, a data handler 265 and / or a reporting instruction 266, as well as many other possible instructions and / or data.
[0118] According to an embodiment, the link information register 262 includes link information for multiple remote clinical data databases. As described herein or otherwise contemplated, the link information in the link information register 262 of the clinical data access system 200 includes information used by the clinical data access system to retrieve clinical data from one or more remote clinical data databases. The link information may also include an identifier of a local data entity whose information can be retrieved (e.g., a sample ID), and a corresponding matching ID in (one or more) remote clinical data databases, either in plain text or in ciphertext for increased security. According to an embodiment, the link information register also includes information required to facilitate communication between the clinical data access system 200 and multiple remote clinical data databases 270. For each remote clinical data database, the link information register may include a table or other mechanism for identifying: (i) the data exchange protocol used by the database; (ii) the format of the exchanged data; and (iii) any access credentials and / or keys for encryption and / or decryption of the exchanged data.
[0119] According to an embodiment, the data modeling template register 263 includes a plurality of data modeling templates. According to an embodiment, the data modeling templates in the register include at least an identification of an access protocol for a respective remote clinical data database, and a format of clinical data stored in a respective remote clinical data database. According to an embodiment, the data modeling template is defined for a specific clinical data exchange protocol and is therefore applicable to a clinical data database that supports the protocol. Therefore, the data modeling template may include one or more of the following: (i) a specified protocol; (ii) external data resources / fields to be extracted / updated; (iii) any data conversion or semantic translation required between an external data source and a local data source; (iv) a local data structure with a mapping to an external data source / field; (v) a local data format (e.g., XML, JSON, or a defined table format, among other examples); and / or (vi) a unique template ID and a template group ID, so that the same template group ID can be assigned to templates of different protocols but sharing the same local data structure and serving the same purpose.
[0120] According to an embodiment, the orchestrator 264 is a component or module of the clinical data access system, which uses the link information register 262 to identify one or more remote clinical data databases in the plurality of remote clinical data databases 270 that include the requested clinical data. The orchestrator also instantiates a protocol-specific network socket of the remote clinical data database to enable communication of clinical data about one or more objects from the remote clinical data database. The orchestrator can also direct the data handler 265 to perform some or all of its functions.
[0121] According to an embodiment, the data handler 265 applies any required or identified data conversion, translation, mapping and / or encapsulation / extraction to the clinical data received from the remote database according to the instructions defined in the data modeling template, and merges the data with the local data entity for the same object or sample at the clinical data access system. For example, the data handler 265 can be a module of the clinical data access system, which means that the data handler can be a packaged functional hardware unit and / or a part of a program that performs a specific function in the related functions designated for use with other components. According to an embodiment, the orchestrator 264 can direct or control the data handler to perform one or more of its functions.
[0122] According to an embodiment, the report instruction 266 guides the system to provide information retrieved from one or more remote clinical data databases to the user via a user interface, or write the data to a file, or provide the data to another application. According to an embodiment, the system can display the report on a display of the system. The display may include information about the identified data or any other information. Alternatively, the report can be transmitted to another device via wired and / or wireless communication. For example, the system can transmit the report to a mobile phone, a computer, a laptop, a wearable device and / or any other device configured to allow display and / or other communication of the report.
[0123] According to an embodiment, the clinical data access system is configured to process thousands or millions of data, including identifying link information from a link information register, identifying a data modeling template from a data modeling template register, instantiating a network socket for communication, sending a request to one or more remote clinical data databases, receiving a response to the query, and processing the data in the received response to provide information to a user and / or write to a local file and / or provide the data to another application. This requires processing millions of data points. Therefore, retrieving this remote data and using it locally includes a large amount of calculation and analysis, which the human brain cannot complete in a lifetime or several lifetimes. In addition, by providing a faster and more efficient method for communicating between heterogeneous data systems, the methods and systems described herein or otherwise contemplated are technically improved over previous systems that could not perform the same functions in the same manner.
[0124] All definitions, as defined and used herein, should be understood to control over dictionary definitions, definitions in documents incorporated by reference, and / or ordinary meanings of the defined terms.
[0125] The indefinite articles "a" and "an" as used herein in the specification and claims, unless explicitly indicated to the contrary, should be understood to mean "at least one".
[0126] The phrase "and / or" as used herein in the specification and claims should be understood to mean "either or both" of the elements so combined, i.e., elements that are present in some cases in combination and in some cases in isolation. Multiple elements listed with "and / or" should be interpreted in the same manner, i.e., "one or more" of the elements so combined. In addition to the elements specifically identified by the "and / or" clause, other elements may optionally be present, whether or not related to those elements specifically identified.
[0127] As used herein in the specification and claims, "or" should be understood to have the same meaning as "and / or" defined above. For example, when separating items in a list, "or" or "and / or" should be interpreted as inclusive, i.e., including at least one, but also including multiple elements or more than one of the listed elements, and optionally additional unlisted items. Only terms that clearly indicate the opposite meaning, such as "only one of..." or "exactly one of...", or when used in the claims, "consisting of..." will refer to including multiple elements or exactly one of the listed elements. In general, the term "or" used in this article should be interpreted as indicating exclusive alternatives (i.e., "one or the other, but not both") only when it is followed by an exclusive term (e.g., "any," "one of," "only one of..." or "exactly one of...").
[0128] As used herein in the specification and claims, the phrase "at least one" when referring to a list of one or more elements should be understood to mean at least one element selected from any one or more elements in the list of elements, but does not necessarily include at least one of each element specifically listed in the list of elements, nor does it exclude any combination of elements in the list of elements. This definition also allows that other elements may optionally exist in addition to the elements specifically specified in the list of elements referred to by the phrase "at least one", whether or not related to those specifically specified.
[0129] It should also be understood that in any method claimed herein that includes more than one step or action, the order of the steps or actions of the method is not necessarily limited to the order of the steps or actions of the method as described unless explicitly stated to the contrary.
[0130] In the claims, as well as in the above specification, all transitional terms, such as "includes", "comprising", "with", "having", "containing", "involving", "having", "consisting of", etc., are to be understood as open-ended, i.e., meaning including but not limited to. Only the transitional terms "consisting of" and "consisting essentially of" shall be closed or semi-closed transitional terms, respectively.
[0131] Although several innovative embodiments have been described and illustrated herein, a person of ordinary skill in the art will readily conceive of a variety of other means and / or structures for performing the functions described herein and / or obtaining one or more of the results and / or advantages described herein, and each of these variations and / or modifications is considered to be within the scope of the innovative embodiments described herein. More generally, those skilled in the art will recognize that all parameters, dimensions, materials, and configurations described herein are intended to be exemplary, and that actual parameters, dimensions, materials, and / or configurations will depend on the specific application or applications for which the innovative teachings are used. Those skilled in the art will recognize or be able to use no more than routine experiments to ascertain many equivalents to the specific innovative embodiments described herein. Therefore, it is to be understood that the foregoing embodiments are provided by way of example only, and within the scope of the claims and their equivalents, the innovative embodiments may be practiced in other ways other than the specifically described and claimed solutions. The innovative embodiments of the present disclosure are directed to each individual feature, system, product, material, kit, and / or method described herein. In addition, any combination of two or more such features, systems, articles, materials, kits and / or methods (if such features, systems, articles, materials, kits and / or methods are not mutually inconsistent) is also included in the innovative scope of the present disclosure.
Claims
1. A method (100) for accessing clinical data using a clinical data access system (200), wherein: The clinical data access system communicates with a plurality of remote clinical data databases (270), the plurality of remote clinical data databases comprising two or more different access protocols, the method comprising: receiving (120) via a user interface (240) or a client application (280) of the clinical data access system, an access request for clinical data regarding one or more subjects, wherein the clinical data is stored in one or more of the remote clinical data databases; obtaining (130) link information for the one or more objects via a link information register (262) or via a client application, wherein the link information includes: (i) information about each of the one or more remote clinical data databases associated with each of the one or more objects, such as a location and access protocol, and (ii) an identifier for the one or more objects, the identifier being used for lookup in the one or more remote clinical data databases; obtaining (140) one or more data modeling templates specifying protocol-specific data fields to be retrieved from the one or more remote clinical data databases via a data modeling template register (263) using a template or template group identifier from a user interface or a remote client application, or directly via the remote client application; instantiating ( 150 ) a protocol-specific network socket for an identified one of the plurality of remote clinical data databases using the link information specifying the one or more remote clinical data databases associated with the one or more objects; retrieving (160) clinical data regarding the one or more subjects from an identified one of the plurality of remote clinical data databases via the instantiated protocol-specific network socket; and The retrieved clinical data regarding the one or more subjects is provided (190).
2. The method of claim 1, further comprising the following steps of using information from the one or more data modeling templates via a data handler (265) and an orchestrator (264) of the clinical data access system: applying (170) data preprocessing, such as data conversion and semantic translation, to the retrieved clinical data; and The retrieved clinical data is packaged (180) into a desired output data structure.
3. The method of claim 1, further comprising instantiating ( 150 ) a second protocol-specific network socket for a second remote clinical data database identified among the plurality of remote clinical data databases using the link information for a second remote clinical data database identified among the plurality of remote clinical data databases; retrieving (160) clinical data regarding the one or more subjects from the identified second remote clinical data database of the plurality of remote clinical data databases via the instantiated second protocol-specific network socket; as well as The clinical data retrieved from an identified one of the plurality of remote clinical data databases and a second identified one of the plurality of remote clinical data databases are merged and packaged (180).
4. The method of claim 1, wherein: The user browses and selects link information via the user interface or the client application for accessing one or more remote clinical data databases including the clinical data of the one or more subjects among the plurality of remote clinical data databases.
5. The method of claim 1, further comprising the steps of: Via the user interface or the definition or modification tool, define (312) or modify (314) link information to add link information for a new clinical data database or update link information for an existing clinical data database, wherein the link information includes at least: (i) information about each of the one or more remote clinical data databases associated with each of the one or more objects, such as location and access protocol; and, (ii) an identifier for the one or more objects, which is used to search in the one or more remote clinical data databases.
6. The method of claim 1, further comprising the steps of: A data modeling template for the clinical data access system is defined (322) or modified (324) via the definition or modification tool or user interface.
7. The method of claim 6, wherein: The data modeling template for defining the clinical data access system includes: identifying one or more protocol-specific data fields to be retrieved or updated; Specify data preprocessing to be applied to the retrieved data; and Specify how the retrieved data fields are to be organized and packaged in the output data structure and how a data formatting language is to be utilized.
8. The method of claim 1, wherein: The instantiated protocol-specific network socket generates a request to query or update the clinical data in a remote clinical data database identified among the multiple remote clinical data databases, and wherein the instantiated protocol-specific network socket uses a message format of a specified access protocol to parse a received response to the query.
9. The method of claim 1, wherein: The linking information also includes access and / or authentication credentials or encryption / decryption keys for one or more of the plurality of remote clinical data databases.
10. The method of claim 1, wherein: The system also includes a gateway service that handles dynamic data update requests by: listening to and receiving event-triggered push messages from the remote clinical data database, processing the received data using the data socket and data handler, storing the updates locally and sending them to the client application periodically or upon request.
11. A system (200) for accessing clinical data, wherein: The clinical data access system communicates with a plurality of remote clinical data databases (270), the plurality of remote clinical data databases including two or more different access protocols and also including stored clinical data about one or more subjects, the system comprising: A user interface (240); and A processor (220) configured to: (i) receive, via the user interface system or the client application (280), a request for access to clinical data about one or more objects, wherein the clinical data is stored in one or more of the plurality of remote clinical data databases; (ii) obtain, via the link information register (262) or via the client application, link information for the one or more objects, wherein the link information includes: (1) information about each of the one or more remote clinical data databases associated with each of the one or more objects, such as a location and an access protocol, and (2) an identifier for the one or more objects, the identifier being used for searching in the one or more remote clinical data databases; (iii) obtain, via the data modeling template register (262), link information for the one or more objects. 263) obtaining one or more data modeling templates using a template or template group identifier from a user interface or a remote client application or directly via a remote client application, wherein the one or more data modeling templates specify protocol-specific data fields to be retrieved from the one or more remote clinical data databases; (iv) instantiating a protocol-specific network socket for an identified remote clinical data database among the multiple remote clinical data databases using the link information specifying the one or more remote clinical data databases associated with the one or more objects; (v) retrieving clinical data about the one or more objects from an identified remote clinical data database among the multiple remote clinical data databases via the instantiated protocol-specific network socket; and (vi) providing the retrieved clinical data about the one or more objects.
12. The system of claim 11, wherein: The processor is further configured to: instantiate a second protocol-specific network socket for a second remote clinical data database identified among the plurality of remote clinical data databases using the link information for the second remote clinical data database identified among the plurality of remote clinical data databases; retrieving, via the instantiated second protocol-specific network socket, clinical data regarding the one or more subjects from the identified second remote clinical data database among the plurality of remote clinical data databases; The clinical data retrieved from an identified one of the plurality of remote clinical data databases and a second identified one of the plurality of remote clinical data databases are merged and packaged.
13. The system of claim 11, wherein: The user browses and selects link information via the user interface or client application for accessing one or more of the clinical data including the one or more subjects in the plurality of remote clinical data databases.
14. The system of claim 11, wherein: The processor utilizes the instantiated protocol-specific network socket to generate a request to query or update the clinical data in a remote clinical data database identified among the multiple remote clinical data databases, and parses a received response to the query using a message format of a specified access protocol.
15. The system of claim 11, wherein: The linking information also includes access and / or authentication credentials or encryption / decryption keys for one or more of the plurality of remote clinical data databases.
