Cloud Healthcare Data Service System for Secure Cross-Platform Access
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current healthcare data management systems lack seamless integration across different devices and platforms, leading to inefficiencies and security concerns in data storage and access, particularly in cloud-based environments.
Innovation Solution
A cloud-based healthcare data-service system that uses a .NET platform, integrating with iOS, Android, and Google Glass, featuring native apps for healthcare providers, staff, patients, and referring physicians, ensuring secure data storage and access through a Microsoft SQL database, while utilizing mobile camera systems for image acquisition and upload.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If healthcare data is stored on local devices, then data accessibility is improved, but security risks increase
Solution Approach 1:
The patent introduces a cloud-based healthcare data-service system as an intermediary between local devices and data storage. Local devices (mobile phones, tablets, desktops) communicate through secure networks to access healthcare data stored in the cloud, eliminating direct storage on local devices while maintaining accessibility. The cloud system acts as a mediator that provides both security and access functionality.
Solution Approach 2:
The system creates virtual copies of healthcare data in the cloud database, allowing multiple users to access the same data simultaneously without storing copies on local devices. The mobile applications display and interact with data copies retrieved from the cloud, ensuring data remains secure in a centralized location while being accessible across multiple devices.
2Adaptability or versatility
If the system integrates multiple device platforms, then versatility is improved, but system complexity increases
Solution Approach 1:
The patent implements a universal cloud-based healthcare data-service system that serves multiple device platforms through a common database architecture. The system provides standardized interfaces for iOS, Android, and web browsers, allowing the same core system to support diverse devices without requiring separate implementations for each platform.
Solution Approach 2:
The cloud-based system acts as an intermediary layer between diverse local devices and the healthcare data. By using standardized communication protocols and a centralized database, the system translates between different device platforms while maintaining a consistent data structure, thereby reducing integration complexity despite supporting multiple platforms.
3Object-affected harmful factors
If healthcare data is centralized in the cloud, then security is improved, but data access speed may decrease
Solution Approach 1:
The system performs preliminary actions by pre-loading frequently accessed healthcare data into memory caches on local devices when connected to the network. This allows rapid access to recent patient information, imaging data, and clinical notes without requiring continuous connection to the cloud, thereby maintaining speed while keeping data secured in the centralized cloud infrastructure.
Data Source
AI summary
The highly secure method and system acquires, processes and produces health care (HC) data and service records from multiple local devices, notwithstanding different operating systems (OS) in such devices, and all accessed and controlled by a cloud computing network. Devices have memories, displays, keypads, cameras and microphones. The system operates on acquired data including image, keypad-text, audio, and speech-converted-to text data generated by respective devices. The method downloads commands to devices (notwithstanding different OS) which delete-acquired-data upon a request to save (upload) data to the cloud computing network. Further data security includes a disable-print-screen command prohibiting local storage of stored acquired data into local devices. The method and system also produces a customized surgical schedule by (a) obtaining the GPS location of a local device (b) filtering out the non-surgical appointments from the complete appointment schedule of the HC professional; and (c) displaying only surgical appointments.