A record in Chronicles contains information about a unique entity within a master file. In the patient master file, one record corresponds to one patient, while in the user master file, one record corresponds to one user. The record is identified by a unique identifier, and the details of the entity are held in items, some stored on the record itself and others on its contacts. The second option correctly describes this. A file used for personalization does not define a record, although personalization records themselves are records in a master file. A code stored in Radar is a configuration object. A user security access level is a property that may be stored in a record, though it is not the definition of a record. Understanding the record is the basis for understanding the keys of Clarity tables. A table whose primary key is a record identifier holds data that is stored once for each entity, while a table that adds a contact serial number or a line number holds data that is stored at a finer level of detail. The Record Viewer displays the contents of a record.
[Reference: Cogito Fundamentals – Epic Data Architecture: Chronicles Records, ===============, ]
Submit