Universal API Implementation Guide
1.1.19 - ci-build

Universal API Implementation Guide - Local Development build (v1.1.19). See the Directory of published versions

Resource Profile: UAPI RelatedPerson

Official URL: https://fhir.developer.gene.com/StructureDefinition/uapi-relatedPerson Version: 1.1.19
Active as of 2021-06-04 Responsible: Genentech USIX PE Realm: United States of America flag Computable Name: UapiRelatedPerson

This profile constrains the Related Person resource to be included in UAPI data exchanges

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from RelatedPerson

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... patient 1..1Reference(UAPI Patient)The patient this person is related to
.... reference 0..1stringPatient resource UUID
.... type 0..1uriType the reference refers to (e.g. "Patient")
Required Pattern: Patient
... relationship 1..1CodeableConceptThe nature of the relationship
.... coding 1..1CodingCode defined by a terminology system
..... system 1..1uriIdentity of the terminology system
Required Pattern: http://terminology.hl7.org/CodeSystem/v3-RoleCode
..... code 1..1codeSymbol in syntax defined by the system
... name 1..1HumanNameA name associated with the person
.... use 1..1codeusual | official | temp | nickname | anonymous | old | maiden
Required Pattern: official
.... family 1..1stringUp to 255 Characters
.... given 1..1stringUp to 255 Characters
.... telecom:All Slices Content/Rules for all slices
..... system 1..1codephone | fax | email | pager | url | sms | other
..... value 1..1stringThe actual contact point details
..... use 1..1codehome | work | temp | old | mobile - purpose of this contact point
.... telecom:Phone 1..*ContactPointA contact detail for the person
..... system 0..1codephone | fax | email | pager | url | sms | other
Required Pattern: phone
..... value 0..1stringPhone (10 digit numeric values only)
.... telecom:Email 0..*ContactPointA contact detail for the person
..... system 0..1codephone | fax | email | pager | url | sms | other
Required Pattern: email
... photo 0..0

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... active ?!Σ0..1booleanWhether this related person's record is in active use
.... reference ΣC0..1stringPatient resource UUID
.... type Σ0..1uriType the reference refers to (e.g. "Patient")
Binding: ResourceType (extensible)
Required Pattern: Patient
... relationship Σ1..1CodeableConceptThe nature of the relationship
Binding: PatientRelationshipType (preferred): The nature of the relationship between a patient and the related person.


.... coding Σ1..1CodingCode defined by a terminology system
..... system Σ1..1uriIdentity of the terminology system
Required Pattern: http://terminology.hl7.org/CodeSystem/v3-RoleCode
..... code Σ1..1codeSymbol in syntax defined by the system
... name Σ1..1HumanNameA name associated with the person
.... use ?!Σ1..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: NameUse (required)
Required Pattern: official
.... family Σ1..1stringUp to 255 Characters
.... given Σ1..1stringUp to 255 Characters
This repeating element order: Given Names appear in the correct order for presenting the name
... Slices for telecom Σ1..*ContactPointA contact detail for the person
Slice: Unordered, Closed by value:system
.... telecom:All Slices Content/Rules for all slices
..... system ΣC1..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
..... value Σ1..1stringThe actual contact point details
..... use ?!Σ1..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
.... telecom:Phone Σ1..*ContactPointA contact detail for the person
..... system ΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
Required Pattern: phone
..... value Σ0..1stringPhone (10 digit numeric values only)
..... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
.... telecom:Email Σ0..*ContactPointA contact detail for the person
..... system ΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
Required Pattern: email
..... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
RelatedPerson.patient.typeextensiblePattern: Patient
RelatedPerson.relationshippreferredPatientRelationshipType
RelatedPerson.name.userequiredPattern: official
RelatedPerson.telecom.systemrequiredContactPointSystem
RelatedPerson.telecom.userequiredContactPointUse
RelatedPerson.telecom:Phone.systemrequiredPattern: phone
RelatedPerson.telecom:Phone.userequiredContactPointUse
RelatedPerson.telecom:Email.systemrequiredPattern: email
RelatedPerson.telecom:Email.userequiredContactPointUse
NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierA human identifier for this person
... active ?!Σ0..1booleanWhether this related person's record is in active use
... patient Σ1..1Reference(UAPI Patient)The patient this person is related to
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... reference ΣC0..1stringPatient resource UUID
.... type Σ0..1uriType the reference refers to (e.g. "Patient")
Binding: ResourceType (extensible)
Required Pattern: Patient
.... identifier Σ0..1IdentifierLogical reference, when literal reference is not known
.... display Σ0..1stringText alternative for the resource
... relationship Σ1..1CodeableConceptThe nature of the relationship
Binding: PatientRelationshipType (preferred): The nature of the relationship between a patient and the related person.


