The add type of an item defines whether its data is stored for each record or for each contact. An item with an add type that stores data once per record holds a single set of values for the entity, which does not change from one contact to another. An item with an overtime add type is stored on each contact, so a different value can be recorded at each point in time and the history is retained. The first option states this. The number of components on a page is a Radar design concern. The refresh interval for patient data is determined by the extract schedule and not by item properties. The user roles assigned to a component are part of dashboard security configuration. Add type has direct consequences in Clarity, because the primary key of an extracted table reflects it. A record identifier alone indicates no-add data, whereas a contact serial number indicates data stored at the contact level. Reviewing the add type in the Item Editor therefore helps predict the structure of the table in which the item is found.
[Reference: Cogito Fundamentals – Epic Data Architecture: Chronicles Add Types, ===============, ]
Submit