Design Comments: Address(es) for corresponding with the focal person in the context of this registry

Design Comments: Telecommunication address(es) for communicating with the focal person in the context of this registry

Design Comments: An interval of time specifying the period during which this record in a person registry is in effect, if such time limit is applicable and known

Design Comments: Value(s) that control the disclosure of information from a registry about this person

Design Comments: The association of an observation to a record from a registry, either a patient registry or an identified living subject registry.

For example, a "find candidates" query response might return the degree of match for each record returned.

Design Comments: Identifier(s) for this person. Note that these identifiers can only be used for matching purposes since no scoping organization or status information is included.

Design Comments: A textual or multimedia representation of this person. Descriptions are meant to be shown to interested human individuals.

Design Comments: Telecommunication address(es) for communicating with this person

Design Comments: A value representing the gender (sex) of this person. Note: this attribute does not include terms related to clinical gender which is a complex physiological, genetic and sociological concept that requires multiple observations in order to be comprehensively described.

Design Comments: The date and time this person was born. This could be an exact moment such as January 1, 1960 @ 03:00:00 EST or an approximate date such as January 1960.

Design Comments: An indication that this person is dead

Design Comments: The date and time this person died. This could be an exact moment such as January 1, 1960 @ 03:00:00 EST or an approximate date such as January 1960.

Design Comments: An indication that this person was part of a multiple birth

Design Comments: The order in which this person was born if part of a multiple birth

Design Comments: An indication that this person is a candidate to serve as an organ donor. Note: specifics of an organ donor agreement would be conveyed in a medico-legal document.

Design Comments: Address(es) for corresponding with this person

Design Comments: A value representing the domestic partnership status of this person

Design Comments: A relationship of the focal person with an organization to receive wages or salary. The purpose of this class is to identify the type of relationship the employee has to the employer rather than the nature of the work actually performed.

UsageNotes: EMPLOYEE Added Code to qualify employment relationship (e.g., paid employee, consultant, volunteer)

Design Comments: A formal relationship between the focal person (player) who owes loyalty to and is entitled by birth or naturalization to the protection of a nation (scoper)

UsageNotes: CITIZEN Added Code to qualify person’s legal status within nation (i.e., less than full citizen)

Design Comments: An enrollment of the focal person as a student of a school

Design Comments: A membership of the playing living subject in a group such as family, tribe, or religious organization

UsageNotes: MEMBER Changed effectiveTime from IVL<TS> to GTS to allow conveying that a person is an active member of a household on a particular schedule (e.g., alternate weeks).

Design Comments: An identifying relationship between the focal living subject and a scoping organization. Note that this could be an identifier used by the primary scoping organization in a different context.

Design Comments: A person or an organization (playing entity) that is authorized to provide or receive information about the focal person (scoping entity)

UsageNotes: CONTACT PARTY Changed Code from ContactRoleType to PersonalRelationshipRoleType concept domain (see annex)

Design Comments: A person or organization (playing entity) that is legally responsible for the care and management of the focal person (scoping entity)

UsageNotes: GUARDIAN Added Code to qualify guardianship relationship (e.g., guardianship held jointly by legally separated parents of child).

Design Comments: A personal relationship between the focal living subject and another living subject

Design Comments: The birthplace of the focal living subject

Design Comments: A language communication capability of the focal person

Design Comments: Employee identifier(s) for the focal person in this employment relationship

Design Comments: A value that qualifies the employment relationship a person has with the institution for whom he/she provides services, for example, Employee, Volunteer, Contractor, Consultant.

Design Comments: An Employee with negationInd "true" and an EmployerOrganization of "not applicable" null flavor conveys that the focal person is recorded as "not employed"

Design Comments: The focal person's work address(es) for this employment relationship (addr.use = WP)

Design Comments: The focal person's work telecommunications address(es) for this employment relationship (telecom.use = WP)

Design Comments: A value specifying the state of this employment relationship (based on the RIM Role class state-machine), for example, active, suspended, terminated

Design Comments: An interval of time specifying the period during which this employment relationship is in effect, if such time limit is applicable and known

Design Comments: The title of the job held, for example, Vice President, Senior Technical Analyst. This is a local name for the employee's occupation that does not necessarily correspond to any scheme for categorizing occupation. Trading partners that need a coded standard should be using Employee "occupation" attribute.

Design Comments: A code qualifying the employment regarding frequency or periodicity, such as, full-time vs. part-time

Design Comments: A code qualifying the classification of kind-of-work based upon a recognized industry or jurisdictional standard. OccupationCode is used to convey the person's occupation as opposed to jobCode which characterizes this particular job.

Design Comments: Identifier(s) for the focal person as a citizen of a nation

Design Comments: A value that qualifies a person's legal status within a country or nation.

Design Comments: An interval of time specifying the period during which this citizenship is in effect, if such time limit is applicable and known

Design Comments: A non-unique textual identifier or moniker for this nation

Design Comments: Student identifier(s) for the focal person in this school enrollment relationship

Design Comments: Address(es) for corresponding with the focal person in the context of this school enrollment

Design Comments: Telecommunication address(es) for communicating with the focal person in the context of this school enrollment

Design Comments: A value specifying the state of this school enrollment (based on the RIM Role class state-machine), for example, active, suspended, terminated

Design Comments: An interval of time specifying the period during which this school enrollment is in effect, if such time limit is applicable and known

Design Comments: Identifier(s) for this membership

Design Comments: A value further specifying the type of membership the playing living subject has in the scoping entity, drawn from the MemberRoleType domain

