| ARCHETYPE ID | openEHR-EHR-CLUSTER.structured_address.v0 |
|---|---|
| Concept | Structured address |
| Description | Structured details that represent a fine-grained, local level of geographical/physical description of a location for use within a health record. |
| Use | Use to record structured details that, used in conjunction with the other high-level address components i.e. ‘Suburb/Town/Locality’, ‘Postcode’, and ‘State/Territory/Province’, forms a complete geographical/physical address. In most common use cases where an address needs to be included within a health record, the free text entry within the 'Unstructured address' element in the CLUSTER.address archetype will be sufficient. Use this archetype only in situations when finer-grained detail about one or more lower-level address components is required, by nesting this archetype within the 'Structured address' SLOT in CLUSTER.address. |
| Misuse | Not to be used to record an address as part of maintaining an official demographic register or index. Use a formal Master Patient Index or Health Provider Index for this purpose, or archetypes based on the openEHR Demographic Information Model. |
| Purpose | To record structured details that represent a fine-grained, local level of geographical/physical description of a location for use within a health record. |
| References | Health Care Client Identification - AS 5017-2006. New South Wales (AU): Standards Australia; 2006. Health Care Provider Identification - AS 4846-2006. New South Wales (AU): Standards Australia; 2006. Health informatics — Identification of subjects of health care - ISO/TS 22220:2007. Geneva: International Organization for Standardization; 2007. HL7 FHIR Resource - Person v4.0.1: R4 [Internet]. Health Level Seven International; [accessed 2021 05 04]. Available from: http://hl7.org/fhir/2021May/person.html. |
| Copyright | © openEHR Foundation |
| Authors | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2021-04-14 |
| Other Details Language | Author name: Heather Leslie Organisation: Atomica Informatics Email: heather.leslie@atomicainformatics.com Date originally authored: 2021-04-14 |
| Other Details (Language Independent) |
|
| Keywords | |
| Lifecycle | rejected |
| UID | 87cb4a1f-b326-4bdc-ae36-aec11b835023 |
| Language used | en |
| Citeable Identifier | 1013.1.5360 |
| Revision Number | 0.0.1 |
| items | |
| Unit type | Unit type: The specification of the type of a separately identifiable portion within a building/complex, marina etc. to clearly distinguish it from another. Coding with an external terminology is preferred, where possible. For example: Apartment or unit; or Shop. Where a building or other type of unit is present in a complex of such buildings or units, the data elements 'Unit type' and 'Unit number' should be used in conjunction - Apartment 35A; or Shop 209. |
| Unit number | Unit number: The specification of the number or identifier of a building/complex, marina etc. to clearly distinguish it from another. For example: 35A; or 209. Where a building or other type of unit is present in a complex of such buildings or units, the data elements 'Unit type' and 'Unit number' should be used in conjunction - Apartment 35A; or Shop 209. |
| Site name | Site name: The full name used to identify a physical building or property as part of its location. If a 'Site name' requires additional specific details, such as including a reference to a wing or other components of a building complex, use a comma to separate the wing reference from the rest of the site name. For example: Victoria wing, Treasury building; Brindabella station. |
| Level type | Level type: Descriptor used to classify the type of floor or level of a multi-storey building or complex. Coding with an external terminology is preferred, where possible. For example: Floor (FL); Level (L); Basement (B); Lower Ground (LG); Upper Ground (UG); Ground Level (G); or Mezzanine (M). If 'Level' or 'Floor' are selected then they need to be paired with the 'Level number' data element. |
| Level number | Level number: Numeric or alphanumeric descriptor used to identify the floor or level of a multi-storey building or complex. A 'Level number' must be recorded with its corresponding 'Level type'. For example: L3; or FL1A. |
| Street number | Street number: The numeric or alphanumeric reference number of a house or property that is unique within a street name. For example: '17'; '39A'; or '401-403'. If a Lot number is recorded, this data element is redundant - only one of 'Street number' or 'Lot number' is permitted in an address. |
| Lot number | Lot number: The Lot reference allocated to an address in the absence of street numbering. For example: 'Lot 17A'; or 'Lot 716-718'. If a Street number is recorded, this data element is redundant - only one of 'Street number' or 'Lot number' is permitted in an address. |
| Street name | Street name: The name that identifies a public thoroughfare and differentiates it from others in the same suburb, town, city or locality. For example: 'Jessie'; or 'Bourke'. |
| Street type | Street type: A descriptor for the type of public thoroughfare. Coding with an external terminology is preferred, where possible. For example: Hwy (Highway). |
| Street suffix | Street suffix: Descriptor used to qualify the 'Street name' used for directional references. Coding with an external terminology is preferred, where possible. For example: North; or Upper. |
| Postal delivery type | Postal delivery type: Identification for the channel of postal delivery. Coding with an external terminology is preferred, where possible. Used where mail is to be delivered to a box, bag or agent for pick-up by the intended recipient or to a rural mail box number where no other address exists. For example: 'Poste Restante' (also known as Care-of Post Office); 'Roadside Delivery' (RSD); or 'Post Office Box' (PO Box) |
| Postal delivery number | Postal delivery number: Identification number for the channel of postal delivery. For example: 'C96'. |
| Other contributors | |
| Translators |
|