Defines the Polaris standard for AllergyIntolerance resources, based on CA-Core+. Includes instance-specific Polaris identifiers, references via identifier (CII E01).

Simple app consent profile: Patient X consented/refused to share information with Application Y (represented as a Device). This profile models consent for a patient to sign up with an app.

Simple profile for applications that integrate with patient data and require consent tracking. Contains just the essential information: app name, client_id, and basic details.

A profile for representing external application state in Polaris.

Minimal Polaris profile for Appointment resources, primarily for mapping status, start date (Last Visit Date), and required patient/practitioner participants. Assumes filtering for status='fulfilled' happens during data retrieval/processing. Contains embedded aliases and invariants.

A FHIR Bundle representing a complete clinical document with embedded sections and recursive containment capabilities

A FHIR Composition supporting four section types (Text, Form, Canvas, File) with recursive containment

A clinical task for healthcare workflow management combining Polaris design principles with MERT standard compatibility

Polaris profile for ClinicalImpression capturing the Assessment section of a SOAP encounter note. Purpose: export assessment text. Should be exported by EMRs that have the ability to parse the 'A' text out of a SOAP note.

Polaris profile for Condition resource, representing health concerns (CII E11) or clinical assessments (CII E34). Constrains necessary elements, requires a Polaris identifier, and adds support for required extensions and security labels.

DEPRECATED: Use medicationCodeableConcept in MedicationRequest instead.

Defines the Polaris FHIR profile for DiagnosticReport resources, based on CA-Core constraints, for aggregating diagnostic reports (e.g., Lab, Imaging) from multiple EMRs.

Polaris profile for managing clinical document references and their content. This profile provides a standardized approach for document exchange between EMR systems, supporting inline document storage, comprehensive metadata, and clinical context preservation. Aligned with CA-Core+ standards and CII requirements for Canadian healthcare.

Key features:

• Flexible document storage: inline base64-encoded data, blob storage URI, or both
• Flexible categorization using standard terminologies
• Support for multiple document attachments
• Clinical context through encounter references
• Authentication and provenance tracking

Represents an EMR software application/product, capturing key details like manufacturer, product name/model, type, version, and the owning organization using standard Polaris references. Uses a non-instance-specific identifier for the Device itself.

Defines the Encounter resource constraints for the Polaris project (CII), conforming to CA-Core+ requirements.

Polaris profile for Immunization resources, aligned with CA-Core+ and CII requirements. Records details about vaccines administered to a patient.

Generic Polaris core profile for Location, represents an EMR 'location' or 'site' – basically whatever the EMR uses to break the EMR up into separate slices (often for multisite clinics using the same EMR instance) For single-site clinics, at least one Location object must exist that represents the main site: this makes downstream consumers of the FHIR data easier to write as they can always assume Locations exist. Also, note that PolarisAppointment REQUIRES a Location as a participant.

Polaris profile for MedicationDispense resources, primarily for recording dispense events. Aligns with CII N1/N2 requirements and Polaris standards.

Defines the Polaris FHIR profile for MedicationRequest resources, based on CA-Core constraints, for aggregating prescription data from multiple EMRs.

Polaris profile for the Observation resource, based on CA-Core. Represents measurements, tests, and simple assertions originating from source EMRs for aggregation.

Generic Polaris core profile for Organization, based on CA Core+. Designed to support a broad range of integration needs.

Generic Polaris core profile for patient demographic and administrative information, based on CA Core+. Designed to support a broad range of integration needs.

Represents a human that practices medicine. May work at multiple organizations, represented by a PractitionerRole. If you want to reference an EMR user, use PractitionerRole.

Represents an EMR user. Focuses on linking a Practitioner to Organizations and Locations via Polaris identifiers.

Defines the Polaris FHIR profile for Procedure resources, based on CA-Core Procedure constraints, for aggregating data from multiple EMRs.

Represents a roster panel for patient-provider attachment tracking, derived from the Group resource. Uses identifier-based references for managing entity and members. Allows provider/facility links via Polaris OR external IDs. Supports CPAR roster panel requirements and other roster management use cases.

Defines the Polaris FHIR profile for ServiceRequest resources, based on CA-Core ServiceRequest constraints, for aggregating order/referral data from multiple EMRs.

