SIMPLIFIER.NET - FHIRPath Playground

FHIRPath

If you Log in or sign up, you can edit this script yourself.

name

{
  "resourceType": "StructureDefinition",
  "id": "lz-Encounter",
  "text": {
    "status": "empty",
    "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">No narrative is provided for definitional resources. A human-readable rendering can be found in the implementation guide(s) where this resource is used.</div>"
  },
  "url": "http://medmij.nl/fhir/StructureDefinition/lz-Encounter",
  "name": "LzEncounter",
  "title": "lz Encounter",
  "status": "draft",
  "publisher": "MedMij",
  "contact": [
    {
      "name": "MedMij",
      "telecom": [
        {
          "system": "email",
          "value": "info@medmij.nl",
          "use": "work"
        }
      ]
    }
  ],
  "description": "A contact is any interaction, regardless of the situation, between a patient and the healthcare provider, in which the healthcare provider has primary responsibility for diagnosing, evaluating and treating the patient's condition and informing the patient. These can be visits, appointments or non face-to-face interactions.\n\nContacts can be visits to the general practitioner or other practices, home visits, admissions (in hospitals, nursing homes or care homes, psychiatric institutions or convalescent homes) or other relevant contacts. This includes past and future contacts.",
  "purpose": "This Encounter resource represents the Dutch [zib ('Zorginformatiebouwsteen', i.e. Health and Care Information Model) Encounter v3.1 (2017)](https://zibs.nl/wiki/Encounter-v3.1(2017EN)) adjusted such that it is suitable for implementation purposes in the context of Long-term Healthcare.\n\nThis profile is derived from the [zib-Encounter](http://nictiz.nl/fhir/StructureDefinition/zib-Encounter) profile, and differs from the latter profile in the sense that it can be used for future encounters as well as past encounters. This aligns with zib publication 2020. Strictly speaking, the change made in this profile is incompatible with the zib-Encounter profile. However, since the latter profile does not technically enforce contacts to be in the past, it could be used as a base for this profile.",
  "copyright": "Copyright and related rights waived via CC0, https://creativecommons.org/publicdomain/zero/1.0/. This does not apply to information from third parties, for example a medical terminology system. The implementer alone is responsible for identifying and obtaining any necessary licenses or authorizations to utilize third party IP in connection with the specification or otherwise.",
  "fhirVersion": "3.0.2",
  "mapping": [
    {
      "identity": "hcim-encounter-v3.1-2017EN",
      "uri": "https://zibs.nl/wiki/Encounter-v3.1(2017EN)",
      "name": "HCIM Encounter-v3.1(2017EN)"
    }
  ],
  "kind": "resource",
  "abstract": false,
  "type": "Encounter",
  "baseDefinition": "http://nictiz.nl/fhir/StructureDefinition/zib-Encounter",
  "derivation": "constraint",
  "differential": {
    "element": [
      {
        "id": "Encounter.status",
        "path": "Encounter.status",
        "comment": "This element is implictly mapped to the zib concepts NL-CM:15.1.3 (StartDateTime) and NL-CM:15.1.4 (EndDateTime), with the exception that the StartDateTime may attain a value in the future (which functionally is a pre-adopt of zib release 2020). Unless the status is explicitly recorded, the following guidance applies:\n\n* When StartDateTime is in the future, `.status` will usually be set to _planned_.\n* When StartDateTime is in the past and EndDateTime is present and in the future, `.status` will usually be set to _in-progress_.\n* When EndDateTime is present and in the past, `.status` will usually be set to _finished_.\n* When EndDateTime is not present, this means it was a point-in-time encounter and `.status` will usually be set to _finished_.\n* When a system is unable to infer the status from the StartDateTime and EndDateTime, `.status` will be set to _unknown_.\n\nThe _unknown_ code is not to be used to convey other statuses. The _unknown_ code should be used when one of the statuses applies, but the authoring system doesn't know the current state of the procedure.\n\nThis element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.",
        "mapping": [
          {
            "identity": "hcim-encounter-v3.1-2017EN",
            "map": "NL-CM:15.1.3",
            "comment": "StartDateTime (implicit, main mapping is on `Encounter.period.start`)"
          },
          {
            "identity": "hcim-encounter-v3.1-2017EN",
            "map": "NL-CM:15.1.4",
            "comment": "EndDateTime (implicit, main mapping is on `Encounter.period.end`)"
          }
        ]
      },
      {
        "id": "Encounter.period.start",
        "path": "Encounter.period.start",
        "definition": "The date and time at which the contact took or will take place.",
        "comment": "Note that this element may attain a value in the future (which functionally is a pre-adopt of zib release 2020), contrary to the [zib-Encounter](http://nictiz.nl/fhir/StructureDefinition/zib-Encounter) profile."
      }
    ]
  }
}

name : LzEncounter

{

}