Skip to content
Partner Developer Portal

Definition

A Consultation Section represents a structured component within a consultation encounter. Sections are used to organise clinical activity into meaningful areas of care, such as patient history, examination findings, assessment, care planning, medication review, or administrative activities recorded during the consultation.

Each section belongs to a consultation and provides the context through which associated clinical records are captured and linked. Consultation sections act as the primary navigation layer between a consultation and many downstream clinical domains, enabling users to understand both the structure and content of a patient interaction.

A single consultation can relate to multiple concerns that a patient - healthcare professional interaction will cover and might contain multiple consultation sections, each representing a distinct area of activity undertaken during the patient encounter.

Common examples of consultation sections include:

  • Problem
  • History
  • Examination
  • Medication Review
  • Referral
  • Diary
  • Plan

These default section types are commonly available within EMIS source system, however consultation templates and workflows can be configured locally by organisations. As a result, additional section headings and categories may be present depending on local clinical processes, templates, and data-entry configurations.

Each row in the consultation section model represents a single section within a consultation, linked to a parent consultation and an underlying clinical event.

A consultation section may be associated with records in multiple downstream models, including Observation, Allergy, Problem, Referral, Immunisation, Issue record, and Diary.

This model contains the following key information for consultation sections:

  • Record and patient identifiers
  • Linking fields to consultation, consultation section type, location, appointment and clinician
  • Clinical coding and terms
  • Consultation section and system dates
  • Classification information describing the clinical content associated with the section
  • Confidentiality and sensitivity indicators

Each row is a unique consultation section record and each record is uniquely identified by either combining consultation_section_id and organisation or the consultation_section_uuid column.

This model includes the following key identifiers:

  • consultation_section_id: The unique internal identifier for the consultation section record within an organisation.
  • consultation_section_guid: The GUID for the consultation section record within an organisation.
  • consultation_section_uuid: The UUID derived from consultation_section_id and organisation, providing a stable unique identifier.

The following fields are important for tracking data lineage and freshness:

  • is_deleted: Indicates whether the consultation record has been deleted at source.
  • is_confidential: Indicates whether the record is confidential.
  • is_sensitive: Indicates whether the record is flagged as sensitive.
  • transform_datetime: The timestamp indicating when the record was last processed and updated in the data model. This field is crucial for understanding the current state of the data.
flowchart TD
    consultation[(consultation)] --> consultation_section[(consultation_section)]
    patient[(patient)] --> consultation_section
    organisation[(organisation)] --> consultation_section
    user_in_role[(user_in_role)] --> consultation_section
    appointment_slot[(appointment_slot)] --> consultation_section
    consultation_section --> observation[(observation)]
    consultation_section --> diary[(diary)]
    consultation_section --> issue_record[(issue_record)]
    consultation_section --> test_request[(test_request)]
    consultation_section --> report[(report)]
    consultation_section --> care_plan_detail[(care_plan_detail)]

    classDef nodeStyle stroke:#9961a4;
    class consultation,patient,organisation,user_in_role,appointment_slot nodeStyle;

Get all consultation sections for a specific consultation

SELECT
*
FROM
hive.explorer_ipcv_artemis.encounter_section_v2
WHERE
emis_encounter_guid = 'A1B2C3D4-E5F6-7G8H-9I0J-K1L2M3N4O5P6';

Find confidential consultation sections

SELECT
*
FROM
hive.explorer_ipcv_artemis.encounter_section_v2
WHERE
confidential_flag = TRUE;

Join consultation sections with their parent consultations

SELECT
consultation.*,
section.*
FROM
hive.explorer_ipcv_artemis.encounter_v2 consultation
JOIN hive.explorer_ipcv_artemis.encounter_section_v2 section ON consultation.emis_encounter_guid = section.emis_encounter_guid
AND consultation.organisation = section.organisation
WHERE
consultation.emis_patient_id = 123456789;

Get sections by category type

SELECT
*
FROM
hive.explorer_ipcv_artemis.encounter_section_v2
WHERE
hestia_event_type = 'OBS';

Find sections marked as deleted

SELECT
*
FROM
hive.explorer_ipcv_artemis.encounter_section_v2
WHERE
is_deleted = TRUE;