Contact

Overview
Each Indivo record is expected to contain exactly one ContactInformation document, identifying the record holder, and containing his important medical contacts. The core component of that document, however -- the ConciseContactInformationType -- is used throughout the document model whenever one must identify a person, organization, or electronic system.

Schema

 * Syntax-Highlighted Schema
 * Raw Schema

ConciseContactInformationType
When used, choose either a PersonName (with optional JobTitle and Affiliation fields), OrganizationName, or SystemName.


 * NameType (required, multiple - choice among this, OrganizationName, and SystemName)
 * Name of this contact person. When multiple names are provided, first in the list will be considered default.
 * Name of this contact person. When multiple names are provided, first in the list will be considered default.


 * string (optional)
 * Contact person's job title, used especially when medically relevant.
 * Contact person's job title, used especially when medically relevant.


 * string (optional)
 * Contact person's institutional affiliation.
 * Contact person's institutional affiliation.


 * string (required - choice among this, PersonName, and SystemName)
 * Name of this organizational contact. Suitable for hospitals, businesses, etc.
 * Name of this organizational contact. Suitable for hospitals, businesses, etc.


 * string (required - choice among this, PersonName, and SystemName)
 * Name of this electronic system contact. Suitable for subscription agents, third-party health applications, etc.
 * Name of this electronic system contact. Suitable for subscription agents, third-party health applications, etc.


 * AddressType (optional, multiple)
 * Addresses for this contact.
 * Addresses for this contact.


 * CommunicationType (optional, multiple)
 * Methods to contact this person, e.g. phone, e-mail, fax, pager, etc.
 * Methods to contact this person, e.g. phone, e-mail, fax, pager, etc.

NameType

 * string (optional)
 * The contact's title, prefixing his name to signify veneration, official position, or a professional or academic qualification, e.g. Mr., Dr., Prof., Hon., etc.
 * The contact's title, prefixing his name to signify veneration, official position, or a professional or academic qualification, e.g. Mr., Dr., Prof., Hon., etc.


 * string (optional)
 * The contact's first name.
 * The contact's first name.


 * string (optional)
 * The contact's middle name.
 * The contact's middle name.


 * string (optional)
 * The contact's last, or family, name.
 * The contact's last, or family, name.


 * string (optional)
 * A professional, academic, or familial addition to the contact's name, e.g. Jr., Sr., III., MD., PhD.
 * A professional, academic, or familial addition to the contact's name, e.g. Jr., Sr., III., MD., PhD.


 * string (optional)
 * Optional description of this name's purpose, most suitable for when multiple names are used for a single contact, e.g. birth/maiden name, alias, etc.
 * Usage: Common values include birth (birth name), premarital (pre-marital, or "maiden," name), and alias.
 * Usage: Common values include birth (birth name), premarital (pre-marital, or "maiden," name), and alias.

AddressType

 * string (required)
 * Purpose of this addresses vis-a-vis the contact, e.g. default, home, office, mailing.
 * Usage: Set Type to default when describing the primary address of an organization or system, or when great specificity is unavailable. Home and office are suitable for persons.  Mailing addresses should be provided when they differ from a contact's geographical location.  Using other values is at the discretion of the data source.  Data processors should treat this field in a case-insensitive manner, and should display addresses marked default before other types.
 * Usage: Set Type to default when describing the primary address of an organization or system, or when great specificity is unavailable. Home and office are suitable for persons.  Mailing addresses should be provided when they differ from a contact's geographical location.  Using other values is at the discretion of the data source.  Data processors should treat this field in a case-insensitive manner, and should display addresses marked default before other types.


 * integer (required)
 * The relative priority of this address among others listed for this contact.
 * Usage: Set Priority to 1 by default. Data processors should display addresses in order of Priority, then Type.
 * Usage: Set Priority to 1 by default. Data processors should display addresses in order of Priority, then Type.


 * string (optional)
 * First line of the contact's street address.
 * First line of the contact's street address.


 * string (optional)
 * Second line of the contact's street address.
 * Second line of the contact's street address.


 * string (optional)
 * Contact's county name.
 * Contact's county name.


 * string (optional)
 * Contact's city or town name.
 * Contact's city or town name.


 * string (optional)
 * Contact's state, province, or other national subdivision.
 * Usage: The Indivo Reference User Interface expects state abbreviations, rather than full state names, but either is permissible.
 * Usage: The Indivo Reference User Interface expects state abbreviations, rather than full state names, but either is permissible.


 * string (optional)
 * Contact's ZIP or other postal code.
 * Contact's ZIP or other postal code.


 * string (optional)
 * Contact's country name.
 * Contact's country name.

CommunicationType

 * string (required)
 * The communication method described in by this element.
 * Usage: Commonly used values include phone, email (no hyphen), pager, and fax. Data processors should treat this field in a case-insensitive manner.
 * Usage: Commonly used values include phone, email (no hyphen), pager, and fax. Data processors should treat this field in a case-insensitive manner.


 * integer (required)
 * The relative priority of this communication method among others listed for this contact.
 * Usage: Set Priority to 1 by default. Data processors should display communication types in order of Medium, then Priority (note distinction from AddressType).
 * Usage: Set Priority to 1 by default. Data processors should display communication types in order of Medium, then Priority (note distinction from AddressType).


 * string (required)
 * Describes the general destination of this communication method.
 * Usage: Commonly used values include default, home, mobile, and office. Choose default when greater specificity is unavailable.  Data processors should treat this field in a case-insensitive manner.
 * Usage: Commonly used values include default, home, mobile, and office. Choose default when greater specificity is unavailable.  Data processors should treat this field in a case-insensitive manner.


 * string (required)
 * The actual unique code to reach the contact via this communication method, e.g. telephone number, e-mail address, etc.
 * The actual unique code to reach the contact via this communication method, e.g. telephone number, e-mail address, etc.

ContactInformationType
Each Indivo Record must contain exactly one ContactInformation document, defined by the ContactInformationType. This type extends the ConciseContactInformationType (described above), adding the following three fields.


 * PersonalIdentifierType (optional, multiple)
 * Government- or institution-issued identifiers, e.g. social security number, driver's license number, etc.
 * Government- or institution-issued identifiers, e.g. social security number, driver's license number, etc.


 * RelationInformationType (optional, multiple)
 * Record holder's important family or medical contacts.
 * Record holder's important family or medical contacts.


 * ImageType (optional, multiple)
 * Photograph of record holder.
 * Photograph of record holder.

RelationInformationType
This type extends the ConciseContactInformationType (described above), adding the following two fields.


 * boolean (required)
 * A true value indicates that this individual is the record holder's emergency contact.
 * A true value indicates that this individual is the record holder's emergency contact.


 * CodedValueType (required)
 * The relationship of this contact to the record holder.
 * &raquo; Refer to coding systems indivo-personal-relationships-1.0, indivo-medical-relationships-1.0, and indivo-org-relationships-1.0.
 * &raquo; Refer to coding systems indivo-personal-relationships-1.0, indivo-medical-relationships-1.0, and indivo-org-relationships-1.0.

PersonalIdentifierType

 * string (required)
 * The identifier value.
 * The identifier value.


 * string (required)
 * Description of this identifier.
 * Usage: Common values include ssn (social security number) or drivers-license (driver's license number). Data processors should treat this field in a case-insensitive manner.
 * Usage: Common values include ssn (social security number) or drivers-license (driver's license number). Data processors should treat this field in a case-insensitive manner.