Frequently Asked Questions

  1. Does Greenway Health have a sandbox or developer environment for FHIR Services?
    At this time, we do not have a sandbox environment available for developers. We understand the importance of having a dedicated testing environment with non-production data and are actively working on incorporating this feature into our platform. The sandbox environment is on our roadmap, but we do not have a specific ETA.

  2. Does the FHIR ecosystem support writeback?
    Currently, our FHIR ecosystem does not support the writeback feature. We understand that this functionality is important for many of our users. The development of the writeback feature is on our roadmap, but we do not have a specific ETA at this moment. We appreciate your patience and understanding as we work towards enhancing our system.

  3. What are the options for patients whose data is not in FHIR?

    • Contact the Practice: Ask the practice to create a dummy or empty visit, encounter, or an appointment on your chart. This will allow your historical data to load into FHIR.
    • Request a Digital Copy: If the practice is unwilling to append your charts, they should be able to provide a digital copy of your chart.
    • Use Records.GreenwayHealth.com: If the practice is unable or unwilling to do either of the above (e.g., your chart is deactivated due to inactivity), you can obtain your records via a data export process at records.greenwayhealth.com.
  4. What steps do Greenway Health clients need to take to use SMART on FHIR applications that are not Backend Services?
    To enable SMART on FHIR applications (excluding Backend Services), clients should refer to the official support articles for their specific product. These resources provide instructions and additional links to assist sites beginning their FHIR adoption journey.

    Note: You must be signed in to MyGreenway to access these articles.

    • Intergy: To view the support article for the Intergy product, click here
    • Prime Suite: To view the support article for the Prime Suite product, click here

    If you have questions on the provided help pages, please contact Greenway Support at 877-932-6301 or through MyGreenway access.

  5. We have registered our Backend Service SoF (Smart on FHIR) application, what are the next steps?
    To protect our sites’ data security and HIPAA requirements for backend services to access a site’s data, we require explicit permission from the site to grant this access. The steps below outline the process which will happen after we approve your backend service SoF application. Please note that this process may take up to a week or longer, depending on client response times.

    1. Obtaining Site Information:
      Once your app has been registered, Greenway Health will reach out to your organization to request the following details:
      • Intergy License/GID or Prime Suite ID
      • For Intergy: Which Practice ID(s)/Name(s)
      • Whether confidential data access is required (Y/N)
      • A site contact who can confirm the access
    2. Site Permission
      Greenway Health will connect with the provided site contact to obtain written permission for your application. If a site does not reply or declines permission, Greenway Health cannot proceed further.
      Please ensure that the practice contact you are coordinating with is informed about the upcoming request and understands that a response is required for us to proceed.
    3. Granting of Access
      Once permission is granted, Greenway Health will reach out to internal teams with the Information provided.
    4. Notification
      After completion, Greenway Health will notify both the site and the developer that access has been successfully provisioned.

      📘

      Note

      If your application is already registered but you need access to another client, developers can start the process by emailing to FHIR support with the same information listed in Step 1.

      The process is the same, whether it is initiated by Greenway Health after registration or by an application developer at a later stage.