PackagesCanonicalsLogsProblems
    Packages
    ForgePatientChart.0830@0.1.0
    http://telus.com/fhir/patientChart/StructureDefinition/profile-encounter
{
  "description": "This profile is closely aligned with the TELUS DW profile",
  "_filename": "profile-encounter.json",
  "package_name": "ForgePatientChart.0830",
  "date": "2022-06-16T19:15:04.6499186+00:00",
  "derivation": "constraint",
  "publisher": null,
  "fhirVersion": "4.0.1",
  "name": "Encounter",
  "abstract": false,
  "type": "Encounter",
  "experimental": null,
  "resourceType": "StructureDefinition",
  "title": null,
  "package_version": "0.1.0",
  "status": "draft",
  "id": "251e9495-7ff7-44d5-ad7c-8a47f394f23d",
  "kind": "resource",
  "url": "http://telus.com/fhir/patientChart/StructureDefinition/profile-encounter",
  "version": null,
  "differential": {
    "element": [ {
      "id": "Encounter.id",
      "path": "Encounter.id",
      "mustSupport": true
    }, {
      "id": "Encounter.meta",
      "path": "Encounter.meta",
      "mustSupport": true
    }, {
      "id": "Encounter.meta.lastUpdated",
      "min": 1,
      "path": "Encounter.meta.lastUpdated",
      "mustSupport": true
    }, {
      "id": "Encounter.meta.source",
      "min": 1,
      "path": "Encounter.meta.source",
      "mustSupport": true
    }, {
      "id": "Encounter.meta.profile",
      "path": "Encounter.meta.profile",
      "comment": "Usage:   This will be determined by each implementation project.   This may be useful for validating a message instance against this profile.\r\n\r\nIt is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time.  The list of profile URLs is a set.",
      "mustSupport": true
    }, {
      "id": "Encounter.text",
      "path": "Encounter.text",
      "mustSupport": true
    }, {
      "id": "Encounter.text.status",
      "path": "Encounter.text.status",
      "mustSupport": true
    }, {
      "id": "Encounter.text.div",
      "path": "Encounter.text.div",
      "mustSupport": true
    }, {
      "id": "Encounter.identifier",
      "max": "1",
      "path": "Encounter.identifier",
      "comment": "Usage Note:   This must be sent where available; Most EMRs have a mapping to a business identifier\r\n\r\nMA:   Mapping - chainID",
      "mustSupport": true
    }, {
      "id": "Encounter.identifier.system",
      "min": 1,
      "path": "Encounter.identifier.system",
      "comment": "urn:telus:emr:::encounter\r\n\r\nIdentifier.system is always case sensitive.",
      "mustSupport": true
    }, {
      "id": "Encounter.identifier.value",
      "min": 1,
      "path": "Encounter.identifier.value",
      "comment": "Usage note: Internal primary id for this table \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": "Encounter.status",
      "path": "Encounter.status",
      "mustSupport": true
    }, {
      "id": "Encounter.class",
      "path": "Encounter.class",
      "comment": "Usage note:    If sending applicaitons are able to find it use the mapping below. If NOT then default to AMB\r\n\r\nEMR ---> FHIR \r\nClinic Visit ----> AMB\r\nVirtual Visit -----> VR\r\nHome visit/Nursing Home---> HH\r\nMobile clinics--->FLD\r\n\r\nCodes may be defined very casually in enumerations or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information.",
      "mustSupport": true
    }, {
      "id": "Encounter.class.system",
      "path": "Encounter.class.system",
      "mustSupport": true
    }, {
      "id": "Encounter.class.code",
      "min": 1,
      "path": "Encounter.class.code",
      "mustSupport": true
    }, {
      "id": "Encounter.type",
      "path": "Encounter.type",
      "comment": "Usage note: MA - N/A\r\nPSS - Note category\r\n\r\nSince there are many ways to further classify encounters, this element is 0..*.",
      "mustSupport": true
    }, {
      "id": "Encounter.type.text",
      "path": "Encounter.type.text",
      "mustSupport": true
    }, {
      "id": "Encounter.subject",
      "min": 1,
      "path": "Encounter.subject",
      "mustSupport": true
    }, {
      "id": "Encounter.subject.reference",
      "path": "Encounter.subject.reference",
      "mustSupport": true
    }, {
      "id": "Encounter.subject.display",
      "path": "Encounter.subject.display",
      "mustSupport": true
    }, {
      "id": "Encounter.participant",
      "path": "Encounter.participant",
      "comment": "Usage Note:   At a minimum, the primary participant should be indicated.    There is no current use identified for related person.\r\nUsage Note:   This is limited to specific use cases and may not be relevant to some, eg referrals",
      "mustSupport": true
    }, {
      "id": "Encounter.participant.individual",
      "path": "Encounter.participant.individual",
      "mustSupport": true
    }, {
      "id": "Encounter.participant.individual.reference",
      "path": "Encounter.participant.individual.reference",
      "mustSupport": true
    }, {
      "id": "Encounter.appointment",
      "path": "Encounter.appointment",
      "comment": "Usage note - Where applicable provide the reference to the appointment\r\nUsage Note:   This is limited to specific use cases and may not be relevant to some, eg referrals\r\n\r\nReferences SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
      "mustSupport": true
    }, {
      "id": "Encounter.appointment.reference",
      "path": "Encounter.appointment.reference",
      "mustSupport": true
    }, {
      "id": "Encounter.appointment.display",
      "path": "Encounter.appointment.display",
      "mustSupport": true
    }, {
      "id": "Encounter.period",
      "path": "Encounter.period",
      "mustSupport": true
    }, {
      "id": "Encounter.period.start",
      "path": "Encounter.period.start",
      "mustSupport": true
    }, {
      "id": "Encounter.period.end",
      "path": "Encounter.period.end",
      "mustSupport": true
    }, {
      "id": "Encounter.reasonCode",
      "path": "Encounter.reasonCode",
      "comment": "Useage note: \r\nMA - provide the reason for the visit provide by the patient i.e task concern on the left\r\nPSS - N/A\r\n\r\nFor systems that need to know which was the primary diagnosis, these will be marked with the standard extension primaryDiagnosis (which is a sequence value rather than a flag, 1 = primary diagnosis).",
      "mustSupport": true
    }, {
      "id": "Encounter.reasonCode.coding",
      "path": "Encounter.reasonCode.coding",
      "mustSupport": true
    }, {
      "id": "Encounter.reasonCode.coding.system",
      "path": "Encounter.reasonCode.coding.system",
      "mustSupport": true
    }, {
      "id": "Encounter.reasonCode.coding.code",
      "path": "Encounter.reasonCode.coding.code",
      "mustSupport": true
    }, {
      "id": "Encounter.reasonCode.text",
      "path": "Encounter.reasonCode.text",
      "mustSupport": true
    }, {
      "id": "Encounter.diagnosis",
      "path": "Encounter.diagnosis",
      "comment": "Usage note: Provide the diagnosis for the encounter if documented.   \r\nNote:   Submitted a change request to allow either a reference->condition OR a codeable concept, as often this is all that the EMR will have.",
      "mustSupport": true
    }, {
      "id": "Encounter.diagnosis.condition",
      "path": "Encounter.diagnosis.condition",
      "mustSupport": true
    }, {
      "id": "Encounter.diagnosis.condition.reference",
      "path": "Encounter.diagnosis.condition.reference",
      "mustSupport": true
    }, {
      "id": "Encounter.diagnosis.condition.display",
      "path": "Encounter.diagnosis.condition.display",
      "mustSupport": true
    }, {
      "id": "Encounter.serviceProvider",
      "path": "Encounter.serviceProvider",
      "comment": "Usage note: Reference to the organization resource that corresponds with the sub-organization where this service occured.   Note:  In the EMR, a single application can support 1..* partitioned patient groups, referred to by EMRs as locations, groups or sub-organizations.\r\n\r\nReferences SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
      "mustSupport": true
    }, {
      "id": "Encounter.serviceProvider.reference",
      "path": "Encounter.serviceProvider.reference",
      "mustSupport": true
    }, {
      "id": "Encounter.serviceProvider.display",
      "path": "Encounter.serviceProvider.display",
      "mustSupport": true
    } ]
  },
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Encounter"
}