Use to record details about the location of a person, physical building or landmark as they are known or understood in the course of clinical documentation, often ad hoc or when it is not appropriate or possible to use an address lookup service. Examples include:
- the business address of an organisation providing home care to an individual; or
- the postal address of the copyholder of an advanced care record, within the EVALUATION.advance_care_directive archetype; or
- the physical location of a fall or accident.
The scope of this archetype has been constrained to carry the commonest structured components for identifying a specific physical building or landmark. In this context, a complete address may be described using:
- One or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded; and
- 'Town' to represent a suburb, town, city, village, or community;
- 'District/County' to represent a local government district;
- 'State/Territory/Province’ to represent a major government district;
- ‘Postcode’, and
- ‘Country'.
However, this archetype can be extended to include additional fine-grained details about the address by nesting the CLUSTER.structured_address within the 'Structured address' SLOT.
This CLUSTER.address archetype can also be used as a proxy for an address in formal demographic address data when reviewing a template with domain experts - for example, an assessment where reviewers would expect to see the individual's full contact details at the top of the assessment form.
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.
HL7 FHIR Resource - Organization v4.0.1: R4 [Internet]. Health Level Seven International; [accessed 2021 05 04]. Available from: http://hl7.org/fhir/2021May/organization.html
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2021-04-14
Organisation: Atomica Informatics
Email: heather.leslie@atomicainformatics.com
Date originally authored: 2021-04-14
- Licence: This work is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/4.0/.
- Custodian Organisation: openEHR Foundation
- 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. HL7 FHIR Resource - Organization v4.0.1: R4 [Internet]. Health Level Seven International; [accessed 2021 05 04]. Available from: http://hl7.org/fhir/2021May/organization.html
- Original Namespace: org.openehr
- Original Publisher: openEHR Foundation
- Custodian Namespace: org.openehr
- MD5-CAM-1.0.1: 112E6F77A1FACD78CC4B7ED6810372F4
- Build Uid: 7ce6e91c-68bd-4aa0-b33e-934ce14d0911
- Revision: 1.1.3
Occurrences for this data element is set to 0..* to allow one or more free text 'Address line' data elements to represent the huge variety of ways that ‘street-level' details may need to be recorded within the context of a specified 'Town'. Multiple address lines can be represented in a template, renamed as 'Address line 1', 'Address line 2,' etc. For example: '7A/52 Davis Street' or 'Apartment 7A' as Address line 1 with '52 Davis Street' as Address line 2; a roadside mail box location, such as 'RMB 725, Princes Highway'; or using a descriptive landmark, such as or 'Corner of Smith & Brown Streets' or 'Second house north of the general store with the red door'.
For example: suburb, town, city, settlement, village, or community. Coding with an external terminology is preferred, where possible. For example: 'Fitzroy'; 'Manchester'; 'Kingston' or 'Bergen'.
Coding with an external terminology is preferred, where possible. For example: 'Surf Coast' and 'Yarra' local government councils in Victoria, Australia;and the Parishes of 'Saint Andrew' and 'Kingston' in Jamaica..
Coding with an external terminology is preferred, where possible. For example: 'New South Wales' and 'Queensland' in Australia; 'British Columbia' and 'Nova Scotia' in Canada; and the Counties of 'Cornwall', 'Middlesex' & 'Surrey' in Jamaica.
Also known as a postcode or ZIP code.
For example: Australia; Canada; Jamaica; or Norway. Coding with an external terminology, such as EN ISO 3166–1 Alpha 2 country code, is recommended.
For example: to represent a structured, fine-grained address, or be used as standardised concepts that can be concatenated together to consistently construct a single 'Address line'.
Include:
openEHR-EHR-CLUSTER.structured_
Also known as a geocode. For example: GPS coordinates concatenating longitude, latitude +/-altitude; Open Location Code or Plus Code; Universal Transverse Mercator (UTM); and geohash.
Latitude is represented by positive values north of the equator and negative values south of the equator. For example the latitude of the Eiffel Tower is 48.858093.
Property: Angle, plane
Units: -90.0..90.0 °
Limit decimal places: 6
Longitude is represented by negative values west of Prime Meridian and positive values east of Prime Meridian. For example the longitude of the Eiffel Tower is 2.294694.
Property: Angle, plane
Units: -180.0..180.0 °
Limit decimal places: 6
For example, the altitude of the top of the Eiffel Tower is +324m.
Property: Length
Units: m
Limit decimal places: 2
For example: a location on a Google or iOS map.
For example: physical or postal.
Choice of:
Coded Text- Physical [A physical location that can be visited.]
- Postal [Address used as a destination for mailing letters or parcels.]
- Both [Address of a physical location, also used as a destination for mail.]
Text
Choice of:
- Coded Text
- Business [Address of the physical location of a business or office.]
- Residential [Address of where a person is living on a regular basis.]
- Temporary accommodation [Address of where a person is living on a temporary basis.]
- Text
Vebjørn Arntzen, Oslo University Hospital, Norway (openEHR Editor)
Astrid Askeland, Dips AS, Norway
Silje Ljosland Bakke, Helse Vest IKT AS, Norway (openEHR Editor)
Keisha Barwise, MOHW/IDB HSSP Project, Jamaica
SB Bhattacharyya, Bhattacharyyas Clinical Records Research & Informatics LLP, India
Yexuan Cheng, 浙江大学, China
Candice de Lisser, Ministry of Health and Wellness, Jamaica
Ludvig Eek Hofmann, Cambio Healthcare Systems AB, Sweden
Valborg Ellingsen, Haraldsplass Diakonale sykehus, Norway
Heather Grain, Llewelyn Grain Informatics, Australia
Martin Grundberg, Cambio Healthcare Systems, Sweden
Mikkel Johan Gaup Grønmo, Regional forvaltning EPJ, Helse Nord, Norway (openEHR Editor)
Rebecka Hansson, Cambio Healthcare Systems AB, Sweden
Anca Heyd, DIPS ASA, Norway
Joost Holslag, Nedap, Netherlands
Evelyn Hovenga, EJSH Consulting, Australia
Gunnar Jårvik, Helse Vest IKT AS, Norway
Gunn-Lisbeth Kleiven, Oslo universitetssykehus HF, Norway
Shinji Kobayashi, National Institute of Public Health, Japan
Kanika Kuwelker, Helse Vest IKT, Norway
Jörgen Kuylenstierna, eWeave AB, Sweden
Liv Laugen, Oslo University Hospital, Norway, Norway (openEHR Editor)
Heather Leslie, Atomica Informatics, Australia (openEHR Editor)
Lars Morgan Karlsen, Nordlandssykehuset Bodø, Norway
Mikael Nyström, Cambio Healthcare Systems AB, Sweden
Jayashree Panickar, Karolinska Institute, Sweden
Erik Skjemstad, Helse Nord RHF, Norway
Natalia Strauch, Medizinische Hochschule Hannover, Germany
Norwegian Review Summary, Norwegian Public Hospitals, Norway
Nyree Taylor, Ocean Health Systems, Australia
Anders Thurin, VGR, Sweden
John Tore Valand, Helse Bergen, Norway (openEHR Editor)
Marit Alice Venheim, Helse Vest IKT, Norway (openEHR Editor)
Ina Wille, Helse-Vest RHF, Norway
- German: Natalia Strauch, Alina Rehberg, Medizinische Hochschule Hannover, Strauch.Natalia@mh-hannover.de, rehberg.alina@mh-hannover.de
- Portuguese (Portugal): Hugo Silva, University of Minho, pg50416@uminho.pt
- Swedish: Erik Sundvall, Karolinska Institutet + Karolinska University Hospital, Region Stockholm + Linköping University, erik.sundvall@regionstockholm.se
- Norwegian Bokmål: Liv Laugen, John Tore Valand, Vebjørn Arntzen, Kanika Kuwelker, Oslo University Hospital, Norway, Helse Bergen, Helse Vest IKT, liv.laugen@ous-hf.no, john.tore.valand@helse-bergen.no, john.tore.valand@helse-vest-ikt.no, varntzen@ous-hf.no, kanika.kuwelker@helse-vest-ikt.no
- Portuguese (Brazil): Nelio Borrozzino, L2d Saúde Digital, nelio.borrozzino@l2d.com.br
- Greek: Erasmia Partafylla, Sigmasoft, c.partafylla@sigmasoft.gr
- French: Vanessa Pereira, Luxembourg Institute of Health (LIH), vanessapereira@protonmail.com
- Dutch: Joost Holslag, Joost Holslag Geneeskunde & Advies, info@joostholslag.nl, MD