Union of http://hl7.org/cda/us/ccda/StructureDefinition/RelatedPersonRelationshipAndNameParticipant and http://hl7.org/cda/us/ccda/StructureDefinition/RelatedPersonRelationshipAndNameParticipant

This is the set of resources that conform to either of the profiles Related Person Relationship and Name Participant (http://hl7.org/cda/us/ccda/StructureDefinition/RelatedPersonRelationshipAndNameParticipant) and Related Person Relationship and Name Participant (http://hl7.org/cda/us/ccda/StructureDefinition/RelatedPersonRelationshipAndNameParticipant). E.g. what you have to deal with if you get resources conforming to one of them

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Participant1 1..1Base for all types and resources
... nullFlavor 0..1??Binding: ?? (required)
... realmCode 0..*CS
... typeId 0..1II
.... nullFlavor 0..1??Binding: ?? (required)
.... assigningAuthorityName 0..1??
.... displayable 0..1??
.... root 1..1??, ??, ??
.... extension 1..1??
... typeCode 1..1??Binding: ?? (required)
... contextControlCode 0..1??Binding: ?? (required)
... functionCode 0..1CE
... time 0..1IVL_TS
... associatedEntity C1..1AssociatedEntityshould-addr: SHOULD contain addr
should-telecom: SHOULD contain telecom
.... nullFlavor 0..1??Binding: ?? (required)
.... realmCode 0..*CS
.... typeId 0..1II
..... nullFlavor 0..1??Binding: ?? (required)
..... assigningAuthorityName 0..1??
..... displayable 0..1??
..... root 1..1??, ??, ??
..... extension 1..1??
.... templateId 0..*II
.... classCode 1..1??Binding: ?? (required)
.... sdtcIdentifiedBy 0..*IdentifiedBy
.... code 1..1CEleft: (USCDI) Related Person's Relationship - This associatedEntity/code represents the person's relationship to the patient.; right: 𝗨𝗦𝗖𝗗𝗜: Related Person's Relationship - This associatedEntity/code represents the person's relationship to the patient.
Binding: ?? (required)
.... addr C0..*??Base for all types and resources
shall-city: SHALL contain exactly one [1..1] city (CONF:81-7292).
shall-streetAddressLine: SHALL contain at least one and not more than 4 streetAddressLine (CONF:81-7291).
should-use: SHOULD contain @use
should-country: SHOULD contain country
81-7296: **SHALL NOT** have mixed content except for white space (CONF:81-7296)
81-10024: If the country is US, the state element is required and SHALL be selected from ValueSet StateValueSet but SHOULD have @nullFlavor if the state is unknown. If country is not specified, it's assumed to be US. If country is something other than US, the state MAY be present but MAY be bound to different vocabularies (CONF:81-10024).
81-10025: If the country is US, the postalCode element is required but SHOULD have @nullFlavor if the postalCode is unknown. If country is not specified, it's assumed to be US. If country is something other than US, the postalCode MAY be present but MAY be bound to different vocabularies (CONF:81-10025).
shall-max-ad-parts: SHALL have at most one of each: state, city, postalCode, and country
.... telecom 0..*TEL
.... associatedPerson 1..1PersonThe associatedPerson represents the name and contact information of the related person
..... nullFlavor 0..1??Binding: ?? (required)
..... realmCode 0..*CS
..... typeId 0..1II
...... nullFlavor 0..1??Binding: ?? (required)
...... assigningAuthorityName 0..1??
...... displayable 0..1??
...... root 1..1??, ??, ??
...... extension 1..1??
..... templateId 0..*II
..... classCode 0..1??Binding: ?? (required)
..... determinerCode 0..1??Binding: ?? (required)
..... name C1..*??left: (USCDI) Related Person's Name; right: 𝗨𝗦𝗖𝗗𝗜: Related Person's Name
pn-no-ls: No PN name part may have a qualifier of LS.
81-9371: The content of name **SHALL** be either a conformant Patient Name (PTN.US.FIELDED), or a string (CONF:81-9371).
81-9372: The string **SHALL NOT** contain name parts (CONF:81-9372).
..... sdtcDesc 0..1ED
..... sdtcAsPatientRelationship 0..*InfrastructureRoot
...... nullFlavor 0..1??Binding: ?? (required)
...... realmCode 0..*CS
...... typeId 0..1II
....... nullFlavor 0..1??Binding: ?? (required)
....... assigningAuthorityName 0..1??
....... displayable 0..1??
....... root 1..1??, ??, ??
....... extension 1..1??
...... templateId 0..*II
...... classCode 1..1??
...... determinerCode 0..1??
...... code 1..1CE
.... scopingOrganization 0..1Organization

doco Documentation for this format