Generated Narrative: StructureDefinition at-core-extendedContactDetail Name Flags Card. Type Description & Constraints ExtendedContactDetail ExtendedContactDetail #xD; address 0..1 HL7ATCoreAddress Address for the contact #xD; organization 0..1 Reference(HL7® AT Core Organization Profile) This contact detail is handled/monitored by a specific organization #xD; Documentation for this format
HL7® AT Core ExtendedContactDetail Profile
Technical Committee for FHIR® at HL7® Austria
HL7® Austria FHIR® Core Profile to use the profile for address data in Austria on the datatype ExtendedContactDetail.
Specifies contact information for a specific purpose over a period of time, might be handled/monitored by a specific named person or organization.
This datatype may be sparsely populated, i.e. only contain a purpose and phone number or address, but other cases could be completed filled out.
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
If no purpose is defined, then these contact details may be used for any purpose.
The purpose for which an extended contact detail should be used.
The name of an individual to contact, some types of contact detail are usually blank.
If there is no named individual, the telecom/address information is not generally monitored by a specific individual.
The contact details application for the purpose defined.
More than 1 address would be for different purposes, and thus should be entered as a different entry,.
This contact detail is handled/monitored by a specific organization
This contact detail is handled/monitored by a specific organization. If the name is provided in the contact, then it is referring to the named individual within this organization.
Some specific types of contact information can be an handled by an organization (eg legal council is via a specific firm).
Period that this contact was valid for usage
If the details have multiple periods, then enter in a new ExtendedContact with the new period.