General availability of the new LAMP Platform

We’ve received a lot of support from everyone in our community and the LAMP Consortium around progress on the mindLAMP 2 project, especially including the ability to self-deploy the new LAMP Platform architecture. We’re working hard to address the feedback that we’ve received and make the process as simple as possible for others to deploy the LAMP Platform themselves no matter where or how.

At the end of July, we completed the data and backend migration for the LAMP Platform to the latest server architecture, incuding our new database system and support for the now-deprecated mindLAMP 1 apps. Since then, the new server architecture has proven to be highly robust and efficient, supporting a number of new features coming soon only to mindLAMP 2, such as push notifications and just-in-time adaptive interventions scheduling. Today, we’d like to announce the general availability of parts of this new backend release for self-deployment.

If you’re interested in deploying the LAMP Platform today, please visit our improved documentation. As part of the general availability release, we’d like to share the following considerations you and your organization may need to understand regarding the LAMP Platform:

  1. If you or your organization has already deployed an instance of the LAMP Platform backend that was previously using Microsoft SQL Server, you will need to contact our team for assistance and data migration support.
    • This process cannot be automated and will need to be carefully monitored to ensure no data loss occurs. Our team will guide you or your organization through the process and as needed, perform data verification and integrity checks.
    • This process may take several hours, incurring system downtime for the end-users of your instance of the LAMP Platform.
  2. If you or your organization like to deploy only the backend portion of the LAMP Platform on-premise, but wish to use our team’s mobile apps for digital phenotyping, you will need to follow our new consortium-wide protocol for requesting a digital certificate.
    • This process is outlined in our improved documentation along with the other requirements for maintaing consortium membership; please reach out to us directly if you have any questions or comments regarding this process.
    • You or your organization will be required to share an IRB or a detailed clinical usage protocol with our team, and once received, we will provide a secure digital certificate allowing your specific backend instance to communicate with our mindLAMP mobile and wearable apps.
      • Should misuse be detected by our automated systems, or Apple and Google, your digital certificate will be revoked and you will be notified.
    • This requirement is due to Apple and Google strictly regulating research and medical uses of apps and contributes to the unique approval process for mindLAMP 2.
      • Should unauthorized usage be detected, the mindLAMP mobile and wearable apps will be removed from the commercial marketplaces which will of course impact every user in the world.
    • An organization not willing to comply will need to download, modify, recompile, and resubmit the apps under different branding to both Apple and Google independently.
  3. An early preview of push notification support is available today, requiring only a simple configuration change to enable.
    • Please set the SCHEDULER=on environment variable in your Docker Stack or local environment to enable this early preview.
    • Please set the PUSH_GATEWAY_APIKEY environment variable to the digital certificate provided to your organization by our team, or our mobile/wearable app gateway will reject your device notification requests.

In making this general availability release possible, our team would like to thank @Synthia_Guimond and her team at University of Ottowa in Canada, @ninaes and her team at Monash University in Australia, @Andrea_Colajacomo and his team at Alecsandria Digital Agency in Italy, and @kkadapa and his team at Northwell Health in New York. If you or your organization notice any bugs or unusual behavior, please let us know either through our new bug tracker or by contacting us directly.

We hope to share more exciting news about mindLAMP 2 with you in the coming weeks!

Hi @avaidyam, does this mean that for new back-end deployments, there is no longer a need for MS SQL Server? If so, is CouchDB the only database required? I do not see a change in the docs regarding deployment and provisioning just yet.

Lastly, will there be a webinar tomorrow (Oct 1), and will you be covering the updates? Thank you!

Hi @nicholaide! Yes, that’s correct! The updated documentation should go live tomorrow, and we will be covering these changes during the webinar as well.

I am a bit confused about these push keys. Are they necessary for your app to connect to our server we deployed? Or is that just something extra and the google store app can send data to our server?

We were unable to log in from mobile device, and we thought it was due to http connection (maybe bad set up of traefik).

Hi @sakac! The push API key is required for the backend to send push notifications for activity schedules, etc. to the mobile/wearable apps.

We were unable to log in from mobile device, and we thought it was due to http connection (maybe bad set up of traefik).

Yes – this is usually the case (i.e. Let’s Encrypt configuration), as you are required to use HTTPS when connecting to your backend externally.

Thank you very much. Hopefully we will be able to do this on our own.

@rbilden can assist your team with acquiring an API Key! (You will not be able to use our team’s provided native apps otherwise, following Apple/Google guidelines.)

Hi @sakac,

In order to give you an API key, we need you to fill out the two forms below and submit your IRB to us—this is in line with Apple/Google guidelines. More information can be here

Form 1:

Form 2:

thank you very much

1 Like