ITK - Document Reference

ITK-RelatedPerson-1

This RelatedPerson resource represents information for a person with a relationship with the patient

NameCard.TypeDescription & Constraints
..RelatedPersonRelatedPersonThis Related Person resource represents information for a person with a relationship with the patient

...id0..1IdLogical id of this artifact

...meta0..1MetaMetadata about the resource

...implicitRules0..1UriA set of rules under which this content was created

...language0..1CodeLanguage of the resource content
Binding A human language. (http://tools.ietf.org/html/bcp47)
Binding Strength Required

...text0..1NarrativeText summary of the resource, for human interpretation

...contained0..*ResourceContained, inline Resources

...identifier0..*IdentifierA human identifier for this person

....id0..1Idxml:id (or equivalent in JSON)

....use0..1Codeusual | official | temp | secondary (If known)
Binding Identifies the purpose for this identifier, if known . (http://hl7.org/fhir/DSTU2/valueset-identifier-use.html)
Binding Strength Required

....type0..1CodeableConceptDescription of identifier
Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. (http://hl7.org/fhir/DSTU2/valueset-identifier-type.html)
Binding Strength Extensible

.....id0..1Idxml:id (or equivalent in JSON)

.....coding0..*CodingCode defined by a terminology system

......id0..1Idxml:id (or equivalent in JSON)

......system0..1UriIdentity of the terminology system

......version0..1StringVersion of the system - if relevant

......code0..1CodeSymbol in syntax defined by the system

......display0..1StringRepresentation defined by the system

......userSelected0..1BooleanIf this coding was chosen directly by the user

.....text0..1StringPlain text representation of the concept

....system0..1UriThe namespace for the identifier
Example Value http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri

....value1..1StringThe value that is unique

....period0..1PeriodTime period when id is/was valid for use

.....id0..1Idxml:id (or equivalent in JSON)

.....start0..1DateTimeStarting time with inclusive boundary

.....end0..1DateTimeEnd time with inclusive boundary, if not ongoing

....assigner0..1Reference (CareConnect-Organization-1)Organization that issued id (may be just text)

.....id0..1Idxml:id (or equivalent in JSON)

.....reference1..1StringRelative, internal or absolute URL reference

.....display0..1StringText alternative for the resource

...patient1..1Reference (CareConnect-Patient-1)The patient this person is related to

....id0..1Idxml:id (or equivalent in JSON)

....reference1..1StringRelative URL reference

....display0..1StringText alternative for the resource

...relationship1..1CodeableConceptThe nature of the relationship
Binding A set of codes that can be used to indicate the relationship between a Patient and a Related Person. (http://hl7.org/fhir/DSTU2/valueset-relatedperson-relationshiptype.html)
Binding Strength Required

....id0..1Idxml:id (or equivalent in JSON)

....coding1..1CodingCode defined by a terminology system

.....id0..1Idxml:id (or equivalent in JSON)

.....system1..1UriIdentity of the terminology system

.....code1..1CodeSymbol in syntax defined by the system

.....display1..1StringRepresentation defined by the system

...name0..1HumanNameA name associated with the person

....id0..1Idxml:id (or equivalent in JSON)

....use0..1CodeTo indicate the type of name
Binding The use of a human name (http://hl7.org/fhir/DSTU2/valueset-name-use.html)
Binding Strength Required

....text0..1StringText representation of the full name

....family0..1StringFamily name (often called 'Surname')

....given0..*StringGiven names (not always 'first'). Includes middle names

....prefix0..1StringParts that come before the name

....suffix0..*StringParts that come after the name

....period0..1PeriodTime period when name was/is in use

.....id0..1Idxml:id (or equivalent in JSON)

.....start0..1DateTimeStarting time with inclusive boundary

.....end0..1DateTimeEnd time with inclusive boundary, if not ongoing

...telecom0..*ContactPointA contact detail for the person

....id0..1Idxml:id (or equivalent in JSON)

....system1..1Codephone | fax | email | pager | other
Binding Telecommunications form for contact point (http://hl7.org/fhir/DSTU2/valueset-contact-point-system.html)
Binding Strength Required

....value1..1StringThe actual contact point details

....use0..1Codehome | work | temp | old | mobile - purpose of this contact point
Binding Use of contact point (http://hl7.org/fhir/DSTU2/valueset-contact-point-system.html)
Binding Strength Required

....rank0..1PositiveIntSpecify preferred order of use (1 = highest)

....period0..1PeriodTime period when the contact point was/is in use

.....id0..1Idxml:id (or equivalent in JSON)

.....start0..1DateTimeStarting time with inclusive boundary

.....end0..1DateTimeEnd time with inclusive boundary, if not ongoing

...gender0..1Codemale | female | other | unknown
Binding The gender of a person used for administrative purposes. (http://hl7.org/fhir/DSTU2/valueset-administrative-gender.html)
Binding Strength Required

...birthDate0..1DateThe date on which the related person was born

...address0..*AddressAddress where the related person can be contacted or visited

....id0..1Idxml:id (or equivalent in JSON)

....use0..1CodeA vocabulary that should be used to further define the organisation address when required.
Binding The use of an address (http://hl7.org/fhir/DSTU2/valueset-address-use.html)
Binding Strength Required

....type0..1Codepostal | physical | both
Binding The type of an address (physical / postal) (http://hl7.org/fhir/DSTU2/valueset-address-type.html)
Binding Strength Required

....text0..1StringText representation of the address

....line0..*StringStreet name, number, direction & P.O. Box etc.

....city0..1StringName of city, town etc.

....district0..1StringDistrict name (aka county)

....postalCode0..1StringPostal code for area

....country0..1StringCountry (can be ISO 3166 3 letter code)

....period0..1PeriodTime period when address was/is in use
Example Value Hl7.Fhir.Model.Period

.....id0..1Idxml:id (or equivalent in JSON)

.....start0..1DateTimeStarting time with inclusive boundary

.....end0..1DateTimeEnd time with inclusive boundary, if not ongoing

...period0..1PeriodPeriod of time that this relationship is considered valid

....id0..1Idxml:id (or equivalent in JSON)

....start0..1DateTimeStarting time with inclusive boundary

....end0..1DateTimeEnd time with inclusive boundary, if not ongoing