Suncoast Analytics Client Login 

• Home • Client Server EHR • Cloud EHR • ftp Other •
This computer system is for authorized use only.

Users have no explicit or implicit expectation of privacy.

Any or all uses of this system and all data on this system may be intercepted, monitored, recorded, copied, audited, inspected, and disclosed to authorized sites and law enforcement personnel, as well as authorized officials of other agencies. By using this system, the user consent to such disclosure at the discretion of authorized site personnel. Unauthorized or improper use of this system may result in administrative disciplinary action, civil and criminal penalties. By continuing to use this system you indicate your awareness of and consent to these terms and conditions of use.

This web server uses HIPAA and bank level encryption technologies when transferring, receiving, and storing quality submission information.

STOP IMMEDIATELY if you do not agree to the conditions stated in this warning.
==================================================

Section A: First time? Instructions for Client Login

1. Bookmark this page.  This is the web page that will document any process changes.
    Also... If you have any problems logging onto Suncoast Analytics, LLC ftp site,
    refer to this page (www.SuncoastAnalyticsLLC2.com/index.htm) for FAQ.

2. Use ftp client FILEZILLA to access Suncoast Analytics, LLC ftp site

    V
erify that FILEZILLA app is installed on your computer.

   Tutorial at:
            http://wiki.filezilla-project.org/FileZilla_Client_Tutorial_(en)
    Info at:
            
https://filezilla-project.org/support.php?type=client&mode=help&version=3.8.0

                 You will receive a FILEZILLA xml  config file via email. 
                 Import this configuration file into your FTP client & name it 'Suncoast Analytics, LLC site'
                 Review the configuration parameters;
                        please take note of any setting (port#, passive/active...) that could interact with your site's firewall
                 Use FILEZILLA to Logon to 'Suncoast Analytics, LLC site'

3. After successful logon , Be sure to refresh directory listing of Suncoast Analytics, LLC ftp site:
        FILEZILLA: -> right panel: Locate 2 windows below label: "REMOTE SITE"
        Right click lower window.  Menu should appear.  Click on "REFRESH"

4. Confirm that you have reached correct FTP site.
    FILEZILLA: Right click on to read the file 'ftpsignon_verify.txt' located on the root directory of the Suncoast Analytics, LLC ftp site.
          The header of this file should contain the following text:

==============================================
Suncoast Analytics, LLC ftp site: scclient site confirmation file
Last update: xx/xx/xxxx
Suncoast Analytics, LLC ftp portal reference documentation:
....

This file serves as verification that you have reached our ftp site.

====================
5) After you complete the above steps, please inform us of your success with the following

a) Notify us of your success via email: send a confirmation message to
              filesentinel@suncoastAnalyticsLLC.com
                   re: Successful ftp login!

Section B: Successive login instructions

  1. Use ftp client filezilla to logon to Suncoast Analytics, LLC ftp site
     
  2. There is a file in the root directory of our FTP site:
    'Suncoast Analytics, LLC.cmsgateways ftp site:txt' is present to enable you to manually confirm you have reached the Suncoast Analytics, LLC ftp site.
    Please verify the presence of  'ftpsignon_verify.txt' before uploading any files..
     
  3. Use bookmark from Section 1 step 1 to review any updates.  i.e. Please review the date at top of web page www.Suncoast Analytics, LLC.org/ftpuploadprotocol1.htm for any updates for operational protocol/maintenance.

======================================

Section C:  File UPLOAD FAQ

Please follow process for file upload:

  1. Procedures: BEFORE file upload:
    1. All files containing PHI must be zipped WITH PASSWORD
                Don't forget to communicate password (See step 3 & 4 below)
    2. ZIP filename convention:    ClientAcctnumber_Datatype _Date_Version (separated by underscore)
          ClientAcctnumber - Embedded in ftp USERID (text after 'sc_client_  ')
          Date: yearmonthday (20180130)
          Version: Use if multiple uploads on same date
          Datatype:   To help us recognize contents of the files you upload, please use these identifiers: 
                
                      CMS(filetype) - CMS Sourced files (CMSCCLF, CMSPatientList ... )
                      CCDA - Structured data exported from EHR
                      Immunization - Data exported from
      Immunization registries (i.e. FL SHOTS, etc)
                      MPI - Master patient Index (Upload to ETC directory)
                      LIS - Lab information data
                        (Please upload TXT note to LIS directory to specify  format )(Format: HL7 2.x, 3.0 or other)
                      PM - Data exported from Practice Management
                         (Please upload TXT note to PM directory to specify  format) (837 other.. )

                      ReportGenerators - Data from Crystal Reports or 3rd party
                      Progress_notes - EHR Unstructured data (Usually RTF documents)
                          (usually RTF files by encounter, extracted by referral template)
                      Scanned - Scanned documents (PDF format, >300dpi, color)

                      Other - Other administrative data (upload to ETC subdir)               
       
    3. Test (i.e. decompress) zip file w/ PW before uploading
       
  2. Upload file to site
    1. Verify your ftp client is accessing correct site: Verify presence of file 'ftpsignon_verify.txt'
    2. All data must be stored in directory denoted for originating system

                      CMS - CMS Sourced files (CCLF#, Patient List...)
                      EHR - Data exported from EHR ( Separate EHR subdirectories are used for multi-vendor sites)
                      Immunization - Data exported from
      Imm registries (i.e. FL SHOTS, etc)
                      LIS - Lab information data (Format: HL7 2.x, 3.0 or other ;  Please include note in LIS directory to specify )
                      PM - Data exported from Practice Management
                      ReportGenerators - Data from Crystal Reports or 3rd party
                      Progress_notes - EHR Unstructured data
                      Scanned - Scanned documents (PDF format, >300dpi, color)
      (EHR, PM, LIS, CMS, Immunization...)

                      ETC -  Catchall directory for admin data (Master patient Index  and other admin data)


           If the datatype you are uploading is not identified by a directory, upload to directory ETC and upload TXT file to document file details.
    3. Do not overwrite any files that have been processed.  Change version# to prevent file overwrite.
    4. Confirm that the file has properly uploaded (i.e. check date size)
    5. Test zip file w/supplied PW
       
  3. Please email filesentinel@suncoastAnalyticsllc2.com to notify us of any uploads . 
    Please document details about uploaded files: specify filenames, type of information, and directory used to upload info.
    For all other files other than CCLF files, include PW in email.
     
  4. CCLF files only: Text Client# and PW to phone: (207) 837-2196

    Thank you!


    =====================================

Copyright © CMS Gateways, LLC  All rights reserved

Universal Health System Metric Tools referenced on this site:
CMS Submission Toolkit, QRDA-CMS Submission Template, QPP Audit Tool, CCDA
Validator, Web Interface Aggregator,
    QCDR-HISP, QRDA Solutions, and
NwHIN/Connect/Direct Sleuth are trademarks of CMS Gateways, LLC

All other products mentioned are registered trademarks or trademarks of their respective companies.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Be sure to upload to correct directory for client: 
        Match client# to directory name (organized by clientaccount#)
        Subdirectories will be identified by organizational layers.
                For details, see online file under clientaccount# directory: orgchart.txt