Mobile Care Services Discovery (mCSD)
3.8.1-current - ci-build International flag

Mobile Care Services Discovery (mCSD), published by IHE IT Infrastructure Technical Committee. This guide is not an authorized publication; it is the continuous build for version 3.8.1-current built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/IHE/ITI.mCSD/ and changes regularly. See the Directory of published versions

Resource Profile: mCSD Location for Jurisdictions

Official URL: https://profiles.ihe.net/ITI/mCSD/StructureDefinition/IHE.mCSD.JurisdictionLocation Version: 3.8.1-current
Active as of 2024-02-08 Computable Name: MCSDJurisdictionLocation

A profile on the mCSD Location for mCSD Jurisdictions.

Jurisdictions are political administrative units or other territories over which authority is exercised. A Jurisdiction has a unique identifier, geographic attributes, etc. Jurisdictions include political administrative units such as village districts or regions. Each Jurisdiction is defined by a pairing of Location and Organization.

In addition to the base requirements of mCSD Location, one type must be set to https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction.

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

This structure is derived from MCSDLocation

NameFlagsCard.TypeDescription & Constraintsdoco
.. Location 0..*MCSDLocationDetails and position information for a physical place
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... boundary 0..1AttachmentWhen a boundary is available, the location-boundary-geojson extension should be used.
URL: http://hl7.org/fhir/StructureDefinition/location-boundary-geojson
.... value[x]
..... contentType 0..1codeThe boundary contentType shall be application/geo+json.
Required Pattern: application/geo+json
..... data 1..1base64BinaryThe boundary data shall be in the valueAttachment data element.
... Slices for type 1..*CodeableConceptOne type must be set to: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction
Slice: Unordered, Open by pattern:$this
.... type:jurisdiction 1..1CodeableConceptA code that describes the type of Location.
Required Pattern: At least the following
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... system1..1uriIdentity of the terminology system
Fixed Value: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: jurisdiction
... managingOrganization 1..1Reference(mCSD Organization for Jurisdictions)The reference to the mCSD Organization resource for this jurisdiction.

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Location 0..*MCSDLocationDetails and position information for a physical place
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... boundary 0..1AttachmentWhen a boundary is available, the location-boundary-geojson extension should be used.
URL: http://hl7.org/fhir/StructureDefinition/location-boundary-geojson
.... extension 0..0
.... url 1..1uri"http://hl7.org/fhir/StructureDefinition/location-boundary-geojson"
.... value[x] 1..1AttachmentValue of extension
..... contentType Σ0..1codeThe boundary contentType shall be application/geo+json.
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.


Required Pattern: application/geo+json
..... data 1..1base64BinaryThe boundary data shall be in the valueAttachment data element.
... status ?!Σ1..1codeThe status code of the Location.
Binding: LocationStatus (required): Indicates whether the location is still in use.

... name Σ1..1stringThe name of the Location.
... Slices for type Σ1..*CodeableConceptOne type must be set to: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction
Slice: Unordered, Open by pattern:$this
Binding: ServiceDeliveryLocationRoleType (extensible): Indicates the type of function performed at the location.


.... type:jurisdiction Σ1..1CodeableConceptA code that describes the type of Location.
Binding: ServiceDeliveryLocationRoleType (extensible): Indicates the type of function performed at the location.



Required Pattern: At least the following
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... system1..1uriIdentity of the terminology system
Fixed Value: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: jurisdiction
... physicalType Σ1..1CodeableConceptA code that describes the physical form of the Location.
Binding: LocationType (example): Physical form of the location.