.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ1..1CodingCode defined by a terminology system
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system Σ1..1uriIdentity of the terminology system
Required Pattern: http://terminology.hl7.org/CodeSystem/v3-RoleCode
..... version Σ0..1stringVersion of the system - if relevant
..... code Σ1..1codeSymbol in syntax defined by the system
..... display Σ0..1stringRepresentation defined by the system
..... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text Σ0..1stringPlain text representation of the concept
... name Σ1..1HumanNameA name associated with the person
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... use ?!Σ1..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: NameUse (required)
Required Pattern: official
.... text Σ0..1stringText representation of the full name
.... family Σ1..1stringUp to 255 Characters
.... given Σ1..1stringUp to 255 Characters
This repeating element order: Given Names appear in the correct order for presenting the name
.... prefix Σ0..*stringParts that come before the name
This repeating element order: Prefixes appear in the correct order for presenting the name
.... suffix Σ0..*stringParts that come after the name
This repeating element order: Suffixes appear in the correct order for presenting the name
.... period Σ0..1PeriodTime period when name was/is in use
... Slices for telecom Σ1..*ContactPointA contact detail for the person
Slice: Unordered, Closed by value:system
.... telecom:All Slices Content/Rules for all slices
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system ΣC1..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
..... value Σ1..1stringThe actual contact point details
..... use ?!Σ1..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
..... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
..... period Σ0..1PeriodTime period when the contact point was/is in use
.... telecom:Phone Σ1..*ContactPointA contact detail for the person
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system ΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
Required Pattern: phone
..... value Σ0..1stringPhone (10 digit numeric values only)
..... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
..... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
..... period Σ0..1PeriodTime period when the contact point was/is in use
.... telecom:Email Σ0..*ContactPointA contact detail for the person
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system ΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
Required Pattern: email
..... value Σ0..1stringThe actual contact point details
..... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
..... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
..... period Σ0..1PeriodTime period when the contact point was/is in use
... gender Σ0..1codemale | female | other | unknown
Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

... birthDate Σ0..1dateThe date on which the related person was born
... address Σ0..*AddressAddress where the related person can be contacted or visited
... 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
.... id 0..1stringUnique id for inter-element referencing
.... 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: CommonLanguages (preferred): IETF language tag

Additional BindingsPurpose
AllLanguagesMax Binding
.... preferred 0..1booleanLanguage preference indicator

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
RelatedPerson.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
RelatedPerson.patient.typeextensiblePattern: Patient
RelatedPerson.relationshippreferredPatientRelationshipType
RelatedPerson.name.userequiredPattern: official
RelatedPerson.telecom.systemrequiredContactPointSystem
RelatedPerson.telecom.userequiredContactPointUse
RelatedPerson.telecom:Phone.systemrequiredPattern: phone
RelatedPerson.telecom:Phone.userequiredContactPointUse
RelatedPerson.telecom:Email.systemrequiredPattern: email
RelatedPerson.telecom:Email.userequiredContactPointUse
RelatedPerson.genderrequiredAdministrativeGender
RelatedPerson.communication.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding

This structure is derived from RelatedPerson

Summary

Mandatory: 13 elements
Prohibited: 1 element

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element RelatedPerson.telecom is sliced based on the value of value:system (Closed)

Differential View

