ADT Integration Implementation Plan

ADT Integration Implementation Plan

Project Planning

  1. Support/Implementers is told by a community that they want integration. This may be as part of a new community implementation or existing customer.
  2. Support/Implementer works with sales to get appropriate paperwork signed at FullCount.
  3. Support/Implementer/Sales works with community to get appropriate paperwork signed at 3rd party.
    1. Need to add specific directions based on 3rd party vendor.
  4. Support/Implementer creates ADT integration Redmine task and assigns to Development.
  5. Support/Implementer provides documentation to community about integration process/FAQs.

    1. MatrixCare 360 or MatrixCare LPC - J:\FullCount\Documentation\Vendors\ADT Integration\MatrixCare\MatrixCare ADT (360 and LPC)\MatrixCare ADT Integration FAQs.docx
    2. myUnity – J:\FullCount\Documentation\Vendors\ADT Integration\myUnity\myUnity FAQs.docx
    3. PointClickCare – J:\FullCount\Documentation\Vendors\ADT Integration\PointClickCare\PointClickCare FAQs.docx
    4. Vitals - J:\FullCount\Documentation\Vendors\ADT Integration\Vitals\Vitals FAQs.docx
    5. Yardi - J:\FullCount\Documentation\Vendors\ADT Integration\Yardi\Yardi ADT Integration FAQs.docx
  6. Support/Implementer fills out integration documentation based on the type of integration.

    1. MatrixCare 360 - J:\FullCount\Documentation\Vendors\ADT Integration\MatrixCare\MatrixCare ADT (360 and LPC)\MatrixCare 360\MatrixCare 360 ADT Integration Setup.docx
    2. MatrixCare LPC - J:\FullCount\Documentation\Vendors\ADT Integration\MatrixCare\MatrixCare ADT (360 and LPC)\MatrixCare LPC\MatrixCare LPC ADT Integration Setup.docx
    3. myUnity – J:\FullCount\Documentation\Vendors\ADT Integration\myUnity\myUnity Integration.docx
    4. PointClickCare – J:\FullCount\Documentation\Vendors\ADT Integration\PointClickCare\PointClickCare Integration.docx
    5. Vitals - J:\FullCount\Documentation\Vendors\ADT Integration\Vitals\Vitals Integration.docx
    6. Yardi - J:\FullCount\Documentation\Vendors\ADT Integration\Yardi\Yardi ADT Integration.docx
  7. Determine Go-Live Expectations

    1. MatrixCare 360 or MatrixCare LPC
      1. Support/Implementer to provide organization and facility ids to Development.
      2. Support/Implementer to determine go-live date with community and development feedback/availability.
    2. myUnity/Netsmart

      1. Development and Support/Implementer attend joint meeting with Netsmart and community. Go-live date will be discussed during this meeting.
      2. Development to coordinate with Netsmart to get Resident Directory/Mapping details.
    3. PointClickCare

      1. Support/Implementer to provide organization and facility ids to Development.
      2. Support/Implementer to determine go-live date with community and development feedback/availability.
    4. Vitals

      1. Support/Implementer to provide organization and facility ids to Development.
      2. Support/Implementer to determine go-live date with community and development feedback/availability.
    5. Yardi

      1. Support/Implementer to provide organization id to Development.
      2. Support/Implementer to determine go-live date with community and development feedback/availability.

Data Work

  1. Development will take information provided by Support/Implementer and update back office fields.
  2. Development will take appropriate customer list from 3rd party and map to existing customers or add new as appropriate.

    1. If a new community and MatrixCare 360, the initial load process can be used to add new residents
    2. If a new community and MatrixCare LPC, MatrixCare can run A08 messages for each resident
    3. If a new community and PCC, the synchronization process can be used to add new residents.
    4. If a new community and Vitals/Netsmart, Vitals/Netsmart can queue up records for all residents that can be used to add new residents.
    5. If a new community and Yardi, the overnight process can be run to populate residents.
    1. Development will add rows to the integration databases where appropriate (PointClickCare, myUnity, and MatrixCare).

Go Live

  1. Development will turn on the interface and determine if there are any outstanding ADT records (sitting in queue) to be processed.
  2. At Go-Live, Support/Implementer will let community know that the interface is live and provide any necessary training.
    1. KB Article with training points - https://kb.fullcount.net/documentation/adt-training-points
  3. Support/Implementer will let FullCount accounting department know that the interface is live to begin billing.

 


    • Related Articles

    • ADT - HL7 Integration Set-Up

      Submitted by junges on Tue, 09/09/2014 - 11:37 Several 3rd party billing systems have developed a queueing system that allows FullCount to access HL7 messages from their system. This allows customers who utilize these billing systems to enter ...

    • PCC Integration Set-up

      PointClickCare (PCC) has developed a system that allows FullCount to access patient information from their system. This allows customers who utilize PCC to enter residents in their interface and have them be automatically entered into FullCount. ...

    • Move-N Integration Set-Up

      Move-N Integration Set-up Move-N has developed a stored procedure that allows customers to export data to a CSV file that can be placed on an SFTP server maintained by the community. FullCount can then access this CSV file on the SFTP server for ...

    • Plan Information - Project Manager Settings

      Plan Information - Project Manager Settings General Information Display Plan As – Use this field to display a plan with a name different than the type of plan it is. For example, community has a plan that is a declining dollar plan from FullCount’s ...

    • ADT and Employee Integration Error Emails

      ADT and Employee Integration Error Emails This article contains commons ADT and Employee Integration error emails that are received by the development team and steps to resolve the issues described. ADT Emails Subject: <Community Name> - unable to ...