FullCount has several different integrations with 3rd party software vendors. These integrations help customers use FullCount along with their other software products for their billing and customer maintenance needs.

Billing File

FullCount can produce a billing file that can be imported into a 3^rd party billing system. This file is generated during the month end close for all transactions that were billed to a customer. This file can be downloaded from the back office and then imported into the 3^rd party billing system. To see a list of current billing file options, reference https://kb.fullcount.net/documentation/billing-file-formats. If the billing system is not listed on the knowledge base article, work with the community to determine the file format required and the summarization level desired. Once the requirements have been gathered, create a task and assign to the Development team. If it would be helpful to have the development team involved in discussions with the community and/or 3^rd party billing software, please contact them to schedule a time for all parties to meet. This is included with a community's monthly subscription.

Payroll File

FullCount can produce a payroll file that can be imported into a 3^rd party payroll system. This file is generated via the Reports tab in the back office. This file can be saved from the reports page and then imported into the 3^rd party payroll system. To see a list of current payroll file options, reference https://kb.fullcount.net/documentation/payroll-file-formats . If the payroll system is not listed on the knowledge base article, work with the community to determine the file format required. Once the requirements have been gathered, create a task and assign to the Development team. If it would be helpful to have the development team involved in discussions with the community and/or 3^rd party payroll software, please contact them to schedule a time for all parties to meet. This is included with a community's monthly subscription.

ADT

ADT Integrations allow a community to enter new customers into a 3^rd party system and have those records be automatically updated in FullCount. ADT is an abbreviation for admission, discharge, transfer. The integration will add, update, and end date customers within FullCount based on information received from a 3^rd party. This is not included with a customer's monthly subscription and requires an additional module on their contract.

Resident

MatrixCare 360 and MatrixCare LPC

For information received on HL7 integrations, reference https://kb.fullcount.net/tutorial/adt-hl7-integration-set.

HL7 files are generated on the MatrixCare side any time a resident is admitted, discharged, or been updated. These files are sent via web service to FullCount. FullCount then processes these files on their application server. These are processed every 5 minutes.

myUnity

For information received on HL7 integrations, reference https://kb.fullcount.net/tutorial/adt-hl7-integration-set.

HL7 files are generated on the myUnity side any time a resident is admitted, discharged, or been updated. These files are sent via web service to FullCount. FullCount then processes these files on their application server (central or remote). These are processed every 5 minutes.

Move-N

Move-N generates a CSV file containing all resident information. This is created once a day and is processed every day by FullCount at 6:30 AM. All resident information is updated for admissions, updates, and discharges.

Point Click Care

Point Click Care generates an event any time a resident is admitted, discharged, or been updated. This event is received by FullCount. Upon receiving the event, FullCount contacts Point Click Care to gather the resident information. The resident information is stored and then processed by FullCount on their application server (central or remote). These are processed every 5 minutes.

Vitals

Vitals generates a queue of HL7 messages. These are created any time a resident is admitted, discharged, or has been updated. FullCount checks the queue every 5 minutes via a GET request. Upon successful processing of the message, FullCount sends a message to Vitals to acknowledge the message was received.

Yardi

Yardi generates a CSV file containing all resident information. This is created once a day and is processed every day by FullCount at 6:30 AM. All resident information is updated for admissions, updates, and discharges.

Employee

SFTP Integration

This is the current employee integration utilized. Information from a payroll system is formatted in a csv file and then placed on an SFTP server. FullCount processes the file once per day. To see required formatting for the csv file, reference https://kb.fullcount.net/documentation/employee-integration-interface.

Resident and Employee

Sensys (Belmont Village)

This is a custom integration implementation. This integration uses json objects to maintain residents and employees in FullCount. This information is processed by FullCount once an hour.

Tab-Delimited (Providence Life)

This is a custom integration implementation. This integration uses a tab delimited file to maintain residents and employees in FullCount. This file is placed on an ftp server and processed by FullCount once a day.