> For the complete documentation index, see [llms.txt](https://connectify.gitbook.io/iot-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://connectify.gitbook.io/iot-protocol/use-cases/healthcare.md). # Healthcare In the healthcare sector, CONNECTIFY facilitates the deployment of new patient-centric digital services through the seamless collection of medical data. For example, our solution enables real-time monitoring of patients at home or on the move, using heterogeneous connected medical devices (blood pressure monitors, oximeters, pacemakers, etc.). Critical data can trigger automatic alerts transmitted to nursing staff, enabling rapid intervention in the event of an emergency. All patient medical data is time-stamped and tracked on blockchain, creating an unforgeable medical diary shared between practitioners. Patients retain total control over access to their data. They decide who can access them, and for what purposes. This guarantees end-to-end security for healthcare data, in line with the sector's ethical requirements. CONNECTIFY removes the technological obstacles to the deployment of e-health, to the benefit of patients and practitioners alike. --- # 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 that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://connectify.gitbook.io/iot-protocol/use-cases/healthcare.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.