FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server  |  FHIR Version n/a  User: [n/a]

Resource StructureDefinition/FHIR Server from package ehealth4u.package#1.0.0 (62 ms)

Package ehealth4u.package
Type StructureDefinition
Id Id
FHIR Version R4
Source https://simplifier.net/resolve?scope=ehealth4u.package@1.0.0&canonical=http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-internationalpatientsummary-r4
Url http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-internationalpatientsummary-r4
Status draft
Name CYEHRSDInternationalPatientSummary
Title Cyprus International Patient Summary Document profile
Experimental False
Description This profile represents the constraints applied to the patient summary clinical document by the eHealth4U project according to the national eHealth law while addressing the requirements for the implementations of the EU cross boarder services as defined by eHDSI and eHealth Network. An eHealth4U Patient Summary (eHealth4U-PS) document is an electronic health record extract containing essential healthcare information about a subject of care as defined in EN 17269 and ISO 27269.
Type Composition
Kind resource

Resources that use this resource

No resources found


Resources that this resource uses

StructureDefinition
http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips Composition (IPS)


Source

{
  "resourceType" : "StructureDefinition",
  "id" : "cyehr-sd-internationalpatientsummary-r4",
  "url" : "http://ig.ehealth4u.eu/fhir/StructureDefinition/cyehr-sd-internationalpatientsummary-r4",
  "name" : "CYEHRSDInternationalPatientSummary",
  "title" : "Cyprus International Patient Summary Document profile",
  "status" : "draft",
  "publisher" : "eHealth4U",
  "contact" : [
    {
      "name" : "eHealth Lab (University of Cyprus)",
      "telecom" : [
        {
          "system" : "email",
          "value" : "ehealthl@ucy.ac.cy",
          "use" : "work"
        }
      ]
    }
  ],
  "description" : "This profile represents the constraints applied to the patient summary clinical document by the eHealth4U project according to the national eHealth law while addressing the requirements for the implementations of the EU cross boarder services as defined by eHDSI and eHealth Network. An eHealth4U Patient Summary (eHealth4U-PS) document is an electronic health record extract containing essential healthcare information about a subject of care as defined in EN 17269 and ISO 27269.",
  "fhirVersion" : "4.0.1",
  "kind" : "resource",
  "abstract" : false,
  "type" : "Composition",
  "baseDefinition" : "http://hl7.org/fhir/uv/ips/StructureDefinition/Composition-uv-ips",
  "derivation" : "constraint",
  "differential" : {
    "element" : [
      {
        "id" : "Composition.identifier",
        "path" : "Composition.identifier",
        "comment" : "Similar to ClinicalDocument/setId in CDA. See discussion in resource definition for how these relate.\r\n\r\nCyprusEHR: For the CYEHR implementation the identifier.system = 2.16.840.1.113883.3.9143.5.3.2 shall be used and the corresponding value."
      },
      {
        "id" : "Composition.type.coding",
        "path" : "Composition.type.coding",
        "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.category",
        "path" : "Composition.category",
        "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: Not to be used in the context of Cyprus EHR."
      },
      {
        "id" : "Composition.author",
        "path" : "Composition.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 Connectathon purposes the eHealth Lab shall be referenced."
      },
      {
        "id" : "Composition.title",
        "path" : "Composition.title",
        "fixedString" : "International Patient Summary"
      },
      {
        "id" : "Composition.attester.mode",
        "path" : "Composition.attester.mode",
        "comment" : "Note that FHIR strings SHALL NOT exceed 1MB in size\r\n\r\nCyprusEHR: Use \"legal\" value."
      },
      {
        "id" : "Composition.custodian",
        "path" : "Composition.custodian",
        "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: For Connectathon use eHealth Lab."
      },
      {
        "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:careProvisioningEvent",
        "path" : "Composition.event",
        "sliceName" : "careProvisioningEvent"
      },
      {
        "id" : "Composition.event:careProvisioningEvent.code.coding",
        "path" : "Composition.event.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.event:careProvisioningEvent.code.coding.system",
        "path" : "Composition.event.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.event:careProvisioningEvent.code.coding.code",
        "path" : "Composition.event.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionMedications",
        "path" : "Composition.section",
        "sliceName" : "sectionMedications"
      },
      {
        "id" : "Composition.section:sectionMedications.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: Medication Summary section"
      },
      {
        "id" : "Composition.section:sectionMedications.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionMedications.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionMedications.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionMedications.entry:medicationRequest",
        "path" : "Composition.section.entry",
        "sliceName" : "medicationRequest",
        "comment" : "If there are no entries in the list, an emptyReason SHOULD be provided.\r\n\r\nCyprusEHR: Not to be used in the context of Cyprus EHR."
      },
      {
        "id" : "Composition.section:sectionAllergies",
        "path" : "Composition.section",
        "sliceName" : "sectionAllergies"
      },
      {
        "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: Add as title: \"Allergies and Intolerances Section\""
      },
      {
        "id" : "Composition.section:sectionAllergies.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionAllergies.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionAllergies.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionProblems",
        "path" : "Composition.section",
        "sliceName" : "sectionProblems"
      },
      {
        "id" : "Composition.section:sectionProblems.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: The title = \"Problems Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionProblems.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionProblems.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionProblems.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionProceduresHx",
        "path" : "Composition.section",
        "sliceName" : "sectionProceduresHx"
      },
      {
        "id" : "Composition.section:sectionProceduresHx.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: The title: \"History of Procedures Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionProceduresHx.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionProceduresHx.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionProceduresHx.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionImmunizations",
        "path" : "Composition.section",
        "sliceName" : "sectionImmunizations"
      },
      {
        "id" : "Composition.section:sectionImmunizations.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\nCyprus: The title \"Immunizations Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionImmunizations.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionImmunizations.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionImmunizations.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionMedicalDevices",
        "path" : "Composition.section",
        "sliceName" : "sectionMedicalDevices"
      },
      {
        "id" : "Composition.section:sectionMedicalDevices.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: The title \"Medical Devices Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionMedicalDevices.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionMedicalDevices.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionMedicalDevices.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionResults",
        "path" : "Composition.section",
        "sliceName" : "sectionResults"
      },
      {
        "id" : "Composition.section:sectionResults.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: The title \"Results Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionResults.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionResults.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionResults.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionVitalSigns",
        "path" : "Composition.section",
        "sliceName" : "sectionVitalSigns"
      },
      {
        "id" : "Composition.section:sectionVitalSigns.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: The title \"Vital Signs Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionVitalSigns.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionVitalSigns.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionVitalSigns.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPastIllnessHx",
        "path" : "Composition.section",
        "sliceName" : "sectionPastIllnessHx"
      },
      {
        "id" : "Composition.section:sectionPastIllnessHx.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: The title \"History of Past Illness Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionPastIllnessHx.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPastIllnessHx.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPastIllnessHx.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionFunctionalStatus",
        "path" : "Composition.section",
        "sliceName" : "sectionFunctionalStatus"
      },
      {
        "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: The title \"Functional Status\" shall be used."
      },
      {
        "id" : "Composition.section:sectionFunctionalStatus.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionFunctionalStatus.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionFunctionalStatus.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPlanOfCare",
        "path" : "Composition.section",
        "sliceName" : "sectionPlanOfCare"
      },
      {
        "id" : "Composition.section:sectionPlanOfCare.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: The title \"Plan of Care Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionPlanOfCare.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPlanOfCare.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPlanOfCare.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionSocialHistory",
        "path" : "Composition.section",
        "sliceName" : "sectionSocialHistory"
      },
      {
        "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: The title \"Social History Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionSocialHistory.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionSocialHistory.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionSocialHistory.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPregnancyHx",
        "path" : "Composition.section",
        "sliceName" : "sectionPregnancyHx"
      },
      {
        "id" : "Composition.section:sectionPregnancyHx.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\nCyprysEHR: The title \"History of Pregnancy Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionPregnancyHx.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPregnancyHx.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionPregnancyHx.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionAdvanceDirectives",
        "path" : "Composition.section",
        "sliceName" : "sectionAdvanceDirectives"
      },
      {
        "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\nCyprysEHR: The title \"IPS Advance Directives Section\" shall be used."
      },
      {
        "id" : "Composition.section:sectionAdvanceDirectives.code.coding",
        "path" : "Composition.section.code.coding",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionAdvanceDirectives.code.coding.system",
        "path" : "Composition.section.code.coding.system",
        "min" : 1
      },
      {
        "id" : "Composition.section:sectionAdvanceDirectives.code.coding.code",
        "path" : "Composition.section.code.coding.code",
        "min" : 1
      }
    ]
  },
  "text" : {
  }
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.