CA Core+
cibuild 
1.2.0-DFT - The specification is version 1.2.0-DFT of CA Core+ For a full list of available versions, see the Directory of published versions
Practitioner (CA-Core)
Many ValueSet and CodeSystem bindings in this guide link to resources hosted on the Canada Health Infoway Terminology Service (Ontoserver). If you are redirected to a login page: This is expected and you are being directed to Infoway’s secure environment. To access these resources: You’ll need an InfoCentral Account.
Links
Profile
Derived from
http://hl7.org/fhir/StructureDefinition/Practitioner
Examples
example-practitioner-ca-core-2, example-practitioner-ca-core-3, example-practitioner-ca-core
Description
This profile applies constraints to the Patient resource for CA Core+ to support identity, demographics, and administrative data in the pan-Canadian context.
References to this resource
AllergyIntoleranceCACore, AppointmentCACore, CommunicationCACore, ConditionCACore, DiagnosticReportCACore, DocumentReferenceCACore, EncounterCACore, ExampleProcedureProfile, ImmunizationCACore, ObservationCACore, ObservationLaboratoryPathologyResultCACore, PatientCACore, PractitionerRoleCACore, ServiceRequestCACore, TaskCACoreeRec, CopiedParticipants
CFMM: 2
Resource Content
| PractitionerCACore (Practitioner) | C | Practitioner | |
| id | Σ | 0..1 | id |
| meta | Σ | 0..1 | Meta |
| implicitRules | Σ ?! | 0..1 | uri |
| language | 0..1 | codeBinding | |
| text | 0..1 | Narrative | |
| contained | 0..* | Resource | |
| extension | C | 0..* | Extension |
| modifierExtension | ?! C | 0..* | Extension |
| identifier | Σ | 0..* | Identifier |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | CodeableConceptBinding |
| system | Σ | 0..1 | uri |
| value | Σ | 0..1 | string |
| period | Σ C | 0..1 | Period |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| start | Σ C | 0..1 | dateTime |
| end | Σ C | 0..1 | dateTime |
| assigner | Σ C | 0..1 | Reference(Organization) |
| active | Σ | 0..1 | boolean |
| name | Σ | 0..* | HumanName |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| use | Σ ?! | 0..1 | codeBinding |
| text | Σ | 0..1 | string |
| family | Σ | 0..1 | string |
| given | Σ | 0..* | string |
| prefix | Σ | 0..* | string |
| suffix | Σ | 0..* | string |
| period | Σ C | 0..1 | Period |
| telecom | Σ C | 0..* | ContactPoint |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| system | Σ C | 0..1 | codeBinding |
| value | Σ | 0..1 | string |
| use | Σ ?! | 0..1 | codeBinding |
| rank | Σ | 0..1 | positiveInt |
| period | Σ C | 0..1 | Period |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| start | Σ C | 0..1 | dateTime |
| end | Σ C | 0..1 | dateTime |
| address | Σ | 0..* | Address |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| preferred | C | 0..1 | Extension(boolean) |
| use | Σ ?! | 0..1 | codeBinding |
| type | Σ | 0..1 | codeBinding |
| text | Σ | 0..1 | string |
| line | Σ | 0..* | string |
| city | Σ | 0..1 | string |
| district | Σ | 0..1 | string |
| state | Σ | 0..1 | string |
| postalCode | Σ | 0..1 | string |
| country | Σ | 0..1 | string |
| period | Σ C | 0..1 | Period |
| gender | Σ | 0..1 | codeBinding |
| birthDate | Σ | 0..1 | date |
| photo | C | 0..* | Attachment |
| qualification | 0..* | BackboneElement | |
| id | 0..1 | string | |
| extension | C | 0..* | Extension |
| modifierExtension | Σ ?! C | 0..* | Extension |
| identifier | 0..* | Identifier | |
| code | 1..1 | CodeableConcept | |
| period | C | 0..1 | Period |
| issuer | C | 0..1 | Reference(Organization) |
| communication | 0..* | CodeableConceptBinding |
| PractitionerCACore (Practitioner) | Practitioner | ||
| identifier | |||
| type | |||
| system | |||
| value | |||
| period | |||
| start | |||
| end | |||
| name | |||
| use | |||
| text | |||
| telecom | |||
| value | |||
| use | |||
| rank | |||
| period | |||
| start | |||
| end | |||
| address | |||
| preferred | 0..1 | Extension(boolean) | |
| type | |||
| line | |||
| state | |||
| postalCode | |||
| country | |||
| qualification | |||
| code | |||
| communication | Binding |
</extension>
</telecom>
</telecom>
</contact>
<description value="This profile applies constraints to the Patient resource for CA Core+ to support identity, demographics, and administrative data in the pan-Canadian context." />
</jurisdiction>
<copyright value="Copyright © 2025+ Canada Health Infoway. All rights reserved. [Terms of Use and License Agreements](https://ic.infoway-inforoute.ca/en/about/tou). [Privacy Policy](https://www.infoway-inforoute.ca/en/legal/privacy-policy)." />
</mapping>
<comment value="pCHDCF modelling for care team concepts (including provider identifiers) is still underway. The requirements to support certain types of identifiers (e.g., province/territory registration identifiers) across all use cases and decisions on whether the identifier requirements should apply to both Practitioner and PractitionerRole are still undefined. Furthermore, the ways that these identifiers will be differentiated for conformance testing purposes is still undefined (see comment on identifier.type). For this reason, slice modelling and application of obligations towards certain identifiers is not currently expressed in this profile. The profile will continue to evolve as care team details undergo data modelling in the pCHDCF." />
</mapping>
</element>
<comment value="The value in identifier.type is typically used to differentiate between identifiers that serve distinct purposes (e.g., Medical License Number, Regional Registry ID, Health Plan Identifier). Profiles typically use the identifier.type to differentiate between expectations that are expressed for some identifier types but not others. However, current implementations of practitioner identifiers in Canada use the identifier.type of 'Provider Number' (coded as 'PRN') to convey a number of different types of identifiers (e.g., registration number, license numbers, and billing numbers). Should there be expectations in the future for this profile to differentiate between these identifiers, current typing practices may need to change and/or further details may need to be used (e.g., identifier.system) to differentiate between concepts like registration number, license number, and billing number." />
</mapping>
</element>
</mapping>
</element>
</mapping>
</mapping>
</element>
</mapping>
</mapping>
</element>
</mapping>
</mapping>
</element>
</mapping>
</element>
</mapping>
</element>
<definition value="Text representation of the full name. Due to the cultural variance around the world a consuming system may not know how to present the name correctly; moreover not all the parts of the name go in given or family. Creators are therefore strongly encouraged to provide through this element a presented version of the name. Future versions of this guide may require this element" />
</element>
<comment value="Although the provider phone number and provider email concepts are expressed in the pCHDCF materials, their current definition does not distinctly identify the resource target(s) where it has to be applied (e.g., Practitioner vs PractitionerRole). The mappings and obligations for these details have been removed from the profile to avoid unintentional placement of these requirements until further pCHDCF data modelling for care team details is complete. Reviewers are encouraged to provide feedback on the potential impact of applying a 'no-error' obligation on this element for clients." />
</mapping>
</element>
</mapping>
</element>
</mapping>
</element>
</mapping>
</element>
</mapping>
</element>
</mapping>
</element>
</mapping>
</element>
</type>
</element>
</mapping>
</element>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</mapping>
</element>
</mapping>
</mapping>
</mapping>
</element>
</mapping>
</mapping>
</element>
</mapping>
</mapping>
</mapping>
</element>
</binding>
</element>
</binding>
</element>
</differential>
</StructureDefinition>
{
],
{
{
},
{
}
]
}
],
"description": "This profile applies constraints to the Patient resource for CA Core+ to support identity, demographics, and administrative data in the pan-Canadian context.",
],
"copyright": "Copyright © 2025+ Canada Health Infoway. All rights reserved. [Terms of Use and License Agreements](https://ic.infoway-inforoute.ca/en/about/tou). [Privacy Policy](https://www.infoway-inforoute.ca/en/legal/privacy-policy).",
],
{
"comment": "pCHDCF modelling for care team concepts (including provider identifiers) is still underway. The requirements to support certain types of identifiers (e.g., province/territory registration identifiers) across all use cases and decisions on whether the identifier requirements should apply to both Practitioner and PractitionerRole are still undefined. Furthermore, the ways that these identifiers will be differentiated for conformance testing purposes is still undefined (see comment on identifier.type). For this reason, slice modelling and application of obligations towards certain identifiers is not currently expressed in this profile. The profile will continue to evolve as care team details undergo data modelling in the pCHDCF.",
]
},
{
"comment": "The value in identifier.type is typically used to differentiate between identifiers that serve distinct purposes (e.g., Medical License Number, Regional Registry ID, Health Plan Identifier). Profiles typically use the identifier.type to differentiate between expectations that are expressed for some identifier types but not others. However, current implementations of practitioner identifiers in Canada use the identifier.type of 'Provider Number' (coded as 'PRN') to convey a number of different types of identifiers (e.g., registration number, license numbers, and billing numbers). Should there be expectations in the future for this profile to differentiate between these identifiers, current typing practices may need to change and/or further details may need to be used (e.g., identifier.system) to differentiate between concepts like registration number, license number, and billing number.",
]
},
{
]
},
{
{
},
{
}
]
},
{
{
},
{
}
]
},
{
{
},
{
}
]
},
{
]
},
{
]
},
{
"definition": "Text representation of the full name. Due to the cultural variance around the world a consuming system may not know how to present the name correctly; moreover not all the parts of the name go in given or family. Creators are therefore strongly encouraged to provide through this element a presented version of the name. Future versions of this guide may require this element"
},
{
"comment": "Although the provider phone number and provider email concepts are expressed in the pCHDCF materials, their current definition does not distinctly identify the resource target(s) where it has to be applied (e.g., Practitioner vs PractitionerRole). The mappings and obligations for these details have been removed from the profile to avoid unintentional placement of these requirements until further pCHDCF data modelling for care team details is complete. Reviewers are encouraged to provide feedback on the potential impact of applying a 'no-error' obligation on this element for clients.",
]
},
{
]
},
{
]
},
{
]
},
{
]
},
{
]
},
{
]
},
{
{
}
]
},
{
]
},
{
{
},
{
},
{
},
{
},
{
},
{
},
{
},
{
},
{
}
]
},
{
{
},
{
},
{
}
]
},
{
{
},
{
}
]
},
{
{
},
{
},
{
}
]
},
{
}
},
{
}
}
]
}
}
Terminology bindings
| Path | Conformance | ValueSet |
|---|---|---|
| Practitioner.qualification.code | example | http://terminology.hl7.org/ValueSet/v2-2.7-0360 |
| Practitioner.communication | preferred | http://hl7.org/fhir/ValueSet/languages |
Additional Terminology Bindings
These bindings may be used in lieu of the primary bindings in the table above.
Mappings to CACDI
The following tables list how the data elements from CA Core+ map to CACDI. For more information visit Mapping Logic.
| FHIR Profile Element | CACDI Element(s) |
|---|---|
| Practitioner.identifier | Health Care Provider Identifier Information |
| Practitioner.identifier.type | Party Non-Health Identifier Type |
| Practitioner.identifier.system | Party Non-Health Identifier System |
| Practitioner.identifier.value | Health Care Provider Licence Number, Party Non-Health Identifier |
| Practitioner.identifier.period.start | Health Care Provider Licence Effective Date, Party Non-Health Identifier Effective Date |
| Practitioner.identifier.period.end | Health Care Provider Licence Expiry Date, Party Non-Health Identifier Expiry Date |
| Practitioner.name | Health Care Provider Name Information |
| Practitioner.name.use | Name Type |
| Practitioner.telecom | Health Care Provider Telecom Information |
| Practitioner.telecom.value | Contact Mechanism Value |
| Practitioner.telecom.use | Contact Mechanism Type Code |
| Practitioner.telecom.rank | Contact Mechanism Rank |
| Practitioner.telecom.period.start | Contact Mechanism Effective Date |
| Practitioner.telecom.period.end | Contact Mechanism Expiry Date |
| Practitioner.address | Health Care Provider Address Information |
| Practitioner.address.type | Address Type Code |
| Practitioner.address.line | Street Number, Street Number Suffix, Street Name, Street Type Code, Street Direction Code, Suite Type Code, Suite Number, Address 2, Address Additional Information Text |
| Practitioner.address.state | Province or Territory Code, Province or Territory English Name, Province or Territory French Name |
| Practitioner.address.postalCode | Non-Canadian Postal Code Value, Canadian Postal Code Value |
| Practitioner.address.country | Country Code, Country English Name, Country French Name |
Constraints
The following table lists constraints (from differential).