Details and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Lista de identificadores únicos de la ubicación. Incluye Cédula Jurídica del Registro Nacional y Código de Prestador de Servicios de Salud.

Organization label locations in registries, need to keep track of those.

Propósito del identificador. Se recomienda usar 'official' para la Cédula Jurídica.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Tipo de identificador: Cédula Jurídica, Código de Prestador u otro tipo de identificación.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

CodeSystem de tipos de identificadores para ubicaciones en Costa Rica.

Allows users to make use of identifiers when the identifier system is not known.

Identificador único del sistema que emite o registra el identificador de la ubicación.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

Valor único del identificador dentro del sistema.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Indica si la ubicación está activa y operativa. Un valor 'active' significa que la ubicación está en uso; 'suspended' indica que está temporalmente inactiva; 'inactive' indica que ha sido desactivada.

ValueSet de estados de Location definidos en FHIR.

Nombre oficial de la ubicación, tal como aparece registrada en el Registro Nacional.

Se recomienda usar el nombre oficial registrado.

Nombres alternativos, apodos o nombres comunes utilizados para referirse a la ubicación.

There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the location.

Over time locations and organizations go through many changes and can be known by different names.

For searching knowing previous names that the location was known by can be very useful.

Persona responsable o punto de contacto dentro de la ubicación.

The address/telecom use code 'home' are not to be used. Note that these contacts are not the contact details of people who provide the service (that would be through PractitionerRole), these are official contacts for the Healthcare itself for specific purposes. E.g. Mailing Addresses, Billing Addresses, Contact numbers for Booking or Billing Enquiries, general web address, web address for online bookings etc.

If this is empty (or the type of interest is empty), refer to the organization's contacts.

Need to keep track of both simple contact details and also assigned contacts within larger organizations.

Nombre completo de la persona de contacto.

If there is no named individual, the telecom/address information is not generally monitored by a specific individual.

Teléfono, correo u otro dato para contactar a la persona.

Dirección postal completa de la ubicación, incluyendo calle, ciudad, provincia y código postal.

Se recomienda usar direcciones oficiales registradas.

If locations can be visited, we need to keep track of their address.

Propósito de la dirección (principal, trabajo, temporal, etc.).

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address (home / work / etc.).

Allows an appropriate address to be chosen from a list of many.

Tipo de dirección (postal, física o ambas).

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Calle, número, apartamento y otras líneas de dirección específicas. Mínimo una línea requerida.

Nombre del cantón (ciudad). Incluye una extensión con el código del cantón basado en el ZipCode de Costa Rica.

Extensión para el código del cantón basado en el ZipCode de Costa Rica.

Nombre del distrito. Incluye una extensión con el código del distrito basado en el ZipCode de Costa Rica.

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

Extensión para el código del distrito basado en el ZipCode de Costa Rica.

Nombre de la provincia. Incluye una extensión con el código de la provincia basado en el ZipCode de Costa Rica.

Extensión para el código de la provincia basado en el ZipCode de Costa Rica.

Código postal o código de localidad de Costa Rica (opcional).

Nombre del país. Incluye una extensión con el código ISO 3166-1 alpha-3 (CR para Costa Rica).

ISO 3166 2- or 3- letter codes MAY be used in place of a human readable country name.

Extensión para el código de país en formato ISO 3166-1 alpha-3.

Coordenadas geográficas (latitud y longitud) que representan la ubicación física.

