<status value="draft" /> <date value="2024-06-18" /> <publisher value="openEHR" /> <contact> <telecom> <system value="url" /> <value value="http://www.veratech.es" /> </telecom> </contact> <description value="The 10-question Edinburgh Postnatal Depression Scale (EPDS) is used to screen for pregnancy or postnatal depression by assessing how a women has been feeling over the past 7 days." /> <purpose value="To detect depression in women who are pregnant or have recently had a baby. Developed by Cox JL, Holden JM and Sagovsky R 1987 (See references). Internationally, the Edinburgh Postnatal Depression Scale (EPDS) is the most widely accepted screening instrument used in the perinatal period. The EPDS was designed to allow screening of postnatal depression in the primary care setting1. It excludes some symptoms that are common in the perinatal period (tiredness, sleep disturbance, irritability) that other depression instruments include, as such symptoms do not differentiate between depressed and non-depressed postnatal women. The value of the EPDS lies in the fact that it is easy to complete, has been validated in relation to other standardized psychiatric measures and has been found to be acceptable to women who are asked to complete it. Its use provides women with the opportunity to discuss their feelings and enables health professionals to discreetly raise the issue of postnatal depression." /> <fhirVersion value="4.0.0" /> <mapping> <identity value="openEHR" /> <uri value="http://openehr.org" /> <name value="openEHR Mapping" /> </mapping> <mapping> <identity value="openEHR-natural" /> <uri value="http://openehr.org" /> <name value="openEHR natural path" /> </mapping> <kind value="logical" /> <abstract value="false" /> <type value="StructureDefinition" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/Element" /> <snapshot> <element id="StructureDefinition"> <path value="StructureDefinition" /> <short value="Base for all elements" /> <definition value="Base definition for all elements in a resource." /> <min value="0" /> <max value="*" /> <base> <path value="StructureDefinition" /> <min value="0" /> <max value="*" /> </base> <condition value="ele-1" /> <constraint> <key value="ele-1" /> <severity value="error" /> <human value="All FHIR elements must have a @value or children" /> <expression value="hasValue() or (children().count() > id.count())" /> <xpath value="@value|f:*|h:div" /> <source value="http://hl7.org/fhir/StructureDefinition/Element" /> </constraint> <mapping> <identity value="rim" /> <map value="n/a" /> </mapping> </element> <element id="StructureDefinition.id"> <path value="StructureDefinition.id" /> <representation value="xmlAttr" /> <short value="Unique id for inter-element referencing" /> <definition value="Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces." /> <min value="0" /> <max value="1" /> <base> <path value="Element.id" /> <min value="0" /> <max value="1" /> </base> <type> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fhir-type"> <valueUrl value="string" /> </extension> <code value="http://hl7.org/fhirpath/System.String" /> </type> <mapping> <identity value="rim" /> <map value="n/a" /> </mapping> </element> <element id="StructureDefinition.extension"> <path value="StructureDefinition.extension" /> <slicing> <discriminator> <type value="value" /> <path value="url" /> </discriminator> <description value="Extensions are always sliced by (at least) url" /> <rules value="open" /> </slicing> <short value="Additional content defined by implementations" /> <definition value="May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension." /> <comment value="There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone." /> <alias value="extensions" /> <alias value="user content" /> <min value="0" /> <max value="*" /> <base> <path value="Element.extension" /> <min value="0" /> <max value="*" /> </base> <type> <code value="Extension" /> </type> <condition value="ele-1" /> <constraint> <key value="ele-1" /> <severity value="error" /> <human value="All FHIR elements must have a @value or children" /> <expression value="hasValue() or (children().count() > id.count())" /> <xpath value="@value|f:*|h:div" /> <source value="http://hl7.org/fhir/StructureDefinition/Element" /> </constraint> <constraint> <key value="ext-1" /> <severity value="error" /> <human value="Must have either extensions or value[x], not both" /> <expression value="extension.exists() != value.exists()" /> <xpath value="exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])" /> <source value="http://hl7.org/fhir/StructureDefinition/Extension" /> </constraint> <mapping> <identity value="rim" /> <map value="n/a" /> </mapping> <mapping> <identity value="rim" /> <map value="N/A" /> </mapping> </element> </snapshot> </StructureDefinition>