Provider Direct Kickoff - Group 1

Download Report

Transcript Provider Direct Kickoff - Group 1

MA Council for Home Care Aide Services
Thursday May 19, 2011
1
Agenda
•
•
•
Introductions
Implementation Strategy
Project Calendar
•
•
Function Of Lead Agency
User Support Model
•
Business Process Review Meetings
•
User Request Forms
•
Project Communications
•
On-line Training (Harmony University)
•
Demonstrate The Application
Contact Info
Jim Ospenson
EOEA Analyst for Home Care/
Clinical
[email protected]
Sean Rogers
EOEA Analyst for Finance
[email protected]
2
Provider Direct Features
•
Provider Direct is:
– A secure web portal that allows
Providers to view real-time agency
data:
– Looks at the SAMS database used
by ASAPs for up-to-the minute
updates
• Consumer records & relevant
information (PHI)
• Planned & ordered services
• History of service delivery records
• Suspensions
• Service Delivery Module – post
service delivery / electronic invoices
• Client-centered messaging for
inquiries, follow-up, and task
assignment (future)
•
System that transmits Protected
Health Information between
providers
Confidential Information
3
3
Implementation Strategy: FAR first, then EVI
•
In a nutshell: FAR first, then EVI
•
Assign Provider to Lead Agency
•
Initial exposure to application
•
–
Schedule of webinars before and after go-live:
•
online demonstrations, watch from your office.
Business Process Meetings
–
–
Provider to meet with each ASAP that they serve
Review details of current-state work process
•
Who talks to whom in what situation
•
Providers: Self-training using Harmony University
•
Stage 1: FAR (faxed authos)
•
–
Thirty (30) days of access per user, starting one week before go-live
–
–
–
Provider Users will start off in a production environment, looking at their own real consumer data.
First job: parallel processing. Compare HPD’s Change Log to FAR faxes.
Next:
–
Objective: Agency & Provider agree to shut down FAR faxes after approx 3 weeks
•
•
Agency-Provider communications. What’s different?
Reporting
Stage 2: EVI (Electronic Vendor Invoices)
–
–
Agency & Provider agree on first HPD billing cycle
Provider identifies desired billing functionality: File Upload, Service Delivery Confirmation Wizard,
other.
4
Project Calendar (1/2)
Week
0
1
2
3
4
Tasks

Kick-off Meetings – Group 2

Agencies schedule Provider meetings to discuss current business process
& possible changes

Agencies collect URF info from Providers

Provider Webinars start (pre-go-live topics, 2 each week) - EOEA

Agency/Provider Business Process meetings conducted

Provider Webinars continue

Agency/Provider Business Process meetings continue

Agencies: Notify EOEA of Providers with multiple business lines, or
recently merged providers (unusual security configurations)

URFs due – IMPLEMENTATION CRITICAL (TBD) – Agency to submit by
end-of-day

Provider Webinars continue

Agency/Provider Business Process meetings continue

LMS (Harmony University) userids transmitted to end-users (TBD) one
week before go-live)

Providers begin self-training using LMS (1 token per user, token is active
for a thirty (30) day period, starts at first login)

Provider Webinars continue
5
Project Calendar (2 of 2)
Week
5
6
7
8
9
Tasks

GO LIVE! TBD. Users receive HPD userid & password email

Parallel Processing begins – Provider/Agency compare faxed authos to
HPD Work Queue

Trouble-shooting conference call

Parallel Processing continues: compare faxes to HPD Work Queue

Webinars continue

Provider & Agency discuss HPD billing methods (File Upload, Service
Delivery Confirmation, other)

Providers begin training for billing

Agency/Providers determine when to cease FAR / faxed authos

Agency/Providers continue to plan for details of first month’s billing, train
as-needed

Provider Webinars conclude

Group 1 Stage 1 (FAR) Implementation completed

Agency/Providers continue to plan for details of first month’s billing, train
as-needed

Group 1 Debrief Conference Call

