COFE-Related-Person-1
RelatedPerson | |
Definition |
Information 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. |
Control | 0..* |
Type | RelatedPerson |
Comments | |
RelatedPerson.extension(Participant Function Code) | |
Definition |
Optional Extensions Element - found in all resources. |
Control | 0..1 |
Type | Extension |
Comments | |
RelatedPerson.extension(Participant Type) | |
Definition |
Optional Extensions Element - found in all resources. |
Control | 0..1 |
Type | Extension |
Comments | |
RelatedPerson.patient | |
Definition |
The patient this person is related to. |
Control | 1..1 |
Requirements |
We need to know which patient this RelatedPerson is related to. |
Comments | |
RelatedPerson.patient.reference | |
Definition |
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources. |
Control | 1..1 ? |
Type | String |
Comments |
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. |
RelatedPerson.patient.display | |
Definition |
Plain text narrative that identifies the resource in addition to the resource reference. |
Control | 0..1 |
Type | String |
Comments |
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. |
RelatedPerson.relationship(recipientRoleCode) | |
Definition |
recipientRoleCode uses a code from the RecipientNonClinicalPersonType vocabulary to describe the role of the non clinical person who is the recipient. |
Control | 1..1 |
Binding |
The relationship between the patient and the named person The codes SHALL be taken from http://fhir.nhs.net/ValueSet/cda-person-relationship-type-1 |
Type | CodeableConcept |
Requirements |
We need to know the relationship with the patient since it influences the interpretation of the information attributed to this person. |
Comments | |
RelatedPerson.relationship.coding | |
Definition |
A reference to a code defined by a terminology system. |
Control | 1..1 |
Binding |
A relationship between one person and another. These relationships are not necessarily mutually exclusive, for example a parent may be a child's next of kin. The codes SHALL be taken from http://fhir.nhs.net/ValueSet/cda-person-relationship-type-1 |
Type | Coding |
Requirements |
Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. |
Comments |
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labelled as UserSelected = true. |
RelatedPerson.relationship.coding.system | |
Definition |
The identification of the code system that defines the meaning of the symbol in the code. |
Control | 1..1 |
Type | Uri |
Requirements |
Need to be unambiguous about the source of the definition of the symbol. |
Comments |
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. |
Fixed Value | http://fhir.nhs.net/ValueSet/cda-person-relationship-type-1 |
RelatedPerson.relationship.coding.code | |
Definition |
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). |
Control | 1..1 |
Type | Code |
Requirements |
Need to refer to a particular code in the system. |
Comments | |
RelatedPerson.relationship.coding.display | |
Definition |
A representation of the meaning of the code in the system, following the rules of the system. |
Control | 1..1 |
Type | String |
Requirements |
Need to be able to carry a human-readable meaning of the code for readers that do not know the system. |
Comments | |
RelatedPerson.name | |
Definition |
A name associated with the person. |
Control | 1..1 |
Type | HumanName |
Requirements |
Related persons need to be identified by name, but it is uncommon to need details about multiple other names for that person. |
Comments | |
RelatedPerson.name.use | |
Definition |
Identifies the purpose for this name. |
Control | 0..1 |
Binding |
The use of a human name The codes SHALL be taken from http://hl7.org/fhir/ValueSet/name-use |
Type | Code |
Is Modifier | True |
Requirements |
Allows the appropriate name for a particular context of use to be selected from among a set of names. |
Comments |
This is labeled as "Is Modifier" because applications should not mistake a temporary or old name etc.for a current/permanent one. Applications can assume that a name is current unless it explicitly says that it is temporary or old. |
RelatedPerson.name.text | |
Definition |
A full text representation of the name. |
Control | 0..1 |
Type | String |
Requirements |
A renderable, unencoded form. |
Comments |
Can provide both a text representation and structured parts. |
RelatedPerson.name.family | |
Definition |
The part of a name that links to the genealogy. In some cultures (e.g. Eritrea) the family name of a son is the first name of his father. |
Control | 0..1 |
Type | String |
Aliases | surname |
Comments |
For family name, hyphenated names such as "Smith-Jones" are a single name, but names with spaces such as "Smith Jones" are broken into multiple parts. |
RelatedPerson.name.given | |
Definition |
Given name. |
Control | 0..* |
Type | String |
Aliases | first name, middle name |
Comments |
If only initials are recorded, they may be used in place of the full name. Not called "first name" since given names do not always come first. |
RelatedPerson.name.prefix | |
Definition |
Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the start of the name. |
Control | 0..1 |
Type | String |
Comments | |
RelatedPerson.name.suffix | |
Definition |
Part of the name that is acquired as a title due to academic, legal, employment or nobility status, etc. and that appears at the end of the name. |
Control | 0..* |
Type | String |
Comments | |
RelatedPerson.name.period | |
Definition |
Indicates the period of time when this name was valid for the named person. |
Control | 0..1 |
Type | Period |
Requirements |
Allows names to be placed in historical context. |
Comments | |
RelatedPerson.name.period.start | |
Definition |
The start of the period. The boundary is inclusive. |
Control | 0..1 ? |
Type | DateTime |
Comments |
If the low element is missing, the meaning is that the low boundary is not known. |
RelatedPerson.name.period.end | |
Definition |
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. |
Control | 0..1 ? |
Type | DateTime |
Comments |
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. |
RelatedPerson.telecom | |
Definition |
A contact detail for the person, e.g. a telephone number or an email address. |
Control | 0..1 |
Type | ContactPoint |
Requirements |
People have (primary) ways to contact them in some way such as phone, email. |
Comments |
Person may have multiple ways to be contacted with different uses or applicable periods. May need to have options for contacting the person urgently, and also to help with identification. |
RelatedPerson.telecom.system | |
Definition |
Telecommunications form for contact point - what communications system is required to make use of the contact. |
Control | 1..1 ? |
Binding |
Telecommunications form for contact point The codes SHALL be taken from http://hl7.org/fhir/ValueSet/contact-point-system |
Type | Code |
Comments | |
Example | phone |
RelatedPerson.telecom.value | |
Definition |
The actual contact point details, in a form that is meaningful to the designated communication system (i.e. phone number or email address). |
Control | 1..1 |
Type | String |
Requirements |
Need to support legacy numbers that are not in a tightly controlled format. |
Comments |
Additional text data such as phone extension numbers, or notes about use of the contact are sometimes included in the value. |
Example | 0191 4021122 |
RelatedPerson.telecom.use | |
Definition |
Identifies the purpose for the contact point. |
Control | 0..1 |
Binding |
Use of contact point The codes SHALL be taken from http://hl7.org/fhir/ValueSet/contact-point-use |
Type | Code |
Is Modifier | True |
Requirements |
Need to track the way a person uses this contact, so a user can choose which is appropriate for their purpose. |
Comments |
This is labeled as "Is Modifier" because applications should not mistake a temporary or old contact etc.for a current/permanent one. Applications can assume that a contact is current unless it explicitly says that it is temporary or old. |
Example | work |
RelatedPerson.telecom.period | |
Definition |
Time period when the contact point was/is in use. |
Control | 0..1 |
Type | Period |
Comments | |
RelatedPerson.telecom.period.start | |
Definition |
The start of the period. The boundary is inclusive. |
Control | 0..1 ? |
Type | DateTime |
Comments |
If the low element is missing, the meaning is that the low boundary is not known. |
RelatedPerson.telecom.period.end | |
Definition |
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. |
Control | 0..1 ? |
Type | DateTime |
Comments |
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. |
RelatedPerson.address | |
Definition |
Address where the related person can be contacted or visited. |
Control | 0..1 |
Type | Address |
Requirements |
Need to keep track where the related person can be contacted per postal mail or visited. |
Comments | |
RelatedPerson.address.use | |
Definition |
The purpose of this address. |
Control | 0..1 |
Binding |
The use of an address The codes SHALL be taken from http://hl7.org/fhir/ValueSet/address-use |
Type | Code |
Is Modifier | True |
Requirements |
Allows an appropriate address to be chosen from a list of many. |
Comments |
This is labeled as "Is Modifier" because applications should not mistake a temporary or old address etc.for a current/permanent one. Applications can assume that an address is current unless it explicitly says that it is temporary or old. |
Example | home |
RelatedPerson.address.type | |
Definition |
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both. |
Control | 0..1 |
Binding |
The type of an address (physical / postal) The codes SHALL be taken from http://hl7.org/fhir/ValueSet/address-type |
Type | Code |
Comments | |
Example | both |
RelatedPerson.address.text | |
Definition |
A full text representation of the address. |
Control | 0..1 |
Type | String |
Requirements |
A renderable, unencoded form. |
Comments |
Can provide both a text representation and parts. |
Example | 137 Nowhere Street, Erewhon 9132 |
RelatedPerson.address.line | |
Definition |
This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information. |
Control | 0..* |
Type | String |
Requirements |
home | work | temp | old - purpose of this address. |
Comments | |
Example | 137 Nowhere Street |
RelatedPerson.address.city | |
Definition |
The name of the city, town, village or other community or delivery center. |
Control | 0..1 |
Type | String |
Aliases | Municpality |
Comments | |
Example | Erewhon |
RelatedPerson.address.district | |
Definition |
The name of the administrative area (county). |
Control | 0..1 |
Type | String |
Aliases | County |
Comments |
District is sometimes known as county, but in some regions 'county' in used in place of city (municipality), so county name should be conveyed in city instead. |
Example | Madison |
RelatedPerson.address.postalCode | |
Definition |
A postal code designating a region defined by the postal service. |
Control | 0..1 |
Type | String |
Aliases | Zip |
Comments | |
Example | 9132 |
RelatedPerson.address.country | |
Definition |
Country - a nation as commonly understood or generally accepted. |
Control | 0..1 |
Type | String |
Comments |
ISO 3166 3 letter codes can be used in place of a full country name. |
RelatedPerson.address.period | |
Definition |
Time period when address was/is in use. |
Control | 0..1 |
Type | Period |
Requirements |
Allows addresses to be placed in historical context. |
Comments | |
Example | Hl7.Fhir.Model.Period |
RelatedPerson.address.period.start | |
Definition |
The start of the period. The boundary is inclusive. |
Control | 0..1 ? |
Type | DateTime |
Comments |
If the low element is missing, the meaning is that the low boundary is not known. |
RelatedPerson.address.period.end | |
Definition |
The end of the period. If the end of the period is missing, it means that the period is ongoing. The start may be in the past, and the end date in the future, which means that period is expected/planned to end at that time. |
Control | 0..1 ? |
Type | DateTime |
Comments |
The high value includes any matching date/time. i.e. 2012-02-03T10:00:00 is in a period that has a end value of 2012-02-03. |