Diagram of Appointment

  • Version 3
  • Published
  • Updated

Use the + and − buttons to zoom, and drag the diagram to pan. Select a class box to open its detail page.

UML 2.1 notation shows multiplicity on relationship ends; coloured boxes indicate classes elaborated in a separate diagram or planned for a future release.

Appointment Subject Area Pan-Canadian Health Data Content Framework Version 3, September 2026 Account Health Care Service Appointment Health Event - Appointment Cancelation Date Time: Date Time [0..1] - Appointment Cancelation Reason Code: Codeable Concept [0..1] - Appointment Class Code: Codeable Concept [0..1] - Appointment Creation Date Time: Date Time [0..1] - Appointment Duration Minutes: Integer [0..1] - Appointment Identifier: Identifier [0..*] - Appointment Instruction: String [0..*] - Appointment Mode Code: Codeable Concept [0..*] - Appointment Patient Attendance Requirement Indicator: Indicator [0..1] - Appointment Period: Period [0..1] - Appointment Priority Code: Codeable Concept [0..1] - Appointment Requested Range Period: Period [0..1] - Appointment Service Category Code: Codeable Concept [0..1] - Appointment Service Type Code: Codeable Concept [0..*] - Appointment Specialty Code: Codeable Concept [0..*] - Appointment Status Code: Codeable Concept - Appointment Type Code: Codeable Concept [0..1] Patient Health Concern Location Patient Document Reference Party Role Health Care Provider Party Group Party Clinical Annotation Encounter Reason Diagnostic Report Observation Clinical Event Patient Procedure Encounter Appointment Participant - Appointment Participant Required Code: Codeable Concept [0..1] - Appointment Participant Status Code: Codeable Concept [0..1] - Appointment Participant Type Code: Codeable Concept [0..1] - Appointment Participation Period: Period [0..1] constraints {Unique Key: {Appointment, Party Role, Appointment Participant Type Code if specified, Appointment Participation Period.Start Date Time if specified}} Party Role Location - Location Purpose Code: Codeable Concept [0..1] - Location Rank: Integer [0..1] - Party Role Location Effective Period: Period constraints {Unique Key: Party Role, Location, Location Purpose Code if specified, Location Rank if specified, Party Role Location Effective Period.Start Date} 0..* 0..1 0..* 0..1 originated from 0..1 0..1 previously scheduled 0..* 0..* replaced by 0..* 0..* covered by 1..* 0..* 0..* 0..* addresses 0..* 0..* for 0..* 0..* at 0..* 0..1 receives primary care from 0..1 0..* subject of 0..* 0..1 is 0..* 1 for 0..* 1 for 0..* 0..* has 0..* 0..1 is 0..* 0..* for 0..1 0..* subject of 0..* 0..1 is 0..* 0..1 is Exclusive OR Exclusive OR Legend Class Elaborated in Separate Diagram Future Release Business Representation Association relationship Uses relationship Relationship to association class Exclusive OR boundary | Inclusive OR boundary Generalization relationship from child to parent Aggregation relationship Composition relationship

Contact us

If you have questions about this initiative, would like to be added to our stakeholder notification list or would like to participate in our consultations, please email us.

connectedcare@cihi.ca

How to cite:

Canadian Institute for Health Information. Diagram of Appointment. Accessed November 02, 2026.

If you would like CIHI information in a different format, visit our Accessibility page.