This structure is derived from RelatedPerson

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... patient 1..1Reference(UAPI Patient)The patient this person is related to
.... reference 0..1stringPatient resource UUID
.... type 0..1uriType the reference refers to (e.g. "Patient")
Required Pattern: Patient
... relationship 1..1CodeableConceptThe nature of the relationship
.... coding 1..1CodingCode defined by a terminology system
..... system 1..1uriIdentity of the terminology system
Required Pattern: http://terminology.hl7.org/CodeSystem/v3-RoleCode
..... code 1..1codeSymbol in syntax defined by the system
... name 1..1HumanNameA name associated with the person
.... use 1..1codeusual | official | temp | nickname | anonymous | old | maiden
Required Pattern: official
.... family 1..1stringUp to 255 Characters
.... given 1..1stringUp to 255 Characters
.... telecom:All Slices Content/Rules for all slices
..... system 1..1codephone | fax | email | pager | url | sms | other
..... value 1..1stringThe actual contact point details
..... use 1..1codehome | work | temp | old | mobile - purpose of this contact point
.... telecom:Phone 1..*ContactPointA contact detail for the person
..... system 0..1codephone | fax | email | pager | url | sms | other
Required Pattern: phone
..... value 0..1stringPhone (10 digit numeric values only)
.... telecom:Email 0..*ContactPointA contact detail for the person
..... system 0..1codephone | fax | email | pager | url | sms | other
Required Pattern: email
... photo 0..0

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... active ?!Σ0..1booleanWhether this related person's record is in active use
.... reference ΣC0..1stringPatient resource UUID
.... type Σ0..1uriType the reference refers to (e.g. "Patient")
Binding: ResourceType (extensible)
Required Pattern: Patient
... relationship Σ1..1CodeableConceptThe nature of the relationship
Binding: PatientRelationshipType (preferred): The nature of the relationship between a patient and the related person.


.... coding Σ1..1CodingCode defined by a terminology system
..... system Σ1..1uriIdentity of the terminology system
Required Pattern: http://terminology.hl7.org/CodeSystem/v3-RoleCode
..... code Σ1..1codeSymbol in syntax defined by the system
... name Σ1..1HumanNameA name associated with the person
.... use ?!Σ1..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: NameUse (required)
Required Pattern: official
.... family Σ1..1stringUp to 255 Characters
.... given Σ1..1stringUp to 255 Characters
This repeating element order: Given Names appear in the correct order for presenting the name
... Slices for telecom Σ1..*ContactPointA contact detail for the person
Slice: Unordered, Closed by value:system
.... telecom:All Slices Content/Rules for all slices
..... system ΣC1..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
..... value Σ1..1stringThe actual contact point details
..... use ?!Σ1..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
.... telecom:Phone Σ1..*ContactPointA contact detail for the person
..... system ΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
Required Pattern: phone
..... value Σ0..1stringPhone (10 digit numeric values only)
..... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
.... telecom:Email Σ0..*ContactPointA contact detail for the person
..... system ΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
Required Pattern: email
..... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
RelatedPerson.patient.typeextensiblePattern: Patient
RelatedPerson.relationshippreferredPatientRelationshipType
RelatedPerson.name.userequiredPattern: official
RelatedPerson.telecom.systemrequiredContactPointSystem
RelatedPerson.telecom.userequiredContactPointUse
RelatedPerson.telecom:Phone.systemrequiredPattern: phone
RelatedPerson.telecom:Phone.userequiredContactPointUse
RelatedPerson.telecom:Email.systemrequiredPattern: email
RelatedPerson.telecom:Email.userequiredContactPointUse

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. RelatedPerson 0..*RelatedPersonA person that is related to a patient, but who is not a direct target of care
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierA human identifier for this person
... active ?!Σ0..1booleanWhether this related person's record is in active use
... patient Σ1..1Reference(UAPI Patient)The patient this person is related to
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... reference ΣC0..1stringPatient resource UUID
.... type Σ0..1uriType the reference refers to (e.g. "Patient")
Binding: ResourceType (extensible)
Required Pattern: Patient
.... identifier Σ0..1IdentifierLogical reference, when literal reference is not known
.... display Σ0..1stringText alternative for the resource
... relationship Σ1..1CodeableConceptThe nature of the relationship
Binding: PatientRelationshipType (preferred): The nature of the relationship between a patient and the related person.


