Health Stash: an interactive health-spending tracker by: Catherine Meakem 2016

Create a To-Do list for your upcoming tasks

Get Started. It's Free
or sign up with your email address
Rocket clouds
Health Stash: an interactive health-spending tracker by: Catherine Meakem 2016 by Mind Map: Health Stash: an interactive health-spending tracker by: Catherine Meakem 2016

1. Week 1

1.1. the need

1.1.1. provides knowledge about out-of-pocket costs for healthcare services

1.1.1.1. will allow patient's to make informed decisions in their healthcare

1.1.2. patient's need accessibility

1.1.2.1. enhance patient engagement

1.2. social context

1.2.1. patients can shop around for the healthcare services

1.2.1.1. become active consumers in their healthcare

1.2.2. intervention that touches on "a person's sense of worth and desire to be respected" (Hamalainen & Saarinen, n.d., p. 191)

1.2.2.1. transparency for patients

1.2.2.2. potential for providers paid for services up front for patient portions of the cost more often

1.2.2.3. connect the divide between care and cost

1.3. synthesis

1.3.1. "Innovation: applied creativity that achieves business value" (Weiss & Legrand, 2011, p. 6)

1.3.1.1. create more revenue for organization through transparency

1.3.1.2. synthesize the data given to patients by other providers

1.3.2. drive third-party payers to encourage members to our organization

1.3.2.1. could offer a discount based on the volume of patients sent to the organization (Nowicki, 2015)

1.3.2.2. could bridge the gap between insurance companies and care

1.3.2.2.1. incentives to comprehensive healthcare services

1.3.2.2.2. incentives to enhancing the EMR

1.4. demand

1.4.1. a way to synthesize the EMR

1.4.1.1. built into patient portal

1.4.1.2. patients can access medical records as well as a breakdown of costs of each services

1.4.1.3. combine billing, patient access and clinical data

1.4.2. reduce schedule procedure cancellations due to unanticipated out-of-pocket costs for patients

1.4.2.1. aware of the costs of their healthcare services prior to scheduling

1.4.2.2. organization needs guidelines to relay costs to patients

2. References

3. Week 2

3.1. Stakeholders

3.1.1. providers

3.1.1.1. combine patient portal information from office to facility

3.1.1.2. patient outreach through their websites

3.1.1.3. comprehensive provider specialties list

3.1.2. app developers

3.1.2.1. user-friendly tool

3.1.2.2. interactive

3.1.2.2.1. relatable data

3.1.2.3. visually appealing

3.1.2.3.1. clearly defined tools within the app

3.1.2.4. content is appealing

3.1.3. social media experts

3.1.3.1. get the word out about Health Stash

3.1.3.2. create an open conversation of budget and health

3.1.4. patients

3.1.4.1. engagement is measurement of success of app

3.1.4.2. health goals and outcomes

3.1.5. caregivers

3.1.5.1. make connections with patient needs

3.1.5.2. make connections with provider needs

3.1.6. hospitals and their resources

3.1.6.1. cautious and reflective (Balance Work Force, 2014)

3.1.6.2. connect specialists through carefully chosen recruiters

3.1.7. insurance companies

3.1.7.1. contracted rates with facility to help calculate budget on Health Stash

3.1.7.2. future evolution

3.1.8. accountants

3.1.8.1. ability to align budget and needs

3.1.8.2. budgets are organized and clear to users

3.2. VAT and DiSC assets

3.2.1. Steadiness

3.2.1.1. makes sure everyone's contributions matter

3.2.1.2. consistent

3.2.1.3. collaborator

3.2.2. Conscientiousness

3.2.2.1. accuracy

3.2.2.2. willing to challenge ideas

3.2.2.3. finds practical solutions to complex problems

3.2.3. Visual

3.2.3.1. Health Stash will be visually appealing

3.2.3.2. make potential users want to click and check it out

3.2.3.3. make sure the tools are clearly defined within the app

3.2.3.3.1. make sure budgets are clear to the user

3.2.3.3.2. data obtained through Health Stash is relatable

3.2.3.3.3. Health Stash tells a story of the patient's budget and their health

4. Key

4.1. VAT learning style

4.2. DiSC personality

4.3. future connections

4.4. stakeholders

4.5. obstacles

4.6. diffusing innovation

4.7. outcomes

4.8. change management

5. Week 3

5.1. Questions

5.1.1. What are the guidelines for the current Patient Portal to display protected health information to patients?

5.1.2. Are there current accountants in the business office that want to introduce their knowledge to the Patient Portal patient budget aspect?

5.1.3. What are the most frequent insurances with denied bill claims and what can we do to alleviate that?

