<status value="draft" /> <date value="2020-11-10T21:07:38.2646453+00:00" /> <fhirVersion value="4.0.1" /> <mapping> <identity value="v2" /> <uri value="http://hl7.org/v2" /> <name value="HL7 v2 Mapping" /> </mapping> <mapping> <identity value="rim" /> <uri value="http://hl7.org/v3" /> <name value="RIM Mapping" /> </mapping> <mapping> <identity value="servd" /> <uri value="http://www.omg.org/spec/ServD/1.0/" /> <name value="ServD" /> </mapping> <mapping> <identity value="w5" /> <uri value="http://hl7.org/fhir/fivews" /> <name value="FiveWs Pattern Mapping" /> </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"> <path value="Practitioner" /> <comment value="In Practitioner up to three identifiers can be provided. One for the issued TPR identifier (CPRID), a jurisdictional billing identifier may also be used under some circumstances, and a licence Number" /> <mustSupport value="true" /> </element> <element id="Practitioner.meta"> <path value="Practitioner.meta" /> <mustSupport value="true" /> </element> <element id="Practitioner.meta.lastUpdated"> <path value="Practitioner.meta.lastUpdated" /> <mustSupport value="true" /> </element> <element id="Practitioner.meta.source"> <path value="Practitioner.meta.source" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.meta.profile"> <path value="Practitioner.meta.profile" /> <mustSupport value="true" /> </element> <element id="Practitioner.text"> <path value="Practitioner.text" /> <mustSupport value="true" /> </element> <element id="Practitioner.text.status"> <path value="Practitioner.text.status" /> <mustSupport value="true" /> </element> <element id="Practitioner.text.div"> <path value="Practitioner.text.div" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier"> <path value="Practitioner.identifier" /> <slicing> <discriminator> <type value="pattern" /> <path value="type" /> </discriminator> <description value="Identifiers are a means to identify the person rather than their current qualifications" /> <rules value="open" /> </slicing> <comment value="Usage Rule: This is used for both licenced clinicians and EMR Users/MOAs. For non-clinicans this may be populated with a unique user identifier issued by the EMR Usage Note: This must be supported where a licence number and/or other known business identifier is specified. Alignment: PS-ON uses identifiers to specify licence number" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier.use"> <path value="Practitioner.identifier.use" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier.type"> <path value="Practitioner.identifier.type" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier.system"> <path value="Practitioner.identifier.system" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier.value"> <path value="Practitioner.identifier.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRProviderID"> <path value="Practitioner.identifier" /> <sliceName value="EMRProviderID" /> <comment value="Usage Note: An identifier that is assigned by the EMR. This links billing data and patient data. A practitioner may have multiples; one per bill book or specialty. eg Provider ID in PSS, is issued per bill book. All identifiers that are available should be sent. This may be structured as (<urn:telus:emr:ma:labtestsk1:providerid>" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRProviderID.type"> <path value="Practitioner.identifier.type" /> <patternCodeableConcept> <coding> <system value="http://terminology.hl7.org/CodeSystem/v2-0203" /> <code value="PRN" /> </coding> </patternCodeableConcept> <mustSupport value="true" /> <binding> <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName"> <valueString value="IdentifierType" /> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-isCommonBinding"> <valueBoolean value="true" /> </extension> <strength value="extensible" /> <valueSet value="http://telus.com/fhir/ValueSet/telus-identifier-type" /> </binding> </element> <element id="Practitioner.identifier:EMRProviderID.type.coding"> <path value="Practitioner.identifier.type.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRProviderID.type.coding.system"> <path value="Practitioner.identifier.type.coding.system" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRProviderID.type.coding.code"> <path value="Practitioner.identifier.type.coding.code" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRProviderID.system"> <path value="Practitioner.identifier.system" /> <comment value="Usage Note: Typically this can be constructed as follows: Vendor.ApplicationInstance.Branch to represent the EMR User ID Identifier.system is always case sensitive." /> <min value="1" /> <fixedUri value="http://telus.com/fhir/Identifiers/TPR" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRProviderID.value"> <path value="Practitioner.identifier.value" /> <comment value="Conformance Rule: This must match the Practitioner.id value." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:JurisdictionalBillingNumber"> <path value="Practitioner.identifier" /> <sliceName value="JurisdictionalBillingNumber" /> <comment value="Usage Note: There may be some use cases that will require this identifier. This only applies to physicians, not to nurse practitioners or other clinicians." /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:JurisdictionalBillingNumber.type"> <path value="Practitioner.identifier.type" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://terminology.hl7.org/CodeSystem/v2-0203" /> <code value="MCR" /> </coding> </patternCodeableConcept> <mustSupport value="true" /> <binding> <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-bindingName"> <valueString value="IdentifierType" /> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/elementdefinition-isCommonBinding"> <valueBoolean value="true" /> </extension> <strength value="extensible" /> <valueSet value="http://telus.com/fhir/ValueSet/telus-identifier-type" /> </binding> </element> <element id="Practitioner.identifier:JurisdictionalBillingNumber.type.coding"> <path value="Practitioner.identifier.type.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:JurisdictionalBillingNumber.type.coding.system"> <path value="Practitioner.identifier.type.coding.system" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:JurisdictionalBillingNumber.type.coding.code"> <path value="Practitioner.identifier.type.coding.code" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:JurisdictionalBillingNumber.type.coding.display"> <path value="Practitioner.identifier.type.coding.display" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:JurisdictionalBillingNumber.system"> <path value="Practitioner.identifier.system" /> <comment value="Conformance Rule: If known, this must be populated If identifier.system is urn:ietf:rfc:3986, then the identifier.value must be a full URI (e.g. start with a scheme)." /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:JurisdictionalBillingNumber.value"> <path value="Practitioner.identifier.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:LicenceNumber"> <path value="Practitioner.identifier" /> <sliceName value="LicenceNumber" /> <comment value="Conformance Rule: This will be populated with the licence numbers that are known to the EMR for this practitioner." /> </element> <element id="Practitioner.identifier:LicenceNumber.type"> <path value="Practitioner.identifier.type" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:LicenceNumber.type.coding"> <path value="Practitioner.identifier.type.coding" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:LicenceNumber.type.coding.system"> <path value="Practitioner.identifier.type.coding.system" /> <min value="1" /> <fixedUri value="http://terminology.hl7.org/CodeSystem/v2-0203" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:LicenceNumber.type.coding.code"> <path value="Practitioner.identifier.type.coding.code" /> <min value="1" /> <fixedCode value="LN" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:LicenceNumber.system"> <path value="Practitioner.identifier.system" /> <comment value="Usage Note: This value set contains the OIDs for the various licencing bodies across Canada. Identifier.system is always case sensitive." /> <min value="1" /> <mustSupport value="true" /> <binding> <strength value="extensible" /> <valueSet value="http://telus.com/fhir/ValueSet/telus-identifier-system-practitioner-ln" /> </binding> </element> <element id="Practitioner.identifier:LicenceNumber.value"> <path value="Practitioner.identifier.value" /> <comment value="Conformance Rule: This is populated with the licence number. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:LicenceNumber.assigner"> <path value="Practitioner.identifier.assigner" /> <comment value="Usage Note: A user-friendly value may be included, eg "Ontario College of Physicians and Surgeons" The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization." /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:LicenceNumber.assigner.display"> <path value="Practitioner.identifier.assigner.display" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRUserID"> <path value="Practitioner.identifier" /> <sliceName value="EMRUserID" /> <comment value="Usage Note: Each practitioner has a single user id assigned by the EMR that may be used Mapping: PSS - Table Key from the User Table" /> <max value="1" /> </element> <element id="Practitioner.identifier:EMRUserID.type"> <path value="Practitioner.identifier.type" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRUserID.type.coding"> <path value="Practitioner.identifier.type.coding" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRUserID.type.coding.system"> <path value="Practitioner.identifier.type.coding.system" /> <fixedUri value="http://terminology.hl7.org/CodeSystem/v2-0203" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRUserID.type.coding.code"> <path value="Practitioner.identifier.type.coding.code" /> <fixedCode value="USER" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRUserID.system"> <path value="Practitioner.identifier.system" /> <comment value="Conformance Rule: As this must be a unique identifier, the EMR must assign an OID or URN for their User ID's. One example of how this can be constructed as follows: Vendor.ApplicationInstance.Branch to represent the EMR User ID Identifier.system is always case sensitive." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.identifier:EMRUserID.value"> <path value="Practitioner.identifier.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.name"> <path value="Practitioner.name" /> <comment value="Conformance Rule: The discrete values (eg family and given names) should be used when known; if not only text may be used. Note: THIS IS NOT CONFORMANT WITH THE CA-CORE PROFILES, WHO MANDATE GIVEN AND FAMILY" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.name.use"> <path value="Practitioner.name.use" /> <comment value="Conformance Rule: Legal name is mandatory." /> <mustSupport value="true" /> </element> <element id="Practitioner.name.text"> <path value="Practitioner.name.text" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.name.family"> <path value="Practitioner.name.family" /> <comment value="Conformance Rule: Family is not to include professional designations. Conformance Rule: A legal name must be provided. It is not acceptable to submit all blanks/spaces." /> <mustSupport value="true" /> </element> <element id="Practitioner.name.given"> <path value="Practitioner.name.given" /> <comment value="Conformance Rule: Given name(s) is not to include profession designations If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to practical limitations. This element is not called "first name" since given names do not always come first." /> <mustSupport value="true" /> </element> <element id="Practitioner.name.prefix"> <path value="Practitioner.name.prefix" /> <comment value="Conformance Rule: Prefix must be used for Practitioner to represent the appropriate professional designation." /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.name.suffix"> <path value="Practitioner.name.suffix" /> <comment value="Conformance Rule: Suffix must be used for Practitioner to represent the appropriate professional designation." /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom"> <path value="Practitioner.telecom" /> <comment value="Usage Note: Home numbers and/or confidential numbers should never be sent in the context of exporting data as part of a patient chart export (eg referral/transfer of care or providing data for insurance purposes). Often the contact information will be part of the cover letter associated with the patient chart data that is being exported. Usage Note: If this resource is used in the context of a migration, all telecom data should be considered for the particular use case. Otherwise this is not expected to be supported. Alignment: Core-CA, PS-ON not supported Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently and to help with identification. These typically will have home numbers, or mobile numbers that are not role specific." /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom.system"> <path value="Practitioner.telecom.system" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom.value"> <path value="Practitioner.telecom.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Practitioner.telecom.use"> <path value="Practitioner.telecom.use" /> <mustSupport value="true" /> </element> <element id="Practitioner.qualification"> <path value="Practitioner.qualification" /> <comment value="Alignment: This is supported for eReferral in Ontario." /> </element> <element id="Practitioner.communication"> <path value="Practitioner.communication" /> <comment value="Alignment: This is supported for eReferral in Ontario The structure aa-BB with this exact casing is one the most widely used notations for locale. However not all systems code this but instead have it as free text. Hence CodeableConcept instead of code as the data type." /> </element> </differential> </StructureDefinition>