Patient Communications
- 26 Apr 2023
- 1 Minute to read
- Print
- DarkLight
Patient Communications
- 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 instance of a communication between a provider and a patient; communication instances can also have children instances, representing discrete messages or parts of the parent communication. Excludes deleted records.
Metadata
- Table Name: ursa.no_ursa_core_pat_007
- Layer: Natural Object
- Object Type: Single Stack
- Temporal Class: Event
- Case ID: Patient Communication ID
- Event Date: Communication Start Date
- Primary Key: Patient Communication ID
Relational Diagram
Related Key Concepts
None.
Dedicated Precursors
- [NO/URSA-CORE] Patient Communications, Precursor 1 (All Source Records): One record per instance of a communication between a provider and a patient; communication instances can also have children instances, representing discrete messages or parts of the parent communication.
FAQs
None.
Was this article helpful?