WO2016064552A1 - Système et procédés améliorés d'échange d'informations d'identités entre des entreprises indépendantes susceptibles de présenter une corrélation par intervention humaine - Google Patents

Système et procédés améliorés d'échange d'informations d'identités entre des entreprises indépendantes susceptibles de présenter une corrélation par intervention humaine Download PDF

Info

Publication number
WO2016064552A1
WO2016064552A1 PCT/US2015/053511 US2015053511W WO2016064552A1 WO 2016064552 A1 WO2016064552 A1 WO 2016064552A1 US 2015053511 W US2015053511 W US 2015053511W WO 2016064552 A1 WO2016064552 A1 WO 2016064552A1
Authority
WO
WIPO (PCT)
Prior art keywords
enterprise
data
server
correlation
login credential
Prior art date
Application number
PCT/US2015/053511
Other languages
English (en)
Inventor
J. Brent WILLIAMS
Dennis Tackett
Dennis RIZZI
Original Assignee
Verato, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/522,670 external-priority patent/US9705870B2/en
Priority claimed from US14/594,068 external-priority patent/US9699160B2/en
Application filed by Verato, Inc. filed Critical Verato, Inc.
Publication of WO2016064552A1 publication Critical patent/WO2016064552A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6245—Protecting personal data, e.g. for financial or medical purposes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
    • H04L63/102—Entity profiles
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/76—Proxy, i.e. using intermediary entity to perform cryptographic operations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
    • H04L2209/88—Medical equipments

