In Chronicles, a record represents a single entity within a master file, such as one patient. A contact is a snapshot of that record at a point in time, or the data that belongs to a particular event such as an encounter. Contacts allow information to change over time while the earlier values are preserved, and some data is stored on the record as a whole and other data on its contacts. The third option states that a contact stores a snapshot of data within a record. A user permission that grants access to reports is a security concept. A timestamp used for logging login history describes audit information and not the contact structure. A type of filter used to organize records describes a reporting function. The notion of a contact is fundamental when interpreting Clarity, where tables whose primary key includes a contact serial number contain data stored at the contact level, while tables keyed on a record identifier alone hold data stored once for the record. Understanding contacts is therefore essential for writing correct queries.
[Reference: Cogito Fundamentals – Epic Data Architecture: Chronicles Records and Contacts, ===============, ]
Submit