WO2022112624A1 - Sistema y método de gestión para una arquitectura de base de datos multimodelo distribuida - Google Patents
Sistema y método de gestión para una arquitectura de base de datos multimodelo distribuida Download PDFInfo
- Publication number
- WO2022112624A1 WO2022112624A1 PCT/ES2021/070271 ES2021070271W WO2022112624A1 WO 2022112624 A1 WO2022112624 A1 WO 2022112624A1 ES 2021070271 W ES2021070271 W ES 2021070271W WO 2022112624 A1 WO2022112624 A1 WO 2022112624A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user
- data
- microservice
- database
- profile
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 12
- 238000012546 transfer Methods 0.000 claims description 21
- 230000006870 function Effects 0.000 claims description 10
- 230000010076 replication Effects 0.000 claims description 4
- CZMRCDWAGMRECN-FBXJDJJESA-N D-sucrose Chemical compound O[C@@H]1[C@@H](O)[C@H](CO)O[C@]1(CO)O[C@H]1[C@@H](O)[C@H](O)[C@@H](O)[C@H](CO)O1 CZMRCDWAGMRECN-FBXJDJJESA-N 0.000 claims description 2
- 238000007726 management method Methods 0.000 description 45
- 238000004891 communication Methods 0.000 description 5
- 238000010801 machine learning Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 4
- 238000003860 storage Methods 0.000 description 4
- 238000004458 analytical method Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 239000013598 vector Substances 0.000 description 3
- 230000002776 aggregation Effects 0.000 description 2
- 238000004220 aggregation Methods 0.000 description 2
- 238000013459 approach Methods 0.000 description 2
- 230000036541 health Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012360 testing method Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000000295 complement effect Effects 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000013467 fragmentation Methods 0.000 description 1
- 238000006062 fragmentation reaction Methods 0.000 description 1
- XVDFMHARQUBJRE-UHFFFAOYSA-N hydron;n-methyl-2-pyridin-2-ylethanamine;dichloride Chemical compound Cl.Cl.CNCCC1=CC=CC=N1 XVDFMHARQUBJRE-UHFFFAOYSA-N 0.000 description 1
- 238000005304 joining Methods 0.000 description 1
- 238000009533 lab test Methods 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000014759 maintenance of location Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000011159 matrix material Substances 0.000 description 1
- 238000011160 research Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
- 230000014616 translation Effects 0.000 description 1
- 238000011282 treatment Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/273—Asynchronous replication or reconciliation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
Definitions
- the present invention relates to a distributed multi-model database architecture, where the database architecture comprises a plurality of user microservices configured to create, store and manage graph databases with sensitive data from conventional databases. existing services, a management system for distributed multi-model database architecture, where the management system comprises a user interface, a plurality of profile microservices, a key-value database and middleware, and a method for manage a distributed multi-model database architecture.
- the records are usually scattered in different storages belonging to various hospitals, sometimes belonging to different jurisdictions. Even in the same hospital, different types of data are stored on different servers that are designed under different medical standards and thus each of these servers has its own data architecture and communication protocols (DICOM, LOINC, RxNORM, SNOMED CT, etc. ); In addition, each of these systems is developed and maintained by different providers, which gives more variability and complexity to data integration. This fragmentation of data is often a serious obstacle to collecting, updating, or researching these records, whether they are considered as a single patient or as a group. These data integrations, or data joins, typically occur at the application level, making data management complex. inefficient and very expensive, due to the need to configure caches, intermediate data lakes and scale databases and processing servers to perform data aggregations and translations.
- BDs databases
- RDBs relational databases
- These relational databases become especially complex and rigid when it comes to expressing relationships between data elements, especially in the case of complex relationships, for example, when it is necessary to obtain information from two or more related database tables ( multi-level joins); on the other hand, these multilevel joins are difficult to scale horizontally. Joins can efficiently compute statistics from existing database tables, but multilevel joining is also too complex for large data sets.
- DGPs database graphs
- BDGs can handle the real complexity of data dependencies.
- ML machine learning algorithms work much better with vectorized implementations, such as those for graph databases, and that implementation makes it much easier to use libraries to process data in parallel; since BDGs are normally represented using an affinity matrix, they share the same structure with vectorized machine learning applications.
- functions in a graph can be represented as a vector, which brings another advantage: graph analysis algorithms can be implemented directly in graph databases, allowing ML and graph analysis techniques to be executed in the same environment, making it possible to close cooperation with each other, for example by feeding the ML algorithms with graphical metrics computed as predictor variables; therefore, the same can be used environment to carry out analysis and efficiency of information and even compartmentalized searches, maintaining the privacy of patient information.
- BDRs are optimized for data aggregation
- other nonrelational databases focus on the volume and properties of the data; for example, BDGs are optimized for data connections:
- BDGs are designed to handle a high level of data complexity, in part because the structure of the data is not fixed in advance. But these are not all benefits: BDGs are also more expensive, and there are fewer tools available to perform complex operations in a production or service environment.
- the invention provides a management system for a distributed multi-model database architecture, the distributed multi-model database architecture comprising a plurality of user microservices, each connected to a database of a plurality of pre-existing relational databases stored on respective servers, where each user microservice is associated with a user, each user microservice is configured to create, store and manage a database of graphs, comprising nodes and edges, with related data with the associated user of the pre-existing database connected to the user microservice, each user microservice comprises an encrypted file that can be decrypted by the user microservice and that contains instructions to create and store the user database with related data with the associated user, each microservice of user is stored in the preexisting database server connected to the user microservice, and the user database is configured to be accessed only through the user microservice; wherein the management system is stored on a cloud server and wherein the management system comprises: a user interface, a plurality of profile microservices, where each profile microservice is associated with a single distinct user, in where each
- the management system provides centralized access to data stored in a plurality of distributed independent multi-model pre-existing databases, with a high degree of security and without loss of property by the legitimate owner of the data; the database architecture provides, for each legacy database, or node, a plurality of user microservices tasked with creating a user-specific data base (BDG) exclusively with user-related data from of the existing database, and the management of access and communication with the management system.
- BDG user-specific data base
- Gratos database data is stored on the legacy database server and encrypted.
- the management system is only authorized to access user microservices, and receives encrypted data, even without gaining access to the rest of the data in the pre-existing database; therefore a high level of security is achieved.
- Each profile microservice is associated with a single user, who preferentially maintains ownership of, or is duly authorized to access, certain data in pre-existing databases.
- the user would access the individual databases and manually extract the relevant information, if the entity hosting the databases allows it.
- the present invention overcomes such difficulties and provides a centralized database management system with a single authentication process through a user interface, a key-value database with an index with the locations of each of the data user interface, and middleware that manages the communication between the management system and the distributed database architecture.
- Profile microservices provide end-to-end management of permissions, data requests, and communications with the database architecture.
- the management system is hosted by a cloud server; per server in the cloud should be understood as a computer or computer system comprising a processor, storage media and Internet access, and configured to host and run the database management system.
- microservice should be understood as each of the software applications or elements of a microservice structure, as is known in the art.
- all microservices are related to users; for example, there may be only a single profile microservice for each user, while there may be more than one user microservice per user; in particular, for each user there is one user microservice per node.
- the names profile and user should be understood as simple denominations of convenience for a first class of microservices and a second class of microservices.
- the profile microservice will always have a higher hierarchy than the user microservice, and will have the authority to read the encrypted files generated by the user microservices.
- a graph database should be understood as either a non-relational database or a pure graph database, comprising nodes and vectors, and storing user-related data;
- the nodes of a BDG must be understood as vertices of the graph, or discrete data elements linked by means of vectors or edges to other vertices, and are different from the nodes that refer to these pre-existing databases.
- the key-value database should be understood as a hash function table comprising at least one index of the location of each data record stored in the graph databases related to each unique user, as well as other relevant data. .
- Middleware is an element configured to enable and manage communication and data transfer between the database architecture, in particular the user microservices, and the management system.
- the present invention is of particular interest for the management of patient records in a health system with a plurality of loosely related or independent databases belonging to autonomous or independent health institutions.
- a patient, the rightful owner of relevant data such as patient records, medical history, etc.
- the user interface is a web-based user interface.
- a web-based interface ensures that any user can access information from anywhere in the world, providing the user has the required permissions.
- the key-value database is configured as a distributed ledger. More particularly, the Clavel Valor database is configured as a distributed ledger (distributed iedger) of blockchains, so that any attempt to manipulate the information stored by a malicious user can be reported and tracked by a user. authorized.
- distributed ledger distributed iedger
- the key-value database comprises key-value pairs encrypted with a public key encryption algorithm.
- the key-value database is encrypted using an asymmetric cryptography system, which includes at least one public key and one private key.
- the key-value database comprises a key-value database manager.
- system further comprises a low-availability backup database controlled by the middleware.
- the middleware is partially stored on a legacy database server.
- part of the middleware is distributed across the nodes of the existing database servers, and is stored in the corresponding database servers, with a higher degree of integration.
- the middleware is configured as a peer-to-peer network.
- the middleware is configured to perform synchronous masterless replication between nodes of the grate databases.
- the middleware is configured to perform multicast queries according to a round-robin schedule.
- at least one profile microservice comprises an intermediate database configured to store data from the grate databases, location data with a hash function of the user microservices, and/or decryption keys.
- Intermediate databases are small-volume, user-specific databases for storage of various data, such as microservice locations and encryption/decryption keys; these intermediate databases function as local stores of information and allow faster access to a user's query.
- the invention provides a computer system comprising a cloud server configured to store and execute the management system according to the first inventive aspect.
- the computer system comprises at least one cloud server with an Internet connection, and optionally additional computers and/or similar devices such as portable devices, tablets, smartphones, and the like.
- the invention provides a distributed multi-model database architecture, comprising a plurality of user microservices, each connected to a database of a plurality of pre-existing relational databases stored on respective servers, in where each user microservice is associated with a user, each user microservice is configured to create, store and manage a database of graphs, comprising nodes and edges, with data related to the associated user from the connected pre-existing database
- each user microservice comprises an encrypted file that can be decrypted by the user microservice and that contains instructions to create and store the grates database with data related to the associated user
- each user microservice is stored in the server of the existing database connected to the m user microservice, the gratos database is configured to be accessed only through the user microservice.
- the user microservices make use of respective encrypted files to create or build the graph database; such encrypted file comprises the specific instructions for the task and is encrypted to avoid security threats. Therefore, the distributed multi-model database architecture advantageously provides a substitute database with a normalized model, regardless of the type of databases. pre-existing
- the encrypted file is encrypted with a public key encryption algorithm.
- Public key encryption algorithms advantageously provide a highly secure asymmetric encryption system that can withstand most attack attempts without requiring high processing load or processing times.
- the encrypted file comprises one or more of the following: user data, hash functions, metadata, encryption keys.
- the encrypted file advantageously stores the instructions to create, or build, the gratos database, and other useful data that ensures access to the gratos database and the security of the information; furthermore, the encrypted file can directly store certain data, instead of simply pointing to a different address.
- the encrypted file is encrypted as a JSON file.
- the JSON-formatted file preferably comprises the instructions to create, or build, the gratos database, as well as hash locations, metadata, and encryption keys for encrypted data that is not stored directly in the gratos database. ; Examples of such data not stored directly in the gratos database are DICOM files, high-resolution videos, or large files.
- the data in the grate databases is encrypted with a public key encryption algorithm.
- the encryption of the BDG data prevents any possible attack from a malicious user accessing the database.
- the data of the grata databases are coded according to DICOM and/or HL7 FHIFi medical standards. Compliance with medical standards, such as DICOM and/or HL7 FHIR ensures the compatibility of data from different sources, such as data from internal databases of hospitals, clinics, research centers and/or universities. Additionally, in one embodiment, the middleware comprises export interfaces configured to output standard compatible files with data from the databases.
- the data in the gratos databases is encoded as JSON files.
- the JSON format is a highly versatile file format that ensures interoperability of microservices and compatibility with pre-existing databases.
- the invention provides a method for managing a distributed multi-model database architecture according to the third inventive aspect with a management system according to the first inventive aspect, wherein the method comprises the steps of: receive, by a profile microservice, a request for data from a user interface, request, by a profile microservice, the location of data in one or more databases of gratos to the key-value database, transfer, by a profiling microservice, the data request and data location to the middleware, transfer, by the middleware, the data request to one or more of the user microservices of the gratos databases where the data is stored requested data, receiving, by the middleware, encrypted data from the one or more user microservices, transferring, by the middleware, the encrypted information to the microser profile vice.
- the invention provides a computer-readable medium comprising instructions that, when executed by a computer, cause the computer to perform the steps of: receiving, by a profile microservice, a request for data from a user interface, request, by a profile microservice, the location of data in one or more databases of gratos to the key-value database, transfer, by a profile microservice, the data request and location to the middleware, transfer, by the middleware, the data request to one or more user microservices in the gratos databases where the requested data is stored, receive, by the middleware, encrypted data from the one or more user microservices, transfer, via the middleware, the encrypted information to the profile microservice.
- Figure 1 shows a preferred embodiment of the management system.
- Figure 2 shows a preferred embodiment of the database architecture.
- Figure 3 shows another aspect of an embodiment of the database architecture.
- Figure 4 shows a preferred embodiment of the management system and database architecture.
- Figure 5 shows the physical structure of the management system and the database architecture.
- the invention is particularly suitable for the management of medical data stored in a plurality of local databases of medical institutions, such as hospitals, clinics and the like; these databases normally contain data from a high number of patients and most of them contain sensitive data; in conventional architectures, access to a single patient's data would entail granting access to the entire data set for all patients, as well as requiring individual access to each database. Consequently, the users are patients, but also doctors and researchers who want to obtain anonymous data from a wide range of sources.
- Figure 1 shows a preferred embodiment of the management system (1); the management system (1) comprises a plurality of profile microservices (3), of which only three are represented in this figure, connected to each other and to the user interface (2).
- the user interface (2) is preferably a web application, accessible from any device with an internet connection.
- the profile microservices (3) are grouped by containers of a suite of platform as a service (PaaS) software products that use OS-level virtualization to deliver the software in packages called containers. These containers are isolated from each other and bundle their own software, libraries, and configuration files; containers can communicate with each other through well-defined channels. All containers are run by a single operating system core and therefore use fewer resources than virtual machines.
- the profile microservices (3) also comprise an intermediate database in the event that the user wishes to permanently store data on the cloud server (10). In practice, the profile microservices (3) act as a virtual representation of the users and have full authority over the data owned by the user.
- the key-value database (4) is a blockchain-based hash function table with the location of each user's data in the database architecture (20).
- Middleware (5) is a distributed database management system NoSQL with peer-to-peer architecture that provides high availability between multiple data nodes, with asynchronous masterless replication between nodes installed within local databases (30) and the management system (1).
- the middleware 5 can execute multicast queries to a number of user microservices 11 through a round-robin scheduling system; the only user microservices (11) that respond to the query are the user microservices (11) that contain the data and have been authorized by the user to share it.
- the general scheme of the distributed multi-model database architecture (20) is shown in Figure 3, which represents four databases (30) or nodes.
- the distributed multi-model database architecture (20) is essentially a federated database with a plurality of pre-existing relational databases (30), data being managed on a per-user basis by a plurality of user microservices (11). , in such a way that only certain data owned by the user is extracted from the database (30), reorganized in a user-specific graph database (12) and encrypted with a public key algorithm, all according to the instructions of an encrypted file (13).
- Figure 3 shows a simplified view of the database architecture (20) with four databases (30) and a single user microservice (11) per database (30), whereas normally each database ( 30) will be associated with a plurality of microservices (11), normally one per user.
- Figure 2 shows a view of a possible embodiment of one of the database architecture nodes (20), with a single database (30) and four user microservices (11); Also, each user microservice (11) is connected to its corresponding graph database (12) and encrypted file (13).
- Figure 4 shows the management system (1) together with the distributed multi-model database architecture (20), represented by only two nodes.
- Figure 5 shows a preferred implementation of the management system (1) and the distributed database architecture (20); the Figure shows the profile microservice (3), the key-value database (4) and part of the middleware (5) hosted on the cloud server (10); the user interface (2) in this example is a web application.
- the database servers (31), of which only one unit is represented in Figure 5 host the user microservices (11), of which only one unit is represented in Figure 5, the same pre-existing database (30) and a part of the intermediate software (5).
- the graph database (12) the data structure is implemented by a graph with a tree-like structure in documents that store references to "parent" nodes in child nodes.
- the "parent reference pattern" stores each tree node in a document; in addition to the tree node, the document stores the identification, or ID, of the node's parent.
- the key challenge in data modeling is balancing application needs, database engine performance characteristics, and data retrieval patterns.
- gratos database collections by default, do not require their documents to have the same schema.
- Documents in a single collection do not need to have the same set of fields, and the data type for a field may differ across documents within a collection.
- To change the structure of documents in a collection such as adding new fields, removing existing fields, or changing field values to a new type, the documents are updated to the new structure.
- the database architecture (20) is not only compatible with medical standards such as DICOM and HL7, the middleware (5) also comprises export interfaces to these formats, so that the database architecture data (20) is fully compatible with the existing hospital system and independent of software service providers.
- the data is encrypted in such a way that the profile microservices (3) always have higher authority to decrypt the data.
- the data location is known through the hierarchy established by the tree, and the cost of going from one node to another to build our necessary data structure at each moment. Therefore, the Dijkstra algorithm is the preferred algorithm to build the data network.
- a minimum path algorithm will be used, that is, an algorithm for determining the shortest path between nodes.
- the management system (1) executes these steps: receive, by a profile microservice (3), a data request from a user interface
- Management system (1) according to any of the preceding clauses, wherein the key-value database (4) is configured as a distributed ledger.
- Management system (1) according to any of the preceding clauses, further comprising a low-availability backup database controlled by middleware (5).
- Management system (1) according to any of the previous clauses, where the intermediate software (5) is partially stored in a server (31) of the pre-existing database (30).
- Management system (1) according to any of the preceding clauses, wherein the middleware (5) is configured to perform asynchronous masterless replication between nodes of the graph databases (12).
- Management system (1) in accordance with any of the previous clauses, where the middleware (5) is configured to perform multicast queries according to a round-robin schedule.
- At least one profile microservice (3) comprises an intermediate database configured to store data from the graph databases (12), data location with hash function of the user microservices (11), and/or decryption keys.
- Computer system comprising a cloud server (10) configured to store and run the management system (1) according to clauses 1-11.
- Distributed multi-model database architecture (20 comprising a plurality of user microservices (11), each connected to a database (30) of a plurality of pre-existing relational databases (30) stored in respective servers (31), where each user microservice (11) is associated with a user, each user microservice (11) is configured to create, store and manage a graph database (12), comprising nodes and edges, with data related to the associated user from the pre-existing database (30) connected to the user microservice (11), each user microservice (11) comprises an encrypted file (13) that can be decrypted by the user microservice (11) and containing instructions to create and store the graph database (12) with data related to the associated user, and each user microservice (11) is stored in the server (31) of the database pr database (30) connected to the user microservice (11), the graph database (12) is configured to be accessed only through the user microservice (11).
- Computer-readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the steps of: receiving, by a profile microservice (3), a request for data from a user interface
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Storage Device Security (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202180079847.1A CN116917881A (zh) | 2020-11-27 | 2021-04-23 | 一种分布式多模型数据库体系结构的管理系统和方法 |
EP21724345.0A EP4254219A1 (en) | 2020-11-27 | 2021-04-23 | Management system and method for a distributed multi-model database architecture |
US18/253,715 US20230418839A1 (en) | 2020-11-27 | 2021-04-23 | Management System And Method For A Distributed Multi-Model Database Architecture |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
ESU202032593 | 2020-11-27 | ||
ES202032593 | 2020-11-27 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2022112624A1 true WO2022112624A1 (es) | 2022-06-02 |
Family
ID=81755361
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/ES2021/070271 WO2022112624A1 (es) | 2020-11-27 | 2021-04-23 | Sistema y método de gestión para una arquitectura de base de datos multimodelo distribuida |
Country Status (4)
Country | Link |
---|---|
US (1) | US20230418839A1 (es) |
EP (1) | EP4254219A1 (es) |
CN (1) | CN116917881A (es) |
WO (1) | WO2022112624A1 (es) |
-
2021
- 2021-04-23 CN CN202180079847.1A patent/CN116917881A/zh active Pending
- 2021-04-23 EP EP21724345.0A patent/EP4254219A1/en active Pending
- 2021-04-23 US US18/253,715 patent/US20230418839A1/en active Pending
- 2021-04-23 WO PCT/ES2021/070271 patent/WO2022112624A1/es active Application Filing
Non-Patent Citations (3)
Title |
---|
CARPENTER JEFFREY: "Data Model Meets World, Part IV: How Many Databases? | Datastax", 25 October 2020 (2020-10-25), pages 1 - 8, XP055831558, Retrieved from the Internet <URL:https://web.archive.org/web/20201025230246/https://www.datastax.com/blog/data-model-meets-world-part-iv-how-many-databases> [retrieved on 20210811] * |
DE SANTIS SANDRO ET AL: "Evolve the Monolith to Microservices with Java and Node", 5 December 2016 (2016-12-05), pages 1 - 132, XP055831625, Retrieved from the Internet <URL:https://www.redbooks.ibm.com/redbooks/pdfs/sg248358.pdf> [retrieved on 20210811] * |
KUMAR ROSHAN: "Selecting the Right Database for Your Microservices - The New Stack", 30 January 2019 (2019-01-30), pages 1 - 19, XP055831512, Retrieved from the Internet <URL:https://web.archive.org/web/20190130224759/https://thenewstack.io/selecting-the-right-database-for-your-microservices/> [retrieved on 20210811] * |
Also Published As
Publication number | Publication date |
---|---|
EP4254219A1 (en) | 2023-10-04 |
US20230418839A1 (en) | 2023-12-28 |
CN116917881A (zh) | 2023-10-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Chen et al. | A Blockchain‐Based Medical Data Sharing Mechanism with Attribute‐Based Access Control and Privacy Protection | |
Alonso et al. | Proposing new blockchain challenges in ehealth | |
US20230009198A1 (en) | Query generation for collaborative datasets | |
AU2017282656B2 (en) | Collaborative dataset consolidation via distributed computer networks | |
EP2241986B1 (en) | Privacy and confidentiality preserving schema mapping repository for mapping reuse | |
US20170041298A1 (en) | System for accessing data | |
Huang et al. | FSSR: Fine-grained EHRs sharing via similarity-based recommendation in cloud-assisted eHealthcare system | |
Kuo et al. | Design and construction of a big data analytics framework for health applications | |
Misbhauddin et al. | MedAccess: a scalable architecture for blockchain-based health record management | |
Chen et al. | Secure search for encrypted personal health records from big data NoSQL databases in cloud | |
Chrimes et al. | Towards a real-time big data analytics platform for health applications | |
Damiani et al. | Metadata management in outsourced encrypted databases | |
Haack et al. | Computing the diameter of the space of maximum parsimony reconciliations in the duplication-transfer-loss model | |
Shin et al. | Secured e-health data retrieval in DaaS and Big Data | |
Hu et al. | A semantic privacy-preserving model for data sharing and integration | |
Agoun et al. | Access control based on entity matching for secure data sharing | |
WO2022112624A1 (es) | Sistema y método de gestión para una arquitectura de base de datos multimodelo distribuida | |
Lebre et al. | Decentralizing the storage of a DICOM compliant PACS | |
Karapiperis et al. | FEMRL: A framework for large-scale privacy-preserving linkage of patients’ electronic health records | |
Kaniovskyi et al. | A semantic cloud infrastructure for data-intensive medical research | |
Sony et al. | An intuitionistic fuzzy-based intelligent system for semantic interoperability and privacy preservation in healthcare systems | |
Sindhu et al. | Handling Complex Heterogeneous Healthcare Big Data | |
Alamri et al. | Secure sharing of health data over cloud | |
Lebre et al. | An Efficient and Reliable Architecture for Distributing Medical Imaging Data | |
Divyashree et al. | A scoping review of data storage and interoperability in blockchain based electronic health record’s (EHR) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 21724345 Country of ref document: EP Kind code of ref document: A1 |
|
DPE1 | Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 18253715 Country of ref document: US |
|
WWE | Wipo information: entry into national phase |
Ref document number: 202180079847.1 Country of ref document: CN |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
ENP | Entry into the national phase |
Ref document number: 2021724345 Country of ref document: EP Effective date: 20230627 |