The Data Vault Handbook - Concepts and Applications

In this case, the two Hubs consolidate the Patient and Doctor business keys respectively, while a Link establishes the relationships between them. Addi- tionally, a Satellite captures the history of the patient’s details. 3.2. DERIVED ENTITIES In addition to the Hubs, Links and Satellites the Data Vault model includes a set of derived entities designed to address specific data and business chal- lenges. These entities stem from the core entities but undergo adaptations to suit various needs, such as handling transactional data, managing multiple active records, or incorporating reference data. In this section, we will explore a selection of the most relevant derived en- tities, including Non-Historized Links and Satellites, Multi-Active Satellites, and Reference data tables. It’s important to note that the list of derived en- tities extends beyond those discussed here, and we will provide external re- sources for further exploration if desired. Our focus will be on explaining the structures and use cases of these entities, complemented by practical examples that demonstrate their real-world applications. 3.2.1. NON-HISTORIZED LINKS AND SATELLITES

In certain scenarios, Data Vault Links are used to store transactional data, such as sensor readings or financial transactions, where the data should re-