A simple extension to hold the value of a Polaris application-state entry as a boolean.

A simple extension to hold the value of a Polaris application-state entry as a string.

Indicates if the panel submission is automated.

Records the date when the panel was confirmed or validated.

Captures the facility(ies) associated with the panel. Links via identifier.

Supports drawings, signatures, positioned elements, and embedded complete sections at specific coordinates on canvas

Canvas dimensions, coordinate system, PDF page mapping

Allows questionnaire answer options to contain complete embedded sections

Embeds complete Polaris sections (Text/Form/Canvas/File) within text content as actual nested content

Contains complete sections as questionnaire response values

Additional metadata for file attachments including display hints and embedded sections

Provides Markdown representation of text content for systems supporting markdown rendering

Extension to capture medication strength information when using medicationCodeableConcept

Captures the primary provider(s) associated with the panel. Links via identifier.

Indicates if the panel should be submitted during the next available window.

Naming systems for provincial and territorial health numbers across Canada, based on Infoway standards

LOINC codes for file attachment sections

Types of annotations that can be placed on canvas sections

Coordinate systems for canvas positioning

Types of sections that can be embedded within other sections

Categories for file attachments to aid in processing and display

LOINC codes for form-based sections

URIs for provincial and territorial health number naming systems across Canada

Clinical research platform - MORE INFO REQUESTED by Avery

Example document reference for anemia consultation note from April 8, 2025

Example diagnostic report for anemia workup from April 8, 2025

Example condition record for patient Avery Linwood's anemia diagnosis

Example patient encounter for Avery Linwood's visit on April 8, 2025

Example diastolic blood pressure observation for Avery Linwood

Example height measurement observation for Avery Linwood

Example patient record demonstrating Polaris patient profile

Example systolic blood pressure observation for Avery Linwood

Example immunization record for TDAP vaccine given to Avery Linwood

Example healthcare organization demonstrating Polaris organization profile

Example healthcare facility location for Cedarbrook Clinic

Example EMR device record for Cedarbrook Clinic's Juno system

Example medication request demonstrating Polaris profile with detailed information

Example practitioner record demonstrating Polaris practitioner profile

Example practitioner role linking Dr. Navarro to family medicine practice

Example service request for hemoglobin laboratory test

Example hemoglobin laboratory result observation

Example medication dispense for iron supplement sample given to Avery Linwood

Example procedure record for iron therapy prescribed to Avery Linwood

Example allergy intolerance record demonstrating Polaris profile

FHIR R4 consent deny pattern - patient declined WellnessTracker Pro (3:45 PM)

FHIR R4 consent grant pattern - patient consented to SmartDocs AI Scribe (10:30 AM)

FHIR R4 consent request pattern - more info needed for research study (2:15 PM)

Example application state record demonstrating Polaris AppState profile

Example appointment with requested period demonstrating Polaris profile

Example roster panel group demonstrating Polaris roster panel profile used in CPAR implementations

AI clinical documentation app - CONSENT GRANTED by Avery

Personal wellness monitoring app - CONSENT DENIED by Avery

Assessment: Patient presents with acute symptomatic anemia (hemoglobin 68 g/L) following new-onset dizziness and fatigue. Iron therapy prescribed (ferrous sulfate 325 mg daily) and follow-up assessment scheduled in two weeks.

Patient message about blood pressure concerns requires triage assessment with AI assistance. Message: 'I've been checking my BP at home and it's been running 150/90. Should I be concerned?'

Provide diabetes education follow-up for Jennifer Martinez. Review blood glucose logs, insulin adjustment, and dietary counseling. Patient newly diagnosed with Type 2 diabetes.

Review CBC results for John Doe - flagged values need clinical assessment. Hemoglobin 8.2 g/dL (low), requires evaluation for anemia workup.

Complete medication reconciliation for David Chen following hospital discharge. Patient returned from Calgary General Hospital after pneumonia treatment. Reconcile discharge medications with home medications.

Process cardiology referral for Alice Johnson - chest pain evaluation. Patient reports intermittent chest discomfort with exertion. ECG shows possible T-wave abnormalities in leads V4-V6.