Two Integration Types - Lite and Full

How Greenlight fits into your workflows - the big picture

Greenlight offers two approaches to integration.

  1. A Lite Integration, which requires less development on your side, and Greenlight provides more automation and interacts more with your patients, to help them be successful
  2. A Full Integration, where you embed a Greenlight application in your patient facing workflow, and you provide all patient engagement, messaging, and follow up
  3. If your organization requires aspects of both of these integration approaches, talk with our Customer Success team about a possible hybrid.

While the technical API Reference simply describes the different API resources available for EITHER integration type, this "Guide" provides more insight into how those API resources would be used, depending on whether you choose the Lite Integration, or the Full Integration. Those details are found in the "WORKFLOWS" section of this guide.

The big difference between the two approaches is how you deliver the patient to the Greenlight app (Greenlight Record Finder). If you are redirecting within your own patient facing application, look at the Full Integration. If you need Greenlight to "invite" the patient into the Greenlight experience with a text or email, look at the Lite Integration.

Lite Integration

Here is a brief description of a typical Lite Integration.

  1. Your system calls the Greenlight API to send patient and record request data
  2. Greenlight sends messages to the patient, to engage them in the Greenlight experience
  3. The patient uses a Greenlight application to provide consent and access to records
  4. The Greenlight platform retrieves records
  5. Your system monitors progress using the Changes API, which shows status changes and documents/data to retrieve
  6. Your system gets documents or FHIR data from Greenlight
  7. If there are obstacles encountered in the process (such as patient errors, or the access requires additional steps) Greenlight sends messages to the patient, and the patient returns to the Greenlight app to resolve them

Full Integration

Here is a brief description of a typical Full Integration.

  1. Your system calls the Greenlight API to send patient and record request data
  2. Your patient facing application redirects to a Greenlight application for the consent and access steps
    1. (The Greenlight application is branded with your logo and key colors)
  3. The patient uses the Greenlight application to provide consent and access to records
  4. The Greenlight app returns control to your app
  5. Your system calls the Greenlight API to get updates that happened within the Greenlight app
  6. Your application provides any next steps to the patient
  7. The Greenlight platform retrieves records
  8. Your system monitors progress using the Changes API, which shows status changes and documents/data to retrieve
  9. Your system gets documents or FHIR data from Greenlight
  10. If there are any obstacles encountered in the process (such as patient errors, or the access requires additional steps) your system would see them in the Changes data from Greenlight
  11. Your system would message the patient to return to your app to make any corrections
  12. If the patient needed to provide access again, or change credentials, you would redirect again to the Greenlight app

The Workflows section of this guide is divided into two, so you can follow either the Lite path or the Full path.