PackagesCanonicalsLogsProblems
    Packages
    ForgePatientChart.0830@0.1.0
    http://telus.com/fhir/patientChart/StructureDefinition/profile-practitioner
{
  "description": null,
  "_filename": "profile-practitioner.StructureDefinition.json",
  "package_name": "ForgePatientChart.0830",
  "date": "2020-11-10T21:07:38.2646453+00:00",
  "derivation": "constraint",
  "meta": {
    "versionId": "1",
    "lastUpdated": "2022-08-10T17:34:21.9601358+00:00"
  },
  "publisher": null,
  "fhirVersion": "4.0.1",
  "name": "Practitioner",
  "mapping": [ {
    "uri": "http://hl7.org/v2",
    "name": "HL7 v2 Mapping",
    "identity": "v2"
  }, {
    "uri": "http://hl7.org/v3",
    "name": "RIM Mapping",
    "identity": "rim"
  }, {
    "uri": "http://www.omg.org/spec/ServD/1.0/",
    "name": "ServD",
    "identity": "servd"
  }, {
    "uri": "http://hl7.org/fhir/fivews",
    "name": "FiveWs Pattern Mapping",
    "identity": "w5"
  } ],
  "abstract": false,
  "type": "Practitioner",
  "experimental": null,
  "resourceType": "StructureDefinition",
  "title": "TELUS Practitioner",
  "package_version": "0.1.0",
  "status": "draft",
  "id": "a2dd8008-5a59-4877-99b9-73559f200646",
  "kind": "resource",
  "url": "http://telus.com/fhir/patientChart/StructureDefinition/profile-practitioner",
  "version": null,
  "differential": {
    "element": [ {
      "id": "Practitioner",
      "path": "Practitioner",
      "comment": "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": true
    }, {
      "id": "Practitioner.meta",
      "path": "Practitioner.meta",
      "mustSupport": true
    }, {
      "id": "Practitioner.meta.lastUpdated",
      "path": "Practitioner.meta.lastUpdated",
      "mustSupport": true
    }, {
      "id": "Practitioner.meta.source",
      "path": "Practitioner.meta.source",
      "mustSupport": true
    }, {
      "id": "Practitioner.meta.profile",
      "path": "Practitioner.meta.profile",
      "mustSupport": true
    }, {
      "id": "Practitioner.text",
      "path": "Practitioner.text",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier",
      "path": "Practitioner.identifier",
      "comment": "Usage Rule:   This is used for both licenced clinicians and EMR Users/MOAs\r\n\r\nConformance Rule: The must be the TPR identifier (CPRID) if the practitioner is the initiating practitioner for the tasks in a message. The TPR identifier (CPRID) SHOULD be sent if known if the practitioner is being sent for other purposes.\r\n\r\nConformance Rule:  For non-clinican users, this must be populated with a unique user identifier issued by the EMR\r\n\r\nConformance Rule:   The licence numbers must be conveyed if known",
      "slicing": {
        "rules": "open",
        "discriminator": [ {
          "path": "type",
          "type": "pattern"
        } ]
      },
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier.use",
      "path": "Practitioner.identifier.use",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier.type",
      "path": "Practitioner.identifier.type",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier.system",
      "min": 1,
      "path": "Practitioner.identifier.system",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier.value",
      "min": 1,
      "path": "Practitioner.identifier.value",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRProviderID",
      "path": "Practitioner.identifier",
      "comment": "Usage Note:    A practitioner may have multiples; one per bill book.  eg Provider ID in PSS, is issued per bill book.",
      "sliceName": "EMRProviderID",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRProviderID.type",
      "path": "Practitioner.identifier.type",
      "binding": {
        "strength": "extensible",
        "valueSet": "http://telus.com/fhir/ValueSet/telus-identifier-type"
      },
      "mustSupport": true,
      "patternCodeableConcept": {
        "coding": [ {
          "code": "PRN",
          "system": "http://terminology.hl7.org/CodeSystem/v2-0203"
        } ]
      }
    }, {
      "id": "Practitioner.identifier:EMRProviderID.type.coding",
      "max": "1",
      "min": 1,
      "path": "Practitioner.identifier.type.coding",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRProviderID.type.coding.system",
      "min": 1,
      "path": "Practitioner.identifier.type.coding.system",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRProviderID.type.coding.code",
      "min": 1,
      "path": "Practitioner.identifier.type.coding.code",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRProviderID.system",
      "min": 1,
      "path": "Practitioner.identifier.system",
      "comment": "Usage Note:  Typically this can be constructed as follows:   Vendor.ApplicationInstance.Branch to represent the EMR User ID\r\n\r\nIdentifier.system is always case sensitive.",
      "fixedUri": "http://telus.com/fhir/Identifiers/TPR",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRProviderID.value",
      "min": 1,
      "path": "Practitioner.identifier.value",
      "comment": "Conformance Rule: This must match the Practitioner.id value.",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:JurisdictionalBillingNumber",
      "max": "1",
      "path": "Practitioner.identifier",
      "comment": "Usage Note:   Thee may be some use cases that will require this idnetifier.    This only applies to physicians, not to nurse practitioners or other clinicians.",
      "sliceName": "JurisdictionalBillingNumber",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:JurisdictionalBillingNumber.type",
      "min": 1,
      "path": "Practitioner.identifier.type",
      "binding": {
        "strength": "extensible",
        "valueSet": "http://telus.com/fhir/ValueSet/telus-identifier-type"
      },
      "mustSupport": true,
      "patternCodeableConcept": {
        "coding": [ {
          "code": "MCR",
          "system": "http://terminology.hl7.org/CodeSystem/v2-0203"
        } ]
      }
    }, {
      "id": "Practitioner.identifier:JurisdictionalBillingNumber.type.coding",
      "max": "1",
      "min": 1,
      "path": "Practitioner.identifier.type.coding",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:JurisdictionalBillingNumber.type.coding.system",
      "path": "Practitioner.identifier.type.coding.system",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:JurisdictionalBillingNumber.type.coding.code",
      "path": "Practitioner.identifier.type.coding.code",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:JurisdictionalBillingNumber.type.coding.display",
      "path": "Practitioner.identifier.type.coding.display",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:JurisdictionalBillingNumber.system",
      "path": "Practitioner.identifier.system",
      "comment": "Conformance Rule: If known, this must be populated\r\n\r\nIf identifier.system is urn:ietf:rfc:3986, then the identifier.value must be a full URI (e.g. start with a scheme).",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:JurisdictionalBillingNumber.value",
      "min": 1,
      "path": "Practitioner.identifier.value",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:LicenceNumber",
      "path": "Practitioner.identifier",
      "comment": "Conformance Rule:   This will be populated with the licence numbers that are known to the EMR for this practitioner.",
      "sliceName": "LicenceNumber"
    }, {
      "id": "Practitioner.identifier:LicenceNumber.type",
      "min": 1,
      "path": "Practitioner.identifier.type",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:LicenceNumber.type.coding",
      "max": "1",
      "min": 1,
      "path": "Practitioner.identifier.type.coding",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:LicenceNumber.type.coding.system",
      "min": 1,
      "path": "Practitioner.identifier.type.coding.system",
      "fixedUri": "http://terminology.hl7.org/CodeSystem/v2-0203",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:LicenceNumber.type.coding.code",
      "min": 1,
      "path": "Practitioner.identifier.type.coding.code",
      "fixedCode": "LN",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:LicenceNumber.system",
      "min": 1,
      "path": "Practitioner.identifier.system",
      "binding": {
        "strength": "extensible",
        "valueSet": "http://telus.com/fhir/ValueSet/telus-identifier-system-practitioner-ln"
      },
      "comment": "Usage Note:   This value set contains the OIDs for the various licencing bodies across Canada.\r\n\r\nIdentifier.system is always case sensitive.",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:LicenceNumber.value",
      "min": 1,
      "path": "Practitioner.identifier.value",
      "comment": "Conformance Rule:   This is populated with the licence number.\r\n\r\nIf 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.",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:LicenceNumber.assigner",
      "path": "Practitioner.identifier.assigner",
      "comment": "Usage Note:   A user-friendly value may be included, eg \"Ontario College of Physicians and Surgeons\"\r\n\r\nThe 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": true
    }, {
      "id": "Practitioner.identifier:LicenceNumber.assigner.display",
      "path": "Practitioner.identifier.assigner.display",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRUserID",
      "max": "1",
      "path": "Practitioner.identifier",
      "comment": "Conformance Rule:   Each practitioner has a single user id.   .\r\nMapping:   PSS - Table Key from the User Table",
      "sliceName": "EMRUserID"
    }, {
      "id": "Practitioner.identifier:EMRUserID.type",
      "path": "Practitioner.identifier.type",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRUserID.type.coding",
      "path": "Practitioner.identifier.type.coding",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRUserID.type.coding.system",
      "path": "Practitioner.identifier.type.coding.system",
      "fixedUri": "http://terminology.hl7.org/CodeSystem/v2-0203",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRUserID.type.coding.code",
      "path": "Practitioner.identifier.type.coding.code",
      "fixedCode": "USER",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRUserID.system",
      "min": 1,
      "path": "Practitioner.identifier.system",
      "comment": "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\r\n\r\nIdentifier.system is always case sensitive.",
      "mustSupport": true
    }, {
      "id": "Practitioner.identifier:EMRUserID.value",
      "min": 1,
      "path": "Practitioner.identifier.value",
      "mustSupport": true
    }, {
      "id": "Practitioner.name",
      "max": "1",
      "min": 1,
      "path": "Practitioner.name",
      "comment": "Conformance Rule: The discrete values (eg family and given names) should be used when known; if not only text may be used.\r\n\r\nNote:   THIS IS NOT CONFORMANT WITH THE CA-CORE PROFILES, WHO MANDATE GIVEN AND FAMILY",
      "mustSupport": true
    }, {
      "id": "Practitioner.name.use",
      "path": "Practitioner.name.use",
      "comment": "Conformance Rule: Legal name is mandatory.",
      "mustSupport": true
    }, {
      "id": "Practitioner.name.text",
      "min": 1,
      "path": "Practitioner.name.text",
      "mustSupport": true
    }, {
      "id": "Practitioner.name.family",
      "path": "Practitioner.name.family",
      "comment": "Conformance Rule: Family is not to include professional designations.\r\n\r\nConformance Rule: A legal name must be provided. It is not acceptable to submit all blanks/spaces.",
      "mustSupport": true
    }, {
      "id": "Practitioner.name.given",
      "path": "Practitioner.name.given",
      "comment": "Conformance Rule: Given name(s) is not to include profession designations\r\n\r\nIf 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": true
    }, {
      "id": "Practitioner.name.prefix",
      "max": "1",
      "path": "Practitioner.name.prefix",
      "comment": "Conformance Rule: Prefix must be used for Practitioner to represent the appropriate professional designation.",
      "mustSupport": true
    }, {
      "id": "Practitioner.name.suffix",
      "max": "1",
      "path": "Practitioner.name.suffix",
      "comment": "Conformance Rule: Suffix must be used for Practitioner to represent the appropriate professional designation.",
      "mustSupport": true
    }, {
      "id": "Practitioner.telecom",
      "path": "Practitioner.telecom",
      "comment": "Usage Note:    Home numbers and/or confidential numbers should never be automatically 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.\r\n\r\nUsage Note:  If this resource is used in the context of a migration, all telecom data should be considered for the particular use case.    \r\n\r\nPerson 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": true
    }, {
      "id": "Practitioner.telecom.system",
      "min": 1,
      "path": "Practitioner.telecom.system",
      "mustSupport": true
    }, {
      "id": "Practitioner.telecom.value",
      "min": 1,
      "path": "Practitioner.telecom.value",
      "mustSupport": true
    }, {
      "id": "Practitioner.telecom.use",
      "path": "Practitioner.telecom.use",
      "mustSupport": true
    } ]
  },
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Practitioner"
}