Generated Narrative: StructureDefinition EHDSDataSet Name Flags Card. Type Description & Constraints EHDSDataSet 0..* Base EHDS data exchange #xD; identifier 0..* Identifier Document ID #xD; subject 0..1 EHDSPerson Subject #xD; country 0..1 CodeableConcept Country Binding Description: (preferred): ISO 3166 #xD; relatedPerson 0..* BackboneElement Related person #xD; person 0..1 EHDSPerson Identification and description of the person #xD; relationship 0..1 CodeableConcept Relationship Binding Description: (preferred): HL7 RoleCode #xD; authorship 1..* Base Authorship #xD; author 1..1 EHDSHealthProfessional Author #xD; datetime 1..1 dateTime Date and time of authoring/issuing #xD; lastUpdate 0..1 dateTime Date and time of the last update to the data object #xD; status 1..1 CodeableConcept Status of the information #xD; version 0..1 string Version #xD; language 0..1 CodeableConcept Language Binding Description: (preferred): BCP 47 #xD; presentation 1..* Base Presentation form #xD; author 1..1 EHDSHealthProfessional Author #xD; datetime 1..1 dateTime Date and time of authoring/issuing #xD; Documentation for this format
Common elements for all EHDS data exchange.
Patient/subject guardian and related person information
Some roles for the related person are essential for data access control. For example, the role of the guardian is essential for the data access control of a minor patient.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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 managable, 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.
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.
Must have either extensions or value[x], not both
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Identification and description of the person
Identification and description of the contact person for that patient. This includes relatives, guardians, caring persons etc.
The nature of the relationship between the patient and the related person.
Author by whom the resource was/were authored. Multiple authors could be provided.
Date and time of the issuing the document/resource by its author.
Date and time of the last update to the data object
Date and time of the last update to the document/information
Language in which the information is written. Language is expressed by the IETF language tag.
The presentation of the data, e.g. a PDF document, a video, a text file, etc. In case of unstructured data, this is the actual content.