> For the complete documentation index, see [llms.txt](https://cdpi.gitbook.io/dpi-for-healthcare/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cdpi.gitbook.io/dpi-for-healthcare/dpi-blocks-for-health/trusted-registries-in-healthcare/guiding-principles.md).

# Guiding Principles

## Guiding design principles and key technical characteristics for architecting registries: 

* **Minimalist:** Include only necessary identifying data, preferably fewer than 10 data fields per registry, that is easy for individuals and entities to keep updated, and tends not to change significantly over time.
* **Ease of Data Reuse:** Make data accessible in machine-readable format via open APIs to allow seamless reuse across many applications.
* **Privacy & Security by design:** Embed privacy and security features into digital IDs and registries, adopting encryption, strong cybersecurity measures, and digital signatures for authentication of source of data.
* **Single source of truth:** The registries should ensure that they are the single source of truth for the entity in question that health systems and organisations can leverage for data exchange and service delivery
* **Self-Maintainable:** 

a. Mechanisms to enable auto-audit ensuring deduplication, error flagging, or completeness flagging can be configured at agreed intervals as defined by the system owner.

b. To ensure data is always updated, interval-based updation alerts to citizens, organisations, government departments, and accountable entities can be enabled via defined updation and verification processes.

c. Automated updates to registries can also be ensured by crawling relevant databases or individual systems with consent and authentication. 

* **Ease of Data Capture along with legacy data migration:** Ease of Data Capture along with legacy data migration: Should enable features like bulk uploads or API-based integration to pull/push data from existing legacy systems and digital databases. For a new registration, multimodal options should be made available for inclusivity such as mobile app, portal, or in-person enrolment.
* **Scalability:** Architect the infrastructure to handle national scale volumes of onboarding and updates while maintaining high performance.
* **Trustworthiness and Integrity of data:** Claim and attestation workflows should be maintained to ensure trustworthy data.
* **Auditable:** The system should ensure mechanisms to maintain comprehensive logs of data edits, updates, and deletions. These logs must include a complete history documenting what was changed, who made the changes, and when each event occurred.