# Simple Docs ## Simple Docs - [What is Simple?](https://docs.simple.org/readme.md): Simple is the fast, free app for clinicians to manage their patients with high blood pressure and diabetes. More details at Simple.org - [Background](https://docs.simple.org/readme/background.md): Why did we develop Simple? How can a data system benefit a hypertension control program? - [Simple app features](https://docs.simple.org/readme/simple-app-features.md): The main features of the Simple Android app, created for healthcare workers to record patient visits. The app is optimized to record a very high volume of patient follow-up visits. - [Dashboard features](https://docs.simple.org/readme/dashboard-features.md): The main features of the Simple web-based Dashboard, which is used by health officials, surveillance officers, and system administrators - [Who uses Simple?](https://docs.simple.org/readme/who-uses-simple.md): This is a deceptively difficult question: Simple is used by thousands of healthcare workers and health systems managers. - [Clinic workflows](https://docs.simple.org/readme/clinic-workflows.md): Clinics can be very different, but we will describe some typical workflows for data entry into the Simple Android app for clinicians. - [Try it out](https://docs.simple.org/how-to-test-the-simple-app.md): We welcome anyone to kick the tires of Simple. If you are a health systems manager and would like a hands-on demo, please get in contact with us. - [Training materials](https://docs.simple.org/training-materials.md): Training presentations and videos for trainers and Simple users - [Contact us](https://docs.simple.org/contact/contact.md): Please feel free to reach out if you would like to contribute to Simple or if you're interested in using Simple in your area. - [Customer support](https://docs.simple.org/contact/support.md): We appreciate your help in making Simple better for everyone! - [Bug priority definitions](https://docs.simple.org/contact/support/bug-priority-definitions.md): We mark priorities using these labels on Github and Clubhouse. - [What we report](https://docs.simple.org/reports/what-we-report.md): This document lists and defines the key indicators program managers use to track the hypertension and diabetes control programs with Simple. - [Building custom reports](https://docs.simple.org/reports/building-custom-reports.md): Details on how to creating your own reports using Metabase, and the reporting tables. - [Data dictionary & API](https://docs.simple.org/engineering/data-dictionary.md) - [Android](https://docs.simple.org/engineering/android.md) - [Conventions](https://docs.simple.org/engineering/android/conventions.md): We try to stick to these conventions as much as possible. Think of them as strong guidelines! - [Deploying to Play Store](https://docs.simple.org/engineering/android/deploying-to-play-store.md): The variants of the app have slightly different ways they get deployed to the Store. - [Bitrise Workflow Quirks](https://docs.simple.org/engineering/android/bitrise-workflow-quirks.md) - [Headers sent from the app](https://docs.simple.org/engineering/android/headers-sent-from-the-app.md): This lists out all the headers which the app sends to the Simple server in all the requests - [Backend](https://docs.simple.org/engineering/backend.md) - [Audit logs](https://docs.simple.org/engineering/backend/audit-logs.md): How to audit access to patient data in the logs - [Major flows](https://docs.simple.org/engineering/backend/major-flows.md) - [Localization](https://docs.simple.org/engineering/localization.md): How we localize the Simple apps (mobile and backend) and other projects. - [Android](https://docs.simple.org/engineering/localization/android.md): Specific information related to localizing the Simple Android app - [Server](https://docs.simple.org/engineering/localization/server.md): Specific information related to localizing the Rails app - [Adding/Editing translations for a project](https://docs.simple.org/engineering/localization/adding-editing-translations-for-a-project.md) - [Reviewing a translation](https://docs.simple.org/engineering/localization/reviewing-a-translation.md) - [Technical Hiring Process](https://docs.simple.org/engineering/technical-hiring-process.md) - [Design](https://docs.simple.org/design-1/design.md): There are several full-time designers and UX researchers on the Simple project. Please join us on Slack if you would like to contribute. - [User testing](https://docs.simple.org/design-1/user-studies.md) - [Key moments in the user journey](https://docs.simple.org/design-1/user-studies/users-key-moments.md): This document is an illustrated sequence that depicts the end-to-end experience of Simple’s primary users: the nurses. - [User tests](https://docs.simple.org/design-1/user-studies/user-tests.md) - [Conducting user tests](https://docs.simple.org/design-1/user-studies/conducting-user-tests.md) - [Code of conduct](https://docs.simple.org/onboarding/code-of-conduct.md): We take our code of conduct seriously. Please read this as a guide for being a positive contributor to this open source project. - [Acronyms](https://docs.simple.org/onboarding/acronyms.md): Definitions for common acronyms you'll run into on the project - [Glossary](https://docs.simple.org/onboarding/glossary.md): Common terms you'll run into on the project. - [Recommended reading](https://docs.simple.org/onboarding/recommended-reading-material.md): Books and articles for people who are new to the Simple project and want to get up to speed on public health and data systems. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on a page URL with the `ask` query parameter: ``` GET https://docs.simple.org/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.