Patient-Source Timelines of Data Coverage
- 26 Apr 2023
- 1 Minute to read
- Print
- DarkLight
Patient-Source Timelines of Data Coverage
- Updated on 26 Apr 2023
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Object Description
One record per patient-source timeline period during which at least one of the flagged data types for that patient would be included in the imported files from that data source if such records existed. NB: Input data to this object from each source should already be non-overlapping within a patient, and therefore the union of those should also be non-overlapping within a patient-source pair; using a Simple Timeline here represents a fail-safe that guarantees this non-overlapping structure.
Metadata
- Table Name: ursa.no_ursa_core_pat_002
- Layer: Natural Object
- Object Type: Simple Timeline
- Temporal Class: Interval (Timeline)
- Case ID: Patient ID, Source ID
- Interval Start Date: Period Start Date
- Interval End Date: Period End Date
- Primary Key: Patient ID, Source ID, Period Start Date, Period End Date
Relational Diagram
Related Key Concepts
None.
Dedicated Precursors
- [NO/URSA-CORE] Patient-Source Timelines of Data Coverage, Precursor 1 (All Source Records): One record per patient-source timeline period during which at least one of the flagged data types for that patient would be included in the imported files from that data source if such records existed.
FAQs
None.
Was this article helpful?