<status value="active" /> <experimental value="false" /> <date value="2025-03-04" /> <publisher value="Canada Health Infoway" /> <contact> <name value="National Standards Release Centre" /> <telecom> <system value="url" /> <value value="http://www.infoway-inforoute.ca" /> </telecom> <telecom> <system value="email" /> <value value="standards@infoway-inforoute.ca" /> </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> <coding> <system value="urn:iso:std:iso:3166" /> <code value="CA" /> </coding> </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)." /> <fhirVersion value="4.0.1" /> <mapping> <identity value="CACDI" /> <name value="Canadian Core Data for Interoperability (CACDI)" /> </mapping> <kind value="resource" /> <abstract value="false" /> <type value="Practitioner" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Practitioner" /> <derivation value="constraint" /> <differential> <element id="Practitioner.identifier"> <path value="Practitioner.identifier" /> <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> <identity value="CACDI" /> <map value="Health Care Provider Identifier Information" /> </mapping> </element> <element id="Practitioner.identifier.type"> <path value="Practitioner.identifier.type" /> <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> <identity value="CACDI" /> <map value="Party Non-Health Identifier Type" /> </mapping> </element> <element id="Practitioner.identifier.system"> <path value="Practitioner.identifier.system" /> <mapping> <identity value="CACDI" /> <map value="Party Non-Health Identifier System" /> </mapping> </element> <element id="Practitioner.identifier.value"> <path value="Practitioner.identifier.value" /> <mapping> <identity value="CACDI" /> <map value="Health Care Provider Licence Number" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Party Non-Health Identifier" /> </mapping> </element> <element id="Practitioner.identifier.period.start"> <path value="Practitioner.identifier.period.start" /> <mapping> <identity value="CACDI" /> <map value="Health Care Provider Licence Effective Date" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Party Non-Health Identifier Effective Date" /> </mapping> </element> <element id="Practitioner.identifier.period.end"> <path value="Practitioner.identifier.period.end" /> <mapping> <identity value="CACDI" /> <map value="Health Care Provider Licence Expiry Date" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Party Non-Health Identifier Expiry Date" /> </mapping> </element> <element id="Practitioner.name"> <path value="Practitioner.name" /> <mapping> <identity value="CACDI" /> <map value="Health Care Provider Name Information" /> </mapping> </element> <element id="Practitioner.name.use"> <path value="Practitioner.name.use" /> <mapping> <identity value="CACDI" /> <map value="Name Type" /> </mapping> </element> <element id="Practitioner.name.text"> <path value="Practitioner.name.text" /> <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> <element id="Practitioner.telecom"> <path value="Practitioner.telecom" /> <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> <identity value="CACDI" /> <map value="Health Care Provider Telecom Information" /> </mapping> </element> <element id="Practitioner.telecom.value"> <path value="Practitioner.telecom.value" /> <mapping> <identity value="CACDI" /> <map value="Contact Mechanism Value" /> </mapping> </element> <element id="Practitioner.telecom.use"> <path value="Practitioner.telecom.use" /> <mapping> <identity value="CACDI" /> <map value="Contact Mechanism Type Code" /> </mapping> </element> <element id="Practitioner.telecom.rank"> <path value="Practitioner.telecom.rank" /> <mapping> <identity value="CACDI" /> <map value="Contact Mechanism Rank" /> </mapping> </element> <element id="Practitioner.telecom.period.start"> <path value="Practitioner.telecom.period.start" /> <mapping> <identity value="CACDI" /> <map value="Contact Mechanism Effective Date" /> </mapping> </element> <element id="Practitioner.telecom.period.end"> <path value="Practitioner.telecom.period.end" /> <mapping> <identity value="CACDI" /> <map value="Contact Mechanism Expiry Date" /> </mapping> </element> <element id="Practitioner.address"> <path value="Practitioner.address" /> <mapping> <identity value="CACDI" /> <map value="Health Care Provider Address" /> </mapping> </element> <element id="Practitioner.address.extension:preferred"> <path value="Practitioner.address.extension" /> <sliceName value="preferred" /> <min value="0" /> <max value="1" /> <type> <code value="Extension" /> <profile value="http://hl7.org/fhir/StructureDefinition/iso21090-preferred" /> </type> </element> <element id="Practitioner.address.type"> <path value="Practitioner.address.type" /> <mapping> <identity value="CACDI" /> <map value="Address Type Code" /> </mapping> </element> <element id="Practitioner.address.line"> <path value="Practitioner.address.line" /> <mapping> <identity value="CACDI" /> <map value="Street Number" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Street Number Suffix" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Street Name" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Street Type Code" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Street Direction Code" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Suite Type Code" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Suite Number" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Address 2" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Address Additional Information Text" /> </mapping> </element> <element id="Practitioner.address.state"> <path value="Practitioner.address.state" /> <mapping> <identity value="CACDI" /> <map value="Province or Territory Code" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Province or Territory English Name" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Province or Territory French Name" /> </mapping> </element> <element id="Practitioner.address.postalCode"> <path value="Practitioner.address.postalCode" /> <mapping> <identity value="CACDI" /> <map value="Non-Canadian Postal Code Value" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Canadian Postal Code Value" /> </mapping> </element> <element id="Practitioner.address.country"> <path value="Practitioner.address.country" /> <mapping> <identity value="CACDI" /> <map value="Country Code" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Country English Name" /> </mapping> <mapping> <identity value="CACDI" /> <map value="Country French Name" /> </mapping> </element> <element id="Practitioner.qualification.code"> <path value="Practitioner.qualification.code" /> <binding> <strength value="example" /> <valueSet value="http://terminology.hl7.org/ValueSet/v2-2.7-0360" /> </binding> </element> <element id="Practitioner.communication"> <path value="Practitioner.communication" /> <binding> <strength value="preferred" /> <valueSet value="http://hl7.org/fhir/ValueSet/languages" /> </binding> </element> </differential> </StructureDefinition>