One or moregraphical user interfaces (GUIs) 213 and communication and media interfaces 214can exist within the MyTeleDoc application 212.A GUI 213 can represent theinteraction mechanism by which a user (patient/guardian), a physician and ahealthcare provider can perform functions with and/or enter data into MyTeleDocapplication 212.
Multiple GUIs 213 can exist, each GUI can containdifferent data and/or functionality. The number of GUIs 213 and/or their configuration can depend upon the design andimplementation of the MyTeleDoc application 212.The communication and media interface 214 can represent the component of MyTeleDocapplication 212 that can use variouscommunication media and/or software applications of the mobile device. Forexample, when an appointment is accepted by the provider, the MyTeleDoc app maybe configured to include GPS location of the user; the communication and mediainterface 214 can request access andutilize the map apps available on the user’s mobile device.
In anotherembodiment, MyTeleDoc app’s 212 communication and media interface 214 can request access and utilize theuser’s mobile device camera/video to provide the user (physician,patient/guardian, healthcare provider, any other service providers) access tovideo conferencing with other user’s (physician, patient/guardian, healthcareprovider, any other service providers). The previous feature can extend toinclude a real-time consultation between physicians, and/or user anotherphysician while undergo treatment with one physician. In anotherembodiment, 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 healthproviders “network” and promote awareness and marketing of MyTeleDocapplication 212. Moreover, theMyTeleDoc app 212 may be able topost messages on social networking sites, in addition to receiving messagesfrom users and prospective users.
MyTeleDoc server220 can include data store 225, which can contain information onphysicians and providers 227. In oneembodiment, data store 225 can alsoinclude user preferences for attachments, such as the ones discussed further in FIGURE 4. Healthcare Provider profiles 227 can include information on userpreconfigured message and medical services, physician preferences, and providerpreferences or can incorporate preconfigured messages and/or preferences intofuture searches for new health service providers. In one concept,a different set of physician/providers can be assigned to different symptoms orservice types and different “requests for service” can be assigned to differentphysician/provider. Furthermore, physicians, users, providers can have one ormore contact addresses or numbers associated with them (for example, a serviceprovider can receive a notification on application, text on mobile device and/oran 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 tophysician/healthcare provider.
Moreover, the MyTeleDoc application 212, in combination with the MyTeleDocserver 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 previouslymentioned, attachments may include patient symptoms and GPS location of thedevice 210, and by extension the user 205. Attachments can be in the formof photo/images, videos, or audio recordings, or in any other written or visualmodes. It should be understood that it is not necessary for MyTeleDoc app tocommunicate with the MyTeleDoc server 220to implement or transfer information, such as healthcare provider contacts, ‘requestfor service’ messages, attachment preferences, and can in another embodimentstore information directly on each user’s mobile device’s storage space itself.