Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 132
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 290
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 164
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 233
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 313
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 354
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 282
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 294
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 304
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 317
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 375
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 110
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 143
Backtrace:
File: /home/u688923760/domains/msdpublications.com/public_html/application/controllers/Site.php
Line: 8
Function: __construct
File: /home/u688923760/domains/msdpublications.com/public_html/index.php
Line: 315
Function: require_once
Geeta Jeevan Aurangabadkar*
Consultant Endocrinologist, Care hospital and Excell hospital, Hyderabad, India
*Address for Correspondence: Dr. Geeta Aurangabadkar, Excell hospital, Hyderabad, India, Email: vrgeeta@yahoo.com
Received: 25 August 2020; Accepted: 07 September 2020; Published: 08 September 2020
Citation of this article: Aurangabadkar G (2020) How do we ensure safety for patients and clinicians while utilising Telemedicine in the field of Diabetes. Rea Int J of End and Diabe. 1(1): 022-025. DOI: 10.37179/rijed.000006.
Telemedicine use has been at its highest for patients in recent times due to ongoing COVID 19 pandemics. Although avoidance of face to face consultations carries many advantages for both patients and clinicians, there are always concerns around safety and legal aspects. So, how do we assure that the way of using teleconsultation in the field of diabetes is a mutually safe, effective, and sustainable option in the long term? This article lays out some important solutions addressing underlying apprehension and barriers in the use of telemedicine for diabetes. This is obviously truly relevant in the current scenario of COVID 19 where we anticipate continued use of telemedicine in near future.
Keywords: COVID-19 (Coronavirus disease of 2019), Information technology (IT), Telemedicine in diabetes, Patient, and clinician safety.
Coming Soon...
Coming Soon...
Coming Soon...
Coming Soon...