Going over some new flow ideas and processes. He has a ton of stuff written up on paper. He is slowly building flow charts and diagrams in MS Publisher (desktop publishing and layout program).

- Permissions chart - certain permissions open up certain sections. See the chart titled "Assisted Living Permissions". Light color codes and flow chart.

- Assisted living menu (food) system - ideas on how thing could flow and ways to build a dining and room service style type menu and notifications. Meal plans and ways of tracking internal builds, items, menus, etc. Backend item tracking and internal builds (making things).

- Activities systems - mixing volunteers, residents, nurses

- Medical interfaces and small mock-ups on flow and even interfaces

- Mock interfaces for medical, food, human resources, maintenance, etc.

- Check things in/out and make assignments and be able to track where things are at.

- To do lists and notifications

- Talking about departments and how that could play in. We almost have a number of different business trying to all play under the same roof. We may need a number of sub flags and tags.

- We were talking about tracking things fairly deep... We also talked about how users may or may not want to track everything (that is totally ok). We need ways to allow them to virtually turn things on/off based on what they want to track and how deep. With a button - you could turn features and modules on/off. Super easy.

- We talked briefly about some IP addresses and even GEO fencing (what is available at what station including what is available from home or on premise or in certain locations). There may be differences. Good discussion.

Chart 2.1 - onboarding chart with more adilas pieces

- Custom web address - like we did on Campaign Rise

- When the potential resident fills out the info online, it creates two pieces inside of adilas. We are seeing a new customer/resident and an element of time to help track stages and general information.

- We want to catch some external info - termed medical interests on the flow chart. This becomes a virtual library of what data we want to catch. Internally, we could store this in flex grid and/or JSON objects, and/or custom database tables. These are key things that the facility wants to track.

- The App piece is for the administrators (a shortcut of sorts). Say for example, a walk-in off the streets. Same options as the web site, but in a shortcut type interface.

- Marketing will be able to control all aspects of the website through special elements of time and just changing their content. We may have to map out custom pages for them, and then make it easy for them to update and change that content.

- On the admin stuff... they may need corp-specific reporting (within a single world or corp) and maybe even multi corp reporting (consolidated reporting). Dave was also saying that the departments would kind be like a general role (aka skip the actual permissions and run based off of departments and assignments).

- There is a need for sub locations (virtual departments) and then track certain inventories per those locations. We may need to figure out a hybrid between departments and locations. For example: Marketing may want to track their own inventories and maintenance may want to track their inventories (kind of this mine and that is yours type mentality).

- In the queue, we will use stages inside of an element of time. These stages may be things like: 1st contact, in-person visit, follow-up, waiting list, actual resident being tied to a location.

- We may need to have a number of virtual locations such as waiting list, cold, not interested, and other hidden departmental needs. This is just an idea. We could also use customer types to do similar type grouping.

- Dave was talking about a transitional invoice... every resident has one... he was talking about medications. A strict record of what is needed on a daily basis. Almost a medication inventory per resident. Not really tied to finances, but a way to track quantities.

- We need to track some inventories on medications. This may involve quite a bit of smoke and mirrors... PO's, locations, tied with flex grid to residents, out bound values on simple invoices or update PO's. Some how, we need a full tracking system for what we have, what we should have, and what has been used. Mini version of inventory tracking. Timestamps, who did it, when, how much, and maybe why...

Chart 2.0 - see uploaded graphic

- This is the onboarding process

- Family and friends interact through the website

- Once they fill out some info and forms, it will put a record in the queue (who is next). It will also send some info out to admin and marketing.

- Marketing will be able to control the content and information on the web site (content management of sorts). Marketing will also be able to view the queue reports.

- The queue stages are just there for placeholders... we don't really know the total number of stages.

- The queue will help us process them all the way from the queue (or maybe element of time) into an actual resident and then into the system being assigned to a location.

- Under the website, there is a possible API socket connection. This allows us to play with and/or interconnect with outside services and/or 3rd party onboarding services.

Going over chart 1.0 - see uploaded image

- In the background, gray is the facility's needs, the white is residence's needs

- a generalization and flow of the information - who needs what and where does it come from

- For example: HR is connected to the employees and what services they offer.

- Maintenance will be taking care of location type things

- the lines are paths of data flow, the different paths are denoted by different patterns

- The volunteers and fundraising care more about the people (resident side). They are not really connected to a certain part, but we have to track them and be accountable for them.

- Very important, under the residents, Dave would like to flag and track: social, spiritual, mental, physical, emotional conditions and/or contributing factors. The goal is to create a diversification and a way to pull reports to check the different aspects of the resident's wellbeing.