πŸ“‘

Project Scope

Introduction

The goals of an over-arching mental health platform include health equity, open data, and open science. The goal of the LAMP Platform is to derive unique insights from the data of individuals with lived experiences, for the benefit of everyone around the world (global mental health). It achieves this by beginning with a set of clinical goals and needs and translating them into engineering principles backing the robust platform. Successful innovations in clinical systems and health data are characterized by improvements in two major domains elucidated from common goals and pain points in prior technology: (1) data and analytics, and (2) accessible technology.

Domain 1: Representative, structured, and secure data

  • Representative data that accurately captures lived experiences in an algorithm-agnostic manner.
  • Structured data that accelerates analysis and produces meaningful outcomes to introduce new vocabulary of digital mental health that allows individuals and systems to communicate effectively.
  • Securely shareable data between devices, hospitals, regions, and countries that expands collaborative possibilities and unique clinical insight via rapid and secure transport.
  • Analytics workloads that support population-wide and real-time inferences or actions, such as just-in-time interventions and delivery of care.

Domain 2: Straightforward and accessible technology

  • Contextual usability that translates functions between different user groups, such as patients, clinicians, administrators, researchers, participants, and more.
  • Mobile device support so platforms can operate virtually anywhere and under anyone, from microcomputers to cloud data centers.
  • Open source systems and tools developed in a collaborative environment and are freely available to all.
  • Efficiency and reliability exercised in all functions of the platform to avoid wasted resources, downtime and operational overheads.

Project Scope

As we aim to build a robust platform able to serve the needs of many individuals, we identify the following as key stakeholders whose perspectives and requirements are specifically considered within this document. Furthermore, we recognize a core set of goals that guide the process of design and development of this platform for use in research and in real world clinical settings.

Stakeholders

  • Patients: individuals seeking increased quality of care under the guidance of a Clinician in a clinical healthcare setting and through the use of the platform.
  • Participants: individuals seeking to advance scientific research in partnership with Researchers through enrollment in studies augmented by the of the platform.
  • Clinicians: individuals seeking to directly provide care for Patients augmented by the use of the platform.
  • Researchers: individuals seeking to advance scientific research through the use of the platform, in partnership with Participants.
  • Data Scientists: individuals seeking to advance scientific research by architecting solutions and analyzing data collected by the platform, in partnership with Patients, Participants, Clinicians, or Researchers.
  • Developers: individuals seeking to design and develop tools and applications for the platform to further the goals and meet the needs of Patients, Participants, Clinicians, Researchers, and Data Scientists.

Design Objectives

  • Global Impact: we aim to design the platform for the Stakeholders of a global age, who come from different cultures, locations, and contexts. Both researchers and clinicians around the world should be able to understand, use, apply, and conduct research alongside the Platform. Patients and participants should be able to access and benefit from the Platform regardless of their environment.
  • Open Source: we aim to develop a welcoming community around the platform that encourages interdisciplinary collaboration on a global scale, and offers the platform free of charge to those seeking to use it.
  • Simplicity: we aim to design a platform whose components and total aggregate are inherently simple to understand, use, and apply to various engineering, research, or clinical contexts without excessive effort or technical support.
  • Efficiency: we aim to design a platform whose facilities are built with efficiency and reliability in mind, such that low maintenance or computing overheads are incurred.
  • Ethical Design: we aim to design a platform with ethically sound principles surrounding the use and collection of data, and allowing those who contribute data to maintain ownership of such data.
  • Security: we aim to design systems using modern encryption methods that secure and maintain the integrity of any and all data both during transmission from one point to another and its storage, requiring consent and permission before one party is allowed to access another party’s data, irrespective of the physical ownership of the hardware upon which the platform is operated.
  • Privacy: we aim to design systems whose data storage inherently avoids and discourages personally identifiable information, though able to empower the originator of any piece of data with the right of ownership and consent, with HIPAA-compliant permanent non-recoverable deletion of data upon request.

Engineering Principles

Clinical needs and goals are first surveyed and understood, before they are translated into an engineering context for the features or technologies that need to be defined. Three core areas of needs and goals are modeled: (1) Data, (2) Network, and (3) Clinical, for the definition of core features and engineering strategies, as indicated in the figure below.

image
🌟

Terminologies in this document, such as the names of components, tools, frameworks, or otherwise, when initially introduced in text will be bolded and referred to as such in all later text.

🌟

We aim to both describe an abstract implementation-agnostic platform suitable for adaptation to any development requirement as well as to provide a reference implementation abiding by the guidelines set forth in this document. As you read this documentation, you will see engineering suggestions or limitations presented in blocks such as this one highlighting current limitations and possible future development venues that underlie the design and architecture of the LAMP platform.

🌟

We aim to provide the same features and tools to clinicians, researchers, patients, and participants regardless of environment. Whether they have constant high-speed internet connectivity, or sparse and inconsistent internet connectivity, the LAMP platform will look, feel, and operate the same way, abstracting, to its best ability, the inconsistencies one may face in its day-to-day use. As you read this documentation, you'll see clinical insight presented in blocks such as this one highlighting the real-world cases that inspire the design and architecture of the LAMP platform.

Was there something we didn't cover, or need more help? Let us know by making a post in the LAMP Community, or contact us directly. Thank you for your contribution! 🌟 Page last updated on February 10th, 2020.