... managingOrganization Σ1..1Reference(mCSD Organization for Jurisdictions)The reference to the mCSD Organization resource for this jurisdiction.

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Location.extension:boundary.value[x].contentTyperequiredPattern: application/geo+json
http://hl7.org/fhir/ValueSet/mimetypes|4.0.1
from the FHIR Standard
Location.statusrequiredLocationStatus
http://hl7.org/fhir/ValueSet/location-status|4.0.1
from the FHIR Standard
Location.typeextensibleServiceDeliveryLocationRoleType
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
Location.type:jurisdictionextensiblePattern: jurisdiction
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
Location.physicalTypeexampleLocationType
http://hl7.org/fhir/ValueSet/location-physical-type
from the FHIR Standard
NameFlagsCard.TypeDescription & Constraintsdoco
.. Location 0..*MCSDLocationDetails and position information for a physical place
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... boundary 0..1AttachmentWhen a boundary is available, the location-boundary-geojson extension should be used.
URL: http://hl7.org/fhir/StructureDefinition/location-boundary-geojson
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..0
.... url 1..1uri"http://hl7.org/fhir/StructureDefinition/location-boundary-geojson"
.... value[x] 1..1AttachmentValue of extension
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... contentType Σ0..1codeThe boundary contentType shall be application/geo+json.
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.


Required Pattern: application/geo+json
..... language Σ0..1codeHuman language of the content (BCP-47)
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding

Example General: en-AU
..... data 1..1base64BinaryThe boundary data shall be in the valueAttachment data element.
..... url Σ0..1urlUri where the data can be found
Example General: http://www.acme.com/logo-small.png
..... size Σ0..1unsignedIntNumber of bytes of content (if url provided)
..... hash Σ0..1base64BinaryHash of the data (sha-1, base64ed)
..... title Σ0..1stringLabel to display in place of the data
Example General: Official Corporate Logo
..... creation Σ0..1dateTimeDate attachment was first created
... identifier Σ0..*IdentifierUnique code or number identifying the location to its users
... status ?!Σ1..1codeThe status code of the Location.
Binding: LocationStatus (required): Indicates whether the location is still in use.

... operationalStatus Σ0..1CodingThe operational status of the location (typically only for a bed/room)
Binding: hl7VS-bedStatus (preferred): The operational status if the location (where typically a bed/room).

... name Σ1..1stringThe name of the Location.
... alias 0..*stringA list of alternate names that the location is known as, or was known as, in the past
... description Σ0..1stringAdditional details about the location that could be displayed as further information to identify the location beyond its name
... mode Σ0..1codeinstance | kind
Binding: LocationMode (required): Indicates whether a resource instance represents a specific location or a class of locations.

... Slices for type Σ1..*CodeableConceptOne type must be set to: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction
Slice: Unordered, Open by pattern:$this
Binding: ServiceDeliveryLocationRoleType (extensible): Indicates the type of function performed at the location.


.... type:jurisdiction Σ1..1CodeableConceptA code that describes the type of Location.
Binding: ServiceDeliveryLocationRoleType (extensible): Indicates the type of function performed at the location.



Required Pattern: At least the following
..... id0..1stringUnique id for inter-element referencing
..... extension0..*ExtensionAdditional content defined by implementations
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... system1..1uriIdentity of the terminology system
Fixed Value: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types
...... version0..1stringVersion of the system - if relevant
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: jurisdiction
...... display0..1stringRepresentation defined by the system
...... userSelected0..1booleanIf this coding was chosen directly by the user
..... text0..1stringPlain text representation of the concept
... telecom 0..*ContactPointContact details of the location
... address 0..1AddressPhysical location
... physicalType Σ1..1CodeableConceptA code that describes the physical form of the Location.
Binding: LocationType (example): Physical form of the location.

... position 0..1BackboneElementThe absolute geographic location
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... longitude 1..1decimalLongitude with WGS84 datum
.... latitude 1..1decimalLatitude with WGS84 datum
.... altitude 0..1decimalAltitude with WGS84 datum
... managingOrganization Σ1..1Reference(mCSD Organization for Jurisdictions)The reference to the mCSD Organization resource for this jurisdiction.
... partOf 0..1Reference(mCSD Location)Another Location this one is physically a part of
... hoursOfOperation 0..*BackboneElementWhat days/times during a week is this location usually open
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... daysOfWeek 0..*codemon | tue | wed | thu | fri | sat | sun
Binding: DaysOfWeek (required): The days of the week.


