The details of a healthcare service available at a location.

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.

An Extension

R4: HealthcareService.telecom (new:ContactPoint)

Element HealthcareService.telecom has a context of HealthcareService based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.telecom has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If this is empty, then refer to the location's contacts.

R4: HealthcareService.availabilityExceptions (new:string)

Element HealthcareService.availabilityExceptions has a context of HealthcareService based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availabilityExceptions has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

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.

This flag is used to mark the record to not be used. This is not used when a center is closed for maintenance, or for holidays, the notAvailable period is to be used for this.

This element is labeled as a modifier because it may be used to mark that the resource was created in error.

R4: HealthcareService.telecom (new:ContactPoint)

Element HealthcareService.telecom has a context of HealthcareService based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.telecom has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If this is empty, then refer to the location's contacts.

R4: HealthcareService.availabilityExceptions (new:string)

Element HealthcareService.availabilityExceptions has a context of HealthcareService based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availabilityExceptions has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

R4: HealthcareService.availableTime.daysOfWeek additional types (code) additional types from child elements (value)

Element HealthcareService.availableTime.daysOfWeek is mapped to FHIR R5 element HealthcareService.availability as SourceIsBroaderThanTarget. The mappings for HealthcareService.availableTime.daysOfWeek do not cover the following types: code. The mappings for HealthcareService.availableTime.daysOfWeek do not cover the following types based on type expansion: value.

R4: HealthcareService.availableTime.allDay (new:boolean)

Element HealthcareService.availableTime.allDay has a context of HealthcareService.availability based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availableTime.allDay has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

R4: HealthcareService.availableTime.availableStartTime (new:time)

Element HealthcareService.availableTime.availableStartTime has a context of HealthcareService.availability based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availableTime.availableStartTime has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The time zone is expected to be for where this HealthcareService is provided at.

R4: HealthcareService.availableTime.availableEndTime (new:time)

Element HealthcareService.availableTime.availableEndTime has a context of HealthcareService.availability based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availableTime.availableEndTime has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The time zone is expected to be for where this HealthcareService is provided at.

R4: HealthcareService.notAvailable.description additional types (string) additional types from child elements (value)

Element HealthcareService.notAvailable.description is mapped to FHIR R5 element HealthcareService.availability as RelatedTo. The mappings for HealthcareService.notAvailable.description do not cover the following types: string. The mappings for HealthcareService.notAvailable.description do not cover the following types based on type expansion: value.

R4: HealthcareService.notAvailable.during (new:Period)

Element HealthcareService.notAvailable.during has a context of HealthcareService.availability based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.notAvailable.during has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

The details of a healthcare service available at a location.

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.

An Extension

R4: HealthcareService.telecom (new:ContactPoint)

Element HealthcareService.telecom has a context of HealthcareService based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.telecom has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). If this is empty, then refer to the location's contacts.

R4: HealthcareService.availabilityExceptions (new:string)

Element HealthcareService.availabilityExceptions has a context of HealthcareService based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availabilityExceptions has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

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.

External identifiers for this item.

This flag is used to mark the record to not be used. This is not used when a center is closed for maintenance, or for holidays, the notAvailable period is to be used for this.

This element is labeled as a modifier because it may be used to mark that the resource was created in error.

The organization that provides this healthcare service.

This property is recommended to be the same as the Location's managingOrganization, and if not provided should be interpreted as such. If the Location does not have a managing Organization, then this property should be populated.

When the HealthcareService is representing a specific, schedulable service, the availableIn property can refer to a generic service.

For example, if there is a generic Radiology service that offers CT Scans, MRIs, etc. You could have HealthcareService resources for the CT Scans and MRIs, which have an offeredIn reference to the Radiology HealthcareService.

Identifies the broad category of service being performed or delivered.

Selecting a Service Category then determines the list of relevant service types that can be selected in the primary service type.

A category of the service(s) that could be provided.

The specific type of service that may be delivered or performed.

Additional details about where the content was created (e.g. clinical specialty).

Collection of specialties handled by the Healthcare service. This is more of a medical term.

A specialty that a healthcare service may provide.

The location(s) where this healthcare service may be provided.

Further description of the service as it would be presented to a consumer while searching.

Any additional description of the service and/or any specific issues not covered by the other attributes, which can be displayed as further detail under the serviceName.

Would expect that a user would not see this information on a search results, and it would only be available when viewing the complete details of the service.

Extra details about the service that can't be placed in the other fields.

If there is a photo/symbol associated with this HealthcareService, it may be included here to facilitate quick identification of the service in a list.

The contact details of communication devices available relevant to the specific HealthcareService. This can include addresses, phone numbers, fax numbers, mobile numbers, email addresses and web sites.

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 HealthcareService 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 location's contacts.

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

The location(s) that this service is available to (not where the service is provided).

The locations referenced by the coverage area can include both specific locations, including areas, and also conceptual domains too (mode = kind), such as a physical area (tri-state area) and some other attribute (covered by Example Care Organization). These types of Locations are often not managed by any specific organization. This could also include generic locations such as "in-home".

