Union of https://hl7.fr/ig/fhir/core/StructureDefinition/fr-core-related-person and https://hl7.fr/ig/fhir/core/StructureDefinition/fr-core-related-person

This is the set of resources that conform to either of the profiles FR Core Related Person Profile (https://hl7.fr/ig/fhir/core/StructureDefinition/fr-core-related-person) and FR Core Related Person Profile (https://hl7.fr/ig/fhir/core/StructureDefinition/fr-core-related-person). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NomDrapeauxCard.TypeDescription et contraintes    Filter: Filtersdoco
.. RelatedPerson 0..*A person that is related to a patient, but who is not a direct target of care
... meta Σ0..1MetaMetadata about the resource
.... extension 0..*ExtensionAdditional content defined by implementations
.... versionId Σ0..1idVersion specific identifier
.... lastUpdated Σ0..1instantWhen the resource version last changed
.... source Σ0..1uriIdentifies where the resource comes from
.... profile Σ0..*canonical(StructureDefinition)Profiles this resource claims to conform to
.... security Σ0..*CodingSecurity Labels applied to this resource
Binding: ?? (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
.... tag Σ0..*CodingTags applied to this resource
Binding: ?? (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: ?? (preferred): A human language.
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ1..1IdentifierA human identifier for this person
... active ?!Σ0..1booleanWhether this related person's record is in active use
... patient Σ1..1Reference(FR Core Patient Profile | #sd-fr-core-patient-fr-core-patient)The patient this person is related to
... relationship Σ0..*CodeableConceptThe nature of the relationship
Binding: ?? (preferred): The nature of the relationship between a patient and the related person.
... name 0..*??left: Name of a human - parts and usage; right: A name associated with the person
... telecom C0..*??left: Details of a Technology mediated contact point (phone, fax, email, etc.); right: A contact detail for the person
Constraints: cpt-2
... gender Σ0..1codemale | female | other | unknown
Binding: ?? (required): The gender of a person used for administrative purposes.
... birthDate Σ0..1dateThe date on which the related person was born
... address 0..*??left: An address expressed using postal conventions (as opposed to GPS or other location definition formats); right: Address where the related person can be contacted or visited
... photo 0..*AttachmentImage of the person
... period 0..1PeriodPeriod of time that this relationship is considered valid
... communication 0..*BackboneElementA language which may be used to communicate with about the patient's health
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... language 1..1CodeableConceptThe language which can be used to communicate with the patient about his or her health
Binding: ?? (preferred): A human language.
.... preferred 0..1booleanLanguage preference indicator

doco Documentation for this format