Greenway Prime Suite

EHR systems differ in complexity due to various factors. Some databases require intricate methods to extract information, while others pose specific challenges related to database backup request timing and document extraction.

Explore the information below to learn more about the complexity ratings, turnaround times, and unique variables determined by Aesto's data extraction and conversion experts.

Complexity & Backup Delivery Timing Rating System

Leveraging Aesto's experience with over 120 different EHR vendors, our team has categorized the difficulty of extracting discrete clinical data and documents into three levels: Low, Average, and High Difficulty.

Take a look at our ratings for Greenway PrimeSuite below, along with the typical turnaround timing for receiving database backups from Greenway.

Discrete, Clinical Data

Complexity Rating

LOW

Document Conversion

Complexity Rating

HIGH

Typical Timing

Full SQL Backup Delivery

6 to 8 Weeks

    Greenway Prime Suite User Access

    Follow the steps below to grant user access to Greenway Prime Suite.

    1. Ensure remote access is granted for the dedicated machine on the care center’s network (using ZohoAssist, VM Horizon, VPN, etc.).
    2. Install the Greenway Prime Suite front-end client on the machine.
    3. Locate the Windows username and password to access the machine and/or VPN.
    4. Locate the EMR username and password to access Greenway Prime Suite.

    Direct Database Access

    If you have a server onsite or are hosted by a third-party IT company with direct access to the database, follow the steps below.

    For care centers pulling the database backups, the Aesto team needs the following information:

    • Request SQL Backups (.bak files) from the below Prime Suite databases:
        • PrimeRecord<site number>
        • PrimeRecordBin<site number>
        • PrimeRecordArcBin<site number>
    • Confirm the transfer method with your dedicated Aesto team. Aesto’s transfer preferences are listed below:
      1. S3 Browser
      2. Hard Drive
      3. Client-controlled transfer method (i.e., SFTP)

    If Aesto is pulling the database backup on your behalf, please provide the information below:

    • Server name or IP address of the SQL server where the database resides.
      • If the SQL server requires a special Windows admin user/password to access, the Aesto team will also need these credentials.

    Deliverable Factors if Self-Hosted

    • Sticky Notes: Only text will be migrated from sticky notes. The Aesto team has found images to have varying types and are typically not clinically relevant. Mapping these images is time consuming and leads to implementation delays.
    • Sketch Pad Information for the Aesto Team: 
      • Do you use sketch pads only for text?
      • Do you use sketch pads to draw on images?
        • Please inform your Aesto team where these image files are located.

    Hosted by Greenway

    If your database is hosted by Greenway, follow the steps below.

    Upon request, Greenway offers a data export option, and Greenway typically provides information about what this export entails. It is important that you confirm SQL backups are included in this export.

    Learn more about Greenway Prime Suite’s export options. We ask that you proceed with Option #1, the Preferred Data Export. 

    Document Migration Factors

    Converting healthcare documents from legacy EHR systems can be highly complex due to the dispersion of data across multiple systems in different formats and varying definitions.

    Patient data can be stored in various locations, including your EHR software, radiology information systems (RIS), pharmacy management systems, and other third-party applications. Some data formats are unique to specific EHR software, leading to compatibility issues during the migration.

    Aesto’s document conversion process is integral to the overall strategy for archiving data, ensuring all documents are easily accessible in Aesto’s DataCapture Platform.

    Learn more about Aesto’s solutions for overcoming technical challenges with document conversions.

    Document Migration Timeline  |  8 to 10 Weeks

    Transfer & Extract of Documents | 25 Days

    • Transfer Documents  |  10 Days
    • Run PrimeSuite Binary Extraction Tool PDF  |  5 Days
    • Run PrimeSuite Binary Extraction Tool XML  |  5 Days
    • Run PrimeSuite Binary Extraction Tool TIF  |  5 Days

    Loading of Documents | 2 Days

    • Create Document Archive List & Categories  |  1 Day
    • Load Binary Document to S3 Folder  |  1 Day

    Document Quality Assurance (QA) | 10 Days

    • Aesto Internal QA/ROI of Archived Documents (4 Days)  |  Resolve QA of Archived Documents (5 Days)
    • Client QA of Archived Documents (4 Days)  |  Resolve Client QA of Archived Documents (5 Days)

    Document Migration | 8 Days

    • Client Document Migration Training  |  1 Day
    • Partner Document Migration Process  |  5 Days
    • Upload Documents  |  1 Day
    • Migrate Documents  |  1 Day

    Document Mapping & Delivery | 4 Days

    • Data Mapping Training  |  1 Day
    • Complete Data Mapping  |  2 Days
    • Deliver Documents to athenahealth  |  1 Day