Common Data Exchange

The Common Data Exchange module defines foundational building blocks that support a broad range of health information exchange use cases. These profiles encompass patient, provider, medication, observation, and encounter-level concepts, ensuring reusability across nearly all pan-Canadian implementations.

Included Profiles

Identity and Roles

• Patient (CA-Core)
  Defines a patient identity profile aligned with pan-Canadian identity guidance and CACDI expectations.

• Practitioner (CA-Core)
  Represents licensed healthcare professionals, including identifiers, names, and qualifications.

• PractitionerRole (CA-Core)
  Captures a practitioner's role, location, and organizational affiliation within the healthcare system.

• Organization (CA-Core)
  Represents healthcare organizations such as hospitals, clinics, custodians, and payers.

• Location (CA-Core)
  Describes physical or virtual places where care is delivered, including wards, offices, and telehealth endpoints.

Clinical Context

• Encounter (CA-Core)
  Represents a patient interaction or healthcare event, including visits, admissions, and virtual sessions.

• Condition (CA-Core)
  Captures clinical conditions, diagnoses, or health concerns relevant to a patient.

• Procedure (CA-Core)
  Documents medical procedures performed on a patient.

• AllergyIntolerance (CA-Core)
  Represents known allergies or intolerances and their clinical implications.

• DiagnosticReport (CA-Core)
  Summarizes findings from diagnostic services, including laboratory tests, imaging, and pathology reports.

• DocumentReference (CA-Core)
  References external clinical documents such as scanned reports, discharge summaries, and consent forms.

Medications

• Medication (CA-Core)
  Defines medication products, including drug form, identifiers, and classifications.

• MedicationRequest (CA-Core)
  Represents an order or prescription for a medication.

• MedicationStatement (CA-Core)
  Captures statements regarding a patient's historical or current medication use.

• Immunization (CA-Core)
  Captures details of vaccinations received by a patient.

Observations

• Observation (CA-Core)
  Generic observation template applicable to various use cases.

• Observation-LaboratoryResult (CA-Core)
  Captures laboratory test results.

• Observation-PathologyResult (CA-Core)
  Represents pathology result observations.

• Observation-RadiologyResults (CA-Core)
  Captures radiology report observations.

• Observation-TobaccoUse (CA-Core)
  Represents tobacco use-related observations.

• Observation-AlcoholUse (CA-Core)
  Captures alcohol use-related observations.

• Observation-SocialHistory (CA-Core)
  Captures social history elements such as occupation and housing status.

• Observation-SexualOrientation (CA-Core)
  Profile to capture a patient's self-reported sexual orientation.

Supporting Structures

Common Data Exchange Extensions

The Common Data Exchange Extensions define additional data elements that extend CA Core+ profiles. These extensions ensure that unique pan-Canadian implementation needs are met while maintaining alignment with international HL7 FHIR standards.

This section includes all extensions specifically defined within CA Core+. Additionally, external extensions from sources such as the HL7 Extension Registry may be referenced in CA Core+ profiles where necessary.

Visit the Extensions page for a list of supported extensions and their intended use.

Common Data Exchange Data Types

The Common Data Exchange Data Types enforce constraints on data elements to ensure consistency across implementations. These constraints define which elements within a data type are required or expected for systems to demonstrate compliance and interoperability.

Profiling data types in CA Core+ ensures that health information exchange adheres to pan-Canadian requirements while aligning with global best practices.

Visit the Data Types page for detailed definitions and constraints applied within CA Core+.

Design Principles

• Profiles in this module are designed for broad applicability and are intended for reuse across all CA Core+ modules.
• Terminology bindings follow pan-Canadian expectations and align with CACDI, CA:FeX, and other pan-Canadian initiatives.
• Extensions are used minimally, only when necessary to support pan-Canadian policies or implementation requirements.

Usage Examples

These profiles may be used:

• As references within Consent or Workflow modules (e.g., a Patient as a consent granter or a Practitioner in a Task.owner role).
• As standalone entities in jurisdictional implementations for administrative, clinical, or reporting workflows.
• As foundational elements for further constraints or slicing in domain-specific implementation guides.

Visit the Examples section for detailed use case demonstrations.

Relationship to Other Modules

Other CA Core+ modules, including Workflows, build upon these core structures. Downstream implementation guides should not redefine these elements, but instead build on the standardized representations defined here to ensure interoperability and consistency across implementations. Review General Guidance for more information.