.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... coding Σ1..1CodingCode defined by a terminology system
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system Σ1..1uriIdentity of the terminology system
Required Pattern: http://terminology.hl7.org/CodeSystem/v3-RoleCode
..... version Σ0..1stringVersion of the system - if relevant
..... code Σ1..1codeSymbol in syntax defined by the system
..... display Σ0..1stringRepresentation defined by the system
..... userSelected Σ0..1booleanIf this coding was chosen directly by the user
.... text Σ0..1stringPlain text representation of the concept
... name Σ1..1HumanNameA name associated with the person
.... id 0..1idUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
.... use ?!Σ1..1codeusual | official | temp | nickname | anonymous | old | maiden
Binding: NameUse (required)
Required Pattern: official
.... text Σ0..1stringText representation of the full name
.... family Σ1..1stringUp to 255 Characters
.... given Σ1..1stringUp to 255 Characters
This repeating element order: Given Names appear in the correct order for presenting the name
.... prefix Σ0..*stringParts that come before the name
This repeating element order: Prefixes appear in the correct order for presenting the name
.... suffix Σ0..*stringParts that come after the name
This repeating element order: Suffixes appear in the correct order for presenting the name
.... period Σ0..1PeriodTime period when name was/is in use
... Slices for telecom Σ1..*ContactPointA contact detail for the person
Slice: Unordered, Closed by value:system
.... telecom:All Slices Content/Rules for all slices
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system ΣC1..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
..... value Σ1..1stringThe actual contact point details
..... use ?!Σ1..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
..... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
..... period Σ0..1PeriodTime period when the contact point was/is in use
.... telecom:Phone Σ1..*ContactPointA contact detail for the person
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system ΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
Required Pattern: phone
..... value Σ0..1stringPhone (10 digit numeric values only)
..... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
..... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
..... period Σ0..1PeriodTime period when the contact point was/is in use
.... telecom:Email Σ0..*ContactPointA contact detail for the person
..... id 0..1idUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... system ΣC0..1codephone | fax | email | pager | url | sms | other
Binding: ContactPointSystem (required)
Required Pattern: email
..... value Σ0..1stringThe actual contact point details
..... use ?!Σ0..1codehome | work | temp | old | mobile - purpose of this contact point
Binding: ContactPointUse (required)
..... rank Σ0..1positiveIntSpecify preferred order of use (1 = highest)
..... period Σ0..1PeriodTime period when the contact point was/is in use
... gender Σ0..1codemale | female | other | unknown
Binding: AdministrativeGender (required): The gender of a person used for administrative purposes.

... birthDate Σ0..1dateThe date on which the related person was born
... address Σ0..*AddressAddress where the related person can be contacted or visited
... 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
.... id 0..1stringUnique id for inter-element referencing
.... 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: CommonLanguages (preferred): IETF language tag

Additional BindingsPurpose
AllLanguagesMax Binding
.... preferred 0..1booleanLanguage preference indicator

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / Code
RelatedPerson.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
RelatedPerson.patient.typeextensiblePattern: Patient
RelatedPerson.relationshippreferredPatientRelationshipType
RelatedPerson.name.userequiredPattern: official
RelatedPerson.telecom.systemrequiredContactPointSystem
RelatedPerson.telecom.userequiredContactPointUse
RelatedPerson.telecom:Phone.systemrequiredPattern: phone
RelatedPerson.telecom:Phone.userequiredContactPointUse
RelatedPerson.telecom:Email.systemrequiredPattern: email
RelatedPerson.telecom:Email.userequiredContactPointUse
RelatedPerson.genderrequiredAdministrativeGender
RelatedPerson.communication.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding

This structure is derived from RelatedPerson

Summary

Mandatory: 13 elements
Prohibited: 1 element

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element RelatedPerson.telecom is sliced based on the value of value:system (Closed)

 

Other representations of profile: CSV, Excel, Schematron