<status value="draft" /> <publisher value="eHealth4U" /> <contact> <name value="eHealth Lab" /> <telecom> <system value="email" /> <value value="ehealthl@ucy.ac.cy" /> <use value="work" /> </telecom> </contact> <description value="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 value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="Composition" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/clinicaldocument" /> <derivation value="constraint" /> <differential> <element id="Composition.meta"> <path value="Composition.meta" /> </element> <element id="Composition.meta.profile"> <path value="Composition.meta.profile" /> <slicing> <discriminator> <type value="value" /> <path value="$this" /> </discriminator> <rules value="open" /> </slicing> <min value="1" /> </element> <element id="Composition.meta.profile:CyprusEHRProfile"> <path value="Composition.meta.profile" /> <sliceName value="CyprusEHRProfile" /> <min value="1" /> <max value="1" /> <fixedCanonical value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-visitsummary-r4" /> </element> <element id="Composition.language"> <path value="Composition.language" /> <mustSupport value="true" /> <binding> <strength value="required" /> <valueSet value="http://ig.ehealth4u.eu/fhir/ValueSet/cyehr-vs-ehdsilanguage" /> </binding> </element> <element id="Composition.text"> <path value="Composition.text" /> <mustSupport value="true" /> </element> <element id="Composition.extension"> <path value="Composition.extension" /> <slicing> <discriminator> <type value="value" /> <path value="url" /> </discriminator> <rules value="open" /> </slicing> <min value="0" /> </element> <element id="Composition.extension:versionNumber"> <path value="Composition.extension" /> <sliceName value="versionNumber" /> <min value="0" /> <mustSupport value="true" /> </element> <element id="Composition.identifier"> <path value="Composition.identifier" /> <definition value="A version-independent identifier for the Composition. This identifier stays constant as the composition is changed over time. CyprusEHR: The National eHealth Authority OID indicating that this is a visit summary document." /> <comment value="Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate. CyprusEHR: This SHALL be used for the visit summaries of the national integrated EHR of Cyprus." /> <patternIdentifier> <use value="official" /> <system value="urn:oid:2.16.840.1.113883.3.9143.5.3.1" /> </patternIdentifier> <mustSupport value="true" /> </element> <element id="Composition.identifier.use"> <path value="Composition.identifier.use" /> <min value="1" /> </element> <element id="Composition.identifier.system"> <path value="Composition.identifier.system" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Composition.identifier.value"> <path value="Composition.identifier.value" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Composition.status"> <path value="Composition.status" /> <fixedCode value="final" /> <mustSupport value="true" /> </element> <element id="Composition.type"> <path value="Composition.type" /> <comment value="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. CyprusEHR: 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: "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.' Mosby'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." All 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). More 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 value="CodeableConcept" /> <profile value="http://hl7.org/fhir/uv/ips/StructureDefinition/CodeableConcept-uv-ips" /> </type> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="11506-3" /> </coding> </patternCodeableConcept> <mustSupport value="true" /> <binding> <strength value="extensible" /> </binding> </element> <element id="Composition.type.coding"> <path value="Composition.type.coding" /> <slicing> <discriminator> <type value="pattern" /> <path value="$this" /> </discriminator> <rules value="open" /> </slicing> <min value="1" /> </element> <element id="Composition.type.coding.system"> <path value="Composition.type.coding.system" /> <min value="1" /> </element> <element id="Composition.type.coding.code"> <path value="Composition.type.coding.code" /> <min value="1" /> </element> <element id="Composition.type.coding.display"> <path value="Composition.type.coding.display" /> <min value="1" /> </element> <element id="Composition.type.coding:outpatientVisitSummary"> <path value="Composition.type.coding" /> <sliceName value="outpatientVisitSummary" /> <min value="1" /> <max value="1" /> <patternCoding> <system value="http://loinc.org" /> <code value="34131-3" /> </patternCoding> </element> <element id="Composition.type.coding:outpatientVisitSummary.system"> <path value="Composition.type.coding.system" /> <min value="1" /> </element> <element id="Composition.type.coding:outpatientVisitSummary.code"> <path value="Composition.type.coding.code" /> <min value="1" /> </element> <element id="Composition.type.coding:outpatientVisitSummary.display"> <path value="Composition.type.coding.display" /> <min value="1" /> </element> <element id="Composition.category"> <path value="Composition.category" /> <slicing> <discriminator> <type value="type" /> <path value="$this" /> </discriminator> <rules value="open" /> </slicing> <short value="Visit Summary categories" /> <definition value="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. CyprusEHR: 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 value="This is a metadata field from [XDS/MHD](http://wiki.ihe.net/index.php?title=Mobile_access_to_Health_Documents_(MHD)). CyprusEHR: 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 value="1" /> <type> <code value="CodeableConcept" /> <profile value="http://hl7.org/fhir/uv/ips/StructureDefinition/CodeableConcept-uv-ips" /> </type> <mustSupport value="true" /> <binding> <strength value="extensible" /> </binding> </element> <element id="Composition.category.coding.system"> <path value="Composition.category.coding.system" /> <min value="1" /> </element> <element id="Composition.category.coding.code"> <path value="Composition.category.coding.code" /> <min value="1" /> </element> <element id="Composition.category.coding.display"> <path value="Composition.category.coding.display" /> <min value="1" /> </element> <element id="Composition.category:visitSummary"> <path value="Composition.category" /> <sliceName value="visitSummary" /> <short value="Summary of an episode of care" /> <definition value="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. CyprusEHR: 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 value="1" /> <type> <code value="CodeableConcept" /> <profile value="http://hl7.org/fhir/uv/ips/StructureDefinition/CodeableConcept-uv-ips" /> </type> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="34133-9" /> </coding> </patternCodeableConcept> <mustSupport value="true" /> <binding> <strength value="extensible" /> </binding> </element> <element id="Composition.category:visitSummary.coding"> <path value="Composition.category.coding" /> <min value="1" /> </element> <element id="Composition.category:visitSummary.coding.system"> <path value="Composition.category.coding.system" /> <min value="1" /> </element> <element id="Composition.category:visitSummary.coding.code"> <path value="Composition.category.coding.code" /> <min value="1" /> </element> <element id="Composition.category:visitSummary.coding.display"> <path value="Composition.category.coding.display" /> <min value="1" /> </element> <element id="Composition.subject"> <path value="Composition.subject" /> <short value="Who the Visit Summary is about" /> <definition value="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 value="1" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-patient" /> </type> <mustSupport value="true" /> </element> <element id="Composition.subject.reference"> <path value="Composition.subject.reference" /> <min value="1" /> </element> <element id="Composition.encounter"> <path value="Composition.encounter" /> <short value="Encounter associated with this visit summary" /> <min value="1" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-encounter-r4" /> </type> <mustSupport value="true" /> </element> <element id="Composition.encounter.reference"> <path value="Composition.encounter.reference" /> <min value="1" /> </element> <element id="Composition.date"> <path value="Composition.date" /> <mustSupport value="true" /> </element> <element id="Composition.author"> <path value="Composition.author" /> <short value="Who and/or what authored the visit summary" /> <definition value="CyprusEHR: Identifies who is responsible for the information in the visit summary, not necessarily who typed it in." /> <comment value="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. CyprusEHR: In the case where a Practitioner has authored the visit summary, the corresponding CYEHRSDPractitionerRole shall be used." /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-practitionerrolehealthcareassociate-r4" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Device" /> </type> <mustSupport value="true" /> </element> <element id="Composition.author.reference"> <path value="Composition.author.reference" /> <min value="1" /> </element> <element id="Composition.title"> <path value="Composition.title" /> <definition value="Official human-readable label for the visit summary." /> <fixedString value="Visit Summary" /> <mustSupport value="true" /> </element> <element id="Composition.confidentiality"> <path value="Composition.confidentiality" /> <comment value="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. CyprusEHR: Following the eHSDI MVC corresponding value set (eHDSIConfidentiality) use only the following codes for the national Integrated EHR system of Cyprus: * N (display: normal) * R (display: restricted) * V (display: very restricted) For Phase I: not to be used." /> <binding> <strength value="required" /> <description value="Codes specifying the level of confidentiality of the composition (eHDSI MVC compatible)" /> </binding> </element> <element id="Composition.attester"> <path value="Composition.attester" /> <mustSupport value="true" /> </element> <element id="Composition.attester.mode"> <path value="Composition.attester.mode" /> <mustSupport value="true" /> </element> <element id="Composition.attester.time"> <path value="Composition.attester.time" /> <mustSupport value="true" /> </element> <element id="Composition.attester.party"> <path value="Composition.attester.party" /> <comment value="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. CyprusEHR: 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 value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/PractitionerRole" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-practitionerrole-r4" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Practitioner" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Organization" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-practitioner-r4" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-organization-r4" /> </type> <mustSupport value="true" /> </element> <element id="Composition.attester.party.reference"> <path value="Composition.attester.party.reference" /> <min value="1" /> </element> <element id="Composition.custodian"> <path value="Composition.custodian" /> <short value="National eHealth Authority of Cyprus" /> <definition value="Identifies the organization or group who is responsible for ongoing maintenance of and access to the composition/document information. CyprusEHR: 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 value="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. CyprusEHR: Every visit summary stored in the national integrated EHR of Cyprus SHALL have as custodian the NeHA." /> <mustSupport value="true" /> </element> <element id="Composition.custodian.reference"> <path value="Composition.custodian.reference" /> <min value="1" /> </element> <element id="Composition.custodian.identifier"> <path value="Composition.custodian.identifier" /> <patternIdentifier> <use value="official" /> <system value="urn:ietf:rfc:3986" /> <value value="urn:oid:2.16.840.1.113883.3.9143.1.1" /> </patternIdentifier> </element> <element id="Composition.custodian.display"> <path value="Composition.custodian.display" /> <fixedString value="National eHealth Authority of Cyprus" /> </element> <element id="Composition.relatesTo"> <path value="Composition.relatesTo" /> <comment value="A document is a version specific composition. CyprusEHR: Not to be used in the context of Cyprus EHR." /> </element> <element id="Composition.event"> <path value="Composition.event" /> <comment value="The event needs to be consistent with the type element, though can provide further information if desired. CyprusEHR: Not to be used in the context of Cyprus EHR." /> </element> <element id="Composition.section"> <path value="Composition.section" /> <slicing> <discriminator> <type value="pattern" /> <path value="code" /> </discriminator> <rules value="open" /> </slicing> <short value="Sections composing the Visit Summary" /> <definition value="The root of the sections that make up the visit summary. CyprusEHR: The structure of the sections composing the CYEHRSDVisitSummary is designed in a way to be conformant with the XeHealth Discharge Report." /> <min value="2" /> <mustSupport value="true" /> </element> <element id="Composition.section.title"> <path value="Composition.section.title" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Composition.section.code"> <path value="Composition.section.code" /> <min value="1" /> <type> <code value="CodeableConcept" /> <profile value="http://hl7.org/fhir/uv/ips/StructureDefinition/CodeableConcept-uv-ips" /> </type> <mustSupport value="true" /> </element> <element id="Composition.section.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> </element> <element id="Composition.section.code.coding.system"> <path value="Composition.section.code.coding.system" /> <min value="1" /> </element> <element id="Composition.section.code.coding.code"> <path value="Composition.section.code.coding.code" /> <min value="1" /> </element> <element id="Composition.section.code.coding.display"> <path value="Composition.section.code.coding.display" /> <min value="1" /> </element> <element id="Composition.section.author"> <path value="Composition.section.author" /> <comment value="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. CyprusEHR: 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." /> </element> <element id="Composition.section.author.reference"> <path value="Composition.section.author.reference" /> <comment value="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. CyprusEHR: Not to be used in the context of Cyprus EHR (Phase I)." /> <min value="1" /> </element> <element id="Composition.section.focus"> <path value="Composition.section.focus" /> <comment value="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. CyprusEHR: Not to be used in the context of Cyprus EHR." /> </element> <element id="Composition.section.text"> <path value="Composition.section.text" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Composition.section.mode"> <path value="Composition.section.mode" /> <comment value="This element is labeled as a modifier because a change list must not be misunderstood as a complete list. CyprusEHR: Not to be used in the context of Cyprus EHR." /> </element> <element id="Composition.section.orderedBy"> <path value="Composition.section.orderedBy" /> <comment value="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. CyprusEHR: Not to be used in the context of Cyprus EHR." /> </element> <element id="Composition.section.entry"> <path value="Composition.section.entry" /> <mustSupport value="true" /> </element> <element id="Composition.section.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="Composition.section.section"> <path value="Composition.section.section" /> <comment value="Nested sections are primarily used to help human readers navigate to particular portions of the document. CyprusEHR: Not to be used in the context of Cyprus EHR." /> </element> <element id="Composition.section:sectionAdmissionCause"> <path value="Composition.section" /> <sliceName value="sectionAdmissionCause" /> <short value="Visit's Admission Cause section" /> <definition value="The root of the sections that make up the composition. CyprusEHR: Chief Complaint and Reason for visit" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Composition.section:sectionAdmissionCause.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use "Admission Cause"" /> <min value="1" /> </element> <element id="Composition.section:sectionAdmissionCause.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="46239-0" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionAdmissionCause.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionAdmissionCause.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionAdmissionCause.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-problem-r4" /> </type> </element> <element id="Composition.section:sectionAdmissionCause.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionTravelHistory"> <path value="Composition.section" /> <sliceName value="sectionTravelHistory" /> <short value="History of Travel section" /> <max value="1" /> </element> <element id="Composition.section:sectionTravelHistory.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use "Travel History"" /> <min value="1" /> </element> <element id="Composition.section:sectionTravelHistory.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="10182-4" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionTravelHistory.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionTravelHistory.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionTravelHistory.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-travelhistory" /> </type> </element> <element id="Composition.section:sectionTravelHistory.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionAllergies"> <path value="Composition.section" /> <sliceName value="sectionAllergies" /> <short value="History of Allergies and Intolerances section" /> <definition value="The root of the sections that make up the composition. CyprusEHR: 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 value="CyprusEHR: This section is designed in a way to be conformant with the sectionAllergies from XeHealth Discharge Report." /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionAllergies.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Allergies and Intolerances"" /> <min value="1" /> </element> <element id="Composition.section:sectionAllergies.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="48765-2" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionAllergies.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionAllergies.code.coding.display"> <path value="Composition.section.code.coding.display" /> <comment value="Note that FHIR strings SHALL NOT exceed 1MB in size CyprusEHR: Display is optional due to the conformance requirement with the XeHealth DischargeReport.sectionAllergies.code.coding" /> </element> <element id="Composition.section:sectionAllergies.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionAllergies.entry"> <path value="Composition.section.entry" /> <slicing> <discriminator> <type value="type" /> <path value="resolve()" /> </discriminator> <rules value="open" /> </slicing> <min value="1" /> </element> <element id="Composition.section:sectionAllergies.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionAllergies.entry:AllergyAndIntolerance"> <path value="Composition.section.entry" /> <sliceName value="AllergyAndIntolerance" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/AllergyIntolerance" /> </type> <mustSupport value="true" /> </element> <element id="Composition.section:sectionAllergies.entry:AllergyAndIntolerance.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionResolvedClosedInactiveProblems"> <path value="Composition.section" /> <sliceName value="sectionResolvedClosedInactiveProblems" /> <short value="History of Resolved, Closed or Inactive Problems section" /> <max value="1" /> </element> <element id="Composition.section:sectionResolvedClosedInactiveProblems.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Resolved, Closed and Inactive Problems"" /> <min value="1" /> </element> <element id="Composition.section:sectionResolvedClosedInactiveProblems.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="11348-0" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionResolvedClosedInactiveProblems.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionResolvedClosedInactiveProblems.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionResolvedClosedInactiveProblems.entry"> <path value="Composition.section.entry" /> <min value="1" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-problem-r4" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-diagnosis-r4" /> </type> </element> <element id="Composition.section:sectionResolvedClosedInactiveProblems.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionProcedures"> <path value="Composition.section" /> <sliceName value="sectionProcedures" /> <short value="History of Procedures section" /> <max value="1" /> </element> <element id="Composition.section:sectionProcedures.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Procedures"" /> <min value="1" /> </element> <element id="Composition.section:sectionProcedures.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="29554-3" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionProcedures.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionProcedures.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionProcedures.entry"> <path value="Composition.section.entry" /> <min value="1" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-procedure-r4" /> </type> </element> <element id="Composition.section:sectionProcedures.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionFunctionalStatus"> <path value="Composition.section" /> <sliceName value="sectionFunctionalStatus" /> <short value="History of Functional Status section" /> <max value="1" /> </element> <element id="Composition.section:sectionFunctionalStatus.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Functional Status"" /> <min value="1" /> </element> <element id="Composition.section:sectionFunctionalStatus.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="47420-5" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionFunctionalStatus.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionFunctionalStatus.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionFunctionalStatus.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/Observation" /> </type> </element> <element id="Composition.section:sectionFunctionalStatus.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionMedicalDevicesImplants"> <path value="Composition.section" /> <sliceName value="sectionMedicalDevicesImplants" /> <short value="History of Medical Devices and Implants section" /> <max value="1" /> </element> <element id="Composition.section:sectionMedicalDevicesImplants.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Medical Devices and Implants"" /> <min value="1" /> </element> <element id="Composition.section:sectionMedicalDevicesImplants.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="46264-8" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionMedicalDevicesImplants.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionMedicalDevicesImplants.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionMedicalDevicesImplants.entry"> <path value="Composition.section.entry" /> <slicing> <discriminator> <type value="type" /> <path value="$this" /> </discriminator> <rules value="open" /> </slicing> </element> <element id="Composition.section:sectionMedicalDevicesImplants.entry:medicalDeviceImplant"> <path value="Composition.section.entry" /> <sliceName value="medicalDeviceImplant" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-device-r4" /> </type> <mustSupport value="true" /> </element> <element id="Composition.section:sectionMedicalDevicesImplants.entry:medicalDeviceImplant.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionMedicationSummary"> <path value="Composition.section" /> <sliceName value="sectionMedicationSummary" /> <short value="History of Medication section" /> <definition value="The root of the sections that make up the composition. CyprusEHR: 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 value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Composition.section:sectionMedicationSummary.title"> <path value="Composition.section.title" /> <short value="Medication Summary section" /> <comment value="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. CyprusEHR: Use the title "Medication Summary"" /> <min value="1" /> </element> <element id="Composition.section:sectionMedicationSummary.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="10160-0" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionMedicationSummary.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionMedicationSummary.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionMedicationSummary.entry"> <path value="Composition.section.entry" /> <min value="1" /> <type> <code value="Reference" /> <targetProfile value="http://hl7.org/fhir/StructureDefinition/MedicationStatement" /> </type> </element> <element id="Composition.section:sectionMedicationSummary.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionPregnancyHistory"> <path value="Composition.section" /> <sliceName value="sectionPregnancyHistory" /> <short value="History of Pregnancy section" /> <max value="1" /> </element> <element id="Composition.section:sectionPregnancyHistory.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "History of Pregnancies"" /> <min value="1" /> </element> <element id="Composition.section:sectionPregnancyHistory.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="10162-6" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionPregnancyHistory.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionPregnancyHistory.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionPregnancyHistory.entry"> <path value="Composition.section.entry" /> <short value="Pregnancy Outcome, Prenancy Status and Pregnancy Expected Delivery Date" /> <definition value="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 value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-pregnancyoutcome" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-pregnancystatus" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-pregnancyedd" /> </type> </element> <element id="Composition.section:sectionPregnancyHistory.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionSocialHistory"> <path value="Composition.section" /> <sliceName value="sectionSocialHistory" /> <short value="Social History section" /> <definition value="The root of the sections that make up the composition. This section includes observations for: * Consumption of Alcohol * Tobacco use * Drug use * Sleep Habits * Exercise" /> <max value="1" /> </element> <element id="Composition.section:sectionSocialHistory.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Social History"" /> <min value="1" /> </element> <element id="Composition.section:sectionSocialHistory.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="29762-2" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionSocialHistory.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionSocialHistory.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionSocialHistory.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-consumptionofalcohol" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-tobaccouse" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-druguse" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-sleep" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-exercise" /> </type> </element> <element id="Composition.section:sectionSocialHistory.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionAdministeredVaccinations"> <path value="Composition.section" /> <sliceName value="sectionAdministeredVaccinations" /> <short value="History of Immunization section" /> <max value="1" /> </element> <element id="Composition.section:sectionAdministeredVaccinations.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Immunization"" /> <min value="1" /> </element> <element id="Composition.section:sectionAdministeredVaccinations.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="11369-6" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionAdministeredVaccinations.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionAdministeredVaccinations.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionAdministeredVaccinations.entry"> <path value="Composition.section.entry" /> <slicing> <discriminator> <type value="type" /> <path value="$this" /> </discriminator> <rules value="open" /> </slicing> <min value="1" /> </element> <element id="Composition.section:sectionAdministeredVaccinations.entry:immunization"> <path value="Composition.section.entry" /> <sliceName value="immunization" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-immunization-r4" /> </type> </element> <element id="Composition.section:sectionAdministeredVaccinations.entry:immunization.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionVitalSignsAndSomatometrics"> <path value="Composition.section" /> <sliceName value="sectionVitalSignsAndSomatometrics" /> <short value="Vital Signs and Somatometrics section" /> <definition value="The root of the sections that make up the composition. This section includes the following observations: Vital Signs: * blood pressure * temperature * heart rate * respiratory rate Somatometrics: * Weight * Height * BMI * Head Circumference" /> <max value="1" /> </element> <element id="Composition.section:sectionVitalSignsAndSomatometrics.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Vital Signs"" /> <min value="1" /> </element> <element id="Composition.section:sectionVitalSignsAndSomatometrics.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="85353-1" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionVitalSignsAndSomatometrics.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionVitalSignsAndSomatometrics.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionVitalSignsAndSomatometrics.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bloodpressure" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bodytemperature" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-heartrate" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-respiratoryrate" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bodyheight" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bodyweight" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-bmi" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-headcircum" /> </type> </element> <element id="Composition.section:sectionVitalSignsAndSomatometrics.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionLaboratoryAndImagingTests"> <path value="Composition.section" /> <sliceName value="sectionLaboratoryAndImagingTests" /> <short value="Laboratory and Imaging Diagnostic Tests" /> <max value="1" /> </element> <element id="Composition.section:sectionLaboratoryAndImagingTests.title"> <path value="Composition.section.title" /> <min value="1" /> </element> <element id="Composition.section:sectionLaboratoryAndImagingTests.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="30954-2" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionLaboratoryAndImagingTests.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionLaboratoryAndImagingTests.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionLaboratoryAndImagingTests.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-diagnosticreport-r4" /> </type> </element> <element id="Composition.section:sectionLaboratoryAndImagingTests.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionFirstImpression"> <path value="Composition.section" /> <sliceName value="sectionFirstImpression" /> <short value="First Impression section" /> <definition value="The root of the sections that make up the composition. CyprusEHR: As described in loinc/51847-2: "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 value="1" /> <mustSupport value="true" /> </element> <element id="Composition.section:sectionFirstImpression.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title: First Impression" /> <min value="1" /> </element> <element id="Composition.section:sectionFirstImpression.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="51847-2" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionFirstImpression.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionFirstImpression.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionFirstImpression.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-diagnosis-r4" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-therapeuticrecommendation-r4" /> </type> </element> <element id="Composition.section:sectionFirstImpression.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> <element id="Composition.section:sectionCourseOfDisease"> <path value="Composition.section" /> <sliceName value="sectionCourseOfDisease" /> <short value="Course of Disease section" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Composition.section:sectionCourseOfDisease.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Course of disease"" /> <min value="1" /> </element> <element id="Composition.section:sectionCourseOfDisease.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="89261-2" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionCourseOfDisease.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionCourseOfDisease.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionCourseOfDisease.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-courseofdisease" /> </type> </element> <element id="Composition.section:sectionAdvanceDirectives"> <path value="Composition.section" /> <sliceName value="sectionAdvanceDirectives" /> <short value="Advance Directives" /> <min value="1" /> <max value="1" /> <mustSupport value="true" /> </element> <element id="Composition.section:sectionAdvanceDirectives.title"> <path value="Composition.section.title" /> <comment value="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. CyprusEHR: Use the title "Advance Directives"" /> <min value="1" /> </element> <element id="Composition.section:sectionAdvanceDirectives.code"> <path value="Composition.section.code" /> <min value="1" /> <patternCodeableConcept> <coding> <system value="http://loinc.org" /> <code value="42348-3" /> </coding> </patternCodeableConcept> </element> <element id="Composition.section:sectionAdvanceDirectives.code.coding"> <path value="Composition.section.code.coding" /> <min value="1" /> <max value="1" /> </element> <element id="Composition.section:sectionAdvanceDirectives.text"> <path value="Composition.section.text" /> <min value="1" /> </element> <element id="Composition.section:sectionAdvanceDirectives.entry"> <path value="Composition.section.entry" /> <type> <code value="Reference" /> <targetProfile value="http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-consenthealthcareassociate-r4" /> </type> </element> <element id="Composition.section:sectionAdvanceDirectives.entry.reference"> <path value="Composition.section.entry.reference" /> <min value="1" /> </element> </differential> </StructureDefinition>