To define a boundary shape for this location use the standard extension [http://hl7.org/fhir/StructureDefinition/location-boundary-geojson](http://hl7.org/fhir/extensions/StructureDefinition-location-boundary-geojson.html), and search using the contains special search parameter.

For mobile applications and automated route-finding knowing the exact location of the Location is required.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Valor decimal que representa la longitud de la ubicación.

Valor decimal que representa la latitud de la ubicación.

Valor decimal que representa la altitud de la ubicación en metros sobre el nivel del mar.

Referencia a otra ubicación de la cual esta ubicación es parte. Por ejemplo, una sala es parte de un hospital o consultorio.

For purposes of location, display and identification, knowing which locations are located within other locations is important.

Lista de identificadores únicos de la ubicación. Incluye Cédula Jurídica del Registro Nacional y Código de Prestador de Servicios de Salud.

Propósito del identificador. Se recomienda usar 'official' para la Cédula Jurídica.

Tipo de identificador: Cédula Jurídica, Código de Prestador u otro tipo de identificación.

CodeSystem de tipos de identificadores para ubicaciones en Costa Rica.

Identificador único del sistema que emite o registra el identificador de la ubicación.

Valor único del identificador dentro del sistema.

Indica si la ubicación está activa y operativa. Un valor 'active' significa que la ubicación está en uso; 'suspended' indica que está temporalmente inactiva; 'inactive' indica que ha sido desactivada.

ValueSet de estados de Location definidos en FHIR.

Nombre oficial de la ubicación, tal como aparece registrada en el Registro Nacional.

Se recomienda usar el nombre oficial registrado.

Nombres alternativos, apodos o nombres comunes utilizados para referirse a la ubicación.

Persona responsable o punto de contacto dentro de la ubicación.

Nombre completo de la persona de contacto.

Teléfono, correo u otro dato para contactar a la persona.

Dirección postal completa de la ubicación, incluyendo calle, ciudad, provincia y código postal.

Se recomienda usar direcciones oficiales registradas.

Propósito de la dirección (principal, trabajo, temporal, etc.).

Tipo de dirección (postal, física o ambas).

Calle, número, apartamento y otras líneas de dirección específicas. Mínimo una línea requerida.

Nombre del cantón (ciudad). Incluye una extensión con el código del cantón basado en el ZipCode de Costa Rica.

Nombre del distrito. Incluye una extensión con el código del distrito basado en el ZipCode de Costa Rica.

Nombre de la provincia. Incluye una extensión con el código de la provincia basado en el ZipCode de Costa Rica.

Código postal o código de localidad de Costa Rica (opcional).

Nombre del país. Incluye una extensión con el código ISO 3166-1 alpha-3 (CR para Costa Rica).

Coordenadas geográficas (latitud y longitud) que representan la ubicación física.

Valor decimal que representa la longitud de la ubicación.

Valor decimal que representa la latitud de la ubicación.

Valor decimal que representa la altitud de la ubicación en metros sobre el nivel del mar.

Referencia a otra ubicación de la cual esta ubicación es parte. Por ejemplo, una sala es parte de un hospital o consultorio.

Details and position information for a place where services are provided and resources and participants may be stored, found, contained, or accommodated.

The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.

The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.

Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.

The base language in which the resource is written.

Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).

IETF language tag for a human language

A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.

Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.

These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.

This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.

May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Lista de identificadores únicos de la ubicación. Incluye Cédula Jurídica del Registro Nacional y Código de Prestador de Servicios de Salud.

Organization label locations in registries, need to keep track of those.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Propósito del identificador. Se recomienda usar 'official' para la Cédula Jurídica.

Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.

Identifies the purpose for this identifier, if known .

Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.

Tipo de identificador: Cédula Jurídica, Código de Prestador u otro tipo de identificación.

This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type.

CodeSystem de tipos de identificadores para ubicaciones en Costa Rica.

Allows users to make use of identifiers when the identifier system is not known.

Identificador único del sistema que emite o registra el identificador de la ubicación.

Identifier.system is always case sensitive.

There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers.

Valor único del identificador dentro del sistema.

If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the http://hl7.org/fhir/StructureDefinition/rendered-value). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.

Time period during which identifier is/was valid for use.

Organization that issued/manages the identifier.

The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization.

