Figure In one embodiment, the MyTeleDoc is downloaded and

Figure
2 is a schematic
diagram depicting a system 200 that coordinates
services between a physician, a provider and a patient. MyTeleDoc App 212 may automatically communicate
messages to one or more of the physicians and providers in accordance with embodiment of the inventive
arrangements disclosed herein.

The system 200 may include a user 205 (who
can either be the patient or guardian of patient), a mobile device (i.e. Apple,
Android, Motorola, Google, etc.) 210,
a MyTeleDoc app server 220, physicians’ database 235, a healthcare providers’ database 245 and network 260. System
200 and its components can be
configured to construct, send and properly route MyTeleDoc app messages 265 to physicians’ device(s) 235 and 270 to providers’
device(s) 245. It should be noted that the components shown within
the system 200 are for illustration
purposes only, and should not be considered the exact implementation, nor
should the invention be limited by the diagram purposed in the present
disclosure.

We Will Write a Custom Essay Specifically
For You For Only $13.90/page!


order now

User (patient or guardian) 205 can utilize mobile device 210 to use the MyTeleDoc application 212 to request medical services
from a physician registered on the MyTeleDoc database 235. Mobile device 210 can include MyTeleDoc application 212, and data store 215 containing MyTeleDoc application
activation pattern 217. MyTeleDoc
activation pattern 217 may be
configured to the patient symptoms or type of service required (checkup,
diagnosis, consultation, etc.) selected by the user 205. Based on the symptom or service selected, the activation pattern
217 may construct a list of possible
physicians, based on their medical background, credentials and availability. Additional activation patterns 217 are contemplated, including, in one
embodiment, physician and provider activation for consultations and
coordinated care with one or more physicians.

MyTeleDoc
communication application 212 may be
utilized within the context of the system 200
or any other system supporting the automatic provision of communication
services from mobile devices to a set of physician and healthcare providers’
database. In one embodiment, the MyTeleDoc communication application can be
integrated with and used from an internet website. Any website integration is
contemplated, through the creation of a MyTeleDoc website that may be accessed
from any web browser (Safari, Chrome, Explorer, etc.). For example, a user’s
phone is inaccessible due to loss, theft, misplacement or malfunction (dead
battery), they may be able to access their account through the internet website
and request a service from a physician.

In one
embodiment, the MyTeleDoc is downloaded and utilized on a tablet from any
manufacturer (i.e. Apple, Google, Android, Microsoft, etc.)  that can connect to internet, either by network
data or Wi-Fi, and access the service. Another embodiment contemplated is the
use of map applications (i.e. Google Maps, Apple Maps, Waze, etc.) to integrate
with the device and guide the provider to the user residence. Another
manifestation considered includes integration with device(s) calendar
applications to remind user(s), physician(s) and provider(s) of the
appointments. Other contemplations include the integration of User’s Electronic
Health Record system (i.e. MozartMD or another system) to transfer patient’s
medical and related history to the physician via MyTeleDoc application 212. Other collaborative endeavors,
such as the integration of Henry Schein’s Medpod or another manufacturer’s telemedicine
device directly with the MyTeleDoc application 212 to ensure delivery of service and payment are contemplated. Furthermore,
integration of mobile laboratory or phlebotomy laboratory services and
pharmaceutical delivery services with the MyTeleDoc application 212 are contemplated. The focus is for
all users (especially elderly, disable or shut-ins) to be able to access most,
if not all, healthcare services from their residence. Assimilation of health
insurance providers, including private and public insurance companies, directly
with the MyTeleDoc application is contemplated. The aim is to make
reimbursement as efficient and automatic as possible to reduce opportunity
costs (time, money and other resources) for all parties involved.

One or more
graphical user interfaces (GUIs) 213 and communication and media interfaces 214
can exist within the MyTeleDoc application 212.

A GUI 213 can represent the
interaction mechanism by which a user (patient/guardian), a physician and a
healthcare provider can perform functions with and/or enter data into MyTeleDoc
application 212. Multiple GUIs 213 can exist, each GUI can contain
different data and/or functionality. The number of GUIs 213 and/or their configuration can depend upon the design and
implementation of the MyTeleDoc application 212.

