Generated Narrative: StructureDefinition DIPSLocation Name Flags Card. Type Description & Constraints Location 0..* NoBasisLocation Details and position information for a physical place #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:validPeriod 0..* Period Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/LocationValidPeriod #xD; extension:labLocalizationId 0..* Identifier Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/LocationLabLocalizationId #xD; extension:workplaceLocalizationId 0..* Identifier Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/LocationWorkplaceLocalizationId #xD; Slices for identifier 0..* Identifier Unique code or number identifying the location to its users Slice: Unordered, Open by value:system #xD; identifier:LocationId 0..* Identifier Unique code or number identifying the location to its users #xD; system 1..1 uri The namespace for the identifier value Fixed Value: urn:oid:1.3.6.1.4.1.9038.70.6 #xD; value 1..1 string The value that is unique #xD; identifier:StandardLocationNumber 0..* Identifier Unique code or number identifying the location to its users #xD; system 1..1 uri The namespace for the identifier value Fixed Value: http://dips.no/fhir/namingsystem/dips-standardlocationnumber #xD; value 1..1 string The value that is unique #xD; identifier:RSH 0..* Identifier Unique code or number identifying the location to its users #xD; system 1..1 uri The namespace for the identifier value Fixed Value: urn:oid:2.16.578.1.12.4.1.2.102 #xD; value 1..1 string The value that is unique #xD; identifier:ShortName 0..* Identifier Unique code or number identifying the location to its users #xD; system 1..1 uri The namespace for the identifier value Fixed Value: http://dips.no/fhir/namingsystem/dips/shortname #xD; value 1..1 string The value that is unique #xD; identifier:BedId 0..* Identifier Unique code or number identifying the location to its users #xD; system 1..1 uri The namespace for the identifier value Fixed Value: http://dips.no/fhir/namingsystem/dips-bedid #xD; value 1..1 string The value that is unique #xD; identifier:TeamId 0..* Identifier Unique code or number identifying the location to its users #xD; system 1..1 uri The namespace for the identifier value Fixed Value: http://dips.no/fhir/namingsystem/dips-teamid #xD; value 1..1 string The value that is unique #xD; identifier:WardId 0..* Identifier Unique code or number identifying the location to its users #xD; system 1..1 uri The namespace for the identifier value Fixed Value: urn:oid:1.3.6.1.4.1.9038.70.4 #xD; value 1..1 string The value that is unique #xD; <a href="StructureDefinition-DIPSLocation-definitions.html#Location.status" title="The status property covers the general availability of the resource, not the current value which may be covered by the operationStatus, or by a schedule/slots if they are configured for the location.#xD;#xA;#xD;#xA;Location : dipscoredb.dwlokalisering AKTUELL#xD;#xA;Team : DIPSCOREDB.DWARBEIDSGRUPPER IBRUK#xD;#xA;Bed : DIPSCOREDB.DWSENG SENGESTATUS#xD;#xA;Ward : DIPSCOREDB.DWPOST POSTIBRUK">status 0..1 code active | suspended | inactive #xD; operationalStatus #xD; system 0..1 uri Identity of the terminology system Fixed Value: http://dips.no/fhir/namingsystem/dips-bedstatus #xD; code 0..1 code Symbol in syntax defined by the system #xD; display 0..1 string Representation defined by the system #xD; name 0..1 string Name of the location as used by humans #xD; alias 0..0 A list of alternate names that the location is known as, or was known as, in the past #xD; Slices for type 0..* CodeableConcept Type of function performed Slice: Unordered, Open by value:coding.system #xD; type:locationtoplevel 0..* CodeableConcept Type of function performed Binding: LocationTypes (required) #xD; coding 1..1 Coding Code defined by a terminology system #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://dips.no/fhir/ValueSet/DIPSLocationTopLevel #xD; type:LocationType 0..* CodeableConcept Type of function performed Binding: LocationTypes (required) #xD; coding #xD; Slices for extension Content/Rules for all slices #xD; extension:locationTypeId 0..1 (Complex) Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/LocationTypeId #xD; value[x] #xD; system 0..1 uri Identity of the terminology system Fixed Value: http://dips.no/fhir/namingsystem/dips-locationtypeid #xD; system 1..1 uri Identity of the terminology system Fixed Value: urn:oid:1.3.6.1.4.1.9038.52.3297 #xD; type:BedType 0..* CodeableConcept Type of function performed #xD; coding 1..1 Coding Code defined by a terminology system #xD; Slices for extension Content/Rules for all slices #xD; extension:bedtypeId 0..1 (Complex) Extension URL: http://dips.no/fhir/R4/StructureDefinition/BedTypeId #xD; value[x] #xD; system 0..1 uri Identity of the terminology system Fixed Value: http://dips.no/fhir/namingsystem/dips-bedtypeid #xD; system 1..1 uri Identity of the terminology system Fixed Value: urn:oid:1.3.6.1.4.1.9038.52.45 #xD; type:TeamType 0..* CodeableConcept Type of function performed #xD; coding 1..1 Coding Code defined by a terminology system #xD; Slices for extension Content/Rules for all slices #xD; extension:teamTypeId 0..1 (Complex) Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/TeamTypeId #xD; value[x] #xD; system 0..1 uri Identity of the terminology system Fixed Value: http://dips.no/fhir/namingsystem/dips-teamtypeid #xD; system 1..1 uri Identity of the terminology system Fixed Value: urn:oid:1.3.6.1.4.1.9038.46 #xD; type:LevelOfCareType 0..* CodeableConcept Type of function performed #xD; coding 1..1 Coding Code defined by a terminology system #xD; system 1..1 uri Identity of the terminology system Fixed Value: urn:oid:1.3.6.1.4.1.9038.52.1010 #xD; type:WardType 0..* CodeableConcept Type of function performed #xD; coding 1..1 Coding Code defined by a terminology system #xD; Slices for extension Content/Rules for all slices #xD; extension:wardTypeCodeId 0..1 (Complex) Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/WardTypeCodeId #xD; value[x] #xD; system 0..1 uri Identity of the terminology system Fixed Value: http://dips.no/fhir/namingsystem/dips-wardtypecodeid #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://dips.no/fhir/namingsystem/dips/wardtype #xD; type:DisasterWard 0..* CodeableConcept Type of function performed #xD; coding 1..1 Coding Code defined by a terminology system #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://dips.no/fhir/namingsystem/dips-disasterward #xD; <a href="StructureDefinition-DIPSLocation-definitions.html#Location.telecom" title="The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites.#xD;#xA;#xD;#xA;Location : dipscoredb.dwlokalisering TELEFON, TELEFAX, EMAILADRESSE, WEBADRESSE#xD;#xA;Bed : DIPSCOREDB.DWSENG TELEFON#xD;#xA;Ward : DIPSCOREDB.DWPOST TELEFON, TELEFAX , EMAILADRESSE">telecom 0..* ContactPoint Contact details of the location #xD; address #xD; Slices for extension Content/Rules for all slices #xD; <a href="StructureDefinition-DIPSLocation-definitions.html#Location.address.extension:propertyInformation" title="Slice propertyInformation: Identification of a real property in Norway is defined using gårdsnummer, bruksnummer and kommunenummer. In addition real property can be rented out, the area of the real property that is rented is measured and is further identified by its festenummer. In addition some real property is split into sections identified by its seksjonsnummer#xD;#xA;#xD;#xA;dipscoredb.dwkodeverkverdier kode#xD;#xA;dipscoredb.dwkodeverkverdier Langtnavn">extension:propertyInformation 0..* NoBasisPropertyinformation real property identification #xD; extension:addressId 0..1 Identifier Optional Extensions Element URL: http://dips.no/fhir/R4/StructureDefinition/LocationAddressId #xD; line 0..* string Street name, number, direction & P.O. Box etc. #xD; <a href="StructureDefinition-DIPSLocation-definitions.html#Location.address.city" title="When a postalcode is given the name of the city must be according to the official list of postalcodes used in Norway.#xD;#xA;#xD;#xA;The name of the city, town, village or other community or delivery center.#xD;#xA;#xD;#xA;Location : dipscoredb.dwkodeverkverdier langtnavn#xD;#xA;Ward : dipscoredb.dwkodeverkverdier langtnavn">city 0..1 string Poststed or city #xD; district 0..1 string name of "kommune" #xD; <a href="StructureDefinition-DIPSLocation-definitions.html#Location.address.state" title="Name of the norwegian "fylke"). If fylkes-number is required "eiendomsinformasjon" should be used with koded kommune-number.#xD;#xA;#xD;#xA;Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes).#xD;#xA;#xD;#xA;Location : dipscoredb.dwkodeverkverdier Langtnavn#xD;#xA;Ward : dipscoredb.dwkodeverkverdier Langtnavn">state 0..1 string norwegian "fylke" #xD; postalCode 0..1 string Postal code for area #xD; physicalType #xD; coding #xD; system 0..1 uri Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/location-physical-type #xD; position 0..0 The absolute geographic location #xD; managingOrganization 0..1 Reference(Organization | no-basis-Organization) Organization responsible for provisioning and upkeep #xD; type 0..0 Type the reference refers to (e.g. "Patient") #xD; identifier #xD; type 0..0 Description of identifier #xD; system 0..1 uri The namespace for the identifier value Fixed Value: urn:oid:2.16.578.1.12.4.1.4.102 #xD; period 0..0 Time period when id is/was valid for use #xD; assigner 0..0 Organization that issued id (may be just text) #xD; hoursOfOperation 0..0 What days/times during a week is this location usually open #xD; availabilityExceptions 0..0 Description of availability exceptions #xD; endpoint 0..0 Technical endpoints providing access to services operated for the location #xD; Documentation for this format
Details and position information for a physical place
Details and position information for a physical place where services are provided and resources and participants may be stored, found, contained or accommodated. no-basis: The use-case for no-basis-Location is representation of organization structure to describe where a specific department or healthcare service is offered.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
not(exists(for $id in f:contained/*/f:id/@value return $contained[not(parent::*/descendant::f:reference/@value=concat('#', $contained/*/id/@value) or descendant::f:reference[@value='#'])]))
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
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 it's narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation
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).
Text summary of the resource, for human interpretation
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 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, and nor can they have their own independent transaction scope.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Optional Extension Element - found in all resources.
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
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 manageable, 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](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Unique code or number identifying the location to its users
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.
Extensions are always sliced by (at least) url
Additional content defined by implementations
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 manageable, 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.
usual | official | temp | secondary | old (If known)
Applications can assume that an identifier is permanent unless it explicitly says that it is temporary.
Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers.
This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one.
Identifies the purpose for this identifier, if known .
A coded type for the identifier that can be used to determine which identifier to use for a specific purpose.
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.
Allows users to make use of identifiers when the identifier system is not known.
A coded type for an identifier that can be used to determine which identifier to use for a specific purpose.
Establishes the namespace for the value - that is, a URL that describes a set values that are unique.
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.
The portion of the identifier typically relevant to the user and which is unique within the context of the system. dipscoredb.dwlokalisering LOKID
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 [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). 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.
II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root)
Time period when id is/was valid for use
Time period during which identifier is/was valid for use.
Role.effectiveTime or implied by context
Organization that issued id (may be just text)
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.
II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper
The portion of the identifier typically relevant to the user and which is unique within the context of the system. dipscoredb.dwlokalisering STANDARDLOKNR
The portion of the identifier typically relevant to the user and which is unique within the context of the system. dipscoredb.dworganizationalunit reshid
The portion of the identifier typically relevant to the user and which is unique within the context of the system. Ward : DIPSCOREDB.DWPOST POSTKORTNAVN Location : dipscoredb.dwlokalisering LOKKORTNAVN
The portion of the identifier typically relevant to the user and which is unique within the context of the system. Bed : DIPSCOREDB.DWSENG SENGEID
The portion of the identifier typically relevant to the user and which is unique within the context of the system. Team: DIPSCOREDB.DWARBEIDSGRUPPER ARBEIDSGRUPPEID Bed : DIPSCOREDB.DWSENG ARBEIDSGRUPPEID
The portion of the identifier typically relevant to the user and which is unique within the context of the system. DIPSCOREDB.DWPOST POSTID
The status property covers the general availability of the resource, not the current value which may be covered by the operationStatus, or by a schedule/slots if they are configured for the location. Location : dipscoredb.dwlokalisering AKTUELL Team : DIPSCOREDB.DWARBEIDSGRUPPER IBRUK Bed : DIPSCOREDB.DWSENG SENGESTATUS Ward : DIPSCOREDB.DWPOST POSTIBRUK
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid
Indicates whether the location is still in use.
The operational status of the location (typically only for a bed/room)
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).
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Note that FHIR strings SHALL NOT exceed 1MB in size Bed : dipscoredb.dwkodeverkverdier KODE
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Note that FHIR strings SHALL NOT exceed 1MB in size Bed : dipscoredb.dwkodeverkverdier LANGTNAVN
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Name of the location as used by humans. Does not need to be unique. Location : dipscoredb.dwlokalisering LOKNAVN Team : DIPSCOREDB.DWARBEIDSGRUPPER NAVN Bed : DIPSCOREDB.DWSENG SENGENAVN Ward : DIPSCOREDB.DWPOST POSTNAVN
If the name of a location changes, consider putting the old name in the alias column so that it can still be located through searches.
A list of alternate names that the location is known as, or was known as, in the past
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.
Additional details about the location that could be displayed as further information to identify the location beyond its name
Description of the Location, which helps in finding or referencing the place.
Humans need additional information to verify a correct location has been identified.
.playingEntity[classCode=PLC determinerCode=INSTANCE].desc
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.
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.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Source of the definition for the extension code - a logical name or a URL.
The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R4/extensibility.html) for a list).
The contact details of communication devices available at the location. This can include phone numbers, fax numbers, mobile numbers, email addresses and web sites. Location : dipscoredb.dwlokalisering TELEFON, TELEFAX, EMAILADRESSE, WEBADRESSE Bed : DIPSCOREDB.DWSENG TELEFON Ward : DIPSCOREDB.DWPOST TELEFON, TELEFAX , EMAILADRESSE
Additional addresses should be recorded using another instance of the Location resource, or via the Organization.
If locations can be visited, we need to keep track of their address.
The name and number of the of the urban district of this address.
Identification of a real property in Norway is defined using gårdsnummer, bruksnummer and kommunenummer. In addition real property can be rented out, the area of the real property that is rented is measured and is further identified by its festenummer. In addition some real property is split into sections identified by its seksjonsnummer dipscoredb.dwkodeverkverdier kode dipscoredb.dwkodeverkverdier Langtnavn
home | work | temp | old | billing - purpose of this address
The purpose of this address. Mapping of values to other Norwegian CodeSystems is documented in the implementation guide. In general the address used for visiting the person should have use "home" and type "physical" or "both". The "official" flag can be either true or false.
Applications can assume that an address is current unless it explicitly says that it is temporary or old.
Allows an appropriate address to be chosen from a list of many.
This is labeled as "Is Modifier" because applications should not mistake a temporary or old address etc.for a current/permanent one
Distinguishes between physical addresses (those you can visit) and mailing addresses (e.g. PO Boxes and care-of addresses). Most addresses are both. Mapping of values to other Norwegian CodeSystems is documented in the implementation guide. In general the address used for visiting the person should have use "home" and type "physical" or "both". The "official" flag can be either true or false.
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](http://hl7.org/fhir/R4/location.html#) 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.
XAD.1 + XAD.2 + XAD.3 + XAD.4 + XAD.5 + XAD.6
Street name, number, direction & P.O. Box etc.
This component contains the house number, apartment number, street name, street direction, P.O. Box number, delivery hints, and similar address information. Location : dipscoredb.dwadresse adresse Ward : dipscoredb.dwadresse adresse
The order in which lines should appear in an address label
XAD.1 + XAD.2 (note: XAD.1 and XAD.2 have different meanings for a company address than for a person address)
When a postalcode is given the name of the city must be according to the official list of postalcodes used in Norway. The name of the city, town, village or other community or delivery center. Location : dipscoredb.dwkodeverkverdier langtnavn Ward : dipscoredb.dwkodeverkverdier langtnavn
Name of the county (norwegian "kommune"). If kommune number is required "eiendomsinformasjon" should be used. The name of the administrative area (county). Location : dipscoredb.dwkodeverkverdier Langtnavn Ward : dipscoredb.dwkodeverkverdier Langtnavn
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)
Coded value for municipality/county Norwegian kommune
Name of the norwegian "fylke"). If fylkes-number is required "eiendomsinformasjon" should be used with koded kommune-number. Sub-unit of a country with limited sovereignty in a federally organized country. A code may be used if codes are in common use (i.e. US 2 letter state codes). Location : dipscoredb.dwkodeverkverdier Langtnavn Ward : dipscoredb.dwkodeverkverdier Langtnavn
A postal code designating a region defined by the postal service. In Norway this is af four digit number defined by the norwegian postal service. Location : dipscoredb.dwkodeverkverdier kode Ward : dipscoredb.dwkodeverkverdier kode
Country (e.g. can be ISO 3166 2 or 3 letter code)
Country - a nation as commonly understood or generally accepted.
ISO 3166 3 letter codes can be used in place of a human readable country name.
Allows addresses to be placed in historical context.
Physical form of the location, e.g. building, room, vehicle, road.
For purposes of showing relevant locations in queries, we need to categorize locations.
The absolute geographic location of the Location, expressed using the WGS84 datum (This is the same co-ordinate system used in KML).
For mobile applications and automated route-finding knowing the exact location of the Location is required.
.playingEntity [classCode=PLC determinerCode=INSTANCE].positionText
Extensions that cannot be ignored even if unrecognized
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 manageable, 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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Longitude. The value domain and the interpretation are the same as for the text of the longitude element in KML (see notes below).
(RIM Opted not to map the sub-elements of GPS location, is now an OBS)
Latitude. The value domain and the interpretation are the same as for the text of the latitude element in KML (see notes below).
Altitude. The value domain and the interpretation are the same as for the text of the altitude element in KML (see notes below).
Organization responsible for provisioning and upkeep
The organization responsible for the provisioning and upkeep of the location. Location : dipscoredb.dwlokalisering SYKEHUSID Team : DIPSCOREDB.DWARBEIDSGRUPPER SYKEHUSID Bed : DIPSCOREDB.DWSENG POSTID Ward : DIPSCOREDB.DWPOST SYKEHUSID
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.
.scopingEntity[classCode=ORG determinerKind=INSTANCE]
Literal reference, Relative, internal or absolute URL
A reference to a location at which the other resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.
Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server.
Type the reference refers to (e.g. "Patient")
The expected type of the target of the reference. If both Reference.type and Reference.reference are populated and Reference.reference is a FHIR URL, both SHALL be consistent. The type is the Canonical URL of Resource Definition that is the type this reference refers to. References are URLs that are relative to http://hl7.org/fhir/StructureDefinition/ e.g. "Patient" is a reference to http://hl7.org/fhir/StructureDefinition/Patient. Absolute URLs are only allowed for logical models (and can only be used in references in logical models, not resources).
This element is used to indicate the type of the target of the reference. This may be used which ever of the other elements are populated (or not). In some cases, the type of the target may be determined by inspection of the reference (e.g. a RESTful URL) or by resolving the target of the reference; if both the type and a reference is provided, the reference SHALL resolve to a resource of the same type as that specified.
Aa resource (or, for logical models, the URI of the logical model).
Logical reference, when literal reference is not known
An identifier for the target resource. This is used when there is no way to reference the other resource directly, either because the entity it represents is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference.
When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Reference is intended to point to a structure that can potentially be expressed as a FHIR resource, though there is no need for it to exist as an actual FHIR resource instance - except in as much as an application wishes to actual find the target of the reference. The content referred to be the identifier must meet the logical constraints implied by any limitations on what resource types are permitted for the reference. For example, it would not be legitimate to send the identifier for a drug prescription if the type were Reference(Observation|DiagnosticReport). One of the use-cases for Reference.identifier is the situation where no FHIR representation exists (where the type is Reference (Any).
The portion of the identifier typically relevant to the user and which is unique within the context of the system.
Plain text narrative that identifies the resource in addition to the resource reference.
This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it.
Another Location this one is physically a part of
Another Location of which this Location is physically a part of.
For purposes of location, display and identification, knowing which locations are located within other locations is important.
What days/times during a week is this location usually open
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.
Indicates which days of the week are available between the start and end Times.
A description of when the locations opening ours are different to normal, e.g. public holiday availability. Succinctly describing all possible exceptions to normal site availability as detailed in the opening hours Times.
Technical endpoints providing access to services operated for the location
no-basis don't use this element to reference endpoints registered in the Norwegian Address register (endpoints connected to a kommunikasjonspart in tjenestebasert adressering). Endpoints registered in the Norwegian Address register should only be referenced through a kommunikasjonspart-Organization resource. 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.