Indica si la ubicación está activa y operativa. Un valor 'active' significa que la ubicación está en uso; 'suspended' indica que está temporalmente inactiva; 'inactive' indica que ha sido desactivada.

ValueSet de estados de Location definidos en FHIR.

The operational status covers operation values most relevant to beds (but can also apply to rooms/units/chairs/etc. such as an isolation unit/dialysis chair). This typically covers concepts such as contamination, housekeeping, and other activities like maintenance.

The operational status if the location (where typically a bed/room).

Nombre oficial de la ubicación, tal como aparece registrada en el Registro Nacional.

Se recomienda usar el nombre oficial registrado.

Nombres alternativos, apodos o nombres comunes utilizados para referirse a la ubicación.

There are no dates associated with the alias/historic names, as this is not intended to track when names were used, but to assist in searching so that older names can still result in identifying the location.

Over time locations and organizations go through many changes and can be known by different names.

For searching knowing previous names that the location was known by can be very useful.

Description of the Location, which helps in finding or referencing the place.

Humans need additional information to verify a correct location has been identified.

Indicates whether a resource instance represents a specific location or a class of locations.

This is labeled as a modifier because whether or not the location is a class of locations changes how it can be used and understood.

Indicates whether a resource instance represents a specific location or a class of locations.

When using a Location resource for scheduling or orders, we need to be able to refer to a class of Locations instead of a specific Location.

Indicates the type of function performed at the location.

Indicates the type of function performed at the location.

Persona responsable o punto de contacto dentro de la ubicación.

The address/telecom use code 'home' are not to be used. Note that these contacts are not the contact details of people who provide the service (that would be through PractitionerRole), these are official contacts for the Healthcare itself for specific purposes. E.g. Mailing Addresses, Billing Addresses, Contact numbers for Booking or Billing Enquiries, general web address, web address for online bookings etc.

If this is empty (or the type of interest is empty), refer to the organization's contacts.

Need to keep track of both simple contact details and also assigned contacts within larger organizations.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

The purpose/type of contact.

If no purpose is defined, then these contact details may be used for any purpose.

The purpose for which an extended contact detail should be used.

Nombre completo de la persona de contacto.

If there is no named individual, the telecom/address information is not generally monitored by a specific individual.

Teléfono, correo u otro dato para contactar a la persona.

Address for the contact.

More than 1 address would be for different purposes, and thus should be entered as a different entry,.

This contact detail is handled/monitored by a specific organization. If the name is provided in the contact, then it is referring to the named individual within this organization.

Some specific types of contact information can be an handled by an organization (eg legal council is via a specific firm).

Period that this contact was valid for usage.

If the details have multiple periods, then enter in a new ExtendedContact with the new period.

Dirección postal completa de la ubicación, incluyendo calle, ciudad, provincia y código postal.

Se recomienda usar direcciones oficiales registradas.

If locations can be visited, we need to keep track of their address.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Propósito de la dirección (principal, trabajo, temporal, etc.).

Applications can assume that an address is current unless it explicitly says that it is temporary or old.

The use of an address (home / work / etc.).

Allows an appropriate address to be chosen from a list of many.

Tipo de dirección (postal, física o ambas).

The definition of Address states that "address is intended to describe postal addresses, not physical locations". However, many applications track whether an address has a dual purpose of being a location that can be visited as well as being a valid delivery destination, and Postal addresses are often used as proxies for physical locations (also see the Location resource).

The type of an address (physical / postal).

Specifies the entire address as it should be displayed e.g. on a postal label. This may be provided instead of or as well as the specific parts.

Can provide both a text representation and parts. Applications updating an address SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part.

A renderable, unencoded form.

Calle, número, apartamento y otras líneas de dirección específicas. Mínimo una línea requerida.

Nombre del cantón (ciudad). Incluye una extensión con el código del cantón basado en el ZipCode de Costa Rica.

unique id for the element within a resource (for internal references)

Código de la ciudad basado en el ZipCode de Costa Rica.