The communication and media interface 214 can represent the component of MyTeleDoc
application 212 that can use various
communication media and/or software applications of the mobile device. For
example, when an appointment is accepted by the provider, the MyTeleDoc app may
be configured to include GPS location of the user; the communication and media
interface 214 can request access and
utilize the map apps available on the user’s mobile device. In another
embodiment, MyTeleDoc app’s 212 communication and media interface 214 can request access and utilize the
user’s mobile device camera/video to provide the user (physician,
patient/guardian, healthcare provider, any other service providers) access to
video conferencing with other user’s (physician, patient/guardian, healthcare
provider, any other service providers). The previous feature can extend to
include a real-time consultation between physicians, and/or user another
physician while undergo treatment with one physician. In another
embodiment, communication and media interface 214 can allow MyTeleDoc application 212 to synch with social media services (e.g. FACEBOOK, TWITTER,
INSTRAGRAM, LINKEDIN, SNAPCHAT, etc.) to visually display MyTeleDoc app health
providers “network” and promote awareness and marketing of MyTeleDoc
application 212.  Moreover, the
MyTeleDoc app 212 may be able to
post messages on social networking sites, in addition to receiving messages
from users and prospective users.

MyTeleDoc server
220 can include data store 225, which can contain information on
physicians and providers 227. In one
embodiment, data store 225 can also
include user preferences for attachments, such as the ones discussed further in FIGURE 4. Healthcare Provider profiles 227 can include information on user
preconfigured message and medical services, physician preferences, and provider
preferences or can incorporate preconfigured messages and/or preferences into
future searches for new health service providers.

In one concept,
a different set of physician/providers can be assigned to different symptoms or
service types and different “requests for service” can be assigned to different
physician/provider. Furthermore, physicians, users, providers can have one or
more contact addresses or numbers associated with them (for example, a service
provider can receive a notification on application, text on mobile device and/or
an email for request for service).

When activated,
the MyTeleDoc application 212 can,
in one embodiment, communicate with MyTeleDoc server 220 to determine the specific message to send to
physician/healthcare provider. Moreover, the MyTeleDoc application 212, in combination with the MyTeleDoc
server 220 can establish, if any,
type of message/attachment to include with the “request for service” message 265 and 270 to be sent to healthcare providers 235 and 245. As previously
mentioned, attachments may include patient symptoms and GPS location of the
device 210, and by extension the user 205. Attachments can be in the form
of photo/images, videos, or audio recordings, or in any other written or visual
modes. It should be understood that it is not necessary for MyTeleDoc app to
communicate with the MyTeleDoc server 220
to implement or transfer information, such as healthcare provider contacts, ‘request
for service’ messages, attachment preferences, and can in another embodiment
store information directly on each user’s mobile device’s storage space itself.

 

Network 135, 260 can include any hardware/software/and firmware required to
transfer data encoded within carrier waves. Data can be contained within analog
or digital signals and conveyed through data or voice channels. Network 135,
260 can include local mechanisms and data pathways that can be used to communicate
and exchange information amongst the computing device’s components and between
integrated device components and with other devices. In addition, Network 135, 260 can include network
components, such as but limited to, routers, data lines, hubs, and intermediary
servers, which together form a data network, such as the Internet. Furthermore,
Network 135, 160 can have
circuit-based communication mechanisms and mobile communication components,
such as but not limited to, telephony switches, modems, cellular communications
towers, etc. Network 135, 260 can
include line based and/or wireless communication pathways.

As used herein,
presented data stores 215 and 225 can be a physical or virtual
storage space configured to store digital information. Data
stores 215 and 225 can be physically incorporated in any type of hardware
including, but not limited to, a magnetic disk, an optical disk, a
semiconductor memory, a digitally encoded plastic memory, a holographic memory,
or any other recording medium or they can be cloud-based storage systems. Data
stores 215 and 225 can be a stand-alone storage unit as well as a storage unit
formed from a plurality of physical devices. Additionally, information can be
stored in data stores 215 and 225 in a variety of manners. For
example, information can be stored within a database structure or can be stored
within one or more files of a file storage system, where each file may or may
not be indexed for information searching purposes. Furthermore, data stores 215 and 225 can utilize one or more encryption mechanisms to protect stored
information from unauthorized access.