Design Comments: A value specifying the state of this membership (based on the RIM Role class state-machine), for example, active, suspended, terminated

Design Comments: Time specification for when this membership is in effect, if such time limit is applicable and known

Design Comments: Identifier(s) for this Group

Design Comments: A value further specifying the type of Group drawn from the OrganizationEntityType domain, for example "religious institution"

Design Comments: A non-unique textual identifier or moniker for the Group

Design Comments: A textual or multimedia depiction of the Group

Design Comments: A value representing whether the information associated with the Group is currently active or inactive

Design Comments: An interval of time specifying the period in which this Group physically existed if such time interval is applicable and known

Design Comments: Telecommunication address(es) for communicating with this group

Design Comments: An address for corresponding with this group

Design Comments: A membership of the playing living subject in a group such as family, tribe, or religious organization

UsageNotes: MEMBER Added 2nd member role to allow navigating from household to members

Design Comments: Identifier(s) for this membership

Design Comments: A value further specifying the type of membership the playing living subject has in the scoping entity, drawn from the MemberRoleType domain

Design Comments: A value specifying the state of this membership (based on the RIM Role class state-machine), for example, active, suspended, terminated

Design Comments: Time specification for when this membership is in effect, if such time limit is applicable and known

Design Comments: Observation about household composition and the reasons for that composition.

UsageNotes: OBSERVATION Added Observation Act about household membership

Design Comments: A value that qualifies the type of observation. For example, HHOBS indicating that this the observation of a person's living situation in a household.

Design Comments: The time for which the observation holds.

Design Comments: A value representing constraints around appropriate disclosure of this observation information.

Design Comments: A value representing the primary language in which the observation is recorded.

Design Comments: The result of the observation, i.e., a narrative report regarding the person's membership in a household, household and the composition of the household.

Design Comments: The means or technique used to ascertain the observation, for example, home visit, telephone interview, form completed by someone in the household.

Design Comments: A value specifying the state of this identifying relationship (based on the RIM Role class state-machine), for example, active, terminated, nullified

Design Comments: An interval of time specifying the period during which this identifying relationship is in effect, if such time limit is applicable and known

Design Comments: An identifier for this Care Provision agreement.

Design Comments: A value that qualifies the scope of responsibility taken-on by the performer of the Care Provision for a specific subject of care.

Design Comments: A value specifying the state of this Care Provision agreement, for example active, suspended, completed.

Design Comments: The time interval for which the performer exercises Care Provision for the subject, for example "week days from 7am to 8:30am".

Design Comments: Identifier(s) for this contact party relationship

Design Comments: For persons who play the role of contact (emergency contact or next of kin) for the focal person this attribute qualifies the type of personal relationship the contact has with the focal person. For example, spouse, parent,child.

Design Comments: An ContactParty with negationInd "true" and a contactPartyChoice association of "not applicable" null flavor conveys that the scoping person does not have a contact party relationship of the type specified by the ContactParty.code value; for example, "no next of kin" or "no emergency contact"

Design Comments: Address(es) for corresponding with this contact party

Design Comments: A value specifying the state of this contact party relationship (based on the RIM Role class state-machine), for example, active, suspended, terminated

Design Comments: An interval of time specifying the period during which this contact party relationship is in effect, if such time limit is applicable and known

Design Comments: Identifier(s) for this guardian relationship

Design Comments: A value that qualifies the guardianship relationship of a living subject (e.g., "guardianship held jointly by legally separated parents").

Design Comments: A Guardian with negationInd of "true" and a guardianPartyChoice association of "not applicable" null flavor conveys that the scoping person does not have a legal guardian

Design Comments: Address(es) for corresponding with the guardian of the focal person

Design Comments: Telecommunication address(es) for communicating with the guardian of the focal person

Design Comments: A value specifying the state of this guardian relationship (based on the RIM Role class state-machine), for example, active, suspended, terminated

Design Comments: An interval of time specifying the period during which this guardian relationship is in effect, if such time limit is applicable and known

Design Comments: A facsimile of the legal document establishing guardianship

Design Comments: Identifier(s) for this personal relationship

Design Comments: A PersonalRelationship with negationInd "true" and a relationshipHolder of "not applicable" null flavor conveys that the registry record for the scoping person explicitly does not include a related person with a personal relationship of the type specified by the code value. For example, the record for a child might convey "no recorded natural father."

Design Comments: Address(es) for corresponding with the related person

Design Comments: Telecommunication addresses for contacting the related person

Design Comments: A value specifying the state of this personal relationship (based on the RIM Role class state-machine), for example, following divorce a spouse relationship would be "terminated"

Design Comments: An interval of time specifying the period during which this personal relationship is in effect, if such time is applicable and known

Design Comments: A living subject's birth place represented as an address. Note: Either BirthPlace.addr or an associated Place.name must be valued

Design Comments: The position of a BirthPlace can be specified using spatial coordinates

Design Comments: A value representing the person's method of expression of this language Examples: expressed spoken, expressed written, expressed signed, received spoken, received written, received signed

Design Comments: A value representing the person's level of proficiency in this language. Examples: excellent, good, fair, poor

Design Comments: An indicator specifying whether or not this language is preferred by the focal person for the associated mode

Design Comments: An observation that conveys peripheral administrative information that is not central to model. Examples of administrative observations might be Shared Secret, Preferred Contact Method, Preferred Contact Times, Preferred Written Communication Format.

Design Comments: Identifier(s) for this observation instance

Design Comments: A value specifying the state of this observation (based on the RIM act state-machine), for example, completed, aborted, active

Design Comments: The time for which the observation holds (is effective) for the subject