| Literature DB >> 35035477 |
Abstract
Technological innovation plays a crucial role in digital healthcare services. A growing number of telehealth platforms are concentrating on using digital tools to improve the quality and availability of care. Virtual care solutions employ not only advanced telehealth technology but also a comprehensive range of healthcare services. As a result, these can reduce patient healthcare costs as well as increase accessibility and convenience. At the same time, the healthcare service provider can leverage healthcare professionals to get a better perspective into the needs of their patients. The objective of this research is to provide a comprehensive design blueprint for a large-scale telehealth platform. Telehealth is the digital healthcare service combining online services and offline access for healthcare facilities to offer various healthcare services directly to patients. This design blueprint covers the digital healthcare ecosystem, new patient journey design for digital health services, telehealth functionality design, and an outline of the platform infrastructure and security design. Ultimately, telehealth platforms establish a completed digital healthcare service and new ecosystem that provides better care for every patient worldwide.Entities:
Year: 2022 PMID: 35035477 PMCID: PMC8754604 DOI: 10.1155/2022/8486508
Source DB: PubMed Journal: Int J Telemed Appl ISSN: 1687-6415
Figure 1New era of digital healthcare ecosystem.
Figure 2Existing telehealth patient journey pattern.
Figure 3A comprehensive patient journey design of telemedicine services.
Figure 4A hybrid design of patient journey.
Figure 5A design of base telehealth functionality.
Figure 6Infrastructure design for a large-scale telehealth platform.
Blockchain technology comparisons for telehealth platform.
| Measurement | Ethereum | Hyperledger | EOS | Tendermint |
|---|---|---|---|---|
|
| ||||
| (1) Number of transactions per second (TPS) | 15-30 | 300 | 500 | 2,002 |
| (2) Data reading response time of 1,000 records under 10 concurrent sessions | 3.72 min | 1333 ms | 1 ms | 3 ms |
| (3) Insert of one record response time under 10 concurrent sessions with duplication check | 209 ms | 235 ms | 9662 ms | 3 ms |
| (4) Update data in one record response time under 10 concurrent sessions | 208 ms | 544 ms | 260 ms | 2 ms |
|
| ||||
| (5) Mutuality level (5 years) | Y | Y | N | Y |
| (6) Live application in health technology | Y | Y | Y | Y |
|
| ||||
| (7) Fault tolerant (nodes) | 2 | 3 (orderer) | (ratio 2/3) | (ratio 2/3) |
| (8) Restructure blockchain (add nodes) | N | Y | N | N |
|
| ||||
| (9) Smart contract language supports | Solidity | Go | C++ | Go, Js |
| (10) Transaction management | N | Y | N | N |
| (11) Cryptocurrency account balance for trading | Y | N | Y | Y |
| (12) Access data from smart contract with ranges | N | Y | Y | N |
| (13) Creating index on data from smart contract | N | N | Y | Y |
|
| ||||
| (14) Authentication and account management | Y | Y | Y | Y |
| (15) Encryption data in the smart contract | N | Partial | N | N |
| (16) Access control on smart contract | N | Y | N | N |
Big data technology comparisons for IoT streaming in telemonitoring.
| Study #1 | Study #2 | Study #3 | Study #4 | Study #5 | |
|---|---|---|---|---|---|
| Big data technology | KUDU | Hive | Cassandra | HBase | Elasticsearch |
| Big data Interface | Library | JDBC | Library | Library | RapidMQ |
| (1) Insert data∗ | |||||
| Insert 100 b/100k rows | 1.54 | 13,207.80 | 1.11 | 1.22 | 0.34 |
| Insert 1 kb/100k rows | 1.70 | No response | No response | 1.31 | 0.75 |
| Insert 10 kb/100k rows | 2.73 | No response | No response | 2.73 | 7.30 |
| Insert 100 kb/100k rows | 17.72675 | No response | No response | 23.4235 | 13.33 |
| (2) Select data∗ | |||||
| Select 1 row | 800.00 | 19,709.20 | No response | 1,000.00 | 230 |
| Select 5 rows | 800.00 | 21,882.20 | No response | No response | 450 |
| (3) Architecture | Master/slave | Master/slave | Multimaster | Master/slave | Master/slave |
| (4) File structure | Distributed DB | Hadoop | Distributed DB | Hadoop | Database |
| (5) Storage fault tolerant | Multicopies | Multicopies | Multicopies | Multicopies | Multicopies |
| (6) Large volume data access for analytics | Average | Best | Worse | Worse | Average |
| (7) Access data by key | No | No | Yes | No | No |
| (8) Built-in visualization | No | No | No | No | Best |
| (9) Min. server required | 3 | 5 | 3 | 3 | 3 |
| (10) Security | |||||
| Client-node encryption | TLS/SSL | TLS/SSL | N/A | TLS/SSL | |
| Web UI encryption | TLS/SSL | N/A | N/A | ||
| Peer node authentication | N/A | N/A | N/A | ||
| User authentication | Kerberos | Internal | Kerberos | ||
| Authentication tokens | Y | N/A | Kerberos |
∗A unit of measurement is a response time (millisecond) per 1 transaction.
Figure 7Software architecture design for a large-scale telehealth platform.
Figure 8Security design for a large-scale telehealth platform.