The code(s) that detail the conditions under which the healthcare service is available/offered.

The provision means being commissioned by, contractually obliged or financially sourced. Types of costings that may apply to this healthcare service, such if the service may be available for free, some discounts available, or fees apply.

The code(s) that detail the conditions under which the healthcare service is available/offered.

Does this service have specific eligibility requirements that need to be met in order to use the service?

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.

Coded value for the eligibility.

Coded values underwhich a specific service is made available.

Describes the eligibility conditions for the service.

The description of service eligibility should, in general, not exceed one or two paragraphs. It should be sufficient for a prospective consumer to determine if they are likely to be eligible or not. Where eligibility requirements and conditions are complex, it may simply be noted that an eligibility assessment is required. Where eligibility is determined by an outside source, such as an Act of Parliament, this should be noted, preferably with a reference to a commonly available copy of the source document such as a web page.

Programs that this service is applicable to.

Programs are often defined externally to an Organization, commonly by governments; e.g. Home and Community Care Programs, Homeless Program, ….

Government or local programs that this service applies to.

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 accessibility).

Some services are specifically made available in multiple languages, this property permits a directory to declare the languages this is offered in. Typically this is only provided where a service operates in communities with mixed languages used.

When using this property it indicates that the service is available with this language, it is not derived from the practitioners, and not all are required to use this language, just that this language is available while scheduling.

IETF language tag for a human language

Ways that the service accepts referrals, if this is not provided then it is implied that no referral is required.

The methods of referral can be used when referring to a specific HealthcareService resource.

Indicates whether or not a prospective consumer will require an appointment for a particular service at a site to be provided by the Organization. Indicates if an appointment is required for access to this service.

A collection of times that the healthcare service is available.

More detailed availability information may be provided in associated Schedule/Slot resources.

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 NotAvailableTime(s) included indicate the general days/periods where the service is not available (for things such as public holidays).

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

An Extension

R4: HealthcareService.availableTime.daysOfWeek additional types (code) additional types from child elements (value)

Element HealthcareService.availableTime.daysOfWeek is mapped to FHIR R5 element HealthcareService.availability as SourceIsBroaderThanTarget. The mappings for HealthcareService.availableTime.daysOfWeek do not cover the following types: code. The mappings for HealthcareService.availableTime.daysOfWeek do not cover the following types based on type expansion: value.

R4: HealthcareService.availableTime.allDay (new:boolean)

Element HealthcareService.availableTime.allDay has a context of HealthcareService.availability based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availableTime.allDay has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

R4: HealthcareService.availableTime.availableStartTime (new:time)

Element HealthcareService.availableTime.availableStartTime has a context of HealthcareService.availability based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availableTime.availableStartTime has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The time zone is expected to be for where this HealthcareService is provided at.

R4: HealthcareService.availableTime.availableEndTime (new:time)

Element HealthcareService.availableTime.availableEndTime has a context of HealthcareService.availability based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.availableTime.availableEndTime has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The time zone is expected to be for where this HealthcareService is provided at.

R4: HealthcareService.notAvailable.description additional types (string) additional types from child elements (value)

Element HealthcareService.notAvailable.description is mapped to FHIR R5 element HealthcareService.availability as RelatedTo. The mappings for HealthcareService.notAvailable.description do not cover the following types: string. The mappings for HealthcareService.notAvailable.description do not cover the following types based on type expansion: value.

R4: HealthcareService.notAvailable.during (new:Period)

Element HealthcareService.notAvailable.during has a context of HealthcareService.availability based on following the parent source element upwards and mapping to HealthcareService. Element HealthcareService.notAvailable.during has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).

Times the {item} is available.

A collection of times that the {item} is available.

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.

mon | tue | wed | thu | fri | sat | sun.

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

Indicates which days of the week are available between the start and end Times.

Always available? i.e. 24 hour service.

Is this always available? (hence times are irrelevant) i.e. 24 hour service.

Opening time of day (ignored if allDay = true).

The timezone is expected to be specified or implied by the context this datatype is used.

The opening time of day. Note: If the AllDay flag is set, then this time is ignored.

Closing time of day (ignored if allDay = true).

The timezone is expected to be specified or implied by the context this datatype is used.

The closing time of day. Note: If the AllDay flag is set, then this time is ignored.

Not available during this time due to provided reason.

The {item} is not available during this period of time due to the provided reason.

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.

Reason presented to the user explaining why time not available.

The reason will generally be provided to give the textual reason for displaying when the {item} is not available, e.g. 'Closed public holidays' or 'Independence Day'. In cases such as this, the during might not be included and local knowledge would be required in such cases (as don't desire to keep updating when the holiday occurs each year).

e.g.2: 'Closed for maintenance over the summer' for this example you would want to include the during period, unless this was a university hospital and the "summer" period was well known, but would recommend its inclusion anyway.

The reason that can be presented to the user as to why this time is not available.

Service not available during this period.

The {item} is not available (seasonally or for a public holiday) during this period.

Technical endpoints providing access to services operated for the specific healthcare services defined at this resource.