.... allDay 0..1booleanThe Location is open all day
.... openingTime 0..1timeTime that the Location opens
.... closingTime 0..1timeTime that the Location closes
... availabilityExceptions 0..1stringDescription of availability exceptions
... endpoint 0..*Reference(Endpoint)Technical endpoints providing access to services operated for the location

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Location.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
http://hl7.org/fhir/ValueSet/languages
from the FHIR Standard
Location.extension:boundary.value[x].contentTyperequiredPattern: application/geo+json
http://hl7.org/fhir/ValueSet/mimetypes|4.0.1
from the FHIR Standard
Location.extension:boundary.value[x].languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
http://hl7.org/fhir/ValueSet/languages
from the FHIR Standard
Location.statusrequiredLocationStatus
http://hl7.org/fhir/ValueSet/location-status|4.0.1
from the FHIR Standard
Location.operationalStatuspreferredHl7VSBedStatus
http://terminology.hl7.org/ValueSet/v2-0116
Location.moderequiredLocationMode
http://hl7.org/fhir/ValueSet/location-mode|4.0.1
from the FHIR Standard
Location.typeextensibleServiceDeliveryLocationRoleType
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
Location.type:jurisdictionextensiblePattern: jurisdiction
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
Location.physicalTypeexampleLocationType
http://hl7.org/fhir/ValueSet/location-physical-type
from the FHIR Standard
Location.hoursOfOperation.daysOfWeekrequiredDaysOfWeek
http://hl7.org/fhir/ValueSet/days-of-week|4.0.1
from the FHIR Standard

This structure is derived from MCSDLocation

Summary

Mandatory: 2 elements (1 nested mandatory element)

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element Location.type is sliced based on the value of pattern:$this

Differential View

This structure is derived from MCSDLocation

NameFlagsCard.TypeDescription & Constraintsdoco
.. Location 0..*MCSDLocationDetails and position information for a physical place
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... boundary 0..1AttachmentWhen a boundary is available, the location-boundary-geojson extension should be used.
URL: http://hl7.org/fhir/StructureDefinition/location-boundary-geojson
.... value[x]
..... contentType 0..1codeThe boundary contentType shall be application/geo+json.
Required Pattern: application/geo+json
..... data 1..1base64BinaryThe boundary data shall be in the valueAttachment data element.
... Slices for type 1..*CodeableConceptOne type must be set to: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction
Slice: Unordered, Open by pattern:$this
.... type:jurisdiction 1..1CodeableConceptA code that describes the type of Location.
Required Pattern: At least the following
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... system1..1uriIdentity of the terminology system
Fixed Value: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: jurisdiction
... managingOrganization 1..1Reference(mCSD Organization for Jurisdictions)The reference to the mCSD Organization resource for this jurisdiction.

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Location 0..*MCSDLocationDetails and position information for a physical place
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... boundary 0..1AttachmentWhen a boundary is available, the location-boundary-geojson extension should be used.
URL: http://hl7.org/fhir/StructureDefinition/location-boundary-geojson
.... extension 0..0
.... url 1..1uri"http://hl7.org/fhir/StructureDefinition/location-boundary-geojson"
.... value[x] 1..1AttachmentValue of extension
..... contentType Σ0..1codeThe boundary contentType shall be application/geo+json.
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.


Required Pattern: application/geo+json
..... data 1..1base64BinaryThe boundary data shall be in the valueAttachment data element.
... status ?!Σ1..1codeThe status code of the Location.
Binding: LocationStatus (required): Indicates whether the location is still in use.

