PL 008.docx

DATA Exchange

EXPORTS from Phoenix These are methods where Phoenix will push reference data changes to the FMS Provider.

Data Objects The following Data Objects can be exported:

· Provider – Provider information including approved services

· Worker – Worker information including registered services

· Client (Participant or Consumer) – Client information including registered phone numbers, addresses, and locations

· FMS_Match – Participant, Employer, and Employee matches for consumer-directed care

Object: Provider The Provider data from Phoenix will contain the following:

6 character provider ID (alphanumeric) – FMS is EXG300, FMS Providers modeled as workers under EXG300

# - . ; special characters allowed.

Can be blank

Address/Location Information - Multiple Entries can be Stored, One of each type, Type is User defined

1=Home, 2=Work, 3=Billing, 4=Other

Alpha-numeric characters and may contain spaces or these special characters # - . ;

Alpha-numeric characters and may contain spaces or these special characters# - . ;

Alpha characters and may contain spaces or these special characters# - . ;

2 characters, alpha characters only, no special characters.

5 or 9 digit zip – 111112222

Phone Information- Collection (Multiple Entries can be Stored, ONE of each type allowed)

1 = Home, 2 = Work, 3 = Mobile, 4 = Fax, 5 = Other

Phone number format:

3335551212

Provider Services (collection)

Object: Client The Client data from Phoenix will contain the following:

Alpha characters, spaces allowed. # - . ; special characters allowed.

Alpha characters, spaces allowed. # - . ; special characters allowed.

Can be blank

Object: FMS_Match The FMS Match data from Phoenix will contain the following:

1 = Active 2 = Terminated

MatchVisit Successful

01 Verbal Resignation 02 Written Resignation 03 Suspended – Nursing Home 04 Suspended – Hospital 05 Suspended – Other 06 Fired 07 Terminated – Deceased 08 Terminated – Nursing Home

Termination Comment

IMPORTS to the FMS Vendor

Data Objects The following Data Objects can be Imported:

· Claim (Check-in and Checkout Information) – This information includes ANI phone number and registered phone numbers at the time of an IVRS call, or location and registered locations at the time of a Mobile app transaction.

· FMS_Employer – FMS registration Employer record and EIN from Public Partnerships (PPL).

· FMS_Document – FMS registration document status from Public Partnerships (PPL).

· ID_Card – ID card data associated with a Client ID card (Q-R Card) Object: Claim The claim data will be printed on the check stub and contain the following.

Blank if not in a Group

(If FMS, return the Rendering Provider ID from the Worker record.)

1900-01-01 00:00:00.000 indicates a time-based claim where a Check-out was performed without a Check-In.

Blank for check in only services 2099-12-31 00:00:00.000 indicates a time-based claim that has yet to be checked out.

4 – Mobile Set when claim created, doesn’t change

Object: FMS_Employer The FMS Employers data to Phoenix will contain the following:

6 character ID

3 = Terminated

1 = Home, 2 = Work, 3 = Mobile, 4 = Fax, 5 = Other

3335551212

1 = Home, 2 = Work, 3 = Billing, 4 = Other

Object: FMS_Document The FMS Documents data to Phoenix will contain the following:

R – Employer

* Explicit Good to Go indication from PPL.