> For the complete documentation index, see [llms.txt](https://icure.gitbook.io/icure/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://icure.gitbook.io/icure/icure-data-stack/icure-data-model.md). # iCure Data Model Data within the iCure ecosystem are managed according to the iCure Data Model, a physical data model optimized for data integrity, anonymization and encryption, that is compatible with higher level Medical Data conceptual Data Models such as Open EHR and FHIR. At the same time, assumptions are being made for common features of Logical Models used in Healthcare, so that the physical model is impervious to conflicts at implementation. The iCure Data Model has been designed to facilitate the systematic collection of organized data from a wide range of health provider points. It is an HL7 based model that has been designed to achieve optimal performance of the Medical Data Storage. It organizes data, so that identifiable data can be encrypted and other data can remain unencrypted for Business Intelligence purposes. Encryption is maintained throughout the whole Data Cycle on the designated data and also maintained, when data is being exchanged through connectors. It is in its core compatible with the SNOMED CT and ICPC-2 Terminologies as well as the ICD-10, LOINC and ATC classifications. It also enables by default partial encryption for allowing the application of Business Intelligence analytics while maintaining the necessary privacy. It is optimized for efficient use in a distributed environment along several user groups. ### Data Anonymization The iCure Data Model is optimized for implementing and handling \\ --- # 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://icure.gitbook.io/icure/icure-data-stack/icure-data-model.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.