One data store 225, which can contain information on

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.

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


order now

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.