[NO/URSA-CORE] Patient Communications

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

Published Fields

• Data Model Keys

  • Patient Communication ID -- The database identifier for an instance of communication between a provider organization staff member and a patient.
  • Parent Patient Communication ID -- The Patient Communication ID for the instance of communication of which the current record is a subordinate component. (See also [URSA-CORE] Patient Communication ID)
  • Child Patient Communication Sequence Number -- The sequence number, in chronological order, of the instance of communication associated with the current record within the context of the parent communication instance. (See also [URSA-CORE] Parent Patient Communication ID, [URSA-CORE] Patient Communication ID)
  • Patient ID -- The internal database identifier (used, e.g., for joins and primary keys) for the patient. This value is typically mastered, i.e., all records for the same patient, regardless of the source data system from which that record originated, should have the same Patient ID value. (Note that while the mastered Patient ID value might resemble a local identifier used in one of the upstream data sources, this does not indicate any special priority of that source system in determining the characteristics of the patient.) (See also [URSA-CORE] Patient)
  • Provider ID -- The database identifier for a individual or organization provider. (See also [URSA-CORE] Provider)
  • Parent EMR Encounter ID -- The database identifier for the EMR Encounter during or within which the event associated with the current record occurred.
  • Referenced EMR Encounter ID -- The database identifier for the EMR Encounter referred to or discussed in the event associated with the current record.
  • Source ID -- The identifier for the original source data system from which the current record originated.
  • Document ID

• Source Local Keys

  • Source Local Patient Communication ID -- The database identifier in the source system for the instance of patient communication associated with the current record.

• Date Fields

  • Communication Start Date -- The date the current instance of patient communication started.
  • Communication Start Datetime -- The date and time the current instance of patient communication started.
  • Communication End Date -- The date on which the current instance of patient communication ended.
  • Communication End Datetime -- The date and time at which the current instance of patient communication ended.

• Metadata Fields

  • Other EMR Comments -- Any other annotations or comments associated with the current record entered into the EMR.
  • Is Record Deleted -- Indicator for whether the current record should be considered deleted; useful for certain incremental data loading scenarios.
  • Record Last Updated Datetime -- The date and time the current record was last updated in the original data source.
  • Source Data Effective Datetime -- The "as of" date and time of the original source data system at the moment the current record was extracted. For example, if a snapshot of the data in a production system is taken at 12:05 AM on the first of each month and used to generate a package of flat files that are eventually loaded into the Ursa Studio client database later that month, the Source Data Effective Datetime of all records in that month's package will be 12:05 AM on the first. Not to be confused with Record Last Updated Datetime. (See also [URSA-CORE] Record Last Updated Datetime)

• Communications Fields

  • Communication Duration Minutes -- The duration of the communication in minutes, calculated as the elapsed time between communication start and end; for asynchronous communication, this might include time between the communication start and end not spent in active communication.
  • Is Sender Patient -- Indicates that the current instance of communication originated with the patient. (A value of 0 indicates the communication originated with the provider.)
  • Campaign Description -- The natural-language description of the broader communication campaign that the current instance of communication is a part of.
  • Campaign Operational ID -- The "real-life" identifier for the broader communication campaign that the current instance of communication is a part of.
  • Medium Description -- The natural language description of the medium through which the communication takes place, e.g., telephone call, email, etc.
  • Medium Operational ID -- The "real-life" identifier for the medium through which the communication takes place.
  • Is Medium Letter -- Indicates the medium of the current instance of communication is a mailed letter.
  • Is Medium Email -- Indicates the medium of the current instance of communication is email. (A conversation over email can be represented by a single Patient Communication instance, or by a series of Patient Communication instances contained within a Parent Patient Communication instance.)
  • Is Medium Telephone Call -- Indicates the medium of the current instance of communication is a telephone call.
  • Is Medium Text Message -- Indicates the medium of the current instance of communication is a text message. (A conversation over text can be represented by a single Patient Communication instance, or by a series of Patient Communication instances contained within a Parent Patient Communication instance.)
  • Is Medium Web Chat -- Indicates the medium of the current instance of communication is a web chat. (A conversation over web chat can be represented by a single Patient Communication instance, or by a series of Patient Communication instances contained within a Parent Patient Communication instance.)
  • Is Medium Other -- Indicates the medium of the current instance of communication is something other than letter, email, telephone call, text message, or web chat. (Should not be used to indicate that the medium is unknown.)
  • Content Type Description -- The natural language description of the type of content discussed in the current instance of communication, e.g., "Appointment Reminder Email".
  • Content Type Operational ID -- The "real-life" identifier of the type of content discussed in the current instance of communication.
  • Content Description -- The natural language description of the content of an instance of communication; could be the actual transcript of the communication, or a summary, as desired.
  • Conclusion Description -- The natural language description of the results of activity, such as a task or instance of communication, whether it was completed successfully or not.
  • Conclusion Operational ID -- The "real-life" identifier for the results of activity, such as a task or instance of communication, whether it was completed successfully or not.

Foreign Keys

• pat_id → ursa.no_ursa_core_pat_001.pat_id
• prov_id → ursa.no_ursa_core_prov_001.prov_id
• parent_emr_enc_id → ursa.no_ursa_core_enc_001.parent_emr_enc_id
• referenced_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id

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.