Generated Narrative: StructureDefinition CustomIdatValues Name Flags Card. Type Description & Constraints Extension 0..* Extension Custom IDAT Values #xD; Slices for extension Content/Rules for all slices #xD; extension:value1 S 0..1 Extension Benutzerdefinierter Wert 1 #xD; extension 0..0 Extension #xD; url 1..1 uri "value1" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value2 S 0..1 Extension Benutzerdefinierter Wert 2 #xD; extension 0..0 Extension #xD; url 1..1 uri "value2" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value3 S 0..1 Extension Benutzerdefinierter Wert 3 #xD; extension 0..0 Extension #xD; url 1..1 uri "value3" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value4 S 0..1 Extension Benutzerdefinierter Wert 4 #xD; extension 0..0 Extension #xD; url 1..1 uri "value4" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value5 S 0..1 Extension Benutzerdefinierter Wert 5 #xD; extension 0..0 Extension #xD; url 1..1 uri "value5" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value6 S 0..1 Extension Benutzerdefinierter Wert 6 #xD; extension 0..0 Extension #xD; url 1..1 uri "value6" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value7 S 0..1 Extension Benutzerdefinierter Wert 7 #xD; extension 0..0 Extension #xD; url 1..1 uri "value7" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value8 S 0..1 Extension Benutzerdefinierter Wert 8 #xD; extension 0..0 Extension #xD; url 1..1 uri "value8" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value9 S 0..1 Extension Benutzerdefinierter Wert 9 #xD; extension 0..0 Extension #xD; url 1..1 uri "value9" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; extension:value10 S 0..1 Extension Benutzerdefinierter Wert 10 #xD; extension 0..0 Extension #xD; url 1..1 uri "value10" #xD; value[x] 1..1 Value of extension #xD; valueBase64Binary base64Binary #xD; valueBoolean boolean #xD; valueCanonical canonical(Any) #xD; valueCode code #xD; valueDate date #xD; valueDateTime dateTime #xD; valueDecimal decimal #xD; valueId id #xD; valueInstant instant #xD; valueInteger integer #xD; valueMarkdown markdown #xD; valueOid oid #xD; 0)">valuePositiveInt positiveInt #xD; valueString string #xD; valueTime time #xD; = 0)">valueUnsignedInt unsignedInt #xD; valueUri uri #xD; valueUrl url #xD; valueUuid uuid #xD; valueAddress Address #xD; valueAge Age #xD; valueAnnotation Annotation #xD; valueAttachment Attachment #xD; valueCodeableConcept CodeableConcept #xD; valueCoding Coding #xD; valueContactPoint ContactPoint #xD; valueCount Count #xD; valueDistance Distance #xD; valueDuration Duration #xD; valueHumanName HumanName #xD; valueIdentifier Identifier #xD; valueMoney Money #xD; valuePeriod Period #xD; valueQuantity Quantity #xD; valueRange Range #xD; valueRatio Ratio #xD; valueReference Reference(Any) #xD; valueSampledData SampledData #xD; valueSignature Signature #xD; <span title="Base StructureDefinition for Timing Type: Specifies an event that may occur multiple times. Timing schedules are used to record when things are planned, expected or requested to occur. The most common usage is in dosage instructions for medications. They are also used when planning care of various kinds, and may be used for reporting the schedule to which past regular activities were carried out.">valueTiming Timing #xD; valueContactDetail ContactDetail #xD; valueContributor Contributor #xD; valueDataRequirement DataRequirement #xD; valueExpression Expression #xD; valueParameterDefinition ParameterDefinition #xD; valueRelatedArtifact RelatedArtifact #xD; valueTriggerDefinition TriggerDefinition #xD; valueUsageContext UsageContext #xD; valueDosage Dosage #xD; url 1..1 uri "https://ths-greifswald.de/fhir/StructureDefinition/epix/CustomIdatValues" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
Unabhängige Treuhandstelle der Universitätsmedizin Greifswald
Set von bis zu zehn individualisierbaren Werten zur Dokumentation von personenidentifizierenden Daten im E-PIX
Copyright 2020-2026 Unabhängige Treuhandstelle der Universitätsmedizin Greifswald
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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 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.
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.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).