Address: This evidence captures details of a description of a location - as written or printed on mail, as directions for delivery.

Many concurrent addresses can be stored for a participant, but one address is marked as the primary or default address. A type e.g. home, work, etc. can be recorded for each address.

Example

John Smith is a registered person in Curam. Two address records are stored for John; his home address and his business address.

Technical Notes

Many types of Curam entities can have a related address; logically these entities have an 'address' attribute which is a 'complex data type'. Physically, however, each of these entities has an address attribute which relates to a row in the address table.

Addresses may vary over time (e.g. a participant may move house or notify the organization of a typographical error in the address). Most organizations have a legal requirement to keep an exact record (including any typographical errors) of an address to which correspondence or payment has been sent. To support this requirement, Curam has the ability to 'clone' an address record and mark the clone as non-modifiable. Typically Curam financial and correspondence functionality stores references to these non-modifiable clone addresses.

The storage format for address data is as follows:

• client widget version required

• address ID

• address layout type

• country code

• modifiable indicator

• address version number

• a list of type/value pairs (list differs according to the address layout type - see below)

By default, Curam supports these address layout types:

• US address format (Line1/Line2/Line3/City/State/Zip)

• UK address format (Line1/Line2/Line3/Line4/Line5/City/County/Postcode/Country)

• Freeform address format (Free text)

Named parts of an address may be stored as rows on address element.