5.1.3.1. Cigna

5.1.3.2. United Healthcare

5.1.3.3. BCBS

5.1.4. What are the current contracted rates that our organization has with insurance companies?

5.1.5. What are incentive program models that our top insurance companies have with our organization as well as others?

5.1.6. What are the biggest obstacles for patient collections after discharge?

5.1.6.1. incorrect demographic information

5.1.6.2. not knowing healthcare costs prior to scheduling out-patient procedures

5.1.7. What are patient motivations for paying bills for scheduled procedures?

5.1.8. What are patient's current ways for healthcare bill budgeting?

5.2. Information gathering

5.2.1. failed bill accounts

5.2.2. previous insurance payment tracking for procedures

5.2.3. business office collection process

5.2.3.1. survey calls

5.2.4. integration of care surveys

5.2.4.1. whether patient payments coincide with care received

5.2.4.2. quality surveys

5.2.4.3. assess effectiveness of virtual care system for budgeting (Porter-O'Grady & Malloch, 2010)

6. Week 4

6.1. Evaluation technique (TACOS)

6.1.1. Trialability

6.1.1.1. prototyping

6.1.1.1.1. evolution

6.1.1.2. external crowd sourcing

6.1.2. Advantage

6.1.2.1. user feedback

6.1.2.1.1. any deterring from the vision of the application, problems will be able to be addressed in real time

6.1.2.1.2. value-based survey tracking

6.1.2.2. vocalize vision and direction

6.1.2.2.1. increased usage

6.1.2.3. address program flaws before competitors

6.1.2.3.1. adoption

6.1.3. Compatibility

6.1.3.1. understanding healthcare finance culture

6.1.3.1.1. identifying patient perception

6.1.3.1.2. adapting to finance and insurance verifier needs for the app

6.1.3.1.3. identifying provider perception

6.1.4. Observability

6.1.4.1. tacit knowledge

6.1.4.2. demonstrate app to colleagues

6.1.4.3. usage

6.1.4.3.1. built-in analytics programs to track usage by providers and patients

6.1.5. Simplicity

6.1.5.1. critical mass

6.1.5.2. time it takes to increase amount of users

6.1.5.2.1. track retention rates

7. Week 5

7.1. Strategies

7.1.1. collaborate

7.1.1.1. members of organizations are full participants

7.1.1.2. data sharing/integration

7.1.1.3. define organization by sharing mission

7.1.2. "focus on value"

7.1.2.1. healthy outcomes

7.1.2.2. cost controlled

7.1.2.3. team innovation skills

7.1.3. conversations with people to assess needs

7.1.3.1. patients

7.1.3.2. caregivers

7.1.3.3. point of service

7.1.3.4. community

7.1.4. evaluate organizational structure

7.1.4.1. create an environment for innovation (Fonseca, 2002)

7.1.4.2. create the organization's future utilizing purpose as a guide

7.1.4.3. identify key stakeholders

7.1.4.3.1. access team's innovative intelligence

7.2. Change Management

7.2.1. demand to change

7.2.1.1. respond to unplanned crisis

7.2.1.2. comittment

7.2.1.3. integrate team's skill for advancement

7.2.1.4. investment

7.2.1.5. ability to organize around change

7.3. Barriers

7.3.1. implementing amongst other innovations

7.3.1.1. comprehensive registration

7.3.1.2. already established programs within organizaton

7.3.1.2.1. Cerner

7.3.1.2.2. MedAssets

7.3.2. additional costs for new program

7.3.3. learning new program and implementing

8. Week 6

8.1. Timeline

8.1.1. Feedback

8.1.1.1. 30-day trial

8.1.1.2. User surveys

8.1.1.2.1. stakeholder feedback

8.1.1.3. similar application pitfalls and advantages

8.1.1.4. beta-testing

8.1.1.4.1. small parts of app introduced at a time

8.1.1.4.2. allows for user creation of app

8.1.2. Prototyping

8.1.2.1. 6-months

8.1.2.2. application design

8.1.2.2.1. picture vs. numbers to display financial information

8.1.2.2.2. downloading

8.1.2.2.3. accessibility on multiple devices (i.e. computer, tablet, mobile)

8.1.2.3. initial funding request

8.1.2.3.1. investor backing

8.1.3. Launch

8.1.3.1. 12-months

8.1.3.2. market

8.1.3.3. emphasize mission

8.1.3.4. funding

8.1.3.4.1. make sure stay on budget

8.1.3.5. emphasize user-friendly

8.1.3.5.1. invest in constant feedback

8.1.4. Updates

8.1.4.1. Every 3 months

8.1.4.2. encourage continuous user feedback

8.1.4.3. track usage