... name Σ1..1stringThe name of the Location.
... Slices for type Σ1..*CodeableConceptOne type must be set to: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction
Slice: Unordered, Open by pattern:$this
Binding: ServiceDeliveryLocationRoleType (extensible): Indicates the type of function performed at the location.


.... type:jurisdiction Σ1..1CodeableConceptA code that describes the type of Location.
Binding: ServiceDeliveryLocationRoleType (extensible): Indicates the type of function performed at the location.



Required Pattern: At least the following
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... system1..1uriIdentity of the terminology system
Fixed Value: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: jurisdiction
... physicalType Σ1..1CodeableConceptA code that describes the physical form of the Location.
Binding: LocationType (example): Physical form of the location.

... managingOrganization Σ1..1Reference(mCSD Organization for Jurisdictions)The reference to the mCSD Organization resource for this jurisdiction.

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Location.extension:boundary.value[x].contentTyperequiredPattern: application/geo+json
http://hl7.org/fhir/ValueSet/mimetypes|4.0.1
from the FHIR Standard
Location.statusrequiredLocationStatus
http://hl7.org/fhir/ValueSet/location-status|4.0.1
from the FHIR Standard
Location.typeextensibleServiceDeliveryLocationRoleType
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
Location.type:jurisdictionextensiblePattern: jurisdiction
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
Location.physicalTypeexampleLocationType
http://hl7.org/fhir/ValueSet/location-physical-type
from the FHIR Standard

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Location 0..*MCSDLocationDetails and position information for a physical place
... id Σ0..1idLogical id of this artifact
... meta Σ0..1MetaMetadata about the resource
... language 0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... Slices for extension 0..*ExtensionExtension
Slice: Unordered, Open by value:url
... boundary 0..1AttachmentWhen a boundary is available, the location-boundary-geojson extension should be used.
URL: http://hl7.org/fhir/StructureDefinition/location-boundary-geojson
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..0
.... url 1..1uri"http://hl7.org/fhir/StructureDefinition/location-boundary-geojson"
.... value[x] 1..1AttachmentValue of extension
..... id 0..1stringUnique id for inter-element referencing
..... extension 0..*ExtensionAdditional content defined by implementations
Slice: Unordered, Open by value:url
..... contentType Σ0..1codeThe boundary contentType shall be application/geo+json.
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.


Required Pattern: application/geo+json
..... language Σ0..1codeHuman language of the content (BCP-47)
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding

Example General: en-AU
..... data 1..1base64BinaryThe boundary data shall be in the valueAttachment data element.
..... url Σ0..1urlUri where the data can be found
Example General: http://www.acme.com/logo-small.png
..... size Σ0..1unsignedIntNumber of bytes of content (if url provided)
..... hash Σ0..1base64BinaryHash of the data (sha-1, base64ed)
..... title Σ0..1stringLabel to display in place of the data
Example General: Official Corporate Logo
..... creation Σ0..1dateTimeDate attachment was first created
... identifier Σ0..*IdentifierUnique code or number identifying the location to its users
... status ?!Σ1..1codeThe status code of the Location.
Binding: LocationStatus (required): Indicates whether the location is still in use.

... operationalStatus Σ0..1CodingThe operational status of the location (typically only for a bed/room)
Binding: hl7VS-bedStatus (preferred): The operational status if the location (where typically a bed/room).

... name Σ1..1stringThe name of the Location.
... alias 0..*stringA list of alternate names that the location is known as, or was known as, in the past
... description Σ0..1stringAdditional details about the location that could be displayed as further information to identify the location beyond its name
... mode Σ0..1codeinstance | kind
Binding: LocationMode (required): Indicates whether a resource instance represents a specific location or a class of locations.

... Slices for type Σ1..*CodeableConceptOne type must be set to: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types#jurisdiction
Slice: Unordered, Open by pattern:$this
Binding: ServiceDeliveryLocationRoleType (extensible): Indicates the type of function performed at the location.


