QuestionQ1

Data Architecture

A healthcare organization uses a Relational Database Management System (RDBMS) to store information about patients’ medical histories. The data is arranged in two primary tables: "Patients," which contains information about individual patients, and "Visits," which contains information about every patient visit. Each row in the "Visits" table links to a row in the "Patients" table, creating a one-to-many relationship. The organization wants to migrate this data to Adobe Real-Time CDP to provide patients with personalized experiences based on their medical histories and requires the one-to-many relationship between patients and visits to be retained.

Which data-modeling approach should the organization use when translating this RDBMS data model to Real-Time CDP’s NoSQL data model?

Explanation

Patient attributes should be modeled in an XDM individual/profile schema, while individual visits should be modeled as records in a separate time-series schema. A shared patient identity associates many visit records with one patient profile, preserving the required one-to-many relationship without using relational foreign keys.

Community Discussion

No comments yet. Be the first to start the discussion!