Practitioner (CA-Core)

Additional information on this profile (including the JSON & XML structure and detailed element descriptions) can be found at package/structuredefinition-practitioner-ca-core.json

This profile imposes the CA Baseline (v1.1.7) Practitioner Profile.

Profile

idΣ0..1string
metaΣ0..1Meta
implicitRulesΣ ?!0..1uri
language0..1codeBinding
text0..1Narrative
contained0..*Resource
extensionI0..*Extension
modifierExtension?! I0..*Extension
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
typeΣ0..1CodeableConceptBinding
systemΣ0..1uri
valueΣ0..1string
periodΣ I0..1Period
assignerΣ I0..1Reference(Organization)
activeΣ0..1boolean
id0..1string
extensionI0..*Extension
useΣ ?!0..1codeBinding
textΣ0..1string
familyΣ0..1string
givenΣ0..*string
prefixΣ0..*string
suffixΣ0..*string
periodΣ I0..1Period
telecomΣ I0..*ContactPoint
addressΣ0..*Address
genderΣ0..1codeBinding
birthDateΣ0..1date
photoI0..*Attachment
id0..1string
extensionI0..*Extension
modifierExtensionΣ ?! I0..*Extension
identifier0..*Identifier
code1..1CodeableConcept
periodI0..1Period
issuerI0..1Reference(Organization)
communication0..*CodeableConceptBinding

Obligations

Obligations are a new (and evolving) mechanism in FHIR to provide a consistent and machine processable way for profiles to define their expectations for system behaviors.

Earlier versions of the profiles exposed an initial set of obligations to garner feedback from the community on their use in Core+ profiles.

Obligations have been temporarily removed in this version to allow for further refinement of the approach against the Core Data for Interoperability (CACDI), which is now in development.

Terminology

This version of the guide is based on the early content development of the pan-Canadian Health Data Content Framework (pCHDCF). The pCHDCF is beginning to introduce recommended terminology for select concepts.

Terminology for CA Core+ Practitioner Profile has not been implemented in this release.

Mappings to pCHDCF

Draft Data Content Standard Element (As of 2024-06-18) Draft Data Content Standard Element Definition (As of 2024-06-18) FHIR Profile Element Additional Notes
Provider National Unique Identifier The registration number, or suitable alternative, that uniquely identifies a provider who may register in more than one province or territory. Practitioner.identifier.value + Practitioner.identifier.system + Practitioner.identifier.type *This is a placeholder concept that has yet to be developed.

*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.
Provider Provincial/Territorial Registration Number The registration number, or suitable alternative, that uniquely identifies a provider in a particular jurisdiction. Assigned by the submitting jurisdiction for administrative purposes. Practitioner.identifier.value + Practitioner.identifier.system + Practitioner.identifier.type *This has been mapped as an identifier to account for the current broad definition that could be used administratively. Further narrowing of this concept towards medical licensure could result in expectations applied to Practitioner.qualification - Further feedback is requested to weigh in on the impact of duplicating license details as both identifiers and qualifications.

*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.
Provider Registration Province/Territory The Canadian province or territory of registration, based on the jurisdiction or organization that submits provider data. N/A* *Likely a candidate for use case specific requirements (e.g., Practitioner.identifier.assigner for registry related use cases/actors) - Further feedback is requested on whether this expectation is appropriate for application on the general Practitioner profile
Provider Concurrent Registration Province/Territory Any other Canadian province or territory that a provider is licensed in (for the same profession) at the time of registration or renewal. N/A* *Likely a candidate for use case specific requirements (e.g., Practitioner.identifier.assigner for registry related use cases/actors) - Further feedback is requested on whether this expectation is appropriate for application on the general Practitioner profile
Provider Concurrent Registration Country Any other country that a provider is licensed in (for the same profession) at the time of registration or renewal. N/A* *Likely a candidate for a use case specific requirements (e.g., Practitioner.identifier.assigner.address for registry related use cases/actors) - Further feedback is requested on whether this expectation is appropriate for application on the general Practitioner profile
Provider Registration Status The class of licence/registration issued to a provider by a regulatory body or other professional association at the time of registration or renewal. N/A* *Likely a candidate for use case specific requirements (e.g., Practitioner.identifier.extension:registrationdetails for registry related use cases/actors) - Further feedback is requested on whether this expectation is appropriate for application on the general Practitioner profile
Provider Registration Date The month/year in which the provider registered (or renewed) with a Canadian provincial/territorial health care provider regulatory body or professional association. N/A* *Likely a candidate for use case specific requirements (e.g., Practitioner.identifier.extension:registrationdetails for registry related use cases/actors) - Further feedback is requested on whether this expectation is appropriate for application on the general Practitioner profile
Provider Provincial/Territorial Billing Number The unique number assigned to a provider by a jurisdiction that allows the calculation and direct payment for claims submitted under the number. Practitioner.identifier.value + Practitioner.identifier.system + Practitioner.identifier.type *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.
Provider Billing Province/Territory The jurisdiction issuing the provider's billing number. N/A* *Likely a candidate for use case specific requirements (e.g., Practitioner.identifier.assigner for registry related use cases/actors) - Further feedback is requested on whether this expectation is appropriate for application on the general Practitioner profile
Provider Last Name The last name of the provider. Practitioner.name.family
Provider First Name The first name of the provider. Practitioner.name.given
Provider Phone Number The provider's phone number. Practitioner.telecom.value* + Practitioner.telecom.system* *Although the Provider Phone Number concept is expressed in the pCHDCF materials, the 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.
Provider Email The provider's email address. Practitioner.telecom.value* + Practitioner.telecom.system* *Although the Provider Email concept is expressed in the pCHDCF materials, the 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.