Definitions

  • the inventions disclosed herein relate to the field of information sharing among computer systems, specifically web services interactions that are conducted between two or more heterogeneous enterprises for the sharing of sensitive information.
  • the inventions disclosed herein relate to, by way of example only, an implementation for the Nationalwide Health Information Exchange (NwHIN) or any other information sharing network.
  • the NwHIN is a 'network of networks' for exchanging health data.
  • the fabric of the NwHIN is based on web services that provide the framework among NwHIN participants to locate and exchange health information. Examples of NwHIN participants currently include: state level exchanges, IDNs, federal entities, public health entities, and geographically-based health information organizations.
  • HIO Health Information Organization
  • NwHIN Validation which includes conformance and compliance testing.
  • Organization A may keep records by Social Security Number (SSN), while Organization B might keep them by some internally generated patient ID.
  • SSN Social Security Number
  • Organization B might keep them by some internally generated patient ID.
  • a system and method for correlating protected data across, for example, independent data systems connected through a network includes, for example, generating, by a first connector module in communication with a first data system, a first permanent token which identifies a subject of a first set of protected data stored in said first data system that is to be correlated with a second set of protected data stored in a second data system.
  • the first and second data systems may be independently operated.
  • the first connector module generates, for example, a first temporary token which identifies a transaction in which the first protected data is to be correlated and which is stored in a data file that is exchanged with said second system over said network.
  • An edge data store in an edge server stores the first temporary token.
  • the edge server propagates the first temporary token and the first permanent token to a root server.
  • the first connector module receives an indication from said first data system that said first set of protected data and said second set of protected data may be correlated, wherein said indication includes a second temporary token.
  • the edge server stores a first correlation data set received from the root server that includes said first permanent identifier and a second permanent identifier generated by the second data system and is associated with the second temporary token.
  • the first correlation data set is stored in the edge data store.
  • FIG. 1 is a system diagram showing an embodiment of an data exchange system.
  • FIG. 2 is a block diagram showing an embodiment of an identity exchange service (IXS) using identity exchange protocol (IXP).
  • IXS identity exchange service
  • IXP identity exchange protocol
  • FIG. 3 is a message flow diagram illustrating a method of using IXS.
  • FIG. 4 is a message flow diagram illustrating a method of using IXS.
  • FIG. 5 is a message flow diagram illustrating a method of using IXP within the IXS system.
  • FIG. 6 is a system diagram showing an embodiment of person enabled correlation.
  • FIG. 7 is a message flow diagram illustrating a method of using person enabled correlation.
  • Embodiments of the present invention are not limited to the particular methodology, uses, and applications described herein, as these may vary. It is also to be understood that the terminology used herein is used for the purpose of describing particular embodiments only, and is not intended to limit the scope of all embodiments of the present invention. It must be noted that as used herein and in the appended claims, the singular forms "a,” “an,” and “the” include the plural reference unless the context clearly dictates otherwise. Thus, for example, a reference to “an element” is a reference to one or more elements, and includes equivalents thereof known to those skilled in the art.
  • a reference to “a step” or “a means” is a reference to one or more steps or means and may include sub-steps or subservient means. All conjunctions used are to be understood in the most inclusive sense possible. Thus, the word “or” should be understood as having the definition of a logical “or” rather than that of a logical “exclusive or” unless the context clearly necessitates otherwise. Structures described herein are to be understood also to refer to functional equivalents of such structures. Language that may be construed to express approximation should be so understood unless the context clearly dictates otherwise.
  • share means provide access for retreiving, downloading, viewing, editing, transferring, or otherwise utilizing or visualizing data in a computer system.
  • To share a data record, or protected data in the data record means to provide such access as described above to another entity.
  • token means any alphanumerical value that can be used to identify a particular transaction and/or entity. Tokens may be randomly generated, sequential, or arbitrary as long as they are sufficiently unique to identify a particular transaction within a particular length of time. Tokens may be permenant or temporary. Permenant tokens are tokens which may be stored indefinitely and may identify a transaction, organization, individual, group, or any other appropriate entity. Temporary tokens may be stored for a defined length of time and may identify a transaction, organization, individual, group, or any other appropriate entity.
  • identity exchange protocol means a protocol that facilitates sharing of identities between enterprises when there is a desire to remove the need to share protected local identity information across the network, and there is a need to provide security and privacy of the linkages between identities.
  • identity exchange service means, for example, the service instantiation, comprised of servers, network, connectors, etc., of the protocol referred to as IXP.
  • IXP connector means, for example, a Web-Services accessible interface between the enterprise and the IXS. It provides the security of the enterprise ID, while also allowing direct connectivity to the IXS platform.
  • IXP connectors may have subcomponents.
  • an IXP connector may include an enterprise connector, which may be communicatively connected to or otherwise networked with the enterprise data system directly and may reside within the enterprise firewall.
  • an IXP connector may include an exchange service connector which may reside outside the enterprise firewall (e.g., in a DMZ) communicatively connected to or otherwise networked with the IXS platform.
  • IXP edge server means, for example, a server deployed with the segment of the IXP protocol that retrieves IXP calls from the attached connectors and forwards them to the Root for redistribution, synchronization, and security verification.
  • Edge servers may hold the latest version of the correlations provisioned by the root servers.
  • Edge servers may also provide a disaster recovery capability in the connectivity to the IXS wherein numerous IXP connections may be deployed to have failover to several IXP edge servers.
  • Edge servers may maintain the security and integrity of the link between the IXP connector (in the enterprise) and the root servers.
  • Edge servers are, for example, intended to be in close geographic proximity to the IXP connectors to facilitate rapid response and load balancing for requests, but may be located anywhere in a network topology.
  • root servers, edge servers and IXP connectors may be deployed within an organization and without a connection to the Internet or other public network.
  • IXP root server(s) means, for example, the core to the security of the IXS. It may maintain a list of all allowed connectors and the enterprises to which they may be attached. Root servers are, for example, responsible for verifying the security and integrity of the request and pushing updates to the edge servers to facilitate synchronization. Root servers can, for example, provide a disaster recovery capability in the connectivity to the IXS wherein numerous IXP edge servers may be deployed to have failover across all IXP root servers. Root servers are or may be continuously replicated.
  • App means, for example, a software application used by an enterprise to access its data system and perform tasks such as, for example, using an enterprise web, software, or other services framework.
  • enterprise service bus means, for example, any software or hardware component of the enterprise web, software, or other services framework used for designing and implementing communication between mutually interacting software applications in a service-oriented system.
  • an ESB may control communications and interactions between the various components of the data exchange system.
  • Data repository CDR and/or Data A, B
  • CDR and/or Data A, B may be any data system or repository which houses enterprise specific data.
  • the patient discovery service interface specification may provide patient arbitration capabilities between organizations to support querying for documents across different organizations, for example Enterprise A and Enterprise B.
  • this specification may use, for example, the cross community patient discovery (XCPD). This defines the role of XCPD Initiating Gateway and XCPD Responding Gateway, i.e. gateways 112 and 144.
  • John Doe on Enterprise A does not equal John Doe on Enterprise B wherein Enterprise A and Enterprise B may both be health information organizations (HIO).
  • HIO health information organizations
  • the Patient Discovery Service may dictate how an HIO may locate and identify patient information that resides on another HIO on the Nationalwide Health Information Exchange (NwHIN), over a public network, such as public network 120.
  • the initiating HIO can enter the demographic data and local identifiers that can be shared about a patient.
  • the responding HIO matches the demographics and identifiers. If a single match is found that is considered highly reliable, it is returned to the initiator, along with its demographic details and identifiers. If no match is found the responder sends an empty response to the initiator, indicating that this patient is not known at this HIO.
  • Patient Discovery can be designed, for example, to avoid all false positives.
  • the Query for Document Service may allow an initiating HIO to request a list of documents about a patient available in the responding HIO. It is dependent on Patient Discovery to provide the patient identifier of the correct patient in the responding HIO. The query permits additional parameters like start/end date and document type to customize which documents are returned.
  • This interface does not specify whether access consent directives should, preferrably be enforced during a document query or during document retrieval.
  • HIOs can store clinical data in whatever format or repository they choose, provided the HIO can respond to queries as described in this interface.
  • One expected use is that these documents transmitted on the NwHIN may be formatted as XML data following the HL7 clinical document architecture (CDA) standard.
  • the retrieve documents service may allow an initiating HIO to request a specific document, by using a unique document identifier. This may be the third step in retrieving data from another HIO, subject discovery and query for documents may be pre-conditions for retrieving documents to be executed.
  • HIOs may generate documents "on demand” by aggregating data from multiple sources. They can ensure that the generated document remains available and unaltered after a document has been retrieved once. As noted in the query for documents section, HIOs can store data internally in the format/repository of choice, as long as they transmit the data in XML/CDA format.
  • the version of the document presented for the request may be also stored and may be retrieved by a document identifier at a later date. As such, the requesting HIO can request the archive data again if required.
  • IXP identity exchange protocol
  • IXS identity exchange service
  • Other system applications include law enforcement, intelligence, legal work, banking, commercial collaborations, and/or any application that requires secure identity exchange, and/or secure exchange of information contained in a given record, and/or secure exchange of information loosely maintained by an enterprise or independent data system.
  • a system may be designed such that a IXP Connector within the enterprise may be connected to an IXS system and can be reached by a wide variety of enterprise applications. There are a wide variety of potential sources within the healthcare enterprise that could interface to the IXP connector.
  • the source of the calls to and from IXS may originate at the ultimate connector to the primary sharing network.
  • IXS may be better able to meet the objectives. It may be able to prevent the need for distribution of personally identifiable information (PII) if the correlation of the individual's identity associated with their records has already occurred.
  • PII personally identifiable information
  • Enterprise A With regard to FIG. 1, two organizations are shown (Enterprise A and Enterprise B) that wish to determine if they both have medical records for a particular individual.
  • Enterprise A and B have declared to IXP that they trust each other, so they can ask each other for records.
  • Enterprise A utilizes a public network 120 to send requests to Enterprise B.
  • Enterprise A may request information related to Alen J. Smith, who is assigned patient ID: 12345.
  • Enterprise A asks the question across the public network, it sends along Alen J. Smith's patient id as it exists in the enterprise database of Enterprise A.
  • Enterprise A may therefore leverage IXP to shield this sensitive data by the following means.
  • An IXP connector 151, 153 may be installed for each organization.
  • the organizations may set up the connector using import files with each organization's patient IDs.
  • Each patient ID imported results in the creation of a new IXP identity or XID, a unique identifier which identifies each individual patient in the organization.
  • the XID may be numerical, alphabetical, a glyph, or any combination, including hexadecimal.
  • a row may be written to the local data store that pairs an XID to a particular patient ID within the organization. To avoid using the potentially sensitive patient ID, IXP may use this XID to refer to an individual.
  • the XID may have meaning only within the IXS system and only for the organization for which it was created and can never be used to look up information about a patient.
  • the only information paired to the XID may be the organization's local patient ID, and that pairing lives only within the organization's firewall on the IXP Connector.
  • the IXP connector may be installed in a number of configurations depending on the needs of the organization.
  • Enterprise A in FIG. 1 has IXP connector 151 connected directly to enterprise service bus (ESB) 114.
  • ESB 114 controls access between Data App A 106 and gateway 112 and ⁇ connector 151.
  • IXP connector 153 is implemented as part of gateway 144.
  • ESB 146 similar to ESB 114 controls access between Data App Bl 136/Data App B2 138 and gateway 144 and IXP connector 153.
  • ESB 146 is connected to IXP connector 153 through a connection to gateway 144.
  • IXP connectors may be software running on the same computer server as gateway 144 or may be a co-located device connected through a wired or wireless data connection to gateway 144.
  • IXP For IXP to resolve identities, it can, for example, have correlation information input into the root servers 156 and edge servers 152, 154. As shown in FIG. 1, a number of physical implementations are available depending on enterprise needs and capability. For example, Enterprise A has implemented IXP edge server 152 as an onsite server. This and similar implementations may provide fast edge server access to the Enterprise A data network. Although IXP edge server 152 is logically outside of the Enterprise A firewall, it is physically co-located with and directly addressable by the IXP connector 151 without the need to communicate over the wider IXS network 150. Alternatively, Enterprise B has implemented IXP edge server 154 in a cloud implementation.
  • IXP connectors 151, 153 and the IXP edge servers 152, 154 logically remain part of the IXS system and are not part of the enterprise data systems.
  • the logical configuration of the IXS system is described in greater detail in reference to FIG. 2.
  • a correlation creates a pairing between two XIDs and assigns a floating point value to the pairing.
  • the floating point value may be a correlation value (or certainty) that the two patients are the same individual.
  • a correlation value of 1.0 means that the two XIDs have been absolutely determined to represent the same individual.
  • a correlation of 0.0 means there may be a zero percent certainty that the two individuals are the same. Anything between indicates a degree of certainty that may not be absolute.
  • IXP provides its the best available information on the degree to which the individuals are correlated. In implementations, correlations can be added to IXP by import or through an IXP management console.
  • a file may be dropped into an import directory of the root IXP server 156.
  • the file contains an entry for each correlation to be added.
  • the correlation record may contain the Organization ID for Enterprise A and the Organization ID for Enterprise B and the correlation value.
  • An optional value of the correlation can be set to 1.0 or 0.0 to define the accuracy of the correlation since there may not be any conditional logic for intermediate values.
  • the next step may be to integrate IXP with the patient discovery profiles.
  • organizations have gateways 112, 144 installed which connect them to the NwHIN network.
  • the organizations pass requests seeking patient information into the NwHIN gateways, those requests are described herein in exemplary fashion as "documents," and receive back documents containing the results of their requests.
  • Enterprise A submits a request across the NwHIN for Enterprise B's records on Alen Smith.
  • Enterprise A will pass Alen Smith's SSN as patient ID but Enterprise B has no records for that ID.
  • IXP is used to assist in the information recovery.
  • An IXP connector can be used to secure the ID that correlates to the patient being inquired about during the exchange between Enterprise A and Enterprise B, as shown in FIG. 1.
  • Enterprise A initiates a request across the public network 120 to Enterprise B with demographic information that identifies the patient 104.
  • a doctor 102 may utilize data app 106 to input or search for records belonging to patient 104.
  • the search may be processed through the master patient index (MPI) 110 and data repository 108.
  • patient 104 may identified by demographic information, such as SSN.
  • the patient 104 may be identified by an identifier created by Enterprise A. In either case, the identifier may contain or may be considered sensitive information and thus as little information pertaining to that identifier should be transferred over a public network more than necessary.
  • Records may also exist in one or more data systems within the control of Enterprise B.
  • a technician 132 may work in a medical laboratory which has performed blood work for patient 134 being treated at a hospital. Both the laboratory and the hospital may or may not be within Enterprise B.
  • data app 136 in communication with data repository 140, may be operated by the medical laboratory and data app 138, in communication with data repository 142, may be operated by the hospital.
  • Each data app 136, 138 may identify patient 134 in data repositories 140, 142 using different identifiers, as shown in FIG. 1.
  • Either patient 104 or doctor 102 may know or believe that records belonging to patient 104 exist in other enterprises.
  • patient 104 and patient 134 may be the same person.
  • the data app utilizes ESB 114 to call IXP connector 151 with the identifier used by Enterprise A (i.e., 12345).
  • an adapter may be implemented within ESB 114 or otherwise in communication with ESB 114 which is capable of intercepting the message sent by data app 106. Upon intercepting the message, the adapter is configured to call IXP connector 151.
  • the adapter may be implemented in software, hardware, or any combination thereof.
  • the adapter may be between data app 106 and gateway 112.
  • the adapter may be implemented as part of ESB 114.
  • the precise location and implementation of the adapter is a design choice dependent on the implementation of the enterprise data system.
  • IXP connector 151 returns a temporary string token A that will replace the identifier in the request that will be sent to Enterprise B.
  • the request contains demographic information that can be used by Enterprise B to identify the patient, but does not include the identifier used in Enterprise A.
  • Enterprise A passes the request through gateway 112 and public network 120 to Enterprise B.
  • a document may include any attributes which can be used to match a file across organizations, and in fact the document can be replaced by an electronic string of data.
  • gateway 144 receives the request and sends it to ESB 146.
  • ESB 146 then examines the demographic information included in the request to determine if there is a patient match in either or both of data repositories 140, 142.
  • the demographic data for patient 104 is matched with data in the data repositories 140, 142 for patient 134 and a correlation score is assigned to the match, as described above. If the correlation score is above a threshold, the match between is deemed to be confirmed and a response is sent over public network 120 to gateway 112 stating that a match has been confirmed.
  • IXP connectors 151, 153 and IXP edge servers 152, 154 are part of IXS system 150, along with IXP root server 156.
  • IXP root server 156 Although shown in FIG. 1 as including one root server, an IXS system may have any number of IXP root servers.
  • the components of IXS system 150 may communicate with each other through a network. Any networking technology may be used.
  • Each enterprise may have access to a dedicated IXP edge server which includes a data store of the correlations between the data of that enterprise and that of, for example, all other enterprises.
  • the IXP root server(s) include a data store of, for example, all correlations between any two enterprises connected to the IXS system 150.
  • the data stored on the edge servers is a subset of the data stored on the root servers.
  • the root servers store the aggregation of, for example, all the data stored in all the edge servers connected to the IXS system 150.
  • IXP connector 151 retrieves a permanent token identifier which identifies patient 104 and an organization identifier which identifies Enterprise A. These two identifiers can, for example, be coupled with the temporary token A and sent from IXP connector 151 to IXP edge server 152. The correlation is propagated to IXP root server 156.
  • IXP connecter 153 retrieves the permanent token for patient 134 and the organization identifier for Enterprise B and correlates them with temporary token A. This correlation is then sent to IXP edge server 154 and is propagated to IXP root server 156.
  • IXP root server 156 the identifiers for patient 104 at Enterprise A are correlated with the identifiers for patient 134 at Enterprise B forming a permanent correlation. This permanent correlation is stored in the IXP root server 156 and in IXP edge servers 152, 154 since the correlation involves both Enterprise A and Enterprise B.
  • Connectors 210, 212 may be secure units.
  • the connectors 210, 212 have an exposed Web services API within the enterprise. There are, for example, two sides of the connector.
  • enterprise connector 214, 216 that is exposed to the Web services API within the enterprise. It is called “enterprise connector” because it stores the enterprise identities of the individuals from inside the enterprise. It is assumed, therefore, that all of the activities within the enterprise connector may be running inside of a secure container. Enterprise connectors are sometimes referred to as "red" connectors.
  • the enterprise connector 214, 216 is connected to an exchange service connector 218, 220 through an encrypted exchange that allows the linkage between a subject's identity on one side and an anonymous linkage on the other. It is called “exchange service connector” because it interacts solely with the IXS system and does not contain any enterprise specific information.
  • the exchange service connector 218, 220 is a similar secure container. Exchange service connectors are sometimes referred to as "black" connectors.
  • the secure container on the exchange service connector 218, 220 may, for example, only communicate through two ports. One port communicates to the enterprise connector 214, 216, while the other communicates to the other components of IXS system 202.
  • the connection between the exchange service connector 218, 220 and the other components of IXS system 202 may be a secure VPN between the connector and an IXS edge server 204, 206.
  • each enterprise will have load-balanced and redundant connectors 210, 212 that may be connected to multiple redundant and load- balanced IXS edge server 204, 206.
  • the IXS edge server 204, 206 will resolve the correlation between the two enterprises using data present at the IXS edge server 204, 206 that is processing the transaction and will route it to the proper enterprise to fulfill the transaction.
  • the IXS edge server 204, 206 may be deployed to the edge of the IXS system 202 or behind the enterprise's firewall to minimize the round-trip time for the enterprises conducting the transaction. In these implementations, the IXS edge server 204, 206 is co- located with the enterprise data system 222, 224.
  • the IXS edge servers 204, 206 have similar redundant and load-balanced connections to IXS root server(s) 208.
  • the IXS root server(s) 208 control the distribution of correlation pairs to the IXS edge servers 204, 206 and validate the security of the IXS edge servers 204, 206 as well as the connectors 210, 212.
  • the IXS root server(s) 208 reside at the core of the IXS secure, cloud-based system 202. There may be multiple root servers 208 to provide backup and redundancy across the IXS system 202.
  • the edge deployed IXS edge servers 204, 206 may be within the IXS secure cloud-based system 202 or behind the users firewall stabled through a secure VPN, co-located with enterprise data systems 222, 224.
  • connectors 210, 212 may be deployed include the following.
  • the first example is as an enterprise hardware appliance.
  • One or more physical appliances may be deployed inside the enterprise's datacenter with a secure VPN controlled by the IXS system 202 and connecting the exchange service connector 218, 220 to the appropriate IXS edge servers 204, 206.
  • the IXS service provider may control and manage the physical appliance independent from the Enterprise.
  • IXP enterprise connector 214, 216 exposes Web services directly inside the enterprise that facilitate ready and secure access to the protocol.
  • the second example of a deployment of a connector 210, 212 is an enterprise virtual appliance.
  • One or more virtual appliances may be deployed on a virtual machine inside the enterprise's data center and there is a secure VPN controlled by the IXS service provider connecting the IXS exchange service connector 218, 220 to the appropriate IXS edge servers 204, 206.
  • the IXS service provider controls and manages the virtual appliance, and the local enterprise controls the local machine and the virtual container in which the virtual appliance is operating.
  • Enterprise connector 214, 216 exposes Web services directly inside the enterprise that facilitate ready and secure access to the protocol.
  • a third example of a deployment of a connector 210, 212 is a cloud-based virtual appliance.
  • One or more virtual appliances may be deployed on a virtual machine inside the IXS system 202.
  • the IXS service provider controls and manages the entire environment with the exception of a secure VPN between the enterprise and the IXS system 202.
  • the Web services API for the IXP enterprise connector 214, 216 will be within the local infrastructure extended by a VPN.
  • IXP enterprise connector 214, 216 exposes Web services directly inside the enterprise that facilitate ready and secure access to the protocol.
  • the IXP API may be based on messages that get routed, authenticated, encrypted and replied to by the IXS system 202.
  • IXP may be viewed as a messaging backbone that has service nodes which will respond to service requests.
  • a service request may be made by creating a Message document with content (typically a 'Model' may be a bundle of attributes that can be mapped into a useable form for IXP).
  • the API requires specification of the service name and service action and sending a model with the needed data.
  • Internal IXP logic may build a message, attach the model and translate the service name and action to a service endpoint on the IXS system 202. The message may be sent, and if it requires a response, another message may for example be returned containing a model.
  • the following section will show an example of how these APIs may be used.
  • IXP Services may use a backing NoSQL data store to keep facilitating our expected scaling requirements.
  • the IXS system does not store any sensitive customer data on our network except for the data stored on the IXP enterprise connector 214, 216.
  • the IXP enterprise connector 214, 216 may be in a secured VM behind a customer firewall and/or behind an additional DMZ server (e.g., IXS exchange service connector 218, 220).
  • the IXP enterprise connector 214, 216 may map the clients secured data (for example SSN) to tokens that can be used on the public network 226 in place of the actual data.
  • the client data system 222, 224 will periodically update this data as new subjects (customers, patients, etc.) may be added at the Enterprise database.
  • clients may be expected only to provide minimal data at the IXP enterprise connector 214, 216 to assist IXP in securing client information for transport on the public network 226.
  • Input files may contain information about subjects.
  • a subject may be a user, patient, customer, and the like that has an identity in the enterprise database.
  • a naming convention for input files may be used.
  • an input file containing subject data for example, it may be named ' 'subj ect-records .xml . ' '
  • IXS root server(s) 208 There are, for example, two types of data that may be imported.
  • First is data that is stored on the IXS root server(s) 208 and IXS edge servers 204, 206.
  • the data in the IXS root server(s) 208 may be produced by interactions with other modules that manage identity resolution and consent.
  • importers can be provided so that bulk updates may be performed in cases where data files have been vetted from IXP clients. This import facility will be used to get the testing data into the IXS root server(s) 208.
  • the second type of data that may be imported is data that is stored inside the customer fire wall (i.e., IXP enterprise connector 214, 216).
  • IXP enterprise connector 214, 216 or IXS root server(s) 208 are started, a process may check whether an import input directory includes import files that need to be processed. If files are available, they may be processed immediately when the node starts up. Thereafter, the node may check every 15 minutes for any additional input files that may need to be processed.
  • This scheduling scheme may be provided only as a convenience for test teams. In a live environment, there may be a separate import process running in its own VM. This process may have a scheduling facility that allows fine grained control of when and how the batch imports occur.
  • the importers may be built into the deployed VMS.
  • the importers that run in the IXS root server(s) 208 and IXP enterprise connector 214, 216 may share behavior but may operate on different data.
  • the data When a file is processed, the data may be imported into the data store in either the IXS root server(s) 208 or IXP enterprise connector 214, 216 and the file may be moved to the processed directory.
  • a results file may be produced.
  • the results file may contain a copy of the actual data that was written to the data store, or an error if the data could not be imported. This file may serve as a snapshot of the output data that was produced and persisted from the input files.
  • Correlation of records may be independent of IXP, but may feed IXP with the data required to perform its function. Correlation, once established, may be pushed to IXP via a provisioning interface.
  • IXP IXP
  • bulk correlation may be performed when two or more enterprises agree to share patient data and seek correlation. Enterprises may send entire patient repositories (just identifying information in headers, not medical data) to be corrected and matched. A correlation tool may seek the best matches from the data set and provisions in ⁇ . Once bulk processing is complete, both enterprises transition to continuous correlation and monitoring (see below).
  • a second type of correlation is pair correlation.
  • an enterprise may already have a correlation between its records that was provided by another organization.
  • the enterprise may seek confirmation of the pairing or correction of any ambiguity in pairing.
  • a correlation tool seeks best matches from set and provisions in IXP. Once paring correlation is complete, both enterprises may transition to continuous correlation and monitoring as further described herein.
  • a third type of correlation is continuous correlation and monitoring. All new identity records created in an enterprise may be correlated with partner organization identity records to determine if it is an existing pairing. Current pairings may be reviewed continuously for errors in process and data attributes that need correction, a process that may use feedback from patients as well as practitioners. For example, a pairing may, in fact, be incorrect. If this is determined through the continuous correlation and monitoring process, the pairing may be deleted permanently. Additional data may also be stored to indicate that that pairing should preferably not be made again in the future. This process updates records in IXP continuously. There may be no need for enterprises to repair correlations and update identity pairings manually.
  • FIG. 3 an example process 300 for exchanging identity information using an implementation of an IXP/IXS system.
  • correlated data for both Enterprise A and Enterprise B is preloaded into root/edge servers.
  • FIGs. 3, 4, and 5 illustrates the exchange of healthcare patient records
  • Some applications may require fewer, additional, or different data messages than those illustrated here.
  • the particular format of the messages and the data they contain are design elements within the ordinary skill in the art.
  • the embodiments disclosed in this document are not limited in this regard. As used in reference to FIGs.
  • a "gateway” means, by way of example only, any hardware or software component that provides access to a public network, such as a wireless or wired local area network, wide area network, telecommunications network, and/or the Internet.
  • IXP means, for example, the IXS system accessible through an IXP connector as described above in reference to FIGs. 1 and 2.
  • a "public network” is any network which is not part of the IXS system.
  • the exemplary process 300 begins when an operator of App A requests patient information or data, such as documents, via patient request 302.
  • the patient document request 302 is sent to Gateway A.
  • Gateway A requests demographic information from enterprise service bus (ESB) A by sending patient identifier cross referencing (PIX)/patient demographics query (PDQ) request 304.
  • ESB A forwards and/or sends PIX/PDQ request 306 to data repository (i.e., Data) A which returns Patient ID A in PIX PDQ response 308.
  • ESB A takes Patient ID A and requests from IXP A, via token request message 310, Token A which represents Patient ID A in IXS.
  • This message cascades from ESB B to Gateway B (response 330), Connect B to Connect A (response 332), Connect A to ESB A (response 334) and ESB A to Data A (response 336). Data A then sends response 338 back to ESB A.
  • an example process 400 for exchanging identity information using an implementation of an IXP/IXS system is correlated in real time and on a continuous basis.
  • Process 400 begins in a similar way to the process 300 in FIG. 3.
  • An operator at App A requests patient documents via patient document query 402 to Gateway A.
  • Gateway A then sends a PIX/PDQ request 404 to ESB A which then sends PIX/PDQ request 406 to Data A.
  • Data A sends PIX/PDQ response 408 to ESB A which includes Patient ID A.
  • ESB A sends token request 410 to ⁇ A which responds with token response 412 which includes Token A.
  • ESB A sends PIX/PDQ response 414 including Token A back to Gateway A.
  • Gateway B sends XCPD response 428, including Token A and Demographics B back to Gateway A where it cascades down to ESB A (response 430) and to Data A (response 432).
  • Data A compares Demographics B to the record corresponding to Demographics A and confirms the match made by Data B.
  • a confirm match message 434 is sent back to ESB A which sends correlation request 436 to IXP A to correlate Token A and Patient ID A.
  • ESB A sends a document request 438, including Token A to Gateway A which sends XCA request 440 including Token A to Gateway B.
  • Gateway B sends document request 442, including Token A to ESB B.
  • ESB B sends correlate token request 444 to IXP B which returns correlate token response 446, including Patient ID B.
  • ESB B then sends document request 448 to Data B using Patient ID B.
  • Data B returns with XCA response 450 which cascades down from ESB B to Gateway B (response 452) and to Gateway A (response 454).
  • Gateway A then sends document response 456 to ESB A which sends document response 458 to Data A.
  • Data A sends retrieve documents message 460 back to ESB A.
  • ESB A then sends document request 478 to Data A requesting documents for Patient ID-A.
  • Data A then sends XCA response 480, with the requested documents, back to ESB A.
  • the XCA response cascades down from ESB A to Gateway A (response 482), Gateway A to Gateway B (response 484), Gateway B to ESB B (response 486), and ESB B to Data B (response 488).
  • FIG. 5 an example process 500 for enabling the secure transfer of information utilizing the IXS system is shown.
  • Enterprise refers to an enterprise, corporation, group, individual, or any other entity which owns, operates, and/or maintains an enterprise data system, such as, for example, that described above in reference to FIG. 2.
  • XS Connector refers to an exchange service connector similar to that described in reference to FIG. 2.
  • Other components shown in FIG. 5 are also similarly defined herein.
  • IXP Edge servers may store correlations between the XIDs assigned to patients in one enterprise (e.g. Enterprise A), and XIDs assigned to patients in other enterprises (e.g. Enterprise B). If such a correlation is present in IXP Edge A, IXP Edge A sends correlation response message 508, informing that a correlation exists, to XS Connector A. If no correlation is present in IXP Edge A, IXP Edge A may send optional message 507A to determine if a correlation exists in IXP Root. As described herein, IXP Root servers store all correlations between the XIDs of any two enterprises which utilize the IXS system and have established correlations.
  • IXP Root sends correlation response message 507B informing IXP Edge A whether a correlation exists in ⁇ Root. If there is no correlation in IXP Root, IXP Edge A sends correlation response message, informing that no correlation exists, 508 to XS Connector A. If a correlation does exist in IXP Root, the correlation is propagated to IXP Edge A via correlation response message 507A and ⁇ Edge A informs XS Connector A of the correlation via correlation response message 508. XS Connector A sends correlation response 510 to Enterprise Connector A informing of the result of the correlation look up.
  • Enterprise Connector A responds to the request token message 502 of Enterprise A with a token response message 512, including Token A, which is used in the processes described herein in reference to FIGs. 3 and 4.
  • Enterprise Connector A also sends Token A, through the IXS system, to Enterprise Connector B (i.e. through XS Connector A, IXP Edge A, IXP Root, IXP Edge B, and XS Connector B) via message 514.
  • a correlation in the IXS system may not be made permanent until the enterprise which initially requested the correlation confirms the match between its records and the records of the other enterprise.
  • Enterprise A confirms the record match performed by Enterprise B via messages 432 and 434.
  • Message 436 is shown as establishing the correlation between Token A and Patient ID A.
  • the confirm match message 524 is received from Enterprise A by Enterprise Connector A.
  • Enterprise Connector A then sends a message 526 to XS Connector A.
  • XS Connector A following look up of the XID associated with Patient ID A, sends confirm match message 528, including the XID/Org ID A and Token A, to IXP Root to set up the permanent correlation between Enterprise A and Enterprise B.
  • IXP Root uses token A to establish the correlation between XID A/Org ID A and XID B/Org ID B and sends a confirm message 530 to propagate the correlation to IXP Edge A. IXP Root also propagates the established correlation to IXP Edge B via message 532.
  • the enterprise data systems may, for example, include an interface for person enabled correlation ("PEC").
  • PEC is a special form of matching implemented to augment records that should, for example, preferably be matched, yet remain somewhat more difficult to match or may be nearly unmatchable via an automatic solution.
  • PEC leverages the accuracy of person provided credentials, such as a username and password, to match the records of an individual that should, for example, preferably be matched across two different organizations when the individual is able to login to each of the organizations at for example roughly or generally the same time (e.g. within the same session). For example, an individual may login to a first site operated by a first enterprise. This may normally give them access to their records at the first enterprise.
  • the health information held by the two distinct enterprises may be linked to the same individual across both different organizations. In other words, the records between the two enterprises are matched.
  • PEC may be, for example, executed through the implementation of the security assertion markup language (SAML), OpenID, Kerberos, or any other identity assertion technology or standard known to one of ordinary skill in the art.
  • SAML security assertion markup language
  • OpenID OpenID
  • Kerberos any other identity assertion technology or standard known to one of ordinary skill in the art.
  • FIG. 6 an example implementation 600 of PEC is shown.
  • a person (for example a patient) 601 using terminal 602 may login to the first site displayed on the terminal 602 and operated by a first enterprise 604 (arrow A).
  • Enterprise 604 may include an identity and access management (ID AM) system 606 which authenticates the person's credentials to a website 612, hosted on web server (arrow B).
  • ID AM identity and access management
  • the technique for authentication is that specified by the operator to get access to their enterprise data about that person.
  • the ID AM system 606 includes a directory table 608 and data store 610.
  • a person 601 While logged on to website 612, a person 601 may be presented an option to correlate records between the first enterprise 604 and a second enterprise 624. If the person 601 elects to, for example, correlate the records between these enterprises, an identity assertion message may be sent from the first enterprise ID AM system 606 to the PEC server 616. The election to correlate records with the second enterprise opens another site 614 such that it is either directly or indirectly associated with the transactional session from the first site. Either the first enterprise 604 or the second enterprise 624 may also put a time requirement on the time period between the login to site 612 and the election by the person 601 to correlate between the enterprise.
  • this new site may communicate with IDAM 626 and allows person 601 to enter login credentials for the second enterprise 624 via website 612 hosted by the first enterprise 604 (arrows C & D). Alternate embodiments allow a person 601 who has not yet created an identity representation in the second enterprise to prove their identity and receive or create login credentials for the new site if they do not already exist. It is important to note that the first IDAM 606 may be physically the same as the second IDAM 626, but it may be configured logically to operate such that the first IDAM 606 and the second IDAM 626 have different authentication requirements for the person 601.
  • IDAM 606 may send a SAML or alternate identity assertion to a first enterprise PEC server 616 (e.g., the enterprise connector) (arrow E).
  • the SAML assertion includes the person's 601 unique identifier assigned by the first enterprise 604 and a unique enterprise identifier of the first enterprise 604.
  • the identity assertion contain some other identifier (or identifiers) that is separately correlated to the unique identifier of the person 601 within enterprise 604.
  • the person 601 may login to the second site operated by second enterprise 624 via site 614, which is similarly capable of sending an identity assertion (for example, SAML) to the second enterprise PEC server 618 (e.g., second enterprise connector) within the second enterprise 624 with a unique identifier assigned by the second enterprise 624 and a unique enterprise identifier of the second enterprise 624. (arrow F).
  • the PEC server 616 and the PEC server 618 may be physically separate or combined into a single physical server. When combined into a single physical PEC server, the first enterprise 604 and the second enterprise 624 is logically unique.
  • the PEC server may be used to provision an identity match between two enterprises in the IXS system or alternate identity correlation system.
  • the IXS system 620 correlate identities across different enterprises (or systems) without the need for the enterprises to maintain the correlations.
  • the IXS system may, for example, obfuscate the enterprise unique identifiers for individuals where the correlation occurs in data store 622.
  • IXS 620 may, for example, operate within a secure network 621 and messages may be transmitted between IXP connectors 617 and 619 through that secure network (arrows G).
  • IXS system or "IXS" include Exchange Service (“XS") connectors, IXS edge servers, and IXS root servers as illustrated and described in FIG. 2 and associated description above.
  • an example signaling diagram shows one implementation of PEC.
  • a person may login to Enterprise A.
  • the person may, for example, be offered the opportunity to manually correlate the records between Enterprise A and any partner with which Enterprise A has the ability to perform PEC.
  • a list of enterprises may be presented to the person containing enterprises with which Enterprise A conducts PEC is present on the PEC server.
  • the person may select Enterprise B from a list of enterprises presented to them and requests that records from Enterprise A and B be correlated with each other 702.
  • the act of selecting Enterprise B from the list of enterprises may send an identity assertion from Enterprise A to the PEC Server via message 704 which may contain, among other things, a Session ID for the authenticated session with Enterprise A.
  • a Session ID for the authenticated session with Enterprise A.
  • PEC Server B may be co-located with Enterprise B.
  • a SAML notification 705 may be sent from the first PEC Server to PEC Server B including, among other things, the Session ID.
  • the login screen from Enterprise B may appear.
  • the portal to Enterprise B the person may login, via message 706, to Enterprise B within the frame for Enterprise A.
  • the login may, for example, be confirmed via message 708.
  • Enterprise B may send an identity assertion 710 to PEC Server with, among other things, the session ID from the login 708.
  • Enterprise B may, for example, send SAML assertion 711, which may contain the same Session ID, to PEC Server B.
  • the login transference process of PEC then may close out, and the correlation between the identity in Enterprise A and the identity in Enterprise B may be sent to IXS via provisioning correlation message 712.
  • PEC server B may send the provisioning correlation message 713 to IXS.
  • the Web workflow for PEC which is shown by way of example only in FIGs. 6 and 7, may be customized to provide a tutorial, for example, to explain the PEC process to the end-user in detail. Additionally, a person who has experience with this process can complete the process very rapidly through a PEC express interface that allows a person to conduct the process without the tutorial steps and explanations.
  • PEC is one example of a mechanism to provision LXS with a matched pair to enable future correlation while it can also be used to provision an identity correlation in other systems.
  • correlation of identities is conducted by deterministic or probabilistic identity matching algorithms.
  • PEC allows an individual who faces historical challenges with automated identity matching to leverage the identity provisioning processes of the enterprises with whom they have done business to serve as the correlation across enterprises without the ability or desire to do so in an otherwise automated or manual process.
  • An enterprise may have the capability to make an identity assertion (as an example, using SAML or OpenID) based upon the person's existing login.
  • an enterprise may be provided the destination for the identity assertion to its PEC Server, or one hosted on an external website for them.
  • the assertion may contain, for example, a unique identifier for the individual associated with the enterprise as well as the session ID that generated the assertion.
  • the unique identifier used in the assertion process may not be the same unique identifier for the person's unique identity in the enterprise (like user ID, medical record number, or account number).
  • the enterprise may enable the PEC Server to resolve the identity assertion unique ID and the enterprise person ID during the transaction. This can be done with a table, or a directory, for example.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Health & Medical Sciences (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Medical Informatics (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention concerne un système et un procédé d'échange d'informations d'identités et de corrélation de données protégées dans l'ensemble de systèmes de données indépendants connectés par l'intermédiaire d'un réseau. Le système contient des connecteurs en communication avec des systèmes de données protégées qui hébergent les données protégées. Les données sont corrélées entre les systèmes de données protégées par l'intermédiaire d'une authentification simultanée des deux systèmes par l'utilisateur. Des messages sont échangés qui permettent au système d'échange d'identités de corréler les données sur la base d'un identifiant de session provenant d'une session authentifiée sur un des systèmes de données protégées.
PCT/US2015/053511 2014-10-24 2015-10-01 Système et procédés améliorés d'échange d'informations d'identités entre des entreprises indépendantes susceptibles de présenter une corrélation par intervention humaine WO2016064552A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US14/522,670 2014-10-24
US14/522,670 US9705870B2 (en) 2014-01-10 2014-10-24 System and methods for exchanging identity information among independent enterprises
US14/594,068 2015-01-09
US14/594,068 US9699160B2 (en) 2014-01-10 2015-01-09 System and methods for exchanging identity information among independent enterprises which may include person enabled correlation

Publications (1)

Publication Number Publication Date
WO2016064552A1 true WO2016064552A1 (fr) 2016-04-28

Family

ID=55761310

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2015/053490 WO2016064550A1 (fr) 2014-10-24 2015-10-01 Système et procédés pour échanger des informations d'identité entre des entreprises indépendantes
PCT/US2015/053511 WO2016064552A1 (fr) 2014-10-24 2015-10-01 Système et procédés améliorés d'échange d'informations d'identités entre des entreprises indépendantes susceptibles de présenter une corrélation par intervention humaine

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2015/053490 WO2016064550A1 (fr) 2014-10-24 2015-10-01 Système et procédés pour échanger des informations d'identité entre des entreprises indépendantes

Country Status (1)

Country Link
WO (2) WO2016064550A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106357684B (zh) * 2016-10-26 2020-09-18 北京奇虎科技有限公司 游戏应用程序的登录方法及装置

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040199768A1 (en) * 2003-04-04 2004-10-07 Nail Robert A. System and method for enabling enterprise application security
US20050138110A1 (en) * 2000-11-13 2005-06-23 Redlich Ron M. Data security system and method with multiple independent levels of security
US20070186106A1 (en) * 2006-01-26 2007-08-09 Ting David M Systems and methods for multi-factor authentication
US7350229B1 (en) * 2001-03-07 2008-03-25 Netegrity, Inc. Authentication and authorization mapping for a computer network
US20100235445A1 (en) * 2004-08-06 2010-09-16 Salesforce.Com, Inc. Providing On-Demand Access to Services in a Wide Area Network
US20110030041A1 (en) * 2002-07-26 2011-02-03 Computer Associates Think, Inc. Session Ticket Authentication Scheme
US20130263234A1 (en) * 2010-11-17 2013-10-03 Ruckus Wireless, Inc. Cross Access Login Controller
US20140020073A1 (en) * 2012-07-13 2014-01-16 Troy Jacob Ronda Methods and systems for using derived credentials to authenticate a device across multiple platforms

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090307755A1 (en) * 2005-02-24 2009-12-10 Dvorak Carl D System and method for facilitating cross enterprises data sharing in a healthcare setting
US8583781B2 (en) * 2009-01-28 2013-11-12 Headwater Partners I Llc Simplified service network architecture

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20050138110A1 (en) * 2000-11-13 2005-06-23 Redlich Ron M. Data security system and method with multiple independent levels of security
US7350229B1 (en) * 2001-03-07 2008-03-25 Netegrity, Inc. Authentication and authorization mapping for a computer network
US20110030041A1 (en) * 2002-07-26 2011-02-03 Computer Associates Think, Inc. Session Ticket Authentication Scheme
US20040199768A1 (en) * 2003-04-04 2004-10-07 Nail Robert A. System and method for enabling enterprise application security
US20100235445A1 (en) * 2004-08-06 2010-09-16 Salesforce.Com, Inc. Providing On-Demand Access to Services in a Wide Area Network
US20070186106A1 (en) * 2006-01-26 2007-08-09 Ting David M Systems and methods for multi-factor authentication
US20130263234A1 (en) * 2010-11-17 2013-10-03 Ruckus Wireless, Inc. Cross Access Login Controller
US20140020073A1 (en) * 2012-07-13 2014-01-16 Troy Jacob Ronda Methods and systems for using derived credentials to authenticate a device across multiple platforms

Also Published As

Publication number Publication date
WO2016064550A1 (fr) 2016-04-28

Similar Documents

Publication Publication Date Title
US7660413B2 (en) Secure digital couriering system and method
US10049230B1 (en) System and methods for exchanging identity information among independent enterprises which may include person enable correlation
US20160112208A1 (en) System and method for providing consent management
WO2018095416A1 (fr) Procédé, dispositif et système de traitement d'informations
US20070124310A1 (en) Distributed Computing System to Enable the Secure Exchange of Information Between Remotely Located Healthcare Applications
BR112019017075A2 (pt) sistema de confiança digital, meio legível por computador e método computadorizado
US20110040814A1 (en) System and Method of Accessing Resources in a Computer Network
JP2005536801A (ja) ピア・ツー・ピア型のデータの遠隔記憶及び共同利用
BRPI0613189A2 (pt) sincronizaÇço de conta para identidade comum em uma rede nço-gerenciada
US20150381571A1 (en) System and method for securely managing medical interactions
CN109379336A (zh) 一种统一认证方法、分布式系统和计算机可读存储介质
WO2020147441A1 (fr) Procédé et appareil de mise à jour d'informations, dispositif informatique et support d'informations
US11849053B2 (en) Automation of user identity using network protocol providing secure granting or revocation of secured access rights
US20170012965A1 (en) Access control system
US9705870B2 (en) System and methods for exchanging identity information among independent enterprises
Madine et al. Application-level interoperability for blockchain networks
US11258782B2 (en) Peer-to-peer notification system
WO2016064552A1 (fr) Système et procédés améliorés d'échange d'informations d'identités entre des entreprises indépendantes susceptibles de présenter une corrélation par intervention humaine
US11646884B2 (en) Database key management
KR20170113192A (ko) 협업 가상 데스크톱 서비스 시스템 및 그 방법
Reniers et al. Authenticated and auditable data sharing via smart contract
WO2018093618A1 (fr) Liaison dynamique de groupes de messagerie et d'informations organisationnelles
US10083313B2 (en) Remote modification of a document database by a mobile telephone device
US20240071633A1 (en) Peer-to-Peer Secure and Scalable Network Architecture
EP3910880A1 (fr) Surveillance de dispositifs basée sur chaîne de blocs

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: 15851710

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205N DATED 30.06.2017)

122 Ep: pct application non-entry in european phase

Ref document number: 15851710

Country of ref document: EP

Kind code of ref document: A1