SIMPLIFIER.NET - FHIRPath Playground

FHIRPath

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

{
  "resourceType": "StructureDefinition",
  "id": "cyehr-sd-visitsummary-r4",
  "url": "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-visitsummary-r4",
  "name": "CYEHRSDVisitSummary",
  "title": "Cyprus EHR Visit Summary profile",
  "status": "draft",
  "publisher": "eHealth4U",
  "contact": [
    {
      "name": "eHealth Lab",
      "telecom": [
        {
          "system": "email",
          "value": "ehealthl@ucy.ac.cy",
          "use": "work"
        }
      ]
    }
  ],
  "description": "Clinical document used to represent a Progress Note describing a visit/encounter. For Phase I, the progress report is mainly used to describe the summary of a visit for outpatient purposes as part of the prototype of the national integrated EHR of Cyprus. The main use-case of this profile is to record all the necessary data describing the actions taken for the patient and/or the findings that were identified during a visit/encounter as part of an episode of care.",
  "fhirVersion": "4.0.1",
  "kind": "resource",
  "abstract": false,
  "type": "Composition",
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/clinicaldocument",
  "derivation": "constraint",
  "differential": {
    "element": [
      {
        "id": "Composition.meta",
        "path": "Composition.meta"
      },
      {
        "id": "Composition.meta.profile",
        "path": "Composition.meta.profile",
        "slicing": {
          "discriminator": [
            {
              "type": "value",
              "path": "$this"
            }
          ],
          "rules": "open"
        },
        "min": 1
      },
      {
        "id": "Composition.meta.profile:CyprusEHRProfile",
        "path": "Composition.meta.profile",
        "sliceName": "CyprusEHRProfile",
        "min": 1,
        "max": "1",
        "fixedCanonical": "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-visitsummary-r4"
      },
      {
        "id": "Composition.language",
        "path": "Composition.language",
        "mustSupport": true,
        "binding": {
          "strength": "required",
          "valueSet": "http://ig.ehealth4u.eu/fhir/ValueSet/cyehr-vs-ehdsilanguage"
        }
      },
      {
        "id": "Composition.text",
        "path": "Composition.text",
        "mustSupport": true
      },
      {
        "id": "Composition.extension",
        "path": "Composition.extension",
        "slicing": {
          "discriminator": [
            {
              "type": "value",
              "path": "url"
            }
          ],
          "rules": "open"
        },
        "min": 0
      },
      {
        "id": "Composition.extension:versionNumber",
        "path": "Composition.extension",
        "sliceName": "versionNumber",
        "min": 0,
        "mustSupport": true
      },
      {
        "id": "Composition.identifier",
        "path": "Composition.identifier",
        "definition": "A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time.\r\n\r\nCyprusEHR: The National eHealth Authority OID indicating that this is a visit summary document.",
        "comment": "Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.\r\n\r\nCyprusEHR: This SHALL be used for the visit summaries of the national integrated EHR of Cyprus.",
        "patternIdentifier": {
          "use": "official",
          "system": "urn:oid:2.16.840.1.113883.3.9143.5.3.1"
        },
        "mustSupport": true
      },
      {
        "id": "Composition.identifier.use",
        "path": "Composition.identifier.use",
        "min": 1
      },
      {
        "id": "Composition.identifier.system",
        "path": "Composition.identifier.system",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Composition.identifier.value",
        "path": "Composition.identifier.value",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Composition.status",
        "path": "Composition.status",
        "fixedCode": "final",
        "mustSupport": true
      },
      {
        "id": "Composition.type",
        "path": "Composition.type",
        "comment": "For Composition type, LOINC is ubiquitous and strongly endorsed by HL7. Most implementation guides will require a specific LOINC code, or use LOINC as an extensible binding.\r\n\r\nCyprusEHR: Following to the LOINC description as adopted by HL7 in http://www.hl7.org/ccdasearch/templates/2.16.840.1.113883.10.20.22.1.9.html (as part of https://www.hl7.org/implement/standards/product_brief.cfm?product_id=492) and according to the guidelines given by the commonwell health aliance for care quality in their document \"Concise Consolidated CDA: Deploying Encounter Summary and Patient Summary Documents with Clinical Notes\" in March 2022, the Progress Note is defined as the following:\r\n\r\n\"This template represents a patient's clinical status during a hospitalization, outpatient visit, treatment with a LTPAC provider, or other healthcare encounter. Taber's medical dictionary defines a Progress Note as 'An ongoing record of a patient's illness and treatment. Physicians, nurses, consultants, and therapists record their notes concerning the progress or lack of progress made by the patient between the time of the previous note and the most recent note.'\r\nMosby's medical dictionary defines a Progress Note as 'Notes made by a nurse, physician, social worker, physical therapist, and other health care professionals that describe the patient's condition and the treatment given or planned.' A Progress Note is not a re-evaluation note. A Progress Note is not intended to be a Progress Report for Medicare. Medicare B Section 1833(e) defines the requirements of a Medicare Progress Report.\"\r\n\r\nAll CYEHRSDVisitSummary instances must include the type.code = loinc.org/11506-3 for \"Progress note\" since they are all considered progress notes including the summary of a visit/encounter created in the context of a specific episode of care  (see more here: https://motorcycleguy.blogspot.com/2010/08/whats-diff.html). \r\n\r\nMore refining codings are allowed like: loinc.org/34131-3 for \"Outpatient Progress note\" (a summarization of an outpatient visit/encounter ). More loinc codes describing progress notes can be found here:  https://hl7.org/fhir/us/ccda/ValueSet-2.16.840.1.113883.11.20.8.1.html .",
        "type": [
          {
            "code": "CodeableConcept",
            "profile": [
              "http://hl7.org/fhir/uv/ips/StructureDefinition/CodeableConcept-uv-ips"
            ]
          }
        ],
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "11506-3"
            }
          ]
        },
        "mustSupport": true,
        "binding": {
          "strength": "extensible"
        }
      },
      {
        "id": "Composition.type.coding",
        "path": "Composition.type.coding",
        "slicing": {
          "discriminator": [
            {
              "type": "pattern",
              "path": "$this"
            }
          ],
          "rules": "open"
        },
        "min": 1
      },
      {
        "id": "Composition.type.coding.system",
        "path": "Composition.type.coding.system",
        "min": 1
      },
      {
        "id": "Composition.type.coding.code",
        "path": "Composition.type.coding.code",
        "min": 1
      },
      {
        "id": "Composition.type.coding.display",
        "path": "Composition.type.coding.display",
        "min": 1
      },
      {
        "id": "Composition.type.coding:outpatientVisitSummary",
        "path": "Composition.type.coding",
        "sliceName": "outpatientVisitSummary",
        "min": 1,
        "max": "1",
        "patternCoding": {
          "system": "http://loinc.org",
          "code": "34131-3"
        }
      },
      {
        "id": "Composition.type.coding:outpatientVisitSummary.system",
        "path": "Composition.type.coding.system",
        "min": 1
      },
      {
        "id": "Composition.type.coding:outpatientVisitSummary.code",
        "path": "Composition.type.coding.code",
        "min": 1
      },
      {
        "id": "Composition.type.coding:outpatientVisitSummary.display",
        "path": "Composition.type.coding.display",
        "min": 1
      },
      {
        "id": "Composition.category",
        "path": "Composition.category",
        "slicing": {
          "discriminator": [
            {
              "type": "type",
              "path": "$this"
            }
          ],
          "rules": "open"
        },
        "short": "Visit Summary categories",
        "definition": "A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type.\r\n\r\nCyprusEHR: Specifies the category of the Visit Summary. The general term \"Visit Summary\" is expected to be used and where applicable a more refiend term can be additionally used.",
        "comment": "This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD)).\r\n\r\nCyprusEHR: For CYEHR the term http://loinc.org/34133-9 for \"Summarization of episode note\"  will be the only coding used for the created progress notes as they are partly used to describe the an episode of care (the summary of an episode's of care visit).",
        "min": 1,
        "type": [
          {
            "code": "CodeableConcept",
            "profile": [
              "http://hl7.org/fhir/uv/ips/StructureDefinition/CodeableConcept-uv-ips"
            ]
          }
        ],
        "mustSupport": true,
        "binding": {
          "strength": "extensible"
        }
      },
      {
        "id": "Composition.category.coding.system",
        "path": "Composition.category.coding.system",
        "min": 1
      },
      {
        "id": "Composition.category.coding.code",
        "path": "Composition.category.coding.code",
        "min": 1
      },
      {
        "id": "Composition.category.coding.display",
        "path": "Composition.category.coding.display",
        "min": 1
      },
      {
        "id": "Composition.category:visitSummary",
        "path": "Composition.category",
        "sliceName": "visitSummary",
        "short": "Summary of an episode of care",
        "definition": "A categorization for the type of the composition - helps for indexing and searching. This may be implied by or derived from the code specified in the Composition Type.\r\n\r\nCyprusEHR: This category indicates that this composition profile represents a progress note on a visit as part of an episode of care. The progress not can be used to give a synopsis of a patient's outpatient visit.",
        "max": "1",
        "type": [
          {
            "code": "CodeableConcept",
            "profile": [
              "http://hl7.org/fhir/uv/ips/StructureDefinition/CodeableConcept-uv-ips"
            ]
          }
        ],
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "34133-9"
            }
          ]
        },
        "mustSupport": true,
        "binding": {
          "strength": "extensible"
        }
      },
      {
        "id": "Composition.category:visitSummary.coding",
        "path": "Composition.category.coding",
        "min": 1
      },
      {
        "id": "Composition.category:visitSummary.coding.system",
        "path": "Composition.category.coding.system",
        "min": 1
      },
      {
        "id": "Composition.category:visitSummary.coding.code",
        "path": "Composition.category.coding.code",
        "min": 1
      },
      {
        "id": "Composition.category:visitSummary.coding.display",
        "path": "Composition.category.coding.display",
        "min": 1
      },
      {
        "id": "Composition.subject",
        "path": "Composition.subject",
        "short": "Who the Visit Summary is about",
        "definition": "CyprusEHR: The visit summary is about a patient to give a synopsis of his/her health data as recorded during his/her admission to a hospital or visit to an outpatient doctor as part of an encounter.",
        "min": 1,
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-patient"
            ]
          }
        ],
        "mustSupport": true
      },
      {
        "id": "Composition.subject.reference",
        "path": "Composition.subject.reference",
        "min": 1
      },
      {
        "id": "Composition.encounter",
        "path": "Composition.encounter",
        "short": "Encounter associated with this visit summary",
        "min": 1,
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-encounter-r4"
            ]
          }
        ],
        "mustSupport": true
      },
      {
        "id": "Composition.encounter.reference",
        "path": "Composition.encounter.reference",
        "min": 1
      },
      {
        "id": "Composition.date",
        "path": "Composition.date",
        "mustSupport": true
      },
      {
        "id": "Composition.author",
        "path": "Composition.author",
        "short": "Who and/or what authored the visit summary",
        "definition": "CyprusEHR: Identifies who is responsible for the information in the visit summary, not necessarily who typed it in.",
        "comment": "References 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.\r\n\r\nCyprusEHR: In the case where a Practitioner has authored the visit summary, the corresponding CYEHRSDPractitionerRole shall be used.",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-practitionerrolehealthcareassociate-r4",
              "http://hl7.org/fhir/StructureDefinition/Device"
            ]
          }
        ],
        "mustSupport": true
      },
      {
        "id": "Composition.author.reference",
        "path": "Composition.author.reference",
        "min": 1
      },
      {
        "id": "Composition.title",
        "path": "Composition.title",
        "definition": "Official human-readable label for the visit summary.",
        "fixedString": "Visit Summary",
        "mustSupport": true
      },
      {
        "id": "Composition.confidentiality",
        "path": "Composition.confidentiality",
        "comment": "The exact use of this element, and enforcement and issues related to highly sensitive documents are out of scope for the base specification, and delegated to implementation profiles (see security section).  This element is labeled as a modifier because highly confidential documents must not be treated as if they are not.\r\n\r\nCyprusEHR: Following the eHSDI MVC corresponding value set (eHDSIConfidentiality) use only the following codes for the national Integrated EHR system of Cyprus: \r\n* N (display: normal)\r\n* R (display: restricted)\r\n* V (display: very restricted)\r\n\r\nFor Phase I: not to be used.",
        "binding": {
          "strength": "required",
          "description": "Codes specifying the level of confidentiality of the composition (eHDSI MVC compatible)"
        }
      },
      {
        "id": "Composition.attester",
        "path": "Composition.attester",
        "mustSupport": true
      },
      {
        "id": "Composition.attester.mode",
        "path": "Composition.attester.mode",
        "mustSupport": true
      },
      {
        "id": "Composition.attester.time",
        "path": "Composition.attester.time",
        "mustSupport": true
      },
      {
        "id": "Composition.attester.party",
        "path": "Composition.attester.party",
        "comment": "References 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.\r\n\r\nCyprusEHR: For the visit summary created by the national integrated EHR of Cyprus, the practitionerRole of a doctor will be referenced to indicate the attester.",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://hl7.org/fhir/StructureDefinition/PractitionerRole",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-practitionerrole-r4",
              "http://hl7.org/fhir/StructureDefinition/Practitioner",
              "http://hl7.org/fhir/StructureDefinition/Organization",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-practitioner-r4",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-organization-r4"
            ]
          }
        ],
        "mustSupport": true
      },
      {
        "id": "Composition.attester.party.reference",
        "path": "Composition.attester.party.reference",
        "min": 1
      },
      {
        "id": "Composition.custodian",
        "path": "Composition.custodian",
        "short": "National eHealth Authority of Cyprus",
        "definition": "Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information.\r\n\r\nCyprusEHR: The National eHealth Authority of Cyprus which is the custodian of the visit summaries that are stored in the national integrated EHR system of Cyprus.",
        "comment": "This is useful when documents are derived from a composition - provides guidance for how to get the latest version of the document. This is optional because this is sometimes not known by the authoring system, and can be inferred by context. However, it is important that this information be known when working with a derived document, so providing a custodian is encouraged.\r\n\r\nCyprusEHR: Every visit summary stored in the national integrated EHR of Cyprus SHALL have as custodian the NeHA.",
        "mustSupport": true
      },
      {
        "id": "Composition.custodian.reference",
        "path": "Composition.custodian.reference",
        "min": 1
      },
      {
        "id": "Composition.custodian.identifier",
        "path": "Composition.custodian.identifier",
        "patternIdentifier": {
          "use": "official",
          "system": "urn:ietf:rfc:3986",
          "value": "urn:oid:2.16.840.1.113883.3.9143.1.1"
        }
      },
      {
        "id": "Composition.custodian.display",
        "path": "Composition.custodian.display",
        "fixedString": "National eHealth Authority of Cyprus"
      },
      {
        "id": "Composition.relatesTo",
        "path": "Composition.relatesTo",
        "comment": "A document is a version specific composition.\r\n\r\nCyprusEHR: Not to be used in the context of Cyprus EHR."
      },
      {
        "id": "Composition.event",
        "path": "Composition.event",
        "comment": "The event needs to be consistent with the type element, though can provide further information if desired.\r\n\r\nCyprusEHR: Not to be used in the context of Cyprus EHR."
      },
      {
        "id": "Composition.section",
        "path": "Composition.section",
        "slicing": {
          "discriminator": [
            {
              "type": "pattern",
              "path": "code"
            }
          ],
          "rules": "open"
        },
        "short": "Sections composing the Visit Summary",
        "definition": "The root of the sections that make up the visit summary.\r\n\r\nCyprusEHR: The structure of the sections composing the CYEHRSDVisitSummary is designed in a way to be conformant with the XeHealth Discharge Report.",
        "min": 2,
        "mustSupport": true
      },
      {
        "id": "Composition.section.title",
        "path": "Composition.section.title",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Composition.section.code",
        "path": "Composition.section.code",
        "min": 1,
        "type": [
          {
            "code": "CodeableConcept",
            "profile": [
              "http://hl7.org/fhir/uv/ips/StructureDefinition/CodeableConcept-uv-ips"
            ]
          }
        ],
        "mustSupport": true
      },
      {
        "id": "Composition.section.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1
      },
      {
        "id": "Composition.section.code.coding.system",
        "path": "Composition.section.code.coding.system",
        "min": 1
      },
      {
        "id": "Composition.section.code.coding.code",
        "path": "Composition.section.code.coding.code",
        "min": 1
      },
      {
        "id": "Composition.section.code.coding.display",
        "path": "Composition.section.code.coding.display",
        "min": 1
      },
      {
        "id": "Composition.section.author",
        "path": "Composition.section.author",
        "comment": "References 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.\r\n\r\nCyprusEHR: For Phase I it is expected that all sections of the visit are authored by the same practitioner and threfore this element shall not be used for now."
      },
      {
        "id": "Composition.section.author.reference",
        "path": "Composition.section.author.reference",
        "comment": "Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries.   Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure \"/[type]/[id]\" then it should be assumed that the reference is to a FHIR RESTful server.\r\n\r\nCyprusEHR: Not to be used in the context of Cyprus EHR (Phase I).",
        "min": 1
      },
      {
        "id": "Composition.section.focus",
        "path": "Composition.section.focus",
        "comment": "Typically, sections in a doument are about the subject of the document, whether that is a  patient, or group of patients, location, or device, or whatever. For some kind of documents, some sections actually contain data about related entities. Typical examples are  a section in a newborn discharge summary concerning the mother, or family history documents, with a section about each family member, though there are many other examples.\r\n\r\nCyprusEHR: Not to be used in the context of Cyprus EHR."
      },
      {
        "id": "Composition.section.text",
        "path": "Composition.section.text",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Composition.section.mode",
        "path": "Composition.section.mode",
        "comment": "This element is labeled as a modifier because a change list must not be misunderstood as a complete list.\r\n\r\nCyprusEHR: Not to be used in the context of Cyprus EHR."
      },
      {
        "id": "Composition.section.orderedBy",
        "path": "Composition.section.orderedBy",
        "comment": "Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.\r\n\r\nCyprusEHR: Not to be used in the context of Cyprus EHR."
      },
      {
        "id": "Composition.section.entry",
        "path": "Composition.section.entry",
        "mustSupport": true
      },
      {
        "id": "Composition.section.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Composition.section.section",
        "path": "Composition.section.section",
        "comment": "Nested sections are primarily used to help human readers navigate to particular portions of the document.\r\n\r\nCyprusEHR: Not to be used in the context of Cyprus EHR."
      },
      {
        "id": "Composition.section:sectionAdmissionCause",
        "path": "Composition.section",
        "sliceName": "sectionAdmissionCause",
        "short": "Visit's Admission Cause section",
        "definition": "The root of the sections that make up the composition.\r\n\r\nCyprusEHR: Chief Complaint and Reason for visit",
        "max": "1",
        "mustSupport": true
      },
      {
        "id": "Composition.section:sectionAdmissionCause.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use \"Admission Cause\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAdmissionCause.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "46239-0"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionAdmissionCause.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionAdmissionCause.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAdmissionCause.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-problem-r4"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionAdmissionCause.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionTravelHistory",
        "path": "Composition.section",
        "sliceName": "sectionTravelHistory",
        "short": "History of Travel section",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionTravelHistory.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use \"Travel History\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionTravelHistory.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "10182-4"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionTravelHistory.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionTravelHistory.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionTravelHistory.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-travelhistory"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionTravelHistory.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAllergies",
        "path": "Composition.section",
        "sliceName": "sectionAllergies",
        "short": "History of Allergies and Intolerances section",
        "definition": "The root of the sections that make up the composition.\r\n\r\nCyprusEHR: Contains a list and description of any allergies or adverse reactions pertinent to current or past medical history. At a minimum this section should contain currently active and any relevant historical allergies and adverse reactions (term description by LOINC).",
        "comment": "CyprusEHR: This section is designed in a way to be conformant with the sectionAllergies from XeHealth Discharge Report.",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionAllergies.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Allergies and Intolerances\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAllergies.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "48765-2"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionAllergies.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionAllergies.code.coding.display",
        "path": "Composition.section.code.coding.display",
        "comment": "Note that FHIR strings SHALL NOT exceed 1MB in size\r\n\r\nCyprusEHR: Display is optional due to the conformance requirement with the XeHealth DischargeReport.sectionAllergies.code.coding"
      },
      {
        "id": "Composition.section:sectionAllergies.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAllergies.entry",
        "path": "Composition.section.entry",
        "slicing": {
          "discriminator": [
            {
              "type": "type",
              "path": "resolve()"
            }
          ],
          "rules": "open"
        },
        "min": 1
      },
      {
        "id": "Composition.section:sectionAllergies.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAllergies.entry:AllergyAndIntolerance",
        "path": "Composition.section.entry",
        "sliceName": "AllergyAndIntolerance",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://hl7.org/fhir/StructureDefinition/AllergyIntolerance"
            ]
          }
        ],
        "mustSupport": true
      },
      {
        "id": "Composition.section:sectionAllergies.entry:AllergyAndIntolerance.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionResolvedClosedInactiveProblems",
        "path": "Composition.section",
        "sliceName": "sectionResolvedClosedInactiveProblems",
        "short": "History of Resolved, Closed or Inactive Problems section",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionResolvedClosedInactiveProblems.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Resolved, Closed and Inactive Problems\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionResolvedClosedInactiveProblems.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "11348-0"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionResolvedClosedInactiveProblems.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionResolvedClosedInactiveProblems.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionResolvedClosedInactiveProblems.entry",
        "path": "Composition.section.entry",
        "min": 1,
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-problem-r4",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-diagnosis-r4"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionResolvedClosedInactiveProblems.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionProcedures",
        "path": "Composition.section",
        "sliceName": "sectionProcedures",
        "short": "History of Procedures section",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionProcedures.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Procedures\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionProcedures.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "29554-3"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionProcedures.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionProcedures.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionProcedures.entry",
        "path": "Composition.section.entry",
        "min": 1,
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-procedure-r4"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionProcedures.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionFunctionalStatus",
        "path": "Composition.section",
        "sliceName": "sectionFunctionalStatus",
        "short": "History of Functional Status section",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionFunctionalStatus.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Functional Status\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionFunctionalStatus.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "47420-5"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionFunctionalStatus.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionFunctionalStatus.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionFunctionalStatus.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://hl7.org/fhir/StructureDefinition/Observation"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionFunctionalStatus.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionMedicalDevicesImplants",
        "path": "Composition.section",
        "sliceName": "sectionMedicalDevicesImplants",
        "short": "History of Medical Devices and Implants section",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionMedicalDevicesImplants.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Medical Devices and Implants\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionMedicalDevicesImplants.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "46264-8"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionMedicalDevicesImplants.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionMedicalDevicesImplants.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionMedicalDevicesImplants.entry",
        "path": "Composition.section.entry",
        "slicing": {
          "discriminator": [
            {
              "type": "type",
              "path": "$this"
            }
          ],
          "rules": "open"
        }
      },
      {
        "id": "Composition.section:sectionMedicalDevicesImplants.entry:medicalDeviceImplant",
        "path": "Composition.section.entry",
        "sliceName": "medicalDeviceImplant",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-device-r4"
            ]
          }
        ],
        "mustSupport": true
      },
      {
        "id": "Composition.section:sectionMedicalDevicesImplants.entry:medicalDeviceImplant.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionMedicationSummary",
        "path": "Composition.section",
        "sliceName": "sectionMedicationSummary",
        "short": "History of Medication section",
        "definition": "The root of the sections that make up the composition.\r\n\r\nCyprusEHR: History of medication use defines a patient's current medications and history of pertinent medications. This term may also include a patient's prescription and dispense history (term description by LOINC).",
        "min": 1,
        "max": "1",
        "mustSupport": true
      },
      {
        "id": "Composition.section:sectionMedicationSummary.title",
        "path": "Composition.section.title",
        "short": "Medication Summary section",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Medication Summary\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionMedicationSummary.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "10160-0"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionMedicationSummary.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionMedicationSummary.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionMedicationSummary.entry",
        "path": "Composition.section.entry",
        "min": 1,
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://hl7.org/fhir/StructureDefinition/MedicationStatement"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionMedicationSummary.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionPregnancyHistory",
        "path": "Composition.section",
        "sliceName": "sectionPregnancyHistory",
        "short": "History of Pregnancy section",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionPregnancyHistory.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"History of Pregnancies\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionPregnancyHistory.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "10162-6"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionPregnancyHistory.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionPregnancyHistory.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionPregnancyHistory.entry",
        "path": "Composition.section.entry",
        "short": "Pregnancy Outcome, Prenancy Status and Pregnancy Expected Delivery Date",
        "definition": "A reference to the actual resource from which the narrative in the section is derive including Pregnancy Outcome, Pregnancy Status and where Pregnancy Status is pregnant include Pregnancy Expected Delivery Date.",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-pregnancyoutcome",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-pregnancystatus",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-pregnancyedd"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionPregnancyHistory.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionSocialHistory",
        "path": "Composition.section",
        "sliceName": "sectionSocialHistory",
        "short": "Social History section",
        "definition": "The root of the sections that make up the composition. This section includes observations for: \r\n* Consumption of Alcohol\r\n* Tobacco use\r\n* Drug use\r\n* Sleep Habits\r\n* Exercise",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionSocialHistory.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Social History\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionSocialHistory.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "29762-2"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionSocialHistory.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionSocialHistory.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionSocialHistory.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-consumptionofalcohol",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-tobaccouse",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-druguse",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-sleep",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-exercise"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionSocialHistory.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAdministeredVaccinations",
        "path": "Composition.section",
        "sliceName": "sectionAdministeredVaccinations",
        "short": "History of Immunization section",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionAdministeredVaccinations.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Immunization\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAdministeredVaccinations.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "11369-6"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionAdministeredVaccinations.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionAdministeredVaccinations.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAdministeredVaccinations.entry",
        "path": "Composition.section.entry",
        "slicing": {
          "discriminator": [
            {
              "type": "type",
              "path": "$this"
            }
          ],
          "rules": "open"
        },
        "min": 1
      },
      {
        "id": "Composition.section:sectionAdministeredVaccinations.entry:immunization",
        "path": "Composition.section.entry",
        "sliceName": "immunization",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-immunization-r4"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionAdministeredVaccinations.entry:immunization.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionVitalSignsAndSomatometrics",
        "path": "Composition.section",
        "sliceName": "sectionVitalSignsAndSomatometrics",
        "short": "Vital Signs and Somatometrics section",
        "definition": "The root of the sections that make up the composition. This section includes the following observations:\r\nVital Signs:\r\n* blood pressure\n* temperature\n* heart rate\n* respiratory rate\r\n\r\nSomatometrics:\r\n* Weight\r\n* Height\r\n* BMI\r\n* Head Circumference",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionVitalSignsAndSomatometrics.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Vital Signs\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionVitalSignsAndSomatometrics.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "85353-1"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionVitalSignsAndSomatometrics.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionVitalSignsAndSomatometrics.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionVitalSignsAndSomatometrics.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bloodpressure",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bodytemperature",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-heartrate",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-respiratoryrate",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bodyheight",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bodyweight",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bmi",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-headcircum"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionVitalSignsAndSomatometrics.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionLaboratoryAndImagingTests",
        "path": "Composition.section",
        "sliceName": "sectionLaboratoryAndImagingTests",
        "short": "Laboratory and Imaging Diagnostic Tests",
        "max": "1"
      },
      {
        "id": "Composition.section:sectionLaboratoryAndImagingTests.title",
        "path": "Composition.section.title",
        "min": 1
      },
      {
        "id": "Composition.section:sectionLaboratoryAndImagingTests.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "30954-2"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionLaboratoryAndImagingTests.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionLaboratoryAndImagingTests.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionLaboratoryAndImagingTests.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-diagnosticreport-r4"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionLaboratoryAndImagingTests.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionFirstImpression",
        "path": "Composition.section",
        "sliceName": "sectionFirstImpression",
        "short": "First Impression section",
        "definition": "The root of the sections that make up the composition.\r\n\r\nCyprusEHR: As described in loinc/51847-2:\r\n\"The Assessment and Plan note (also called impression or diagnoses) represents the clinician's conclusions and working assumptions that will guide treatment of the patient. The assessment formulates a specific plan or set of recommendations. The assessment may be a list of specific disease entities or a narrative block. The Plan section contains data that defines pending orders, interventions, encounters, services, and procedures for the patient. It is limited to prospective, unfulfilled, or incomplete orders and requests only. All active, incomplete, or pending orders, appointments, referrals, procedures, services, or any other pending event of clinical significance to the current care of the patient should be listed unless constrained due to privacy issues. The plan may also contain information about ongoing care of the patient and information regarding goals and clinical reminders. Clinical reminders are placed here to provide prompts for disease prevention and management, patient safety, and health-care quality improvements, including widely accepted performance measures. The plan may also indicate that patient education was given or will be provided.\"",
        "max": "1",
        "mustSupport": true
      },
      {
        "id": "Composition.section:sectionFirstImpression.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title: First Impression",
        "min": 1
      },
      {
        "id": "Composition.section:sectionFirstImpression.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "51847-2"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionFirstImpression.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionFirstImpression.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionFirstImpression.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-diagnosis-r4",
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-therapeuticrecommendation-r4"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionFirstImpression.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      },
      {
        "id": "Composition.section:sectionCourseOfDisease",
        "path": "Composition.section",
        "sliceName": "sectionCourseOfDisease",
        "short": "Course of Disease section",
        "max": "1",
        "mustSupport": true
      },
      {
        "id": "Composition.section:sectionCourseOfDisease.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Course of disease\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionCourseOfDisease.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "89261-2"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionCourseOfDisease.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionCourseOfDisease.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionCourseOfDisease.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-courseofdisease"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionAdvanceDirectives",
        "path": "Composition.section",
        "sliceName": "sectionAdvanceDirectives",
        "short": "Advance Directives",
        "min": 1,
        "max": "1",
        "mustSupport": true
      },
      {
        "id": "Composition.section:sectionAdvanceDirectives.title",
        "path": "Composition.section.title",
        "comment": "The title identifies the section for a human reader. The title must be consistent with the narrative of the resource that is the target of the section.content reference. Generally, sections SHOULD have titles, but in some documents, it is unnecessary or inappropriate. Typically, this is where a section has subsections that have their own adequately distinguishing title,  or documents that only have a single section. Most Implementation Guides will make section title to be a required element.\r\n\r\nCyprusEHR: Use the title \"Advance Directives\"",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAdvanceDirectives.code",
        "path": "Composition.section.code",
        "min": 1,
        "patternCodeableConcept": {
          "coding": [
            {
              "system": "http://loinc.org",
              "code": "42348-3"
            }
          ]
        }
      },
      {
        "id": "Composition.section:sectionAdvanceDirectives.code.coding",
        "path": "Composition.section.code.coding",
        "min": 1,
        "max": "1"
      },
      {
        "id": "Composition.section:sectionAdvanceDirectives.text",
        "path": "Composition.section.text",
        "min": 1
      },
      {
        "id": "Composition.section:sectionAdvanceDirectives.entry",
        "path": "Composition.section.entry",
        "type": [
          {
            "code": "Reference",
            "targetProfile": [
              "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-consenthealthcareassociate-r4"
            ]
          }
        ]
      },
      {
        "id": "Composition.section:sectionAdvanceDirectives.entry.reference",
        "path": "Composition.section.entry.reference",
        "min": 1
      }
    ]
  }
}

name : CYEHRSDVisitSummary

{

}