.... type:jurisdiction Σ1..1CodeableConceptA code that describes the type of Location.
Binding: ServiceDeliveryLocationRoleType (extensible): Indicates the type of function performed at the location.



Required Pattern: At least the following
..... id0..1stringUnique id for inter-element referencing
..... extension0..*ExtensionAdditional content defined by implementations
..... coding1..*CodingCode defined by a terminology system
Fixed Value: (complex)
...... id0..1stringUnique id for inter-element referencing
...... extension0..*ExtensionAdditional content defined by implementations
...... system1..1uriIdentity of the terminology system
Fixed Value: https://profiles.ihe.net/ITI/mCSD/CodeSystem/IHE.mCSD.Organization.Location.Types
...... version0..1stringVersion of the system - if relevant
...... code1..1codeSymbol in syntax defined by the system
Fixed Value: jurisdiction
...... display0..1stringRepresentation defined by the system
...... userSelected0..1booleanIf this coding was chosen directly by the user
..... text0..1stringPlain text representation of the concept
... telecom 0..*ContactPointContact details of the location
... address 0..1AddressPhysical location
... physicalType Σ1..1CodeableConceptA code that describes the physical form of the Location.
Binding: LocationType (example): Physical form of the location.

... position 0..1BackboneElementThe absolute geographic location
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... longitude 1..1decimalLongitude with WGS84 datum
.... latitude 1..1decimalLatitude with WGS84 datum
.... altitude 0..1decimalAltitude with WGS84 datum
... managingOrganization Σ1..1Reference(mCSD Organization for Jurisdictions)The reference to the mCSD Organization resource for this jurisdiction.
... partOf 0..1Reference(mCSD Location)Another Location this one is physically a part of
... hoursOfOperation 0..*BackboneElementWhat days/times during a week is this location usually open
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... daysOfWeek 0..*codemon | tue | wed | thu | fri | sat | sun
Binding: DaysOfWeek (required): The days of the week.


.... allDay 0..1booleanThe Location is open all day
.... openingTime 0..1timeTime that the Location opens
.... closingTime 0..1timeTime that the Location closes
... availabilityExceptions 0..1stringDescription of availability exceptions
... endpoint 0..*Reference(Endpoint)Technical endpoints providing access to services operated for the location

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet / CodeURI
Location.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
http://hl7.org/fhir/ValueSet/languages
from the FHIR Standard
Location.extension:boundary.value[x].contentTyperequiredPattern: application/geo+json
http://hl7.org/fhir/ValueSet/mimetypes|4.0.1
from the FHIR Standard
Location.extension:boundary.value[x].languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
http://hl7.org/fhir/ValueSet/languages
from the FHIR Standard
Location.statusrequiredLocationStatus
http://hl7.org/fhir/ValueSet/location-status|4.0.1
from the FHIR Standard
Location.operationalStatuspreferredHl7VSBedStatus
http://terminology.hl7.org/ValueSet/v2-0116
Location.moderequiredLocationMode
http://hl7.org/fhir/ValueSet/location-mode|4.0.1
from the FHIR Standard
Location.typeextensibleServiceDeliveryLocationRoleType
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
Location.type:jurisdictionextensiblePattern: jurisdiction
http://terminology.hl7.org/ValueSet/v3-ServiceDeliveryLocationRoleType
Location.physicalTypeexampleLocationType
http://hl7.org/fhir/ValueSet/location-physical-type
from the FHIR Standard
Location.hoursOfOperation.daysOfWeekrequiredDaysOfWeek
http://hl7.org/fhir/ValueSet/days-of-week|4.0.1
from the FHIR Standard

This structure is derived from MCSDLocation

Summary

Mandatory: 2 elements (1 nested mandatory element)

Structures

This structure refers to these other structures:

Extensions

This structure refers to these extensions:

Slices

This structure defines the following Slices:

  • The element Location.type is sliced based on the value of pattern:$this

 

Other representations of profile: CSV, Excel, Schematron