Uncured thermosetting resins are loaded with relatively high amounts of solid thermoplastic resin particles to form a resin precursor. The resin precursor is heat treated so as to produce an uncured resin composition wherein the thermoplastic resin particles become substantially dissolved in the thermosetting resin without causing cure of the resin mixture. Heat treatment of highly loaded thermosetting resins in accordance with the present invention provides uncured resin compositions that are well suited for use in fabricating composite structures and particularly prepreg for use in lightning protection surface coatings.
- Salt Lake City UT, US Michael R. Donnelly - Salt Lake City UT, US Orland Kip Williams - Sandy UT, US Cary J. Martin - Kaysville UT, US Ming-Chieh Tu - Salt Lake City UT, US Charlton Park - Holladay UT, US Jeffrey Todd Young - West Valley City UT, US Andrew Mark Hansen - Taylorsville UT, US Jonathan Paul Godfrey - Salt Lake City UT, US Nic Holbrook - Brigham City UT, US Timothy John Morris - Bountiful UT, US Tony Drake - West Jordan UT, US Michael Houston - Kaysville UT, US
In an example implementation, the method includes automatically determining whether a computer system is located on-premises of a health service provider or on a multi-tenant cloud. The method includes communicatively coupling with health service provider data sources via a local network and extracting health service provider data from them. The health service provider data may include protected health information (PHI) and non-PHI data. The method includes storing the PHI data and the non-PHI data in an on-premises operational data store that is located on-premises of the health service provider. The method includes obtaining data analytics based on the PHI data and the non-PHI data stored in the on-premises operational data store. The method also includes communicatively coupling with a multi-tenant cloud via a global network and synchronizing the non-PHI data in the on-premises operational data store with the multi-tenant cloud via the global network.
Multi-Tenant Cloud For Healthcare Data Application Delivery
- Salt Lake City UT, US Michael R. DONNELLY - Salt Lake City UT, US Orland Kip WILLIAMS - Salt Lake City UT, US Cary J. MARTIN - Salt Lake City UT, US Ming-Chieh TU - Salt Lake City UT, US Charlton PARK - Salt Lake City UT, US Jeffrey Todd YOUNG - Salt Lake City UT, US Andrew Mark HANSEN - Salt Lake City UT, US Jonathan Paul GODFREY - Salt Lake City UT, US Nic HOLBROOK - Salt Lake City UT, US Timothy John MORRIS - Salt Lake City UT, US Tony DRAKE - Salt Lake City UT, US Michael HOUSTON - Salt Lake City UT, US
International Classification:
G06F 19/00 H04L 29/08
Abstract:
In an example implementation, a method includes communicatively coupling a tenant instance of a multi-tenant cloud with a corresponding agent that is located on-premises of a health service provider via a global network. The method includes synchronizing the tenant instance with the agent including receiving non-Protected Health Information (non-PHI) data absent Protected Health Information (PHI) data from the agent at the tenant instance via the global network. The method includes extracting the non-PHI data from the agent into a cloud-based operational data store of the tenant instance that corresponds to the agent. The method includes storing the non-PHI data in the cloud-based operational data store. The method includes analyzing the non-PHI data in the cloud-based operational data store by load-balanced services.
- Salt Lake City UT, US Michael R. DONNELLY - Salt Lake City UT, US Orland Kip WILLIAMS - Sandy UT, US Cary J. MARTIN - Kaysville UT, US Ming-Chieh TU - Salt Lake City UT, US Charlton PARK - Holladay UT, US Jeffrey Todd YOUNG - West Valley City UT, US Andrew Mark HANSEN - Taylorsville UT, US Jonathan Paul GODFREY - Salt Lake City UT, US Nic HOLBROOK - Salt Lake City UT, US Timothy John MORRIS - Salt Lake City UT, US Tony DRAKE - Salt Lake City UT, US Michael HOUSTON - Salt Lake City UT, US
International Classification:
G06F 19/00 H04L 29/08
Abstract:
In an example implementation, the method includes automatically determining whether a computer system is located on-premises of a health service provider or on a multi-tenant cloud. The method includes communicatively coupling with health service provider data sources via a local network and extracting health service provider data from them. The health service provider data may include protected health information (PHI) and non-PHI data. The method includes storing the PHI data and the non-PHI data in an on-premises operational data store that is located on-premises of the health service provider. The method includes obtaining data analytics based on the PHI data and the non-PHI data stored in the on-premises operational data store. The method also includes communicatively coupling with a multi-tenant cloud via a global network and synchronizing the non-PHI data in the on-premises operational data store with the multi-tenant cloud via the global network.