Extensión para el código del cantón basado en el ZipCode de Costa Rica.

The actual value

Nombre del distrito. Incluye una extensión con el código del distrito basado en el ZipCode de Costa Rica.

District is sometimes known as county, but in some regions 'county' is used in place of city (municipality), so county name should be conveyed in city instead.

unique id for the element within a resource (for internal references)

Código del distrito basado en el ZipCode de Costa Rica.

Extensión para el código del distrito basado en el ZipCode de Costa Rica.

The actual value

Nombre de la provincia. Incluye una extensión con el código de la provincia basado en el ZipCode de Costa Rica.

unique id for the element within a resource (for internal references)

Código de la provincia basado en el ZipCode de Costa Rica.

Extensión para el código de la provincia basado en el ZipCode de Costa Rica.

The actual value

Código postal o código de localidad de Costa Rica (opcional).

Nombre del país. Incluye una extensión con el código ISO 3166-1 alpha-3 (CR para Costa Rica).

ISO 3166 2- or 3- letter codes MAY be used in place of a human readable country name.

unique id for the element within a resource (for internal references)

Código de país en formato ISO 3166-1 alpha-3

Extensión para el código de país en formato ISO 3166-1 alpha-3.

The actual value

Time period when address was/is in use.

Allows addresses to be placed in historical context.

Physical form of the location, e.g. building, room, vehicle, road, virtual.

Physical form of the location.

For purposes of showing relevant locations in queries, we need to categorize locations.

Coordenadas geográficas (latitud y longitud) que representan la ubicación física.

To define a boundary shape for this location use the standard extension [http://hl7.org/fhir/StructureDefinition/location-boundary-geojson](http://hl7.org/fhir/extensions/StructureDefinition-location-boundary-geojson.html), and search using the contains special search parameter.

For mobile applications and automated route-finding knowing the exact location of the Location is required.

Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.

Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.

Modifier extensions allow for extensions that cannot be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the definition of modifier extensions.

Valor decimal que representa la longitud de la ubicación.

Valor decimal que representa la latitud de la ubicación.

Valor decimal que representa la altitud de la ubicación en metros sobre el nivel del mar.

The organization responsible for the provisioning and upkeep of the location.

This can also be used as the part of the organization hierarchy where this location provides services. These services can be defined through the HealthcareService resource.

Need to know who manages the location.

Referencia a otra ubicación de la cual esta ubicación es parte. Por ejemplo, una sala es parte de un hospital o consultorio.

For purposes of location, display and identification, knowing which locations are located within other locations is important.

Collection of characteristics (attributes).

These could be such things as is wheelchair accessible.

A custom attribute that could be provided at a service (e.g. Wheelchair accessibiliy).

What days/times during a week is this location usually open, and any exceptions where the location is not available.

This type of information is commonly found published in directories and on websites informing customers when the facility is available.

Specific services within the location may have their own hours which could be shorter (or longer) than the locations hours.

Systems may choose to render availability differently than it is exchanged on the interface. For example, rather than "Mon, Tue, Wed, Thur, Fri from 9am-12am; Mon, Tue, Wed, Thur, Fri from 1pm-5pm" as would be implied by two availableTime repetitions, an application could render this information as "Mon-Fri 9-12am and 1-5pm".

The availableStartTime is the opening time, and the availableEndTime is the closing time.

Connection details of a virtual service (e.g. shared conference call facility with dedicated number/details).

There are two types of virtual meetings that often exist:

• a persistent, virtual meeting room that can only be used for a single purpose at a time,
• and a dynamic virtual meeting room that is generated on demand for a specific purpose.

Implementers may consider using Appointment.virtualService for virtual meeting rooms that are generated on-demand.

Technical endpoints providing access to services operated for the location.

Organizations may have different systems at different locations that provide various services and need to be able to define the technical connection details for how to connect to them, and for what purpose.