Agency/Providers continue to plan for details of first month’s billing, train
as-needed
6
Function Of Lead Agency
•
A Provider can serve one or more ASAPs.
–
•
The Lead Agency is (usually) the Agency with the greatest
volume.
Functions
–
Coordinate user management for that Provider
–
Coordinate application training for providers, especially new staff
–
Establish support policies and identify contact staff for Provider
Direct
–
Resolve "Tier One" issues related to users:
•
•
•
•
•
•
•
Distribute HPD user manuals (available from QuickBase)
Receive application and bug reports from Provider
–
Communicate with SIMS Support as needed
•
Lead
Agency
Provider
New & terminated users
ABC
Password resets
Application training
Basic usage questions related to Provider Direct: list formatting, filter
criteria, etc.
Reset Silverlight
–
•
ASAP One
ASAP Two
Train providers in getting screenshots
Providers will not communicate with SIMS Support
ASAP Three
Providers will contact other (non-Lead) agencies to
resolve questions about specific consumers, or to
confirm business processes & contact names
7
User Support Model - Provider Direct
Provider
XYZ
Report to Lead
Agency
ASAP
Only through five (5) SIMS
contacts
SIMS
Support
Harmony
Communicate system-wide
issues, announcements, and
status to the network
•
Each ASAP will support users for providers where they are Lead
Agency.
•
Providers must contact their Lead Agency ONLY for technical issues
– Lead Agency will resolve or escalate
•
Contact the authorizing Agency about client issues.
8
Business Process Review Meetings
•
Between Kickoff & Go-live
–
Agency & Provider to review the current-state processes:
the specifics for each of the changes that result in a fax
•
•
•
•
•
–
New Consumer (Provider
has never before served).
Includes new service
schedule.
2.
One-time Only (temporary
boost in authorized services)
3.
Updated Service Schedule
(same units/week)
Provider has multiple business lines (certified/non-certified)
Recent merges
Unusual security configurations
4.
Updated Service Schedule
(unit change *or* change in
services)
5.
Suspension (ASAP notifies
Provider *or* Provider notifies
ASAP)
6.
Resume (after Suspension)
7.
Terminate consumer
2-3 weeks after go-live
–
–
•
Best as face-to-face meeting, but at ASAP discretion
Providers serving multiple agencies should review with each ASAP
Notify EOEA of multiple business lines, or other requirements
for a provider to view multiple provider records
•
•
•
•
1.
Reviewing your current practice will make post-go-live
parallel process faster & easier
•
•
–
Verbal/phone
Staff contacts
SAMS Data entry
Fax details
Issues in current process?
Seven (7) Business
Processes to replace
FAR (faxed authos)
Agency & Provider review parallel processing
Gauge readiness to shut down FAR (faxed authos)
Business Process Meetings between
Provider and All Agencies doing business
with…
9
User Request Forms (PD-URF)
•
•
•
•
Lead Agency Manages a Provider's
Users
•
Agency manages only one (1) URF form with
information for all of their providers,
containing all present and past users.
Each provider may have up to five (5) active
userids.
•
Request Type
•
•
•
•
•
•
User's First Name
User's Last Name
Four (4) Digit PIN
User's Month (MM) and Day (DD) of birth
User's E-mail Address
User's Office Telephone Number
New, Update, Terminate, Reactivate
Accuracy is key
»
»
•
Must match SAMS provider name
•
–
Provider:
•
Organization Name for User
–
How Many Accounts?
–
Fields on URF, for each user
Spelling of names
Email addresses
Timeliness is key
»
Don’t miss the boat
10
Project Communications
•
For providers, your main point-of-contact about Provider Direct will be your Lead
Agency.
–
–
User, training, application issues should be communicated to Lead Agency.
If there are technical issues that must be escalated, then the Lead Agency will contact SIMS
Support.
•
•
•
For providers, your main point-of-contact about specific Consumers
will be the consumer's Agency.
–
Questions about individual consumers should go to the Consumer's Agency (whoever created the
consumer's Service Plan.
•
•
Agencies: Make sure to keep your "five contacts" up-to-date.
SIMS Support may contact the Provider in certain situations to collect follow-up information.
Each Agency and each Provider should work out the appropriate Agency staff to respond to any particular item:
Case Manager or Supervisor, POS coordinator, Fiscal staff.
Email communications from EOEA to two (2) people at each organization
–
–
–
the Lead and a backup
EOEA will only communicate to providers occasionally
Agencies: Please make sure our records are complete
11
Project Communications
•
Massachusetts User Information
Portal
– http://providerdirect.800ageinfo.com
– Objective: this is the first reference
for users & user support, for any
application, project, or operational
materials.
– Searchable, with date and category
archives
– Categories
–
–
–
–
–
–
–
–
–
–
Announcements
Frequently Asked Questions
Group 1
How-to
Issue Reporting
Lead Agency Info
Manuals
Training
User Management
User Support
– Let us know if anything is missing or
needs to be updated.
12
Harmony University (on-line training)
•
All users will have 30
days of access
13
Billing Methodologies
•
EVI Replacement – Service Plans visible in HPD
– EVI Out Spreadsheet generated from Consumer Monthly Service Plan Report
• Providers run a HPD report on demand
• In Production currently
– EVI In Spreadsheet Replaced by:
• HPD File Upload
–
Current Status
• Service Delivery Confirmation
14
Provider Direct Demo
•
This is a Test environment based on production: all
data is scrubbed. No real consumer info.
•
This user's view is from a real provider in the
production environment, for example XYZ Home Care.
•
Security: A Provider Direct user can
–
See (but not edit) selected elements of the base consumer
record for consumers with XYZ Home Care service plans
(current or historical).
–
See (but not edit) service plans & service schedules where
Provider = XYZ Home Care
–
See (but not edit) service orders where Provider = XYZ Home
Care
–
See (but not edit) service suspensions where Provider = XYZ
Home Care
–
See, create and update service delivery records where
Provider = XYZ Home Care (however, service plans and service
orders must exist first).
•
We will implement service delivery functionality in the second
phase.
–
See, create, and edit rosters where Provider = XYZ Home Care
–
Reports:
•
•
PD User can run reports and save report definitions (criteria)
all data displaying on PD reports is subject to the same security
policy
Each organization
(Agency or Provider)
has a unique "view" of
the SAMS/ Provider
Direct database.
ASAP users (in Provider
Direct or SAMS) will
have a slightly different
view of the data than
the Provider users they
support.
Usually this means that the
Agency users sees more
consumers in the consumer list,
more changes in the Work
Queue, or service records
(plans, orders, deliveries) from
other providers.
15