Generated Narrative: StructureDefinition RelatedPersonRelationshipAndNameParticipant version: 4; Last updated: 2023-07-11 23:42:06+0000 Name Flags Card. Type Description & Constraints Participant1 1..1 Participant1 XML Namespace: urn:hl7-org:v3 Base for all types and resources Instance of this type are validated by templateId Logical Container: ClinicalDocument (CDA Class) #xD; Slices for templateId 1..* II Slice: Unordered, Open by value:root, value:extension #xD; templateId:related-person 1..1 II #xD; @root 1..1 oid, uuid, ruid Required Pattern: 2.16.840.1.113883.10.20.22.5.8 #xD; @extension 1..1 st Required Pattern: 2023-05-01 #xD; @typeCode 1..1 cs Fixed Value: IND #xD; associatedEntity <a style="padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;; padding-left: 3px; padding-right: 3px; border: 1px maroon solid; font-weight: bold; color: #301212; background-color: #fdf4f4;" href="http://hl7.org/fhir/R5/conformance-rules.html#constraints" title="This element has or is affected by constraints ( should-addr, should-telecom )">C 1..1 AssociatedEntity Constraints: should-addr, should-telecom #xD; @classCode 1..1 cs #xD; code 1..1 CE 헨?헦?헖?헗?헜?: Related Person's Relationship - This associatedEntity/code represents the person's relationship to the patient. Binding: Personal And Legal Relationship Role Type (required) #xD; addr 0..* USRealmAddress #xD; telecom 0..* TEL #xD; associatedPerson 1..1 Person The associatedPerson represents the name and contact information of the related person #xD; name 1..* USRealmPersonNamePNUSFIELDED 헨?헦?헖?헗?헜?: Related Person's Name #xD; Documentation for this format
Related Person Relationship and Name Participant
HL7 International - Structured Documents
This template represents a generic participant person that has a relationship to the patient. (e.g., parent, next-of-kin, neighbor). The related person's name is required and it is recommended that the person's contact information is present. The more specific CDA participant of Guardian (recordTarget/patientRole/patient/guardian) can be used to represent a legally responsible guardian of the patient within the header. This template may be used to represent a person with any relationship to the patient within the header, or at the entry level when pertinent to a particular clinical statement.
Defines the basic properties of every data value. This is an abstract type, meaning that no value can be just a data value without belonging to any concrete type. Every concrete type is a specialization of this general abstract DataValue type.
If a value is an exceptional value (NULL-value), this specifies in what way and why proper information is missing.
When valued in an instance, this attribute signals the imposition of realm-specific constraints. The value of this attribute identifies the realm in question
When valued in an instance, this attribute signals the imposition of constraints defined in an HL7-specified message type. This might be a common type (also known as CMET in the messaging communication environment), or content included within a wrapper. The value of this attribute provides a unique identifier for the type in question.
An II instance must have either a root or an nullFlavor.
A human readable name or mnemonic for the assigning authority. The Assigning Authority Name has no computational value. The purpose of a Assigning Authority Name is to assist an unaided human interpreter of an II value to interpret the authority. Note: no automated processing must depend on the assigning authority name to be present in any form.
Specifies if the identifier is intended for human display and data entry (displayable = true) as opposed to pure machine interoperation (displayable = false).
Identifies the type as an HL7 Registered model
A character string as a unique identifier within the scope of the identifier root.
When valued in an instance, this attribute signals the imposition of a set of template-defined constraints. The value of this attribute provides a unique identifier for the templates in question
A unique identifier that guarantees the global uniqueness of the instance identifier. The root alone may be the entire instance identifier.
SHALL contain exactly one [1..1] @typeCode="IND" Indirect (CodeSystem: HL7ParticipationType urn:oid:2.16.840.1.113883.5.90) (CONF:4537-32982).
SHALL contain exactly one [1..1] associatedEntity (CONF:4537-32978).
This associatedEntity SHALL contain exactly one [1..1] code, which SHALL be selected from ValueSet Personal And Legal Relationship Role Type 2.16.840.1.113883.11.20.12.1 DYNAMIC (CONF:4537-32985).
𝗨𝗦𝗖𝗗𝗜: Related Person's Relationship - This associatedEntity/code represents the person's relationship to the patient.
This associatedEntity SHALL contain exactly one [1..1] code, which SHALL be selected from ValueSet Personal And Legal Relationship Role Type urn:oid:2.16.840.1.113883.11.20.12.1 DYNAMIC (CONF:4537-32985).
This associatedEntity SHOULD contain zero or more [0..*] US Realm Address (AD.US.FIELDED) (identifier: urn:oid:2.16.840.1.113883.10.20.22.5.2) (CONF:4537-32979).
This associatedEntity SHOULD contain zero or more [0..*] telecom (CONF:4537-32986).
The associatedPerson represents the name and contact information of the related person
This associatedEntity SHALL contain exactly one [1..1] associatedPerson (CONF:4537-32980).
This associatedPerson SHALL contain at least one [1..*] US Realm Person Name (PN.US.FIELDED) (identifier: urn:oid:2.16.840.1.113883.10.20.22.5.1.1) (CONF:4537-32987).
The desc extension allows multimedia depictions of patients, healthcare providers, or other individuals to be included in a CDA document.
Each participant role other than an informant/relatedEntity may have zero or more relationship roles with the patient. Each of these roles can be expressed with an asPatientRelationship element which further describes the type of role using a code element.