RelatedPerson (47)

#NameSourceVerDescription
1ADHA Authoring RelatedPersonau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a related person in the role of an author or observer for exchange usage scenarios to support the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia.
2ADHA Core RelatedPersonau.digitalhealth.r4#currentR4The purpose of this profile is to provide a core representation of a related person for the electronic exchange of health information between individuals, healthcare providers, and the My Health Record system infrastructure in Australia.
3ADHA My Health Record RelatedPersonau.digitalhealth.r4#currentR4The purpose of this profile is to define a representation of a related person for exchange usage scenarios with the My Health Record system infrastructure in Australia.
4ADI Notaryhl7.fhir.us.pacio-adi#currentR4This profile represents a person participating as a notary for a person's advance directives.
5ADI Participanthl7.fhir.us.pacio-adi#currentR4This profile represents a person participating in a person's advance directives in some capacity such as healthcare agent or healthcare agent advisor.
6ADI Participanthl7.fhir.us.pacio-adi#currentR4This profile represents a person participating in a persons advance directives in some capacity such as healthcare agent or healthcare agent advisor.
7ADI Witnesshl7.fhir.us.pacio-adi#currentR4This profile represents a person participating as a witness for a person's advance directives.
8ANC RelatedPersonwho.fhir.anc-cds#currentR4ANC RelatedPerson
9AU Base Related Personhl7.fhir.au.base#currentR4This profile defines a related person structure that localises core concepts, including identifiers and terminology, for use in an Australian context. The purpose of this profile is to provide national level agreement on core localised concepts. This profile does not force conformance to core localised concepts. It enables implementers and modellers to make their own rules, i.e. [profiling](http://hl7.org/fhir/profiling.html), about how to support these concepts for specific implementation needs.
10AU Core RelatedPersonhl7.fhir.au.core#currentR4This profile sets minimum expectations for a RelatedPerson resource to record, search, and fetch related persons associated with a patient. It is based on the [AU Base RelatedPerson](http://build.fhir.org/ig/hl7au/au-fhir-base/StructureDefinition-au-relatedperson.html) profile and identifies the *additional* mandatory core elements, extensions, vocabularies and value sets that **SHALL** be present in the RelatedPerson resource when conforming to this profile. It provides the floor for standards development for specific uses cases in an Australian context.
11BC RelatedPerson Profilehl7.fhir.us.breastcancer#0.2.0R3A person in a role defined in relationship to a patient
12C4BB RelatedPersonhl7.fhir.us.carin-bb#currentR4This profile is used to convey basic demographic information about a person related to the claim.
13CH EMED EPR RelatedPersonch.cara.fhir.epr.emed#currentR4Definition of the related person for the eMedication context
14CPG Related Personhl7.fhir.uv.cpg#currentR4CPG related person defines the minimum expectations for a person related to a patient in a CPG case, such as a care partner, spouse, or other related person
15Davinci ATR RelatedPersonhl7.fhir.us.davinci-atr#currentR4This is the RelatedPerson Resource profile for the IG.
16Decedent Fatherhl7.fhir.us.vrsandbox#currentR4Decedent Father (USCoreRelatedPerson)
17Decedent Fatherhl7.fhir.us.vrdr#currentR4Decedent Father (USCoreRelatedPerson)
18Decedent Motherhl7.fhir.us.vrsandbox#currentR4Decedent Mother (USCoreRelatedPerson)
19Decedent Motherhl7.fhir.us.vrdr#currentR4Decedent Mother (USCoreRelatedPerson)
20Decedent Spousehl7.fhir.us.vrsandbox#currentR4Decedent Spouse (USCoreRelatedPerson)
21Decedent Spousehl7.fhir.us.vrdr#currentR4Decedent Spouse (USCoreRelatedPerson)
22EEBase RelatedPersonhl7.fhir.ee.base#currentR5This profile builds on RelatedPerson resource. The profile allows information exchange about a person that is involved in the care for a patient, but who is not the target of healthcare, nor has a formal responsibility in the care process.
23IHE Patient Master Identity Registry Related Personihe.iti.pmir#currentR4StructureDefinition for RelatedPerson resource constraints for messages in the IHE PMIR Profile when a Patient is linked to a related person.
24KLGatewayChildrenRelatedParentkl.fhir.dk.children#currentR4Profile for describing the relationship between the child, and the parents, guardians or caregivers who are also relevant for the journal
25MedNet Interface (MNI) - RelatedPersonswiss.mednet.fhir#0.15.0R4MedNet Interface (MNI) - RelatedPerson Profile
26nl-core-relatedpersonnictiz.fhir.nl.stu3.zib2017#2.2.15R3A RelatedPerson resource as defined by the Dutch Health and Care Information models or HCIM (Dutch: Zorginformatiebouwsteen or ZIB) ContactPersoon version 3.1 (Release 2017). The HCIM ContactPerson is meant to deal with both related persons and contacts. This profile targets instantiations of the HCIM ContactPerson who are related persons. An HCIM ContactPerson who is a contact for a patient, belongs in Patient.contact. If a person is both a related person and a contact person, then some data duplication is inevitable. This may or may not be resolved in a future version of the Patient/RelatedPerson resources.
27no-basis-RelatedPersonhl7.fhir.no.basis#2.1.2R4Basisprofil for Norwegian RelatedPerson information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. Should be used as a basis for further profiling in use-cases where specific identity information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case. Typical use-case for no-basis-RelatedPerson involves information about relations person-patient. - Relations registered in norwegian Master Person Information Index (aka Folkeregisteret) - Other relationship information registered on a patient or person neccessary for patient treatment - Should not be used for contact persons for the patient with a predefined role in the patient care, as information as this is registered separately in the Patient resource
28PA Related Personhl7.fhir.us.physical-activity#currentR4A profile on RelatedPerson that mirrors the requirements of future US Core versions
29PetOwnerRelatedPersonfhir.zentricx-grupo-b#currentR4
30QICore RelatedPersonhl7.fhir.us.qicore#currentR4Profile of RelatedPerson for decision support/quality metrics. Defines the core set of elements and extensions for quality rule and measure authors.
31Related Personcara#currentR4This profile is used to add externals to a care team.
32Related Person - Parent - Vital Recordshl7.fhir.us.vr-common-library#currentR4This RelatedPerson profile contains constraints common to the Mother and Father profiles.
33Related Person - Parent Vital Recordshl7.fhir.us.vrsandbox#currentR4The RelatedPerson profile contains constraints common to the Mother and Father profiles. Serves as resource profile for RelatedPersonMother and RelatedPersonFather. This profile is designed to supplant the similar profile in VRDR
34Related Person - Parent Vital Recordshl7.fhir.us.vrsandbox#currentR4The RelatedPerson profile contains constraints common to the Mother and Father profiles.
35RelatedPerson - Father - Vital Recordshl7.fhir.us.vr-common-library#currentR4This RelatedPerson profile represents the father of the subject (patient). Different individuals may play different roles as the father (e.g., biological father, adoptive father, etc.).
36RelatedPerson - Father Natural - Vital Recordshl7.fhir.us.vr-common-library#currentR4This RelatedPerson profile represents the biological (natural) father of the newborn or fetus.
37RelatedPerson - Father Natural Vital Recordshl7.fhir.us.vrsandbox#currentR4The biological (natural) father of the newborn or fetus.
38RelatedPerson - Father Vital Recordshl7.fhir.us.vrsandbox#currentR4The father of the report subject. Different individuals may play different roles as the father (e.g., biological father, adoptive father, etc.). This profile is designed to supplant the similar profile in VRDR
39RelatedPerson - Father Vital Recordshl7.fhir.us.vrsandbox#currentR4The father of the subject. Different individuals may play different roles as the father (e.g., biological father, adoptive father, etc.).
40RelatedPerson - Mother - Vital Recordshl7.fhir.us.vr-common-library#currentR4This RelatedPerson profile represents the mother of the report subject. Different individuals may play different roles as the mother (e.g., biological mother, adoptive mother, etc.).
41RelatedPerson - Mother Gestational - Vital Recordshl7.fhir.us.vr-common-library#currentR4This RelatedPerson profile represents the woman who gave birth to or delivered the infant. The RelatedPerson structure is required in order to link the mother to the newborn or fetus.
42RelatedPerson - Mother Gestational Vital Recordshl7.fhir.us.vrsandbox#currentR4The woman who gave birth to or delivered the infant. The RelatedPerson structure is required in order to link the mother to the newborn or fetus.
43RelatedPerson - Mother Vital Recordshl7.fhir.us.vrsandbox#currentR4The mother of the report subject. Different individuals may play different roles as the mother (e.g., biological mother, adoptive mother, etc.). This profile is designed to supplant the similar profile in VRDR
44RelatedPerson - Mother Vital Recordshl7.fhir.us.vrsandbox#currentR4The mother of the report subject. Different individuals may play different roles as the mother (e.g., biological mother, adoptive mother, etc.).
45RelatedPerson Authorhl7.fhir.us.icsr-ae-reporting#currentR4The fields needed to specify the reporter of an ICSR report who is a related person to the patient.
46US Core RelatedPerson Profilehl7.fhir.us.core#currentR4This profile sets minimum expectations for the RelatedPerson resource to record, search, and fetch basic administrative information about persons with a legal or familial relationship to a patient. It identifies which core elements, extensions, vocabularies, and value sets **SHALL** be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases.
47WHO RelatedPersonwho.fhir.anc-cds#currentR4WHO RelatedPerson
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
RelatedPerson I I D I I D D I D I D I D
RelatedPerson.id D
RelatedPerson.meta C
RelatedPerson.meta.tag D
RelatedPerson.meta.security D
RelatedPerson.meta.source D
RelatedPerson.meta.versionId D
RelatedPerson.meta.extension D
RelatedPerson.meta.profile C
RelatedPerson.meta.lastUpdated C D
RelatedPerson.implicitRules C D C
RelatedPerson.language
RelatedPerson.text C C C C
RelatedPerson.contained
RelatedPerson.extension S C (2) S D (2) S C (3) S C (5) S C (5) S C (5)
RelatedPerson.extension.valueCodeableConcept S B M
RelatedPerson.modifierExtension C D C
RelatedPerson.identifier C S C D (4) C D D S C D (4) C C S D (3) C S C (2) S C (2) S C (2) C
RelatedPerson.identifier.use C C
RelatedPerson.identifier.value C C D (2) C C
RelatedPerson.identifier.system C B M C F D (2) C C
RelatedPerson.identifier.assigner D C
RelatedPerson.identifier.period D C
RelatedPerson.identifier.type D C C F C F C F
RelatedPerson.identifier.type.text C
RelatedPerson.identifier.type.coding C
RelatedPerson.identifier.type.coding.userSelected C
RelatedPerson.identifier.type.coding.display C F
RelatedPerson.identifier.type.coding.code C F
RelatedPerson.identifier.type.coding.version C
RelatedPerson.identifier.type.coding.system C F
RelatedPerson.identifier.extension D
RelatedPerson.active F F C D C F F F F F F C F C C C C
RelatedPerson.patient I C D D
RelatedPerson.patient.display C
RelatedPerson.patient.identifier C
RelatedPerson.patient.type C
RelatedPerson.patient.reference C
RelatedPerson.relationship C S C F B M (2) S B M S C B M (2) S C F B M (2) B M C B M C C F C F C F C F C F C F S C (3) C B M B M S C (3) D B M S D B M (4) C C C B M C F C F B M B M B M C F D C F D B M B M C B M
RelatedPerson.relationship.text F F F F F F (2) C C
RelatedPerson.relationship.coding C (2) S C (3)
RelatedPerson.relationship.coding.userSelected C (2)
RelatedPerson.relationship.coding.version C (2)
RelatedPerson.relationship.coding.code C (2) C F (2)
RelatedPerson.relationship.coding.system C F B M (2) C F (2) F (3) C F (2)
RelatedPerson.relationship.coding.display C (2) C F (2)
RelatedPerson.name C C C C C C C C C D I C C C C
RelatedPerson.name.period C
RelatedPerson.name.suffix C
RelatedPerson.name.prefix C
RelatedPerson.name.text C C
RelatedPerson.name.use C C
RelatedPerson.name.given C
RelatedPerson.name.family C
RelatedPerson.telecom C C C C C C C
RelatedPerson.telecom.extension S C
RelatedPerson.telecom.period C
RelatedPerson.telecom.rank C
RelatedPerson.telecom.use C
RelatedPerson.telecom.value C C C
RelatedPerson.telecom.system C C C
RelatedPerson.gender C C
RelatedPerson.birthDate C C
RelatedPerson.birthDate.extension S C D S C D (2) S C D (2)
RelatedPerson.address D D D C C C C C D C
RelatedPerson.address.period C
RelatedPerson.address.country C
RelatedPerson.address.district C
RelatedPerson.address.text C
RelatedPerson.address.type C
RelatedPerson.address.use C
RelatedPerson.address.postalCode C
RelatedPerson.address.state C
RelatedPerson.address.city C
RelatedPerson.address.line C
RelatedPerson.photo C C C
RelatedPerson.period D C C
RelatedPerson.communication C C
RelatedPerson.communication.extension
RelatedPerson.communication.modifierExtension
RelatedPerson.communication.language D B M
RelatedPerson.communication.preferred
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023