| ARCHETYPE ID | openEHR-DEMOGRAPHIC-ADDRESS.address-provider.v0 |
|---|---|
| Concept | Healthcare provider address |
| Description | Healthcare provider address, based on ISO standards. |
| Use | Used in demographic services to register data about a healthcare provider address. |
| Misuse | This archetype can not used for email address, IP address, computer address, telephone, fax and pager. For these items use the electronic_communication archetype. |
| Purpose | Representation of data about a healthcare provider address, based on ISO standards. This address represents a geographic location which can be used in several ways: business address, postal address, etc. |
| References | ISO/DTS 27527:2007(E) - Provider Identification - Draft Technnical Specification - International Organization for Standardization |
| Copyright | © openEHR Foundation |
| Authors | Forfatternavn: Sergio Miranda Freire & Rigoleta Dutra Mediano Dias Organisasjon: Universidade do Estado do Rio de Janeiro - UERJ E-post: sergio@lampada.uerj.br Opprinnelig skrevet dato: 2009-05-22 |
| Other Details Language | Forfatternavn: Sergio Miranda Freire & Rigoleta Dutra Mediano Dias Organisasjon: Universidade do Estado do Rio de Janeiro - UERJ E-post: sergio@lampada.uerj.br Opprinnelig skrevet dato: 2009-05-22 |
| Other Details (Language Independent) |
|
| Keywords | demographic service, healthcare provider address, geographic location |
| Lifecycle | in_development |
| UID | 5c4b8ea6-4c9c-4c8f-9c37-b95e0a5e0aff |
| Language used | en |
| Citeable Identifier | 1078.36.1555 |
| Revision Number | 0.0.1-alpha |
| details | |
| Address lines | Address lines: A composite of one or more standard address components that describe a low level of geographical/physical description of a location that, used in conjunction with the other high-level address components i.e. ‘suburb / town / locality name’, ‘postal code’, ‘state / territory / province’, and ‘country’, forms a complete geographical/physical address. |
| Building/complex sub-unit type—abbreviation | Building/complex sub-unit type—abbreviation: The specification of the type of a separately identifiable portion within a building/complex, marina etc. to clearly distinguish it from another. Mulige datatyper:
|
| Building/complex sub-unit number | Building/complex sub-unit number: The specification of the number of identifier of a building/complex, marina etc. to clearly distinguish it from another. |
| Address site name | Address site name: The full name used to identify the physical building or property as part of its location. |
| Floor/level number | Floor/level number: Descriptor used to identify the floor or level of a multi-storey building/complex. |
| Floor/level type | Floor/level type: Descriptor used to classify the type of floor or level of a multi-storey building/complex. |
| Lot number | Lot number: Section, allotment number. |
| Street type code | Street type code: A code that identifies the type of public thoroughfare. Mulige datatyper:
|
| Street name | Street name: The name that identifies a public thoroughfare and differentiates it from others in the same suburb/town/locality. |
| Street number | Street number: The numeric or string reference number of a house or property that is unique within a street name, suburb. |
| Street suffix code | Street suffix code: Term used to qualify the street name suitable for directional references. Mulige datatyper:
|
| Address line visualization | Address line visualization: How the address line is presented to the user. |
| District | District: District. |
| Census area | Census area: Area defined by the Brazilian Geographic and Statistics Bureau according to the spacial distribution of the population. |
| Delivery point identifier | Delivery point identifier: A unique number assigned to a postal address as designated by the postal service. |
| Postal code (ZIP code) | Postal code (ZIP code): The code for a postal delivery area, aligned with locality, suburb or place for the address, as defined by the postal service. |
| Suburb/town/locality | Suburb/town/locality: The full name of the general locality containing the specific address. |
| State/territory/province identifier | State/territory/province identifier: An identifier of the province, state or territory containing the address. Begrensning: State codes [valid codes for state/territory/province.] |
| Country identifier | Country identifier: A code representing the country component of an address. Begrensning: Country codes [valid codes for countries.] |
| Address type start date accuracy indicator | Address type start date accuracy indicator: An indication of the accuracy of the address type start date at the component level for the date. It is expressed by means of a sequence of three characters with possible values A (accurate), E (estimated) or U (unknown) each. The characters represent the accuracy for the year, month and day respectively. This element was introduced in order to be compatible with ISO 22220, but openEHR reference model represents date accuracy in a different way (see the data types specification). |
| Address type end date accuracy indicator | Address type end date accuracy indicator: An indication of the accuracy of the address type end date at the component level for the date. It is expressed by means of a sequence of three characters with possible values A (accurate), E (estimated) or U (unknown) each. The characters represent the accuracy for the year, month and day respectively. This element was introduced in order to be compatible with ISO 22220, but openEHR reference model represents date accuracy in a different way (see the data types specification). |
| Communication privacy | Communication privacy: Indicates that this communication mechanism is not to be openly displayed, except to specific providers. |
| Healthcare provider identifier | Healthcare provider identifier: Identifier of a healthcare provider who may access this communication mechanism. |
| Other contributors | Rigoleta Dutra, Ministry of Defense, Brazil (openEHR Editor) Sergio Freire, State University of Rio de Janeiro, Brazil (openEHR Editor) Sebastian Garde, Ocean Informatics, Germany (Editor) Omer Hotomaroglu, Turkey (Editor) Heather Leslie, Ocean Informatics, Australia (Editor) Ian McNicoll, freshEHR Clinical Informatics, United Kingdom (openEHR Editor) |
| Translators |
|