Diagram of Service Request

  • 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.

Service Request Subject Area Pan-Canadian Health Data Content Framework Version 3, September 2026 Party Role Document Reference «Catalog» Health Care Service Provenance Location Service Request - Service Request Additional Instructions Information: String [0..1] - Service Request As Needed Indicator: Indicator [0..1] - Service Request Body Site Code: Codeable Concept [0..*] - Service Request Category Code: Codeable Concept [0..*] - Service Request Code: Codeable Concept [0..1] - Service Request Communication Method Code: Codeable Concept [0..1] - Service Request Consultation or Referral Type Code: Codeable Concept [0..1] - Service Request Day Of Week Code: Codeable Concept [0..*] - Service Request Do Not Perform Indicator: Indicator [0..1] - Service Request Do Not Perform Reason Code: Codeable Concept [0..*] - Service Request Effective Period: Period - Service Request Identifier: Identifier [0..*] - Service Request Intent Code: Codeable Concept - Service Request Internal Indicator: Indicator [0..1] - Service Request Priority Code: Codeable Concept [0..1] - Service Request Quantity Range: Range [0..1] - Service Request Quantity Ratio: Ratio [0..1] - Service Request Quantity Value: Quantity [0..1] - Service Request Time Of Day: Time [0..*] - Service Request Timing Code: Codeable Concept [0..1] - Service Request Timing Frequency: Quantity [0..1] constraints {XOR (Service Request Quantity Value, Service Request Quantity Range, Service Request Quantity Ratio)} ClinicalAnnotation Encounter Service Request Location - Service Request Delivery Location Role Type Code: Codeable Concept constraints {Unique Key: Service Request, Location} Requisition Form Patient Service Request Performer - Service Request Performer Role Type Code: Codeable Concept constraints {Unique Key: Service Request, Party Role} Party Group Device Specimen Order Set Service Request Status - Service Request Status Code: Codeable Concept - Service Request Status Date Time: Date Time [0..1] - Service Request Status Reason Code: Codeable Concept [0..*] constraints {Unique Key: Service Request, Service Request Status Code, Service Request Status Date Time if specified} Service Request Reason - Service Request Reason Code: Codeable Concept [0..1] constraints {Unique Key: Service Request, XOR(Service Request Reason Code, Diagnostic Report, Observation, Patient Health Concern, Document Reference, Patient Procedure) } Observation Patient HealthConcern Diagnostic Report Clinical Document Clinical Information LifeCycle Event - Clinical Information Life Cycle Event Date Time: Date Time [0..1] - Clinical Information Life Cycle Event Type Code: Codeable Concept constraints {Mandatory(Party Role OR Clinical Information Life Cycle Event Date Time)} PatientProcedure 0..1 0..* subject of 0..* 0..* 0..* 0..1 executed by 0..1 0..* subject of 0..* 0..1 is 0..* 0..1 is 0..1 0..* created in 0..* 0..* fulfilled in 0..* 0..* supports 0..* 0..1 is 0..* 0..1 instructs 0..* 0..1 is 0..* 0..1 for 0..* 0..* 0..1 0..* defines 0..* 0..* has {Event Types: "authoring (signed)", "request", "reception","acknowledgment", ..., Party Role is Health Care Providerfor "authoring", "reception", "acknowledgment"} 0..1 0..* subject of 1 1..* has 1 0..* has 0..1 0..* subject of 0..* 0..1 is 0..* 0..1 0..* 0..* replaces 0..* 0..1 0..1 0..* defines 0..1 0..* has 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 Service Request. Accessed November 02, 2026.

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