Pharmacy and Physician Mobile App Prototype

Below is what I would like to mock-up as a basic prototype that I can create fake data to run through the basic steps of how to use the app. Again, this is just a prototype without all the fancy bells and whistles, just the basic capabilities to input data, submit data and receive data. Step 1a: Capture Key Member Data – used to setup and account and to create a health profile (link to Apple Health on iPhones and similar thing on Androids) Member Info Member First Name Member Last Name Date of Birth (YYYYMMDD) Gender (Male or Female) Home Address (Address, City, State, Zip Code) Phone Number Mobile Phone Number Email Address (Home/Personal) Email Address (Work/Business) Social Security Number Employer Name (if insured through employer) Preferred Pharmacy Name, Address, Phone# Primary Care Physician (PCP) Name, Address, Phone# Insurance Info Health Insurer Name Card Holder Name (Primary Insured Person) Card Holder Social Security Number Group ID Bin PCN Relationship to Card Holder Code Step 1b. Capture Key Physician Data – used to setup physicians account and to exchange information with member Physician Info First Name Last Name Date of Birth Gender NPI Number Social Security Number Company Address (Address, City, State, Zip Code) Physicians Phone Number Physicians Company Email Address EHR/EMR System Used Step 2: Method for Member to share information with Physician for visit Select Member info from Step 1a will be shared with Physician for prescribing purposes and updates to EHR/EMR system and to submit prescription to insurer and pharmacy. Initial thought was to use a one-time use QR Code that Physician scans from their mobile device and populates members info to create a visit Step 3: Physician search for medication (NDC) and pharmacy NPI Public API’s are available to locate this information – like what GoodRx does – right now we will just use some sample drugs that we will create for the prototype to keep cost down Step 4: Once Medication found – physician enters: Dispensed quantity Submission Clarification Codes Prior Authorization Number Submitted Dispense as Written Product Selection Code Scheduled Prescription ID Number Physician submits info to members insurance carrier (backend API) Step 5: Physician receives response (see example API for information returned in response) Based upon returned information Physician can repeat Step 3 or continue to Step 5 Step 6: Submit ePrescribe of medication to pharmacy Right now this is unknown how it will function, but we can create a fake process to just demonstrate this functionality and capture the data for Step 7 Step 7: Send visit details and prescription prescribed and location back to member via same or similar method as step 2, along with any notes recorded by physician Physician closes visit and saves member visit information Members accepts prescribed medication and closes visit saving visit information in member record/profile The is a link for the API data source. The link details the flow of data for Steps 4 & 5. the link helps bring the above steps all together. I just want to keep it basic, to demonstrate the functionality and get feedback from my physician testers and patients. I don’t want to spend very much money on this prototype because once I confirm the basic functionality then we will get into the features, functions, bells and whistles to build the actual app. Hopefully this makes sense and helps provide you with enough direction to provide a quote for a prototype. [login to view URL]%238/